Related
Okay I have searched and searched through these forums through and through and there is no possible way the root a Droid 2 Global. I have tried all the ways listed here Pete's way the One Click and the Superone Click and I tried Z4root and that didn't work either! Is there a new way to do this???(When I had my HTC Eris that was unrootable too.) I think Im gonna give up and on my next upgrade I'll probably just get an iPhone 4s or something, because any phone I touch will before outdated and unrootable and unable to flash any of the cool custom roms and play emulators and crap. I'll just an iPhone 4s and talk to siri.
Thanks anyway for all the help guys and thanks developer for all your hard work!!!
-Mars
you're doing something wrong
edit: did you enable usb debugging?
how far did you get?
and miui ics is a cool rom
thousands have rooted their global
at least hundreds anyways
Which stock version are you on? Froyo, GB...
War-Rasta said:
Which stock version are you on? Froyo, GB...
Click to expand...
Click to collapse
Pete's root is suppose to work on froyo too
Sent from my DROID2 GLOBAL using xda premium
Z4root will NOT work on stock 2.3.3. I've been using a Droid 3 one click root tool for linux and it's been working without fail. I've noticed this tool also works on the regular D2. Z4root will only work with the original stock.
EDIT: As far as cool roms, I'm using MIUI ICS. You like ICS but don't want to spend 700 bucks for an off contract phone? That's right. Your D2G runs it just fine lol.
MIUI isn't really ICS. It's just bits and pieces of the framework.
Gasai Yuno said:
MIUI isn't really ICS. It's just bits and pieces of the framework.
Click to expand...
Click to collapse
Diced, mixed, or blended, it's still the best rom I've used
I am using Gingerbread.
System Version 4.5.608.A956
Android Version 2.3.3
What does the DROID3 One-Click Root script tell you? Any errors while you run it?
Gasai Yuno said:
What does the DROID3 One-Click Root script tell you? Any errors while you run it?
Click to expand...
Click to collapse
Nothing. Once it finds the phone and the rooting process begins it will say running expoit 1 of 3 (setting up symlink) and it will remain at the reboot screen forever!
my phone says:
Bootloader DO.11
Battery OK
OK to program
Transfer Mode:
USB
then nothing happens!
This time I got the "server not running" error!
Make sure your phone is set to PC mode with USB debugging on. I usually have to run the script twice. The first time it doesn't do anything. End it and start it again and it works for me every time.
Also, as far as MIUI ICS, it's technically android 2.3.7 but it's still ICS to me lol. It's enough like it to make me happy.
xero925 said:
Nothing. Once it finds the phone and the rooting process begins it will say running expoit 1 of 3 (setting up symlink) and it will remain at the reboot screen forever!
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
then nothing happens!
Click to expand...
Click to collapse
Have you tried pulling the battery without unplugging the phone from the PC and closing the script's window?
So that it boots normally and continues.
Gasai Yuno said:
Have you tried pulling the battery without unplugging the phone from the PC and closing the script's window?
So that it boots normally and continues.
Click to expand...
Click to collapse
I'm gonna try that now! Standby...
Nope that didn't work! I didnt think was going to either!
I just tried the latest version of SuperOneClick and again with this screen on my phone:
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
I'm starting to think somehow that this screen somehow not allowing me the further root my phone! With the SuperOneClick the program running and then immediately stopped responding!
Any ideas?
what is the latest version?
I thought you just need it in usb charge mode and have usb debugging on
edit: I don't see a SuperOneClick that works with GB
---------- Post added at 03:49 PM ---------- Previous post was at 03:18 PM ----------
xero925 said:
I just tried the latest version of SuperOneClick and again with this screen on my phone:
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
I'm starting to think somehow that this screen somehow not allowing me the further root my phone! With the SuperOneClick the program running and then immediately stopped responding!
Any ideas?
Click to expand...
Click to collapse
try petes with a different computer
HTML:
http://www.psouza4.com/Droid3/
1. Make sure you have Motorola drivers installed.
2. Download and unzip 'MotorolaOneClickRoot_psouza4'
3. On your phone: Settings > Applications > Development > USB debugging(check box)
4. Plug phone into computer and select "Charge Only" mode
5. Navigate to 'MotorolaOneClickRoot_psouza4' folder and run 'MotorolaOneClickRoot.exe'
6. Now just follow the instructions in the command window and unlock the phone after each reboot.
For Windows XP users having trouble try this -> v7 .bat One Click
edit: are you trying to using a computer with usb 1.0?
if that doesn't work, maybe sbf
Hi,
i am definitely not an expert, in fact everything i know about android i learned from reading other people's threads but i managed to root my droid 2 global yesterday using superoneclick.
the first time i tried to run it the program froze up in the middle of the process and wouldn't do anything, including close. while i was trying to figure out how to fix i came across a post that said to start the program while usb debugging is off and then turn it on when it says waiting for device so i tried that and it actually worked. go figure.
i have no idea if it will work for you or not but i thought i would share in case you wanted to give it a try.
crazydz said:
Hi,
i am definitely not an expert, in fact everything i know about android i learned from reading other people's threads but i managed to root my droid 2 global yesterday using superoneclick.
the first time i tried to run it the program froze up in the middle of the process and wouldn't do anything, including close. while i was trying to figure out how to fix i came across a post that said to start the program while usb debugging is off and then turn it on when it says waiting for device so i tried that and it actually worked. go figure.
i have no idea if it will work for you or not but i thought i would share in case you wanted to give it a try.
Click to expand...
Click to collapse
Thank you!!!! That worked!!! I can confirm SuperOneClick v2.3.3 works on a D2G running 2.3.3!!!!
Im using Barnacle wireless tethering and gonna flash a custom rom later today!!
Thank you guys so much helping and I plan to donate and support you efforts here!!
the instructions are on the SuperOneClick v2.3.3 thread
http://forum.xda-developers.com/showthread.php?t=803682
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
Hey all. Unfortunately, I can't post in the development forum because this is my seventh post. :crying: Anyways, I had a comment about the verizon root and hopefully somebody can either move this to that sticky or answer... Anyways...
I wanted to see what was done to the modified image to make sure nothing strange was put in it. I downloaded the 'orig' from fus, extracted the image, and ran a md5 check on all the files. I then downloaded your system.img file and ran a md5check on all the files. I found two files were added...
#
330a331
> 65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
2007a2009
> d1a9de9724c662a50a9a128e48b1fb37 xbin/su
#
When I tried to find the versions of those files and the md5 hashes, they don't match. Here's your version...
65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
d1a9de9724c662a50a9a128e48b1fb37 xbin/su
I then downloaded 'superuser' from http://androidsu.com/superuser/, which I'm assuming is the source. For the 3.1.3 version, I get this...
MD5 (system/app/Superuser.apk) = e0bc7b7284b68c9539b6ec6b306310e0
MD5 (system/bin/su) = 054c9a22d8900d50ce6172fd56bbf414
For the 3.2-RC2 version, I get this...
MD5 (system/app/Superuser.apk) = d0abb9413f712f2f7dd43ed47df6c2d8
MD5 (system/bin/su) = 96c672c1339da363232f42dd87b4a3cf
As you can see, the md5's are different which make me a little uneasy about it. I was wondering if anybody knew of the source for these. I think I just email'ed invisiblek the same thing, but don't know if it would get to him or not. Maybe somebody else knows the answer.
Thanks!
WTF?
Im confused, I see active topics saying the S3 hasn't got root yet due to the locked boot loader, I also see active topics saying it has been unlocked + rooted..
answer
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Verizon Failed on on Odin now stuck at SIII boot screen
wiz561 said:
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Click to expand...
Click to collapse
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
1. Bootloader is [still] locked
2. Root has been achieved
Solved the problem. I tried a better micro usb cable and a different usb port.
Everything went great after that. I'm now rooted fully.
daffy113 said:
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
Click to expand...
Click to collapse
..
The answer is that this type of question doesn't belong in the dev threads, but in the S3 Q&A forum. If MD5 doesn't match, then you have a bad download or bad copy, or the posted MD5 is incorrect.
Unable to Root VZW SG3
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
luisdr007 said:
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
Click to expand...
Click to collapse
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
prdog1 said:
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
luisdr007 said:
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
Click to expand...
Click to collapse
Here is direct link from Samsung.
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW
Click see all downloads>software
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
thank you. i will uninstall the current drivers, reboot, and install these and see what happens.
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
I tried installing drivers again, but no avail. i keep getting "There was a problem installing this hardware, SAMSUNG Android ADB Interface. This device is not configured correctly. (code 1)" Not sure what else to do.
Did you reboot the PC
prdog1 said:
Did you reboot the PC
Click to expand...
Click to collapse
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
luisdr007 said:
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
Click to expand...
Click to collapse
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
ok, I did not reboot after I installed drivers. USB debugging is checked on the phone. Let me reboot PC and I will keep you posted. thank you very much for you help with this. I'm not new to rooting, but I am new to the Samsung phones. I've had the DX for the last 2 years, and never had issues rooting or flashing ROMS.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
luisdr007 said:
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
Click to expand...
Click to collapse
ADB shows mine as offline emulator.
I've had my Galaxy Tab 2.0 7 for about 5 months now, and have rooted it, installed Modded ROMs, etc. Really enjoyed it.
However, yesterday, I decided to clean up my 32 gig external memory chip, and hooked up the USB cable to the computer as in the past.
Whoops! PC will now not recognize the tablet in USB mode. Nothing changed from the day before, both PC and tablet had worked together then.
Now, I get this message in the Device manager of the PC "Windows has stopped this device because it has reported problems. (Code 43)".
I tried the normal things, reinstalling drivers, using different USB ports, etc. Nothing worked. So, I'm assuming that I had a hardware failure
in the tablet or the USB cord that came with it.
I'd like to know if there is anyway to "Root" my tablet by Using wireless? That still works, and I can move stuff off and onto the tablet. But I
would still like to have the obvious advantages of it being rooted.
Thanks in advance for any help you might be able to give.
OK, first off, if you've already rooted it and installed custom ROM's, why would you need to root it again? you talk of reinstalling drivers but have you rebooted BOTH the computer and the tablet since this problem occurred and you redid the drivers? Why are you trying to connect to the computer to erase files on the tablet, you do know there is a file manager in android that you can use to delete files? If you don't mind buying the pro version there is an app called "wifi file transfer" that connects to your PC via a web browser and you can copy files off and on (never done onto myself) your tablet with over wifi, I use it when I'm at work and don't have my cords with me but need to moves pictures from an android device to my laptop.
daniel644 said:
OK, first off, if you've already rooted it and installed custom ROM's, why would you need to root it again? you talk of reinstalling drivers but have you rebooted BOTH the computer and the tablet since this problem occurred and you redid the drivers? Why are you trying to connect to the computer to erase files on the tablet, you do know there is a file manager in android that you can use to delete files? If you don't mind buying the pro version there is an app called "wifi file transfer" that connects to your PC via a web browser and you can copy files off and on (never done onto myself) your tablet with over wifi, I use it when I'm at work and don't have my cords with me but need to moves pictures from an android device to my laptop.
Click to expand...
Click to collapse
Need to root it again, because somehow, the root was removed. Still works just fine, have busybox and clockwork recovery, but it is not rooted. Don't ask me why. And, yes, I have rebooted both units, probably 4 or 5 times - reinstalled drivers several times. I normally use wireless to remove files, because it is faster, and easier to find the files I want. I have WiFi Transfer Pro, but that doesn't help the "root" situation. I don't have any problems moving files onto and off of the tablet, just can't root without USB connectivity.
No Answers, I guess. What this boils down to:
Is there anyway to root this device without using USB connectivity?
rothrand said:
No Answers, I guess. What this boils down to:
Is there anyway to root this device without using USB connectivity?
Click to expand...
Click to collapse
Here is a tutorial for rooting with cwm, I'm not sure how well it works though.
http://www.cursed4eva.com/root-galaxy-tab-2/
I guess just download the cwm root file and flash it.
Sent from my GT-P3110 using xda premium
cwm
If you have clockwork mod working then all you need to do is flash the same ROM you are running, you should then be up and running with a fully functional rooted ROM if I'm not mistaken
Bradstheannoying said:
If you have clockwork mod working then all you need to do is flash the same ROM you are running, you should then be up and running with a fully functional rooted ROM if I'm not mistaken
Click to expand...
Click to collapse
Duh, why didn't i think of that. Lol..
Sent from my GT-P3110 using xda premium
bluecarbon -
This tutorial requires USB connectivity to flash the tablet using Odin. (Which I would love to do, but can't).
Thanks for the thought tho.
rothrand said:
bluecarbon -
This tutorial requires USB connectivity to flash the tablet using Odin. (Which I would love to do, but can't).
Thanks for the thought tho.
Click to expand...
Click to collapse
That is for flashing cwm, which you said you all ready have. You just skip to step 11 since you have cwm. There is a cwm flash able root.zip on the page.
Sent from my GT-P3110 using xda premium
Thanks again to both of you. I'll try both and let you know how it goes.
rothrand said:
bluecarbon -
This tutorial requires USB connectivity to flash the tablet using Odin. (Which I would love to do, but can't).
Thanks for the thought tho.
Click to expand...
Click to collapse
wich rom are you using right now?? beacuse if by loosing root you just mean that you do not have anymore the superuser app that does not mean that you losto root!!! for example on my PAC-ROM i have root but no superuser app because superuser is integrated in the setting menu!!!
and so i think that now it is the same for most CM based ROM.
But if you easly want to check it just install from play store superSU from chainfire! it will check root on the first opening!!
dagothe9 said:
wich rom are you using right now?? beacuse if by loosing root you just mean that you do not have anymore the superuser app that does not mean that you losto root!!! for example on my PAC-ROM i have root but no superuser app because superuser is integrated in the setting menu!!!
and so i think that now it is the same for most CM based ROM.
But if you easly want to check it just install from play store superSU from chainfire! it will check root on the first opening!!
Click to expand...
Click to collapse
I am using the "PSN_Stock_P3100XXDMB1_4.1.2" ROM. And I indeed lose "Root", but still had SU and busybox. How it happened, I'm not quite sure. I followed bluecarbon's advice, and flashed a cwm flash able root.zip. That did it very nicely. I now have root and am a very happy camper.
Thanks to everyone, especially bluecarbon.
No problem, now i know it works. I always do the opposite. I root then flash cwm, so...Now I know.
Sent from my GT-P3110 using xda premium
You said you rebooted everything, but did you try a different cable?
Posted from my Fascinate using XDA Premium
Need help bad
I have a galaxy tab 2 10.1 p5110. It came with i think i 4.0.3 or 4. I used odin to upgrade to 4.1.1 then rooted it through the same odin. now the usb connection is gone. when i plug into my pc it only charge the tap and nothing else. Because of this i cannot do anything with it using usb. It also can be boot into recovery but when i try to install a rom it say signiture verification failed. it does this will every rom.
I really need help. I want to install the 4.1.2 firmware for my device but i cannot get usb connection.
rothrand said:
I've had my Galaxy Tab 2.0 7 for about 5 months now, and have rooted it, installed Modded ROMs, etc. Really enjoyed it.
However, yesterday, I decided to clean up my 32 gig external memory chip, and hooked up the USB cable to the computer as in the past.
Whoops! PC will now not recognize the tablet in USB mode. Nothing changed from the day before, both PC and tablet had worked together then.
Now, I get this message in the Device manager of the PC "Windows has stopped this device because it has reported problems. (Code 43)".
I tried the normal things, reinstalling drivers, using different USB ports, etc. Nothing worked. So, I'm assuming that I had a hardware failure
in the tablet or the USB cord that came with it.
I'd like to know if there is anyway to "Root" my tablet by Using wireless? That still works, and I can move stuff off and onto the tablet. But I
would still like to have the obvious advantages of it being rooted.
Thanks in advance for any help you might be able to give.
Click to expand...
Click to collapse
Use mobile Ódin
Hi
I was trying to root Nexus 5 with Windows 7 laptop. Got the error message shown in the picture.
" Rooting Failed! Command write failed (Too many links) "
Anyone know what is going on?
Any and all help is appreciated!
EDIT: I was able to unlock the bootloader but I still do not have root access!
saadster25 said:
Hi
I was trying to root Nexus 5 with Windows 7 laptop. Got the error message shown in the picture.
" Rooting Failed! Command write failed (Too many links) "
Anyone know what is going on?
Any and all help is appreciated!
Click to expand...
Click to collapse
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
GUGUITOMTG4 said:
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
I second this
Sent from my Nexus 5 using XDA Premium 4 mobile app
That and don't use s USB 3 port.
As @aooga said, make sure you use a USB 2.0 port. If that doesn't fix it, try another USB cable.
El Daddy said:
As @aooga said, make sure you use a USB 2.0 port. If that doesn't fix it, try another USB cable.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Dont root with toolkits. Use this method http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
saadster25 said:
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
Click to expand...
Click to collapse
USB 3 is the killer of all this adb stuff especially on Windows 8+. Just use a USB 2.
aooga said:
USB 3 is the killer of all this adb stuff especially on Windows 8+. Just use a USB 2.
Click to expand...
Click to collapse
Alright will try that. However just to let you know under the ADB devices command my device does show up listed and I am able to ADB pull apks off the device. Just this error message seems to come out of no where.
saadster25 said:
Alright will try that. However just to let you know under the ADB devices command my device does show up listed and I am able to ADB pull apks off the device. Just this error message seems to come out of no where.
Click to expand...
Click to collapse
Yeah I know. This happened to a bunch of other people too. I see you already unlocked the bootloader, so I'm assuming you know what to do from here. (flash recovery and flash the root.zip)
saadster25 said:
Wasn't using toolkits, was following CF auto root method as described on various sources including youtube videos.
Could it be just as simple as using a USB 2.0 port? Seems trivial.
Click to expand...
Click to collapse
We consider it a toolkit because it does things (a couple of them) for you. Now you run into issues and don't know what failed because it was doing hidden tasks.
The manual method besides doing the job, will teach you a thing or 2 or 3, plus will help you to troubleshoot simple things.
aooga said:
Yeah I know. This happened to a bunch of other people too. I see you already unlocked the bootloader, so I'm assuming you know what to do from here. (flash recovery and flash the root.zip)
Click to expand...
Click to collapse
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
saadster25 said:
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
Click to expand...
Click to collapse
Technically, yes, but here is a thread with all the workarounds http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
saadster25 said:
Side question, does rooting phone and unlocking the bootloader stop over the air (or any kind of) updates from google?
Click to expand...
Click to collapse
If you only unlock the BL/root the phone and don`t uninstall/replace system components you will still be able to receive and install OTA`s with the stock recovery. You`ll have to reroot afterwards though, but that only takes a minute.
Trying to figure out for the life of me how to root.
On odin I get stuck at get pit mapping.
Tried numerous ways and apps too root, nothing.
I don't know what else to do.
Tried different computer.
My oem usb broke bought another one.:crying:
Don't know if that's the problem.
Never had a problem flashing custom recovery to any Samsung device before.
Couldn't find ways to downgrade.
Oem and debugging shows unlocked.
What do I Do?
Plz help.
Idk wish i had note 5 can you odin a prerooted stock rom
Sent from my SM-N930F using XDA-Developers Legacy app
I get stuck at "get pit mapping" with everything I try to flash with odin.
Back in the day when I first rooted this device on Marshmallow I just used this simple YouTube tutorial. Does it not work on 7.0?
EDIT: If not the same guy has a video for 7.0 as well, but it roots with Magisk(instead of SuperSU), which I personally don't like.
Sent from my SM-N920T using Tapatalk
bogarty said:
Back in the day when I first rooted this device on Marshmallow I just used this simple YouTube tutorial. Does it not work on 7.0?
EDIT: If not the same guy has a video for 7.0 as well, but it roots with Magisk(instead of SuperSU), which I personally don't like.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I don't know if it's my computer or usb cord or driver issue.. but I get stuck at get pit mapping... every time..
Dethbytes said:
I don't know if it's my computer or usb cord or driver issue.. but I get stuck at get pit mapping... every time..
Click to expand...
Click to collapse
Some simple things you can try that I saw worked for others with this issue on XDA:
1) MAKE sure your Odin is up to date.
2) Try a different USB slot.
3) Try a different USB cord.
4) Some even had luck bypassing this issue by running Odin on a Windows Virtual Machine.
There are also many other threads like THIS out there on XDA that you can search for answers.
Dethbytes said:
Trying to figure out for the life of me how to root.
On odin I get stuck at get pit mapping.
Tried numerous ways and apps too root, nothing.
I don't know what else to do.
Tried different computer.
My oem usb broke bought another one.:crying:
Don't know if that's the problem.
Never had a problem flashing custom recovery to any Samsung device before.
Couldn't find ways to downgrade.
Oem and debugging shows unlocked.
What do I Do?
Plz help.
Click to expand...
Click to collapse
Don't root with odin. Install twrp recovery and flash the magisk or super user zip. If you can't flash anything you need to reinstall samsung usb drivers. And I don't mean auto install via Windows I mean download the exe manually. And get the right twrp. Google twrp and your device name. I've never had this issue