trying to unroot phone and odin keeps getting stuck in setup connection - Samsung Galaxy S8+ Questions & Answers

It's very possible I'm missing a step, but every guide that I've found has not helped. I have the stock firmware that I'm trying to flash on odin, I got the most up to date and got a sha256 is invalid error so the guide said switch to odincomsey but now I'm getting the setup connection error. first thought was that I needed to reinstall the usb drivers which I did and rebooted the computer but no change. really not sure if there's something else I need to do on the phone, but I haven't done anything with the root, so far the only thing to come from the root is not beingable to play pokemon go which is why I'm trying to revert to stock, but it's not working. I was able to do it before when I was trying to root it so I'm not sure what the problem is now. any suggestions would be helpful
I have supersu on the phone but it doesn't do anything when I try to open it, which is another issue

What all did u do so far in order to root your phone? Need more details please. Did u enable OEM UNLOCK? Did you enable USB Debugging? Did you then flash TWRP with Odin? Then flash correct SuperSU? Let us know more so we can trouble shoot with you.

Related

gain root after odin back to stock

I need to root. After bricking and using odin to get back to stock, my phone wont root again. why, you ask? well, because the phone will not connect to the computer via adb interface. I have usb debugging on, I connect my phone, it installs to the computer, but adb wont work for me. neither will super one click. is there a way to root without using a computer? maybe through terminal emulator? or an app that will work? I know z4 wont work i tried it. someone please give me some advice here. im on xp, i have tried different drivers, tried rebooting the phone, nothing works. please help.
sidekick_fanatic said:
I bricked my sk4g due to bad rom flash. I wanted to try one click unbrick, but couldnt get it to work on my computer. So my only other option was to odin it back to stock. before bricking, i had rooted it with superoneclick. i immediately tried superoneclick after odin. several different things would happen. one, it would go through the whole process and say i was rooted, but root checker pro would say i didnt have root. two, superoneclick would tell me my device was unreadable. i would ignore it and it would go through, but still not rooted. three, superoneclick would hang after killing the adb server. I then attempted to root manually. I downloaded rageagainstthecage and atempted to push it through a command prompt. I have sdk installed and all the other necessary things for a manual root. but when i typed adb devices in command prompt, the list came up empty. i deleted all the drivers, plugged the phone back in, and let the drivers reinstall several times, but my device still will not connect to the adb interface. the drivers are installing, and the usb is connecting through storage mode and firmware update mode, but not through adb no matter what i do. i am on windows xp and i do not have another computer to use. someone please tell me how to root another way or possibly flash a rooted rom through odin. thank you.
Click to expand...
Click to collapse
Try this and post results:
ODIN
Get KD1 or KG2 Firmware
Then visit..
-x]Trunks[x- said:
HERE and HERE
Click to expand...
Click to collapse
And now you should successfully rooted on stock firmware
some of those pages I have already been to. the stock rom you linked is the rom I used to odin my phone. some of those pages were confusing to me, and as far as cwm recovery goes, need root to change recovery binary. before bricking, I had root and cwm. what i need (sorry to sound like such a noob) is a step by step in this thread. please dont post links to me unless they apply to my particular situation. superoneclick, odin, cwm, these are all things i already know how to do. my question is how can i root if my phone wont connect to my pc through adb?
also, odin still recognizes my phone. i can still brick my phone and odin it all day long if i want to. I used the tutorial in one of the links you posted and downloaded the odexed stock rom and followed the tutorial exactly. the phone works, but i cant root it. there has to be someone who can help me figure this out.
bumping this thread hoping someone out there has some useful info for me. thanks
Did you turn on USB debugging?
settings->applications->development->USB Debugging
yes I did. adb is not connecting.
basically what I need is a way to flash a rooted rom through odin or another way to root without using adb. possibly without connecting to the computer, like through terminal emulator or something?
what if I added superuser, busybox, and su to my stock odin rom that I have and just odin again? would that give me root?
what if I added superuser, busybox, and su to my stock odin rom that I have and just odin again? would that give me root?
You can root the phone fine do it after the odin
Sent from my SGH-T839 using XDA App
I think I should start a new thread so I can be a little more concise. I can see that at least one person here completely does not understand what I am talking about.
No just edit the og post
PM FOR PSN NEED THE RUN PSN
xtrem88, do you understand what I am saying? I bricked my phone and had to use odin to get it back to stock. now my phone will not root. superoneclick runs, but for some reason doesnt configure root properly. i end up with superuser installed, but no root. when i try to root through command prompt, i type in adb devices and the list comes back empty. what I think I want to do at this point is odin a rooted rom.
Ohhh ok now i get it you got to. Odin it again and do not connect storage
PM FOR PSN NEED THE RUN PSN
I am updating the firmware through kies mini right now, since the firmware i odin'd wasnt the latest. I just unmounted and removed the sd card. are you saying that was the problem before?
Yeah dont use the sd card
PM FOR PSN NEED THE RUN PSN
I got it rooted. Im on KD1 firmware, but at least I am rooted. I feel like a simpleton, though. Wait till I tell you what the problem was. I was using superoneclick the whole time, and it wasnt working. I re-read the tutorial for the umpteenth time to see if I had missed anything, and it finally dawned on me that each time root had failed, I hadnt rebooted my device after running superoneclick. I just ran superoneclick, it did its thing, I disconnected and rebooted, and voila, I have root. I verified root by going to superuser and updating the su binary. thats how i knew it failed before. each time i would try to update su, it would say obtaining root access and it would fail. this time when it said obtaining root access, superuser asked for permission and i knew I had root. I am so ticked at myself for spending so much time doing it wrong, but so happy that I finally did it right lol. the whole time I thought odin was causing the problem, but im glad to know it wasnt. now i know if i brick my phone again, i can just odin and root and the phone will be back to running and rooted in like 10 minutes.
Lmao
PM FOR PSN NEED THE RUN PSN
sidekick_fanatic said:
I got it rooted. Im on KD1 firmware, but at least I am rooted. I feel like a simpleton, though. Wait till I tell you what the problem was. I was using superoneclick the whole time, and it wasnt working. I re-read the tutorial for the umpteenth time to see if I had missed anything, and it finally dawned on me that each time root had failed, I hadnt rebooted my device after running superoneclick. I just ran superoneclick, it did its thing, I disconnected and rebooted, and voila, I have root. I verified root by going to superuser and updating the su binary. thats how i knew it failed before. each time i would try to update su, it would say obtaining root access and it would fail. this time when it said obtaining root access, superuser asked for permission and i knew I had root. I am so ticked at myself for spending so much time doing it wrong, but so happy that I finally did it right lol. the whole time I thought odin was causing the problem, but im glad to know it wasnt. now i know if i brick my phone again, i can just odin and root and the phone will be back to running and rooted in like 10 minutes.
Click to expand...
Click to collapse
Soo.....this entire time the process I posted didn't work due to a simple reboot after superoneclick....*crickets*....
LMAO!!!! Glad you got your problem solved
Sent from my SGH-T839 using XDA Premium App

[Q] HTC one s Hard Bricked

I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Waggy2014 said:
I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Click to expand...
Click to collapse
You might want to post in the emergency thread for this.
Someone will chime in I am sure. From what little I know, I would try using the RUU (ROM update utility) to restore the phone.
Before you do that, wait a little while and maybe someone else will post with some other method. The RUU will hopefully restore your phone to stock.
I'm trying to do that now buy it just wont boot up so I can't run the program

Super SU binaries not installing.

http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Anyone?
CannedBullets said:
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Click to expand...
Click to collapse
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
S1L3nTShaDoWz said:
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
Click to expand...
Click to collapse
I have not considered a factory reset. Also, what's S-OFF? I'm not sure what that is. Also do you mean the HTC Transfer Tool? I don't have that.
CannedBullets said:
I have not considered a factory reset. Also, what's S-OFF? I'm not sure what that is. Also do you mean the HTC Transfer Tool? I don't have that.
Click to expand...
Click to collapse
I don't really know how to explain what "S" is other than its security/signature verification(not sure on signature verification), when your phone is S-ON you can't flash any non verified rom or write to protected areas of your phone such as /system which is required for root, etc and I know it does more than that but I'm not 100% educated as to what it means yet though so can't give you a 100% accurate or complete explanation.
Now based off of what I just said and a little research i'm quite sure you actually require it for a permanent root solution such as SuperSU but could be wrong.
Anyways if you're interested in doing it go here: http://forum.xda-developers.com/showthread.php?t=2708628 and follow the instructions carefully. This also unlocks your bootloader which means you can install custom roms, kernels, flash scripts, apps, SuperSU for PERMANENT root, etc. In order to do these things you'll need to flash a custom recovery such as TWRP or CWM (Team Win Recovery Project & Clockwork Mod/Philz Touch). Afterwards it's quite simple from there on out, just be careful and research before you do anything I've suggested/stated. Also on the Sync Manager thing, what you need to do is install it from here http://www.htc.com/us/support/software/htc-sync-manager.aspx and then let it install the phone drivers for your M8 on your computer and then you need to uninstall it "HTC Sync Manager" from your computer in order to do the S-OFF process.
Please do be careful and get a good understanding before you do this though, re-read things a few times and make sure you're well aware of what it means and how to do it properly.
S1L3nTShaDoWz said:
Probably the last thing you wanna do but if it wont work have you considered a factory reset? Usually solves most issues & are you S-OFF? Asking the S-OFF question because if you are you can flash a custom recovery and just flash the binaries. 0% failure rate with that as far as I know. About the ADB Reboot question, did you install the HTC Sync Manager so it would install the proper drivers and then removed the Sync program (not drivers)?
Click to expand...
Click to collapse
S1L3nTShaDoWz said:
I don't really know how to explain what "S" is other than its security/signature verification(not sure on signature verification), when your phone is S-ON you can't flash any non verified rom or write to protected areas of your phone such as /system which is required for root, etc and I know it does more than that but I'm not 100% educated as to what it means yet though so can't give you a 100% accurate or complete explanation.
Now based off of what I just said and a little research i'm quite sure you actually require it for a permanent root solution such as SuperSU but could be wrong.
Anyways if you're interested in doing it go here: http://forum.xda-developers.com/showthread.php?t=2708628 and follow the instructions carefully. This also unlocks your bootloader which means you can install custom roms, kernels, flash scripts, apps, SuperSU for PERMANENT root, etc. In order to do these things you'll need to flash a custom recovery such as TWRP or CWM (Team Win Recovery Project & Clockwork Mod/Philz Touch). Afterwards it's quite simple from there on out, just be careful and research before you do anything I've suggested/stated. Also on the Sync Manager thing, what you need to do is install it from here http://www.htc.com/us/support/software/htc-sync-manager.aspx and then let it install the phone drivers for your M8 on your computer and then you need to uninstall it "HTC Sync Manager" from your computer in order to do the S-OFF process.
Please do be careful and get a good understanding before you do this though, re-read things a few times and make sure you're well aware of what it means and how to do it properly.
Click to expand...
Click to collapse
Yeah I'll have to look into that. I'm not sure if I'll ever flash a custom ROM though on my M8, Sense 6 is good as it is, I need to get Cyanogenmod on my Razr Maxx, Motoblur on it is just slow ever since they updated it to 4.1.2.
CannedBullets said:
Yeah I'll have to look into that. I'm not sure if I'll ever flash a custom ROM though on my M8, Sense 6 is good as it is, I need to get Cyanogenmod on my Razr Maxx, Motoblur on it is just slow ever since they updated it to 4.1.2.
Click to expand...
Click to collapse
Most of the ROM's for the M8 are Sense based anyways so you won't have a problem if you want Sense.
S1L3nTShaDoWz said:
Most of the ROM's for the M8 are Sense based anyways so you won't have a problem if you want Sense.
Click to expand...
Click to collapse
I just had a strange morning. What's new right? This morning I saw that my Titanium Back had a superuser fail. I had no problems yesterday. I used SuperSU to root and checked to see if Titanium Back was granted rights and it was. Still no luck running it. So Titanium suggested I load Superuser which I was not running. I installed it and it said it could not update the binary. That's weird so I read this post and reflashed SuperSU and yep Titanium backup was denied in the grant list. I granted it and everything is OK now. I posted here because I saw an unusual program in the grant list in SuperSU. It is com.koushikdutta.superuser. I don't know what that is but I bet that was the culprit. It did not show before I updated so it was hidden. Anybody know where this came from?
Weaksauce will not install binaries that's why it needs to reroot your phone every time you reboot. If you want your root to stick you need to be S-OFF. Since you are on 4.2.2 you could try Firewater to gain S-OFF. (Only works for some M8'S on 4.2.2)
http://firewater-soff.com/instructions/
If firewater does not work then you need to use Sunshine which I believe it cost $25. (Will not work on 4.4.4!)
http://forum.xda-developers.com/showthread.php?t=2792487
Not sure if you have adb/fastboot set up on your computer but if not...Google! I know there are instructions on how to set that up because I had to Google it. I think that may be the hardest part of all of this, if you can follow instructions WORD FOR WORD after setting that up I don't see how you can mess up. If you do find yourself stuck well we are here
SOLUTION
CannedBullets said:
http://forum.xda-developers.com/showthread.php?t=2699089&page=40
I tried using that method to root my phone, but Super SU just won't install binaries. First time around it just wouldn't work, after a few tries I unrooted my device and started over. I got the same message, "Unable to install, reboot"
Then after that it said something like "If you upgraded to 4.3 then reroot" Something like that. Which is weird because I have 4.4.2.
What's going on? I tried Superuser but when I tried installing the binaries it crashed when it was doing a software update twice so I had to hold down on volume up and the power button to reboot it on both occasions.
Also, how do I do an ADB Reboot? What's the easiest method? I tried doing that on my PC but it keeps saying device not detected Maybe I'm not setting up the program for that right? Yes, Developer Options and USB Debugging are enabled.
Yes my M8 is from Verizon. Is there another method for one-click rooting?
Click to expand...
Click to collapse
**SOLUTION**
Download the SuperSU ZIP from the link below;
http://download.chainfire.eu/supersu
Reboot your device into your custom recovery of choice, install the ZIP (which should be in your download folder on "sdcard" by default), reboot.
It should now work with no issues!
KnightAlex said:
**SOLUTION**
Download the SuperSU ZIP from the link below;
download.chainfire.eu/supersu
Reboot your device into your custom recovery of choice, install the ZIP (which should be in your download folder on "sdcard" by default), reboot.
It should now work with no issues!
Click to expand...
Click to collapse
I installed CM13 on my Moto G 1st Gen also GApps, I also had TWRP working. So my next step was to install SuperSU (UPDATE-SuperSU-v2.46.zip) with TWRP, after it says it was succesfull, i wanted to reboot the system, it is stuck in the Cyanogenmod Bootanimation and won't boot into the system. And It also stuck in the TWRP loading screen when i want to load into recovery!
What can I do? I have still files on the phone which I want to preserve!
Umm. This is a HTC one m8 forum?

Bootloop from root app permissions

Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie

Galaxy J7 Sky Pro (SM-S727VL) Root Help

Title says it, apologies in advance for my noobiness on the entire topic of rooting. Got lucky and my previous device was supported via kingroot. Just looking for SuperSU permissions so I can enable my hotspot really.
This phone is through straight talk btw. I've tried Kingroot, iRoot, and quite a few others to no avail. I don't currently have internet due to me moving to the butt-crack of nowhere, Tried srsroot but seems like it interferes with USB tether and says it's successfully rooted but nothing happens upon reboot.
Anyone had any success with this? Thanks in advance.
Anyone?
Please help for the love of god.
mobliife said:
Please help for the love of god.
Click to expand...
Click to collapse
CF- Autoroot might do it. I see that it works on other variants for the J7. Here's a link with CF-Autoroot and detailed instructions. Hope it works for you. Let me know how it goes.
http://www.theandroidsoul.com/root-samsung-galaxy-devices-cf-auto-root-odin/
mobliife said:
Title says it, apologies in advance for my noobiness on the entire topic of rooting. Got lucky and my previous device was supported via kingroot. Just looking for SuperSU permissions so I can enable my hotspot really.
This phone is through straight talk btw. I've tried Kingroot, iRoot, and quite a few others to no avail. I don't currently have internet due to me moving to the butt-crack of nowhere, Tried srsroot but seems like it interferes with USB tether and says it's successfully rooted but nothing happens upon reboot.
Anyone had any success with this? Thanks in advance
Is this your first time rooting a device. after srsroot says successfully rooted did you verify root by going into playstore and trying a root check app.
Click to expand...
Click to collapse
I tried srsroot 5.1 multiple exploit and it said rooted. I open root checker and it said phone wasn't rooted. I also tried dr. Phone and they didn't have a working root method for j7 sky pro and i was desperate enough to try king root. None of these worked. The guy than mention c.f. auto root, thats for a version of the j7 that was released in other countries. Those variants of the j7 have exoynus processors and us version have snap-dragon processors so the root procedure might brick your phone.
---------- Post added at 03:46 PM ---------- Previous post was at 03:43 PM ----------
When ever I get some free time I'm going to try using adb commands to try and root.
Hopefully not too much longer before someone can root this thing... I'm also looking!
wondering if anyone has seen this video or tried it??
Code:
https://www.youtube.com/watch?v=UtktE0jccnw
I can't open the link but all the videos iv seen on YouTube seems to be j700's and other variants not for s727v.l From my research the devices are a listed under samsung j models but the they all have different hardware, i.e. boards, processors, chipsets,. I did a cross referience with cf-auto root to try and find a divice with the same hardware and builds, there wasnt any other device with the same hardware that would suggest compatibility. Cf-auto root flashes a root file to your device and if it's not compatible you could completely brick your device
Hello, First of, you shouldn't have used kingroot whatever the situation was
However https://play.google.com/store/apps/details?id=com.inkwired.droidinfo&hl=en
download this and capture the system and device tray
Yeah but it was worth a shot. I figured if it worked I could replace it with superSu. I will post those specs In a few. When ever. I get time and free WiFi in going to try adv root
System and device
I'm going to try adb root method when ever I get the time
Trying this again. I try posting last night but it didn't go through
dorain said:
Trying this again. I try posting last night but it didn't go through
Click to expand...
Click to collapse
Hello,
It did pass, however, your device seems to be a Verizon varient, it's hard to root it and there is no really a method to root it.
Sorry I couldn't help
dorain said:
I can't open the link but all the videos iv seen on YouTube seems to be j700's and other variants not for s727v.l From my research the devices are a listed under samsung j models but the they all have different hardware, i.e. boards, processors, chipsets,. I did a cross referience with cf-auto root to try and find a divice with the same hardware and builds, there wasnt any other device with the same hardware that would suggest compatibility. Cf-auto root flashes a root file to your device and if it's not compatible you could completely brick your device
Click to expand...
Click to collapse
Need to talk to mark manning tell to send thread to me please private matter
Thanks for the look and the reply. Im gonna try crack this one. Ive been preparing my computer with Ubuntu, android sdk, and cleaning old drivers. Iol, I'm gonna see what I can do, hopefully I can break it.
dorain said:
Thanks for the look and the reply. Im gonna try crack this one. Ive been preparing my computer with Ubuntu, android sdk, and cleaning old drivers. Iol, I'm gonna see what I can do, hopefully I can break it.
Click to expand...
Click to collapse
Verizon bootloader is most of time locked you can't flash it.
I may have a method for rooting s727vl. I can't test until I get home where I will have unrestricted data in case something goes wrong. I'm gonna keep this short and simple assuming everyone have
knowledge of using odin.
Developer option usb debugging oem unlock no frp or passwords
Download odin
Download latest superSu, this isn't the same as superuser in the playstore. It's used for rooting systemless root os. Yes that what marshmallow is.
After downloading supersu place it on your phones sd card
This is what I'm not sure on. Download clockwork mod RECOVERY. Zip , not the one in the playstore. And place on pc
Use odin to flash cwm to s727vl
Please refer to guide on installing cwm
After flashing cwm go to it in recovery mode and use cwm to flash the supersu zip file and reboot phone. It could take a few minutes but it should boot with root access. Or wait for auto reboot.
What I'm not sure on is cwm compatibility with s727vl, I couldn't find a yeah or nay on compatibility. Cwm say it's compatible with any android.
Hopefully this will work. Make sure u have your data backed up and your stock rom in case things go south. If anyone try this please let me know the result. I'm anxious to try it but I travel a lot and I can't afford to have data throttled by downloading everything I need and I can't risk doing this until I'm i get home.
Possible root method for s727vl straighttalk
Junior Member17 posts Thanks: 1
I may have a method for rooting s727vl. I can't test until I get home where I will have unrestricted data in case something goes wrong. I'm gonna keep this short and simple assuming everyone have
knowledge of using odin.
Developer option usb debugging oem unlock no frp or passwords
Download odin
Download latest superSu and place on phone sdcard
this isn't the same as superuser in the playstore. It's used for rooting systemless root os. Yes that what marshmallow is.
This is what I'm not sure on. Download clockwork mod RECOVERY. Zip ,not the one in the playstore.
And place it on your pc
Use odin to flash cwm to s727vl
Please refer to guide on installing cwm
After flashing cwm go to it in recovery mode and use cwm to flash the supersu zip file and reboot phone. It could take a few minutes but it should boot with root access. Or may reboot on its own.
What I'm not sure on is cwm compatibility with s727vl, I couldn't find a yeah or nay on compatibility. Cwm say it's compatible with any android.
Hopefully this will work. Make sure u have your data backed up and your stock rom in case things go south. If anyone try this please let me know the result. I'm anxious to try it but I travel a lot and I can't afford to have data throttled by downloading everything I need and I can't risk doing this until I'm i get home.
dorain said:
Junior Member17 posts Thanks: 1
I may have a method for rooting s727vl. I can't test until I get home where I will have unrestricted data in case something goes wrong. I'm gonna keep this short and simple assuming everyone have
knowledge of using odin.
Developer option usb debugging oem unlock no frp or passwords
Download odin
Download latest superSu and place on phone sdcard
this isn't the same as superuser in the playstore. It's used for rooting systemless root os. Yes that what marshmallow is.
This is what I'm not sure on. Download clockwork mod RECOVERY. Zip ,not the one in the playstore.
And place it on your pc
Use odin to flash cwm to s727vl
Please refer to guide on installing cwm
After flashing cwm go to it in recovery mode and use cwm to flash the supersu zip file and reboot phone. It could take a few minutes but it should boot with root access. Or may reboot on its own.
What I'm not sure on is cwm compatibility with s727vl, I couldn't find a yeah or nay on compatibility. Cwm say it's compatible with any android.
Hopefully this will work. Make sure u have your data backed up and your stock rom in case things go south. If anyone try this please let me know the result. I'm anxious to try it but I travel a lot and I can't afford to have data throttled by downloading everything I need and I can't risk doing this until I'm i get home.
Click to expand...
Click to collapse
Modt of Verizon phones has a locked bootloader, they can't be flashed with unsigned images

Categories

Resources