Related
Hi all, I've been browsing since yesterday about rooting Lenovo Vibe Z2 Pro, however there was little that could be found. And in this point I'm not even sure whether it is possible.
Does someone have experience with rooting this particular phone. I will appreciate any advice.
Thanks in advance
tadeas_bucha said:
Hi all, I've been browsing since yesterday about rooting Lenovo Vibe Z2 Pro, however there was little that could be found. And in this point I'm not even sure whether it is possible.
Does someone have experience with rooting this particular phone. I will appreciate any advice.
Thanks in advance
Click to expand...
Click to collapse
Try rooting with the following android apps.
Root Master
z4root
Universal Androot
Easy rooting toolkit
Framaroot
Hi Guys,
can somebody list the hi-res games working on this monster??
i know root is not yet possible for lollipop until then we can play some quality games.
Lets Golf 3 is not installing.
i love nature games rather than bang! bang!
so someout out there using z2 pro at the fullest, kindly list the names of the games.
waiting...
jacktackle said:
Hi Guys,
can somebody list the hi-res games working on this monster??
i know root is not yet possible for lollipop until then we can play some quality games.
Lets Golf 3 is not installing.
i love nature games rather than bang! bang!
so someout out there using z2 pro at the fullest, kindly list the names of the games.
waiting...
Click to expand...
Click to collapse
ROOT on Lollipop is actually possible, russian guide HERE.
Every game I tried worked flawlessly. I don't think I have ever had any problems with that. Also resolution change (to 1080p) helped with FPS. I think 1440p is for Adreno 330 too much.
Hi, how is it possible to change the resolution? Thanks.
i used the lenovo companion app and it shows that i'm rooted. but when i installed the supersu, either via playstore of twrp, it keep asking me to update binary. Any idea what i can do? thanks.
rainbow99 said:
i used the lenovo companion app and it shows that i'm rooted. but when i installed the supersu, either via playstore of twrp, it keep asking me to update binary. Any idea what i can do? thanks.
Click to expand...
Click to collapse
After pressing update? Still keeps asking? I just flashed latest SuperSU (2.46 i think) in twrp and everything works fine.
yes it tries to update then say not successful. needs to reboot. but then the same after rebooting. not sure if it's because i don't have root. i did manage to install twrp and can reboot into twrp.
Then flash latest SuperSU zip in twrp. I don't see a reason why it shouldn't work
hi bro, i tried that, and it really didn't work. I'm also puzzled. downloaded v2.46 from the supersu website and flashed via twrp. the message is successful. but when i open up, it still prompts me to update binary. sigh.
Rooting Vibe Z2 Pro
Hi,
First I unlocked the Bootloader and used Kingroot app to root VIbe Z2 pro.
I also installed TWRP and it is working fine.
mandarthedon said:
Hi,
First I unlocked the Bootloader and used Kingroot app to root VIbe Z2 pro.
I also installed TWRP and it is working fine.
Click to expand...
Click to collapse
Do you have ROW or chinese version ? Kingroot mobile or destop version ?
I have a chinese model and after lollipop update Gapps not working [ tried a lot of GMsinstaller in vain ] , if you can help me with detailed steps please, I think only after root I can change pemission to gapps in order to work. Tried download and install directly on the phone kingroot v4.5.0.722 and is not working [I am not unlocked the bootloder yet , I am afraid not to brick the phone ].
rainbow99 said:
hi bro, i tried that, and it really didn't work. I'm also puzzled. downloaded v2.46 from the supersu website and flashed via twrp. the message is successful. but when i open up, it still prompts me to update binary. sigh.
Click to expand...
Click to collapse
Just to share, working with version 2.49 beta
Sent from my LG-D838 using XDA Free mobile app
look dude... i'll be super honest with you. In no android planet will you be able to root your device if you keep a locked bootloader. Get it unlocked first. Does your device have ''fastboot''? because everything will have to start with that.
Sent from my Optimus L4ii using XDA Free mobile app
Izoh George said:
look dude... i'll be super honest with you. In no android planet will you be able to root your device if you keep a locked bootloader. Get it unlocked first. Does your device have ''fastboot''? because everything will have to start with that.
Click to expand...
Click to collapse
There are dozens of devices rootable with those one-click generic apps like KingoRoot or Towelroot etc... which doesn't need unlocked bootloader, or even adb/fastboot. Ofc you won't be able to flash custom recovery (via fastboot) and things like that, but essentialy you'll end up with SuperSU installed along with su binary (that's the point of rooting the device, right?).
Before Lollipop firmware update our device was possible to root via those one-click apps.
Electry said:
There are dozens of devices rootable with those one-click generic apps like KingoRoot or Towelroot etc... which doesn't need unlocked bootloader, or even adb/fastboot. Ofc you won't be able to flash custom recovery (via fastboot) and things like that, but essentialy you'll end up with SuperSU installed along with su binary (that's the point of rooting the device, right?).
Before Lollipop firmware update our device was possible to root via those one-click apps.
Click to expand...
Click to collapse
Honestly to say you are right. I dont know why i was being rogue with you. I think what i should hav said was '' in no android planet would you want to root your device with a locked bootloader''. Reasons being no Nandroid backup restore method.. neither via recovery nor via fastboot image flashing method. Of course taking nandroid backup will be possible e.g using Online Nandroid app, onandroid executable scripts e.t.c. Besides unlocking bootloader only clears your user data. We all know rooting is not a disaster but a window to disaster #BRICK. Think about it.
Sent from my Optimus L4ii using XDA Free mobile app
i have K920 5.0.2 VIBEUI_V22.5_11526_55.574.1_ST_K920
please advise updated method to root this device? thanks.
Tnx for root.
amk said:
i have K920 5.0.2 VIBEUI_V22.5_11526_55.574.1_ST_K920
please advise updated method to root this device? thanks.
Click to expand...
Click to collapse
Kindly provide details of your android version. I mean you could have used some OTA update. Additional information like processor type could be helpful. You could b using an international variant.
Sent from my it1501 using XDA Free mobile app
---------- Post added at 11:24 AM ---------- Previous post was at 11:11 AM ----------
Anyway download pdanet for pc... Install it. Have usb debugging on. Check that on developer options on your device. Connect your device to pc then run pdanet to install the necessary driver. (You could also download and use "adb drivers installer.exe for pc as an alternative".
Check your phone screen to confirm the debug promp.
Download iRoot English version for pc.
Install it and run.
Connect your phone with the usb debug still on.
Once your device is detected and name displayed. A button "Root" will appear. Click on it and your phone will reboot if rooting successful.
Sent from my it1501 using XDA Free mobile app
i tried all roots which are commented here but without success.. i have 5.0.2. -K920_S271_150907_ROW... any idea why?
Wondering if anyone in the know has heard of any development going on for this device? I recently bought one and it's not a bad phone for the price, but I've seen absolutely -nothing- on it anywhere online for the most part. It's barely root-able with what I've been able to find, and no custom recovery or really anything custom has popped up that I've seen.
Not sure if it's just that it's been only a few months since the phone came out, or if it's just not that great a phone. I upgraded from an HTC Desire 510 to this, and it was heavily customized/rooted/etc, and I want so badly to get back to where I was with it on this phone I cant stand it!
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
triiuzii said:
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
Click to expand...
Click to collapse
Right now rooting isn't the problem so much as keeping root. Because apparently the colonel has protection and will remove root whenever you reboot. That means things that require root on boot like backups, Xposed and a lot of other things won't work for us until someone complies a kernel with root protection removed. You can do some debloating and possibly the AdAway but that's about it right now.
*kernel. Damn voice to text.
That sucks. I upgraded from an LG Volt and I was able to do a whole bunch of stuff on it. The J3 is still very new, so hopefully development will happen soon.
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
mallamike said:
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
Click to expand...
Click to collapse
I guess that would depend on what you have experience with and what you can do. Thus-far root has been able to be achieved with Kingroot, though it wont stick through a power cycle (reboot/power off/etc), and using any of the methods available (at least that I'm aware of, only found two legitimate ones) to replace Kingroot with SuperSU (to facilitate having root stick past the reboot hopefully) causes a soft-brick every time forcing a re-flash of stock firmware through Odin.
At the very least make your voice heard, if nothing else hopefully more popularity will come this devices way and we'll see some development for it. My roommate is considering writing something for it, but it is a long process working solo, so anyone who has experience working with kernels or editing stock rom/writing custom roms feels up to helping out, shoot me a message and I'll get it over to him. He's a fairly experienced programmer and picks up what he doesn't already know pretty quickly.
Got one recently too. Would also appreciate any more information on rooting.
I have a J320A (AT&T) came stock with 6.0.1, can help test if needed
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Will this version of TWRP work on the Att variant running 6.0.1? Is there a way to root that device yet?
coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
TechShui said:
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
Click to expand...
Click to collapse
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
what about the
SM-J320VPP = the verizon pre paid planversion. any working roots for me yet?
oh pretty pleeeeeez
Azhero said:
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
Click to expand...
Click to collapse
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
AnierinB said:
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
Click to expand...
Click to collapse
It doesn't work tried it 3 times. I even tried other ones no luck. They locked this thing down. Im surprise chainfire haven't tried this phone yet.
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Gotbootloopedtoomuch said:
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Click to expand...
Click to collapse
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
darknaio said:
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
Click to expand...
Click to collapse
Thank you so much! I tried using Odin to flash a software update and it worked perfectly. The phone is back up and running and all of the files are still there!
Right now i have TWRP 3.0.2 with supersu and i havent lost root yet also had no problem switching between backups, xposed working fine and also overclock too with setcpu, im currently running 5.1.1 using j320FN but TWRP was from j320F, i will put up links to the files if any of you are willing to try its up to you.
TWRP flash through odin : http://www.mediafire.com/download/blk7qa90vs6wik3/TWRP_3.0.2-0_SM-J320F.tar.tar
Supersu flash through recovery then update through playstore then install busybox after through playstore : http://www.mediafire.com/download/cpv2c71cp11x41f/UPDATE-SuperSU-v2.76-20160630161323.zip
Remember to turn on usb debugging and turn on oem unlock before flashing recovery, also if you manage to get recovery press they grey box on the right to change language to english. Hope this might help somebody on here because we really need full root for everyone.
Just got the above device for Christmas. While trying to figure out if I could update the version of Android, I chatted with the Samsung Smart Switch help desk and was told that since my device status is listed as "Custom," it has apparently been rooted. Except that when I downloaded Titanium BackUp, it said it couldn't find the root or the SU (the actual error message disappeared and I can't get it back). Anyway, under Root Access it says Failed.
There is no SuperUser software on the device, nor Busy Box. When I booted into recovery, I got basic Android recovery, although it included an option to update from ADB.
So, any guesses as to whether it's been rooted or not? If it has, any issues with installing TWRP, etc., as per the link here: http://forum.xda-developers.com/gal...overy-samsung-galaxy-tab-a6-sm-t280-t3475381? Or just trying to root it, per instructions here: http://forum.xda-developers.com/gal...m-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788.
I would like to update my version of Android to run a couple apps that are currently incompatible, not to mention get rid of the massive bloatware. Don't have Ubuntu and found the instructions in the above two links a little confusing (how do I ' Flash with ODIN 3.10.7 in the AP slot."?) although I can research my way through it.
Or I can just return the tablet for one that hasn't been modified and hope I can update the OS via Smart Switch.
RobinG34 said:
Just got the above device for Christmas. While trying to figure out if I could update the version of Android, I chatted with the Samsung Smart Switch help desk and was told that since my device status is listed as "Custom," it has apparently been rooted. Except that when I downloaded Titanium BackUp, it said it couldn't find the root or the SU (the actual error message disappeared and I can't get it back). Anyway, under Root Access it says Failed.
There is no SuperUser software on the device, nor Busy Box. When I booted into recovery, I got basic Android recovery, although it included an option to update from ADB.
So, any guesses as to whether it's been rooted or not? If it has, any issues with installing TWRP, etc., as per the link here: http://forum.xda-developers.com/gal...overy-samsung-galaxy-tab-a6-sm-t280-t3475381? Or just trying to root it, per instructions here: http://forum.xda-developers.com/gal...m-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788.
I would like to update my version of Android to run a couple apps that are currently incompatible, not to mention get rid of the massive bloatware. Don't have Ubuntu and found the instructions in the above two links a little confusing (how do I ' Flash with ODIN 3.10.7 in the AP slot."?) although I can research my way through it.
Or I can just return the tablet for one that hasn't been modified and hope I can update the OS via Smart Switch.
Click to expand...
Click to collapse
Seems weird that the device is listed as custom out of the box. Best bet is to reflash the custom firmware using ODIN (you have to download a copy of the stock firmware of course) after that you can follow said guide to flash TWRP and then root after.
jedld said:
Seems weird that the device is listed as custom out of the box. Best bet is to reflash the custom firmware using ODIN (you have to download a copy of the stock firmware of course) after that you can follow said guide to flash TWRP and then root after.
Click to expand...
Click to collapse
It was an Open Box purchase - why we got it so cheap. I'm using it as my reading tablet and the Nook app is one of the two that won't work on it. I can (and will) look up ODIN on my own, but for the sake of expediency, if someone has a good link to the why's and what for's and how's, that would be appreciated.
jedld said:
Seems weird that the device is listed as custom out of the box. Best bet is to reflash the custom firmware using ODIN (you have to download a copy of the stock firmware of course) after that you can follow said guide to flash TWRP and then root after.
Click to expand...
Click to collapse
where can you find stock firmware i cant seem to find it anywhere?
mjohnson4580 said:
where can you find stock firmware i cant seem to find it anywhere?
Click to expand...
Click to collapse
You can check out sammobile.com for that
jedld said:
You can check out sammobile.com for that
Click to expand...
Click to collapse
Ive tried there they have no us version for this tablet
http://updato.com/firmware-archive-select-model that is where I grabbed one for the US model
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
stumbows said:
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
Click to expand...
Click to collapse
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
acejavelin said:
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
Click to expand...
Click to collapse
I didn't take a backup as TWRP broke during the process but the root worked. I am only on 6.0 so is that ok to resolve? I can't see the baseband details at the moment as I am boot looping due to trying to follow another guide on resolving my issues. Trying to load a stock rom on to my device through TWRP now. Will report back soon.
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
stumbows said:
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
Click to expand...
Click to collapse
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
acejavelin said:
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
Click to expand...
Click to collapse
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
stumbows said:
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
Click to expand...
Click to collapse
Nope... Not a clue, sorry.
Hello!
These are a few files and guides for rooting a G930T with the Android Oreo 8.0.0 G930TUVS9CSC1 update.
Most Samsung apps, such as S-Health and Samsung Pay, will not function as Knox has detected root.
I've included a link to a patched S-Health app that allows for step-counting, but HR and Sp02 functionalities are missing.
Read all of this and the original guide linked at the bottom before performing any steps towards rooting the device.
-ROOT GUIDE-
-Backup any data on the device.
-Enable "OEM Unlock" in the Developer Options menu on the device.
-Reboot the device into Download mode. ODIN v3.13 should recognize it with an "Added!!"
-Add the v9 Bootloader into the "BL" entry box. Nothing else should be added or checked.
-Begin the transfer with "Start."
-Once the phone has rebooted into Android, open CMD with "cmd-here.exe."
-Enter "root.bat" into the command prompt window to begin the root process.
-Follow the root directions. There will be descriptions of each step in the CMD window, so read them carefully.
-Once the device has been rebooted and rooted, FlashFire, SuperSU, and other apps will appear on the device.
-Use FlashFire to flash the VoLTE icon removal zip. Check both mounting boxes for the flash to succeed.
The guide has been completed with hopefully no issues.
If for any reason there has been an issue or you'd like to unroot the device, stock files have been linked at the bottom.
In my experience, a factory reset and a flash of the stock files should undo most user errors.
-SOURCE LINKS-
(Root Method Guide)
https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 @jrkruse
(The rooted v9 Bootloader)
https://forum.xda-developers.com/showpost.php?p=79528528&postcount=1623 @robdog82
(Patched S-Health)
https://forum.xda-developers.com/galaxy-s9/how-to/knox-patched-samsung-health-6-3-0-027-t3919737 @xpirt
(Stock G930TUVS9CSC1 files)
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930T/TMB/download/G930TUVS9CSC1/264972/
(Archive of these files as of July 2019)
https://www.dropbox.com/sh/oohvm7zxcgf51kc/AAB2Hy8C0HJyEygRpJIV8z35a?dl=0
Anyone try this yet?
Can somebody help me out? I am trying to go back to stock and despite having a free membership on sam, it will not allow me to download the stock firmware. It keeps telling me to sign up even though I am a free member. Free members should be able to get the latest firmware at a slow speed without paying correct? I dunno why somebody just doesn't toss these files up on a dropbox or google drive.
ftateen said:
Can somebody help me out? I am trying to go back to stock and despite having a free membership on sam, it will not allow me to download the stock firmware. It keeps telling me to sign up even though I am a free member. Free members should be able to get the latest firmware at a slow speed without paying correct? I dunno why somebody just doesn't toss these files up on a dropbox or google drive.
Click to expand...
Click to collapse
Did the root work?
damon420l said:
Did the root work?
Click to expand...
Click to collapse
Root worked . But i'm trying to return to stock because a deal came up with Tmobile and i want to return everything to stock for a possible trade in.
I've added an archive of all of the files at the bottom of the original post, @ftateen.
OK I have read every post in this thread and now my brain hurts. It's been a long day so I am probably just being stupid, however.... I have a 930 with bootloaderv9 I believe (g930tuvsacsg1). Can I follow the rooting guide but use the 930u engineer to gain root or is my phone still a no love zone>
alarmdude9 said:
OK I have read every post in this thread and now my brain hurts. It's been a long day so I am probably just being stupid, however.... I have a 930 with bootloaderv9 I believe (g930tuvsacsg1). Can I follow the rooting guide but use the 930u engineer to gain root or is my phone still a no love zone>
Click to expand...
Click to collapse
I'm in the same boat. From what I can tell, it seems like T-Mobile added bootloader 9 to the update, but I can't confirm whether using the version linked to in this post will work without issue or if the versions have to be a perfect match to not fail/brick/trip Knox.
All I really want is to root my old S7 so I can play around with root-level access. I'm not using it for mobile data, just tethering to my current phone's mobile hotspot, so it makes no difference to me if I end up with a T-Mobile tweak of Android or something more like a stock version.
SV REV CHECK FAIL : [boot]Fused 10 > Binary 9
Hi,
Upon trying the files you provide, I get the above error msg.
I've search everywhere (I think) in order to find the updated BL...
Thanks anyway - If you have a solution???
sp
Hello! I'm a newbie in all of this, so forgive me if I'm asking something obvious.
I used this thread to root my Galaxy S7 (SM-G930T), Baseband version G930TUVS9CSC1, Android version 8.0, but I can't edit the hosts file.
Root Checker says Root Access is properly installed but when I try to edit and save the hosts file I get a message that I can't save because it's a read-only file system.
I tried to edit using ES File Explorer and Cx File Explorer with no luck.
A long time ago I had this same phone rooted with Android version 6.0 and I was able to edit the hosts file.
Any idea how to fix this? All help would be appreciated.
-------------
UPDATE: I found a solution. Another file explorer worked. I have no idea why the others didn't.