Related
How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after Augu
It took me over a week to search through threads and learn how to root my S5 Active SM-G870A after I installed the new August 2014 update and then later discovered the SD card issue (i.e. needing root access to allow apps to write to it).
Anyway, these forums helped but I had to piece lots together in order to do it right and make sure that I was not going to destroy a $600 phone.
Below is a compilation of what I found. I do not take any credit for the original contents. I have simply organized what I have found in many other threads so that others searching to resolve the same issue can do so in less time than me. Also, I put this together so that I do not feel like my time was wasted hunting all of this down!
How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after August 2014 Update
Step 1: Downgrade your Phone’s Firmware to an Earlier Version
Original Thread Link: http://forum.xda-developers.com/showthread.php?t=2799754
Before Starting:
1. Download and Install the latest Samsung USB Drivers.
2. Download and install the latest version of Odin (you may need to extract it using a zip program).
3. Download and extract the firmware file: http://www.sammobile.com/firmwares/3/?download=31669 (May 9th, 2014) OR HERE.
4. Make sure USB debugging is checked under “Settings/Developer Options” (If you don't know how to do that, go to "About Device" in Settings, and click on "Build Number” 5 times to unlock “Developer Options").
5. Back up your phone using any backup program that does not require root, just in case.
Flash Instructions:
6. Open Odin v3.09.
7. Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons).
8. Connect phone to your PC and wait until you get a blue sign in Odin.
9. Add the un-zipped firmware file to AP / PDA (Make sure re-partition is NOT ticked).
10. Click the start button, sit back and wait a few minutes.
You should see a bar at the bottom of your phone indicating progress and also in Odin. Once the phone restarts Odin will check to see if the firmware flash was a success. If it is, the “System” box will now display “Success.” Congratulations, you have downgraded your phone’s firmware, now you can root it using towelroot (www.towelroot.com).
Step 2: Install Towelroot
Before Starting:
1. Disable antivirus software on your phone. Towelroot is an exploit: it is how you get root. So your antivirus (if it’s worth a damn) will flag it.
2. Make sure that your phone can install application from unknown sources: Settings>Security>Unknown Sources>Check.
Towelroot Instructions:
3. Using your phone’s browser navigate to www.towelroot.com.
4. Click on the lambda in order to download the tr.apk file.
5. Locate the file on your phone and click on it. Chose the Android Package installer.
6. Follow the additional instructions.
Step 3: Do I have REALLY have Root Access?
1. Go to the Play Story and search “root checker.”
2. Download and install the app with the same name.
3. Run it. If it is a success, then download and install SuperSU.
I recommend getting Titanium Backup and paying for the pro-version ($5.99). Doing so will allow you to disable the AT&T notifications (“Freeze” AT&T Update) that will bug you once you downgrade your firmware, and there are lots of other things you can do with it now that your phone it rooted.
This “complete” intro guide should help anyone (especially newbies) root their S5 Active SM-G870A in a safe way if they have upgrade their phone in August 2014 or after.
UPDATE-Post Flash/Root
After working with the downgrade for a few days everything works fine except I lost the ability to use the default e-mail app. I noticed an "email" failure upon the first boot after the flash, but I ignored it because I was so focused on rooting.
This is not a big deal to me since I was not in love with the stock e-mail app to begin with. I have since found acceptable alternatives (that are actually better IMO). But if this is a big deal to you just be aware. It may be the firmware downgrade or it may have just happened to me. However, some people in the other thread mentioned losing GPS, but mine works fine (as does everything else).
I'm not a noob but thanks for putting this together
GS5 Firmware Download
Whenever I go to the SamMobile website, and go to the page for my phone (Samsung Galaxy S5 AT&T). When I download the file, I'm not able to extract the file because there is nothing in it. What am I doing wrong/does anyone have a direct download link. I tried googling around, but I couldn't find anything that worked.
Dont use the Odin Link, it is SPAM! just search xda
http://forum.xda-developers.com/galaxy-s-advance/help/version-odin3-v3-10-t2859776
Nice to have it all in one place!
UPDATE: Failed to work on SM-g900a. Guess I'll just keep waiting for someone to n crack lollipop code.
ranthon007 said:
It took me over a week to search through threads and learn how to root my S5 Active SM-G870A after I installed the new August 2014 update and then later discovered the SD card issue (i.e. needing root access to allow apps to write to it).
Anyway, these forums helped but I had to piece lots together in order to do it right and make sure that I was not going to destroy a $600 phone.
Below is a compilation of what I found. I do not take any credit for the original contents. I have simply organized what I have found in many other threads so that others searching to resolve the same issue can do so in less time than me. Also, I put this together so that I do not feel like my time was wasted hunting all of this down!
How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after August 2014 Update
Step 1: Downgrade your Phone’s Firmware to an Earlier Version
Original Thread Link: http://forum.xda-developers.com/showthread.php?t=2799754
Before Starting:
1. Download and Install the latest Samsung USB Drivers.
2. Download and install the latest version of Odin (you may need to extract it using a zip program).
3. Download and extract the firmware file: http://www.sammobile.com/firmwares/3/?download=31669 (May 9th, 2014) OR HERE.
4. Make sure USB debugging is checked under “Settings/Developer Options” (If you don't know how to do that, go to "About Device" in Settings, and click on "Build Number” 5 times to unlock “Developer Options").
5. Back up your phone using any backup program that does not require root, just in case.
Flash Instructions:
6. Open Odin v3.09.
7. Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons).
8. Connect phone to your PC and wait until you get a blue sign in Odin.
9. Add the un-zipped firmware file to AP / PDA (Make sure re-partition is NOT ticked).
10. Click the start button, sit back and wait a few minutes.
You should see a bar at the bottom of your phone indicating progress and also in Odin. Once the phone restarts Odin will check to see if the firmware flash was a success. If it is, the “System” box will now display “Success.” Congratulations, you have downgraded your phone’s firmware, now you can root it using towelroot (www.towelroot.com).
Step 2: Install Towelroot
Before Starting:
1. Disable antivirus software on your phone. Towelroot is an exploit: it is how you get root. So your antivirus (if it’s worth a damn) will flag it.
2. Make sure that your phone can install application from unknown sources: Settings>Security>Unknown Sources>Check.
Towelroot Instructions:
3. Using your phone’s browser navigate to www.towelroot.com.
4. Click on the lambda in order to download the tr.apk file.
5. Locate the file on your phone and click on it. Chose the Android Package installer.
6. Follow the additional instructions.
Step 3: Do I have REALLY have Root Access?
1. Go to the Play Story and search “root checker.”
2. Download and install the app with the same name.
3. Run it. If it is a success, then download and install SuperSU.
I recommend getting Titanium Backup and paying for the pro-version ($5.99). Doing so will allow you to disable the AT&T notifications (“Freeze” AT&T Update) that will bug you once you downgrade your firmware, and there are lots of other things you can do with it now that your phone it rooted.
This “complete” intro guide should help anyone (especially newbies) root their S5 Active SM-G870A in a safe way if they have upgrade their phone in August 2014 or after.
Click to expand...
Click to collapse
Like you, I have been scouring the Web trying to downgrade my sm-g900a back to Kitkat since Lollipop and At&t's locked bootloader prohibits rooting or any kind of customization. Whatsoever. So I really appreciate you taking the time to compile these steps! I am wondering however, is there a way to use Odin on a device other than a PC or Mac? For example an LG tablet? Sorry if that's a noob question. I know how and have successfully rooted previous Samsung galaxies using my PC Odin. I'm just away from home and only have a tablet with me. And this Lollipop cap has got to go ! Really appreciate your response.
FAIL! (AUTH)
the message I get is FAIL! (AUTH) in Odin 3.09.
now I am stuck at the Android system recovery screen <3E>
I'm looking for a way back from this.
squirt r6 said:
the message I get is FAIL! (AUTH) in Odin 3.09.
now I am stuck at the Android system recovery screen <3E>
I'm looking for a way back from this.
Click to expand...
Click to collapse
I found solution. Just follow the guide in decription and everything is ok. https://www.youtube.com/watch?v=8481Qm0l010
nhutung said:
I found solution. Just follow the guide in decription and everything is ok.
Click to expand...
Click to collapse
I had the same exact problem you did. I followed the link. Thanks for that! I got a PASS from Odin! But I am still stuck on the recovery boot screen. Doing a Data wipe and Cache wipe then restart doesn't work. Still stuck on that page. Any suggestions? Every forum I find just says to perform the data wipe and cache wipe then restart and I should be golden, except I'm not.
Updated method!
Allows downgrade from MM 6.0 down to OF3, which we now have the ability to root using this guide.
sure this guide is for the G870A?
IJoxer said:
Updated method!
Allows downgrade from MM 6.0 down to OF3, which we now have the ability to root using this guide.
Click to expand...
Click to collapse
lJOXER, this guide seems to be for the standard S5 and not the ACTIVE? am i correct? is there any way to root a 5.0 OC3 ACTIVE?
---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------
electric101 said:
lJOXER, this guide seems to be for the standard S5 and not the ACTIVE? am i correct? is there any way to root a 5.0 OC3 ACTIVE?
Click to expand...
Click to collapse
Sorry "OF3"
bigpapi19 said:
I'm not a noob but thanks for putting this together
Click to expand...
Click to collapse
you ever try this on the active?
electric101 said:
you ever try this on the active?
Click to expand...
Click to collapse
Hey @electric101, sorry, I upgraded to an S7 and have been using another account. This guide actually applied to both, which is also the case for most custom roms. I actually owned the Active myself, often flashed and rooted with 900a methods. Hope that helps, good luck!
thats interesting.... the guy who posted the actual guide (AptLogic) told me that it didnt work with the 870A .... did you try it on an unrooted 870A running 5.0 or newer? when i try it fails on the first step of flashing experimental firmware using odin 3.11
if you were able to maybe i'm just not doing something right....
thank u..
those who r havin trouble...change cords & keep tryin! took me 3 trys.... and a few mins to get passed the att logo screen.. dont get discouraged
i did and walked away came back later at it was all gravy... w android 5.0... still cant root it... so if anyone has any idea...
Hi guys,
I've had this note 3 for a year now and it's waranty has finally expired. That means it's time to root!
I've never rooted a device before and to be honest I'm VERY paranoid about bricking it because it's my baby!
I've been following the ChainFire thread and install video by TK Here
I've got the MD5 file and Odin3 installed. I've booted the phone into "download mode".
The trouble I'm having is that my computer can't find a driver for the device in this mode, it shows as it's snapdragon processor / mobo "MSM8960"
After looking about for quite a while, I've realized there are A LOT of variables when it comes to rooting your phone.
Can an experienced rooter please reply to let me know if I should be OK rooting my device. Info below.
Model number: SM-N9005
Android Version: 4.4.2
Baseband Version: N9005XXUGNG1
Build Number: KOT49H.N9005XXUGNG1
Kernel Version: 3.4.0 - 1955971
Thank you for reading.
- Pano
Shameless Self Bump.
Just looking for a yes or no here anyone who has good rooting history
Hiya, first of all you need drivers, go to this site:
http://androidxda.com/download-samsung-usb-drivers
Download the drivers for the note 3, I'm assuming you're using windows 7, install the drivers &reboot your computer, then connect your phone in normal mode, not download mode. Once you've verified the phone is recognised as the note 3 disconnect the phone &reboot into download mode, leave for a few seconds &connect the phone to the pc, the drivers should install for download mode. Verify on the pc that the phones recognised, (under device manager there shouldn't be an exclamation mark anywhere really) One that's done you're good to go.
An alternative method to root is using an app called towel root. It's a new way to root using an exploit &shouldn't trip knox. Read up on it very carefully though, I think some ppl are having issues with it with the note 3.
See how you get on with all that lol.
Sent from my SM-N9005 using XDA Free mobile app
Panomosh said:
Hi guys,
I've had this note 3 for a year now and it's waranty has finally expired. That means it's time to root!
I've never rooted a device before and to be honest I'm VERY paranoid about bricking it because it's my baby!
I've been following the ChainFire thread and install video by TK Here
I've got the MD5 file and Odin3 installed. I've booted the phone into "download mode".
The trouble I'm having is that my computer can't find a driver for the device in this mode, it shows as it's snapdragon processor / mobo "MSM8960"
After looking about for quite a while, I've realized there are A LOT of variables when it comes to rooting your phone.
Can an experienced rooter please reply to let me know if I should be OK rooting my device. Info below.
Model number: SM-N9005
Android Version: 4.4.2
Baseband Version: N9005XXUGNG1
Build Number: KOT49H.N9005XXUGNG1
Kernel Version: 3.4.0 - 1955971
Thank you for reading.
- Pano
Click to expand...
Click to collapse
- Regarding the device's info, you can use Phone INFO ★Samsung★ app for more detailed info.
- As for rooting, you can use any method to root. I personally use CF-Auto-root. Some notes: Install driver. Set USB Debug ON. Set Reactivation Lock OFF. Recommend flashing CWM Recovery immediately after rooting.
- You can get the driver here: https://dl.dropboxusercontent.com/u/25370185/SAMSUNG_USB_Driver_v1.5.27.0.exe
Or you can install Kies so that the driver also be installed.
seraphism said:
I think some ppl are having issues with it with the note 3
Click to expand...
Click to collapse
Thanks dude. I'll have a look at that link you posted for drivers.
But I think I'll avoid the Towel method for now if people are having trouble, already paranoid enough about bricking it!
- Pano
vndnguyen said:
As for rooting, you can use any method to root. I personally use CF-Auto-root. Some notes: Install driver. Set USB Debug ON. Set Reactivation Lock OFF. Recommend flashing CWM Recovery immediately after rooting.
Click to expand...
Click to collapse
Thanks for the help, I'm planning on using the CF auto root myself, I've not tried to install the drivers through Kies because I wasn't sure if it would try to auto update my firmware to some unrootable version. I guess it doesn't so I'll have a look at that
Sorry I'm like new as of today to rooting, I've done iPhone jailbreaks but psssh, they're nothing.
whats the CWM Recovery?
Thanks
- Pano
Panomosh said:
Thanks for the help, I'm planning on using the CF auto root myself, I've not tried to install the drivers through Kies because I wasn't sure if it would try to auto update my firmware to some unrootable version. I guess it doesn't so I'll have a look at that
Sorry I'm like new as of today to rooting, I've done iPhone jailbreaks but psssh, they're nothing.
whats the CWM Recovery?
Thanks
- Pano
Click to expand...
Click to collapse
Dont worry, Kies will not auto update without asking you. Anyway you can use the driver in the link I've given above.
Recovery is the special partition where you can backup/restore all phone firmware/data... Phone comes with the stock recovery, however its function is very limited, and you may want to use custom recovery. There are some custom recoveries available: CWM or TWRP... I personally use CWM. You can google 'CWM or TWRP recovery' for the download link.
vndnguyen said:
Phone INFO ★Samsung★
Click to expand...
Click to collapse
Just downloaded your app, pretty sweet! Thanks for the freebie
OK vndnguyen I've used the exe you linked for the drivers.
Gonna boot phone into download now and see how it goes. I'll let you know :fingers-crossed:
Worked a charm, thanks for your help!
whole process took about 15 seconds, don't know why I was so worried about it bricking
Going to have a look at that CWM now and enjoy the freedom!
Thanks!
-Pano :good:
Panomosh said:
Worked a charm, thanks for your help!
whole process took about 15 seconds, don't know why I was so worried about it bricking
Going to have a look at that CWM now and enjoy the freedom!
Thanks!
-Pano :good:
Click to expand...
Click to collapse
Rooting never actually bricks your phone. But flashing ROMs does.Its not hard if you have proper instructions to do it. So just be careful while flashing or messing with your phone. Anyways congrats and best of luck :good::victory:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
Wasn't it much easier if you install TWRP first, then root it using magisk?
Thank you for thatsuggestion. I didnt know that I can install TWRP before rooting the phone first
I had trouble rooting with CF auto root on my SM-N910F, not exactly the same problem as you.
Then I did some reading into other root alternatives and basically found out that SuperSU, which CF autoroot uses, was sold to a Chinese company called Coding Code Mobile Technlogy sometime around 2015. As it's closed source and Chinese firms particularly have been known not to respect user privacy, I would go with Magisk instead as it's open source, plus I have had zero problems with it so far.
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
hgroth said:
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
Click to expand...
Click to collapse
I'm no expert myself, in fact I'm new to it! but I'll share with you what I know.
I basically flashed TWRP to the phone using Samsung Odin (Loads of videos Youtube showing the process) Then I used Android Debug Bridge to push the Magisk flashable .zip file over to the phone (I think I could have actually just copied it into /sdcard - Androids name for internal storage bizarrely - through windows just like any other external device) before booting into TWRP on the phone, and simply selecting "install", selecting the Magisk .zip and flashing it from there. Then I just booted into Android and I seem to remember either the Magisk manager app will now be in your app draw, or alternatively there is an app placeholder there which allows you to download the full manager app, I can't remember which it is but small difference. Here is a link to the official Magisk thread on XDA which you can use find the download links you need. Take note that right at the top it states...
"Magisk does NOT have a website. Do NOT download Magisk from unofficial sites"
When I did it I downloaded Magisk from one of the top websites that appears when you search "Magisk" in Duckduckgo (they look very official) however after I read the notice above in the official thread I wiped the phone and did the process over again just to be safe! I hope that is helpful. :good:
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
did you remove battery after the flash?
Thanks for your help. Yes I tried that after the 2nd attempt when I set Odin not to auto reboot, I removed the battery
and then booted the phone after inserting the battery with the same result, not root. I am wondering why it says
boot image not found, aborting....... since I loaded the CF Auto Root which should be the correct boot image