I want to be able to mod my phone so I can install SDFix, but I cannot figure out how to get root access. I downloaded the towelroot and installed it but it keeps saying that my device is not supported, yet I see in several threads that people have claimed that it is.
I did recently update the software from AT&T (before I knew I needed to get root access) so that might have something to do with it. If it does, can anyone tell me AND let me know if it is possible that it will be fixed in the future? Thanks.
P.S. I anyone know a work-around the SD card issue without root that would work too. This is mainly why I am rooting, so I can ACTUALLY use the extra storage that I installed.
ranthon007 said:
I want to be able to mod my phone so I can install SDFix, but I cannot figure out how to get root access. I downloaded the towelroot and installed it but it keeps saying that my device is not supported, yet I see in several threads that people have claimed that it is.
I did recently update the software from AT&T (before I knew I needed to get root access) so that might have something to do with it. If it does, can anyone tell me AND let me know if it is possible that it will be fixed in the future? Thanks.
P.S. I anyone know a work-around the SD card issue without root that would work too. This is mainly why I am rooting, so I can ACTUALLY use the extra storage that I installed.
Click to expand...
Click to collapse
Yes a recent update disabled towelroot. You might be able to work around this issue by flashing an older firmware in Odin or by trying this tutorial.
lingowistico said:
Yes a recent update disabled towelroot. You might be able to work around this issue by flashing an older firmware in Odin or by trying this tutorial.
Click to expand...
Click to collapse
Thanks. I will try that out when I get a chance! I will let you know what happens when I do.
FYI: Where to Start for Root Access
For anyone who may search this forum and find my mention of the G870A, and have no idea where to start (like I did) follow this thread: http://forum.xda-developers.com/showthread.php?t=2799754 I can confirm that this firmware (once installed following the steps) will allow towelroot to work if you updated (like I did) in mid-August 2014.
P.S. I did not wipe all of my data clean like the post mentions at the bottom, but I did downgrade the firmware without issue.
It Works!
ranthon007 said:
For anyone who may search this forum and find my mention of the G870A, and have no idea where to start (like I did) follow this thread: http://forum.xda-developers.com/showthread.php?t=2799754 I can confirm that this firmware (once installed following the steps) will allow towelroot to work if you updated (like I did) in mid-August 2014.
P.S. I did not wipe all of my data clean like the post mentions at the bottom, but I did downgrade the firmware without issue.
Click to expand...
Click to collapse
I've been looking for this for a while now... I'm glad I finally found it. Thank you!!! It worked like a charm!
I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app
I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.
JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.
joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf
I've been reading numerous threads in this forum in regards to rooting but I cannot unlock the bootloader.
Been trying to follow snowwolf's unofficial method to the letter but to no avail. Tried both .bat and manually doing fastboot .raw. https://forum.xda-developers.com/showpost.php?p=69001601&postcount=2.
Currently at the latest update as of today and have NOT rooted or unlocked bootloader prior to this.
USB debugging is also set to on.
I have uploaded screenshots of the error messages and information of the phone.
https://imgur.com/a/XPSDP
Any suggestions/opinions are welcome.
It's possible the unofficial unlock method was blocked in the newer firmware (bootloader) that you have installed. Try flashing the Marshmallow firmware, but you'll probably need to remove the checks in the updater script (first 7 lines or so). I'm not sure it'll work though, but worth a shot. If you can't downgrade though, then the only option is to use the official unlock method.
Yep, that seems to be the case. The official unlock method still works on the latest one and successfully rooted. Thank you for your help.
Sorry for the foolish question but what is the proper way to do a total clean "hard" reset to the latest version when its rooted? Just been messing with a lot of things and wanted to start anew since I'm relatively new to android from iOS.
droidoogle said:
Sorry for the foolish question but what is the proper way to do a total clean "hard" reset to the latest version when its rooted? Just been messing with a lot of things and wanted to start anew since I'm relatively new to android from iOS.
Click to expand...
Click to collapse
Factory reset through settings or in recovery mode
droidoogle said:
Yep, that seems to be the case. The official unlock method still works on the latest one and successfully rooted. Thank you for your help.
Click to expand...
Click to collapse
Will this work on version WW_14.2020.1703.28_20170410? Latest version of nougat. Even if its for marshmallow only? Thanks
Ok so I am just going to say I am a idiot and need some help. Please don't hate on me. I am not good with phone technology, but I followed directions to root my phone with TWRP & Magisk 12.0 and everything is working ok for the most part. The problem is I need a specific app to work for my job, but it fails to start due to the failed Safety Net. I would probably be able to figure out how to unroot it & relock the bootloader, but in my haste to root my phone, I did not backup the stock ROM image 1st. If anyone can help me figure out the next step to go back to a factory phone, I would forever be indebted to you. My specific model is an XT-1681 dual sim which I believe is from Brazil. I am in the US and not sure if I can use a different stock rom because I have tried searching to no avail. Please help if you can.
Thanks for your time.
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Karlinski said:
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Click to expand...
Click to collapse
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
ronefx said:
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
Click to expand...
Click to collapse
Which phone version you have retin?
Sent from my Moto G (5) Plus using Tapatalk
Hello,
So I've had this S7 Edge for a few years, never thought about rooting it until recently when I wanted to download a nice firewall app that requires a rooted phone.
Well, I'm a complete newbie to this, never rooted a phone before, and I've been digging through the forums for a few days trying to figure out how to root this phone. From what I've been seeing, it's much more complicated to root the Verizon variant of this S7 Edge.
From what I understand, the only way to root this phone is to unlock the bootloader. I was researching and figured I had to download ADB, so I did, and I got it working. Using the command prompt on Windows, ADB communicated with the phone successfully. But, before I could continue messing with it further, I tested to see if the Fastboot was working aswell (apparently I'm supposed to have both ADB and Fastboot working). I tried using the Fastboot command to test it. What happened was that it sent my phone into a different screen, but the screen was not the typical bootloader screen that I've been seeing other people get. It was a fairly blank screen with nothing but an android logo with the word "Downloading" in the middle. Typing the "fastboot -devices" command returned no devices. After waiting 5 minutes the screen stayed the same and I just gave up on that part, deciding I should consult the experts here =]. Not sure what I should do next.
I am no expert, by any definition. I used the method described here and it works perfectly for me (SM-G935V). However, if you are on the absolute latest version of Verizon's firmware you might be out of luck- and no, you can not downgrade bootloader versions.
http://https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Hope this helps.
SkylineDriver said:
I am no expert, by any definition. I used the method described here and it works perfectly for me (SM-G935V). However, if you are on the absolute latest version of Verizon's firmware you might be out of luck- and no, you can not downgrade bootloader versions.
http://https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Hope this helps.
Click to expand...
Click to collapse
By latest firmware, does that mean the latest security updates from verizon? Like the ones that automatically pop up on the phone and you can't delay them forever? Well, I could try that link out and see if it works, but I'm scared I'll brick my phone, was hoping for a bit of a step by step guide. Thanks for the suggestion though.
Also may I ask how long ago you used this method for yours?
If you took the latest OTA update from Verizon you are probably out of luck. You will have to check your firmware bootloader version (5th digit from the RIGHT). If is 8 or under you should be able to root using the thread mentioned above. If it is 9 or a letter then you can not root as of right now. As mentioned earlier, you can not downgrade bootloader versions.
FWIW, you can not get any more of a step-by-step guide than what that thread lists. And I have not heard of anyone bricking a S7e using that method- worst case scenario you flash stock and move on.
I have been rooted for at least 9 months now and have not had one issue. Only thing I wish we had was Pie but that will never happen.
SkylineDriver said:
If you took the latest OTA update from Verizon you are probably out of luck. You will have to check your firmware bootloader version (5th digit from the RIGHT). If is 8 or under you should be able to root using the thread mentioned above. If it is 9 or a letter then you can not root as of right now. As mentioned earlier, you can not downgrade bootloader versions.
Click to expand...
Click to collapse
Got sidetracked for a couple months there haha, but I'm still determined to root this thing.
I figured out the bootloader version. It has the letter A (Baseband version: 5th digit from the right).
So now what? This version isn't the latest I don't think. Haven't had an OTA update for months now. Do I cross my fingers hoping someone has a rooting method for this particular Bootloader version?