Hello one and all,
I've been watching this forum from the digital shadows for well over a week now, hoping to find some good news in regards to a root method for the Samsung Galaxy J7 Sky Pro (SM-S727VL). I've tried several of the "one-click" options (Kingroot, SRSroot, Kingoroot just to name a few) with no real success. I have even been watching for a possible root via CF-Autoroot to no avail.
Which led me to create this account for the sole purpose of creating this thread. Has anyone had any luck or made any progress in the realm of rooting for this phone? I will be honest and say I have never successfully rooted a phone as of the creation of this thread, which may tag me as a noob of sorts, but I can also say I have never bricked a phone either.
I have heard whispers of a possible ADB method, and having played around with ADB commands a bit I believe if there was a basic rundown of how to achieve it via adb commands I might have a decent shot at it.
At any rate, before I ramble off onto any other tangents, I'm going to end this post. The title alone asks my question eloquently enough.
Thanks for your time!
Adb is my next move. I travel a lot and I haven't had time to try it yet, it may be a few weeks b4 I have some free time. I have tried every known 1 click apk with no success. And also the windows version. Iv also tried going through cf-root phone list to find a device with the same hardware and buulds, no luck there either.
I'm willing to give adb a go, I just don't really know the steps to take. I've managed to pull off some basic adb actions, but no idea how to use it to gain root access.
There is a detailed guide on rooting using adb here on the form. Just type rooting any android device using adb
Ok I had a little free time today but no good internet connection. Man I miss my Verizon s5 with mobile hotspot. I spent most of the day getting adb to connect with my pc, what a b!+$h. So far this is what I got. You will possibly need to clear all android drivers from your computer. To do this u will need a free utility called driver store. How to use, click every box that says a cellphone or tablet manufactur including yours s727vl samsung. Hit force stop and delete. Close that out and you need to download ADB DRIVER and it should connect. Don't try root process yet. You need to download Ubuntu 11.4 . It's a Linux os. To get this working you will need a utilty to make it bootable from a usb drive. I don't remember the exact process but to boot from a usb drive restart your pc and while it's booting press f8 I believe and that will give you your boot options. There is a guide to root using adb on the forum .The author says there is good chancr of rooting with his method. I wish i had time and internet so i could report back weither all this work will payout with a rooted phone. I spent all day just trying to get adb to connect.
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
Also the adb commands isn't hard. Once are connected just type in the commands that's listed and hit enter after each command. I rooted my first phone smart phone using adb. It was as complicated as it is now.
I've got an external hard drive that connects via usb, and I have the iso for that version of Ubuntu already. Tried going the sneaky way and just using a virtual machine to get the job done, but no luck. I'll try installing it on that external drive here in a bit and see if I can make any progress.
What happens to motto fail? The guys who made that root using an exception err?
dorain said:
Ok I had a little free time today but no good internet connection. Man I miss my Verizon s5 with mobile hotspot. I spent most of the day getting adb to connect with my pc, what a b!+$h. So far this is what I got. You will possibly need to clear all android drivers from your computer. To do this u will need a free utility called driver store. How to use, click every box that says a cellphone or tablet manufactur including yours s727vl samsung. Hit force stop and delete. Close that out and you need to download ADB DRIVER and it should connect. Don't try root process yet. You need to download Ubuntu 11.4 . It's a Linux os. To get this working you will need a utilty to make it bootable from a usb drive. I don't remember the exact process but to boot from a usb drive restart your pc and while it's booting press f8 I believe and that will give you your boot options. There is a guide to root using adb on the forum .The author says there is good chancr of rooting with his method. I wish i had time and internet so i could report back weither all this work will payout with a rooted phone. I spent all day just trying to get adb to connect.
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
Also the adb commands isn't hard. Once are connected just type in the commands that's listed and hit enter after each command. I rooted my first phone smart phone using adb. It was as complicated as it is now.
Click to expand...
Click to collapse
So what's the process lol
ADB does not work with the Samsung J7 Sky Pro. Unfortunately, this was one of the first Samsung phones to not have the OEM unlock button in the Developer Options. Therefore unlocking the bootloader and flashing the phone isn't possible. I work on computer and electronics for a living and still can not find a successful Flash/Rot option for the phone.
Related
I used to have a rooted EVO 4G through work, but recently they switched me over to an iSheep, and as you can imagine I absolutely hate it. And since it’s for work they’ve installed AirWatch so I can’t jailbreak it. But I also have a TF101 that's currently not rooted.
I got my TF101 about a year ago and rooted it like every good android user should. But after about 6 months, I found a small hair line crack in the touch screen. I unrooted it and sent it in to ASUS for them to repair. I always keep my tablet closed in the docking station when it wasn’t in use. I then found this thread, http://forum.xda-developers.com/showthread.php?t=1498237 that stated this is why the screen cracked. So ASUS and I went back and forth for about a month before they finally covered it under warranty and repaired my tablet.
When I got my tablet back I found they upgraded it to 9.2.1.27. I connected it to a computer so I could reroot it, but my tablet is no longer detected by a computer. I tried two computers and two data cables. I’ve also tried all the methods for installing the drivers. I didn’t want to send it back to ASUS due to the issues I previously had with them. I’ve been following Thing O Doom’s thread, http://forum.xda-developers.com/showthread.php?t=1681155 because he stated he's working on a rooting apk, but he no longer has his TF101 so progress has been slow.
But in my searching I found this thread,http://www.transformerforums.com/fo...rmed-fix-gain-root-after-8-6-5-21-update.html that stated I can get the zip out of an old ASUS update and put that on my sdcard and let the tablet update itself to an older version. ASUS made an instruction sheet for manually updating with a zip, http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101G/e6754_TF101_Update_SOP.pdf. Once downgraded I could use RazerClaw http://forum.xda-developers.com/showthread.php?t=1345049 to root, and then flash a recovery, rom, etc.
Will this method work? I have to believe no, it just seems too easy. I haven’t tried it yet because I worried about bricking my tablet and not being able to fix it since it won’t connect to a computer.
Any response, opinion, recommendation, experience would be greatly appreciated.
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
frederuco said:
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
Click to expand...
Click to collapse
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
You may be able to use Wolf's tut for this...
benmatlock said:
You may be able to use Wolf's tut for this...
Click to expand...
Click to collapse
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
air adb, there's at least 1 good free one in the play store.
Lethe6 said:
air adb, there's at least 1 good free one in the play store.
Click to expand...
Click to collapse
Thanks for the response, I looked into that and I thought you had to be rooted for it to work. I'll look at it again.
akt27x said:
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
Click to expand...
Click to collapse
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
akt27x said:
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
Click to expand...
Click to collapse
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
frederuco said:
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
Click to expand...
Click to collapse
I tried this and you're right it didn't install the older firmware. It looked like it was going to because the status bar was moving at the bottom, but after a few minutes it went to an android laying down with his guts open and a exclamation mark above him.
benmatlock said:
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
Click to expand...
Click to collapse
I think I've tried this. I have a terminal emulator installed and I followed some instructions about entering things like this in but I think I got a message stating access denied. But I'll try it again tonight and reply back with the results.
Re: [Q] Possible Downgrade to Root
Using wolf's instructions I tried this with a terminal app on my tablet and got the following.
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
I then tried this and got the following.
[email protected]:/ $ dd if=/sdcard/recoveryblob.bin of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
Sent from my Transformer TF101 using XDA Premium HD app
Woody said:
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
Click to expand...
Click to collapse
This weekend I tried to install the drivers again. I first went through the control panel and device manager and deleted anything that said android and asus, then rebooted my computer. I then tried to install PDANet because I read that it'll install the drivers needed and if you're having a problem it's an easy way to install them. During the PDANet install it told me to plug my transformer in to load the drivers. When I did it said it was installing new drivers but then it said they didn't install. My transformer came up as an unknown device in device manager.
I then went through and deleted the unknown device and checked in the control panel again, then rebooted my computer. I then put my tablet in APX mode to try and get it to load the drivers. Again it didn't install them and my transformer came up as an unknown device. I deleted the unknown device agian, rebooted, and went to ASUS website and installed ASUS Sync. When it finished I rebooted and then started ASUS Sync. Again when I connected my transformer to my computer it said it was loading the drivers, then it failed, and the computer showed my transformer as an unknown device. ASUS Sync also stated there was no device connected to it.
All the reading I've been doing, it seems like there are some other people experiencing the same issues I am, and I haven't seen where anybody has posted a solution. If anybody has any input please let me know.
I think I'm getting closer. I downloaded WLanAdb from the play store and followed the directions and downloaded the needed files to my computer. In the command prompt I type "WLanAdbTerminal devices" and my tablet will show in the list of devices. But WLanAdb is only setup to except a few commands, the main purpose of the app is for pushing files. It was the only wireless ADB app that I could find that didn't require root.
I then found SSHDroid in the play market and I downloaded putty to my computer. I connect to my computer using that. When I type "adb devices" I get a mesage that states
daemon not running. starting it now on port 5038
daemon started successfully
List of devices attached
I then left putty and went back to the command prompt and typed "adb connect (with my ip address and port from SSHDroid)" and it said it connected to that ip address and port. I then type "adb devices" and there are no devices listed.
Again I think I'm very close to getting my tablet connected wirelessly to adb. I think there is just one simply thing I'm missing. Any help would be greatly appreciated.
I'll continue to update this thread until my tablet is rooted or I reach a dead end, so this will be a reference for anybody experiencing the same issues as me.
Thanks in advance.
akt27x, did you ever come to a solution?
presbypenguin said:
akt27x, did you ever come to a solution?
Click to expand...
Click to collapse
I haven't. I'm now trying to make a Linux boot flash drive to see if I can get my tablet to connect that way, since I've read that Linux doesn't require drivers. I downloaded LinuxLive USB Creator but haven't had the time to try it yet.
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone
has to be a way to get a connection between the pc and phone
I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.
ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?
[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.
when i just boot it goes to download mode and says "could not do do normal boot"
i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?
If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.
fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me
never let up
Basically what had happened was I was out on Friday night, drunkenly gave my phone to my friend to keep safe, and then totally forget about it. Fast forward to me panicking and immediately setting a password lock using Android Device Manager. For some reason when setting a password remotely from your PC it can be as long as you want, but when typing it in my phone there was a limit, meaning I could not get in.
Why don't you just use ADM again to reset your password and put a new one?! Well apparently they don't let you form a new password once there is one already locked on your phone. Why don't you try unlocking it via findyoursamsung?! I didn't create a samsung account when prompted to. (hindsight is 20/20)
I also tried some other third-party backup apps such as Kies3 and Samsung Watch, both of which required the phone to be unlocked to function - which is also why I can't simply just connect my phone via USB and drag the data into a folder.
This lead me to doing a ton of research and it seemed the only way to get my pictures and videos back without resetting my phone would be through those coding programs and ADB and such. I am not well versed in this area at all so I looked at a bunch of sites explaining what to do.
From my limited understanding, it came down to a few things:
- My device is a Samsung Galaxy S4, probably kit kat or jelly bean. It is neither rooted nor does it have the "USB debugging" enabled
- I have successfully installed CWM (clockwork mod) and ADB (android debugging bridge) onto my computer/phone because apparently when CWM goes into recovery mode, the debugging is automatically enabled, where I'd then be able to unlock the screen (but I don't seem to know how to input adb commands - where would I do this?!)
- I installed a few other programs that were of no use to me because I had (almost) no idea how to use them (Cygwin, Odin, JOdin3, Heimdall) in conjunction with ADB and the "Download" mode on my phone to flash CWM to be my "custom Recovery" instead of the stock recovery
- I saw there were some third party apps that would automatically (?) unlock your phone screen for you but I wasn't too keen on trusting them seeing as most of thm were outdated , so unless you guys recommend one I would rather not download those
- I think my main issue is not knowing how to simply bring up a terminal and input commands but sometimes they wouldn't even recognize my device (probably because USB debugging is disabled)
I have been infront of my computer for almost a whole day now trying everything and reading everything simply trying to figure out what to do. I have looked at way too many guides and could probably recite them to you. I guess the point of this is I really would prefer not to lose this data as it has a lot of sentimental value, so I'm straying away from those methods that require you to wipe your phone. If any of you know any helpful sites or guides (I probably have seen them) that explains things very formally and easy to understand, let me know, I will be forever gracious for your help.
XDA Visitor said:
Basically what had happened was I was out on Friday night, drunkenly gave my phone to my friend to keep safe, and then totally forget about it. Fast forward to me panicking and immediately setting a password lock using Android Device Manager. For some reason when setting a password remotely from your PC it can be as long as you want, but when typing it in my phone there was a limit, meaning I could not get in.
Why don't you just use ADM again to reset your password and put a new one?! Well apparently they don't let you form a new password once there is one already locked on your phone. Why don't you try unlocking it via findyoursamsung?! I didn't create a samsung account when prompted to. (hindsight is 20/20)
I also tried some other third-party backup apps such as Kies3 and Samsung Watch, both of which required the phone to be unlocked to function - which is also why I can't simply just connect my phone via USB and drag the data into a folder.
This lead me to doing a ton of research and it seemed the only way to get my pictures and videos back without resetting my phone would be through those coding programs and ADB and such. I am not well versed in this area at all so I looked at a bunch of sites explaining what to do.
From my limited understanding, it came down to a few things:
- My device is a Samsung Galaxy S4, probably kit kat or jelly bean. It is neither rooted nor does it have the "USB debugging" enabled
- I have successfully installed CWM (clockwork mod) and ADB (android debugging bridge) onto my computer/phone because apparently when CWM goes into recovery mode, the debugging is automatically enabled, where I'd then be able to unlock the screen (but I don't seem to know how to input adb commands - where would I do this?!)
- I installed a few other programs that were of no use to me because I had (almost) no idea how to use them (Cygwin, Odin, JOdin3, Heimdall) in conjunction with ADB and the "Download" mode on my phone to flash CWM to be my "custom Recovery" instead of the stock recovery
- I saw there were some third party apps that would automatically (?) unlock your phone screen for you but I wasn't too keen on trusting them seeing as most of thm were outdated , so unless you guys recommend one I would rather not download those
- I think my main issue is not knowing how to simply bring up a terminal and input commands but sometimes they wouldn't even recognize my device (probably because USB debugging is disabled)
I have been infront of my computer for almost a whole day now trying everything and reading everything simply trying to figure out what to do. I have looked at way too many guides and could probably recite them to you. I guess the point of this is I really would prefer not to lose this data as it has a lot of sentimental value, so I'm straying away from those methods that require you to wipe your phone. If any of you know any helpful sites or guides (I probably have seen them) that explains things very formally and easy to understand, let me know, I will be forever gracious for your help.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
A bit of a doozy....
This thread may help:
> Samsung Galaxy S 4 i9500, i9505, i9505G, i9506 > Galaxy S 4 Q&A, Help & Troubleshooting > [RESOLVED] HELP please!! Unable to unlock device locked by Google Device Manager
May need to modify solution two to use under CWM. That is, mount data via adb (or via recovery if there's an option) before issuing (the rest of) the adb commands.
By the way, here is a primer to adb:
http://www.xda-developers.com/all-in-one-guide-to-adb/
Hope this helps, and good luck!
Truth: I don't generally use or develop for Android devices, but I got one today to use as a testing platform for an app I'm working on. So pardon me in advance if I'm sounding like a noob. I promise I mostly know what I'm doing with this thing. Just having some trouble...
I purchased the Nextbook Ares 8 and am marveling at what you get for the cost these days considering my first personal PC ran about 18.3x slower than this thing, with 1\4 the power, and was considerably bigger. Amazing.
But I wanted to root it and put Marshmallow on it. Now, here's the thing: I don't have a MicroSD. So I'm being a bit hasty and trying to do this via strictly USB. I've read every post on this site about this specific tab and rooting it. I've also installed KingoRoot, iRoot, VRoot, King Root... all with no luck. They all fail.
I figure it's because the device is encrypted? I've been attempting to get around that all day.
And yes, it's been put into developer mode with USB debugging enabled, too.
I've also tried doing "adb reboot bootloader", and then "fastboot oem unlock", and it'll reboot fine, but it'll just hang in CMD on <waiting for device>.
I know if I had a MicroSD, I could pull it off, but I don't at the moment. Am I screwed until I do?
Thank you guys! :fingers-crossed:
domilu said:
Truth: I don't generally use or develop for Android devices, but I got one today to use as a testing platform for an app I'm working on. So pardon me in advance if I'm sounding like a noob. I promise I mostly know what I'm doing with this thing. Just having some trouble...
I purchased the Nextbook Ares 8 and am marveling at what you get for the cost these days considering my first personal PC ran about 18.3x slower than this thing, with 1\4 the power, and was considerably bigger. Amazing.
But I wanted to root it and put Marshmallow on it. Now, here's the thing: I don't have a MicroSD. So I'm being a bit hasty and trying to do this via strictly USB. I've read every post on this site about this specific tab and rooting it. I've also installed KingoRoot, iRoot, VRoot, King Root... all with no luck. They all fail.
I figure it's because the device is encrypted? I've been attempting to get around that all day.
And yes, it's been put into developer mode with USB debugging enabled, too.
I've also tried doing "adb reboot bootloader", and then "fastboot oem unlock", and it'll reboot fine, but it'll just hang in CMD on <waiting for device>.
I know if I had a MicroSD, I could pull it off, but I don't at the moment. Am I screwed until I do?
Thank you guys! :fingers-crossed:
Click to expand...
Click to collapse
Hello,
You need proper drivers for your device, also adb and fastboot tools. (Here's an easy one Minimal ADB and Fastboot)
Also you may visit here Root Nextbook Ares 8 & TWRP Recovery, If you mess up somewhere here's How to restore your Nextbook Ares 8 to stock
Good luck!
-Vatsal
Vatsal said:
Hello,
You need proper drivers for your device, also adb and fastboot tools. (Here's an easy one Minimal ADB and Fastboot)
Also you may visit here Root Nextbook Ares 8 & TWRP Recovery, If you mess up somewhere here's How to restore your Nextbook Ares 8 to stock
Good luck!
-Vatsal
Click to expand...
Click to collapse
Well all drivers are installed properly. adb devices returns the serial number (YFAV1015088537), and fastboot devices returns BaytrailB94034F3. Both are valid identifiers.
Now, however, no matter what fastboot command I do, such as fastboot oem unlock, it returns FAILED (remote: unknown command)
This is exactly why I don't do Android, right here. It's like a never ending track full of hurdles.
domilu said:
Well all drivers are installed properly. adb devices returns the serial number (YFAV1015088537), and fastboot devices returns BaytrailB94034F3. Both are valid identifiers.
Now, however, no matter what fastboot command I do, such as fastboot oem unlock, it returns FAILED (remote: unknown command)
This is exactly why I don't do Android, right here. It's like a never ending track full of hurdles.
Click to expand...
Click to collapse
Hello,
You may try the link I posted above.
Also, if you have any issues with them, please post in the respective threads. The experts there maybe able to assist you.
Good luck!
-Vatsal
Hello Everyone..!
I Am Using Samsung M30s [Rooted]
[Please Read Patiently]4 To 5 Months Ago My Phone MTP Stopped Working.
Still Finding Solutions.
My Device Can't Be Recognized As A MTP Device By Any PC Via USB.
I Tried Many Cables And Many PCs.
My Phone Doesn't Show Fast Charging Since It Started Not Recognized By PC.
I Watched Almost All YouTube Videos About This Issue None Of Them Worked.
I Think It Would Be Charging Port Problem But I Am So Confused.
Please Help And Suggest Me Someting.
Whenever I Restart Or Switch-Off From Home Button My Root Getting Lost.
I Have To Click Factory Reset To Get Into Recovery In Order To Restore Root.
[I TRIED 100+ METHODS. I DID EVERYTHING BUT NO LEAD]
Thank You.!
In Android settings enable USB-MTP mode if not done yet.
BTW: If in phone's USB-options PTP is listed but not MTP, then maybe what Android may refer to as "File transfer" is the same as MTP.
Thanks For Your Reply But Sadly It Is Not The Problem.
As I Mentioned Above I Explored Almost All YouTube Videos On Related Topic.
This Is Not The Problem.
BTW Thanks...
cursedhawk said:
Hello Everyone..!
I Am Using Samsung M30s [Rooted]
[Please Read Patiently]4 To 5 Months Ago My Phone MTP Stopped Working.
Still Finding Solutions.
My Device Can't Be Recognized As A MTP Device By Any PC Via USB.
I Tried Many Cables And Many PCs.
My Phone Doesn't Show Fast Charging Since It Started Not Recognized By PC.
I Watched Almost All YouTube Videos About This Issue None Of Them Worked.
I Think It Would Be Charging Port Problem But I Am So Confused.
Please Help And Suggest Me Someting.
Whenever I Restart Or Switch-Off From Home Button My Root Getting Lost.
I Have To Click Factory Reset To Get Into Recovery In Order To Restore Root.
[I TRIED 100+ METHODS. I DID EVERYTHING BUT NO LEAD]
Thank You.!
Click to expand...
Click to collapse
The USB issues might be a hardware problem, the port itself might be faulty or maybe the soldering around the pins where it connects to your main board may need re-flowing due to breakdown from heat. Have you tried using wireless methods of transferring files between your device and PC?
But I don't see how that has anything to do with your device losing root. These issues may or may not be related.
Is your bootloader unlocked(OEM unlock)?
Do you have stock recovery or custom recovery?
What method did you use to root the device?
Hello Brother Thank You For Your Reply...
And I Will Sure Check Out My Charging Pin.
I Thought It Could Be
Soon If I Discover Something I'll Tell You
And One More Thing. I Used A Method From YouTube Channel AndroidHowTo 10 Months Ago.
I Have TWRP Custom Recovery.(But I Can't Boot Into It) [Because Of This USB Problem]
I Have Root.
Bootloader Unlocked.
cursedhawk said:
Hello Brother Thank You For Your Reply...
And I Will Sure Check Out My Charging Pin.
I Thought It Could Be
Soon If I Discover Something I'll Tell You
And One More Thing. I Used A Method From YouTube Channel AndroidHowTo 10 Months Ago.
I Have TWRP Custom Recovery.(But I Can't Boot Into It) [Because Of This USB Problem]
I Have Root.
Bootloader Unlocked.
Click to expand...
Click to collapse
When you installed TWRP, what method did you use to install it? Which rooting method did you use, SuperSu or Magisk? Did your rooting method include flashing DM-verity?
Can you give me a link to the specific guide/video that you followed?
Install a terminal emulator app on the device, open the app and type the following commands:
su (press enter, grant superuser permission if prompted)
Then type:
reboot recovery
If you are properly rooted, have granted su permission to terminal emulator and if TWRP is properly installed in the correct partition, this should boot you into TWRP.
You may have overlooked a step or you may have missed a detail somewhere in your rooting method. Or you may have used an incorrect method or file for your specific device. Your device might require something that wasn't in the guide that you followed.
Off the top of my head, those are possible causes of your issue, I may think of others, if I do, I'll post them here.
Droidriven said:
When you installed TWRP, what method did you use to install it? Which rooting method did you use, SuperSu or Magisk? Did your rooting method include flashing DM-verity?
Can you give me a link to the specific guide/video that you followed?
Install a terminal emulator app on the device, open the app and type the following commands:
su (press enter, grant superuser permission if prompted)
Then type:
reboot recovery
If you are properly rooted, have granted su permission to terminal emulator and if TWRP is properly installed in the correct partition, this should boot you into TWRP.
You may have overlooked a step or you may have missed a detail somewhere in your rooting method. Or you may have used an incorrect method or file for your specific device. Your device might require something that wasn't in the guide that you followed.
Off the top of my head, those are possible causes of your issue, I may think of others, if I do, I'll post them here.
Click to expand...
Click to collapse
The Video Guide I Followed While Rooting.
I Did All The Guy Did.
The Method You Told That Using "reboot recovery" Code In Terminal Emulator Is Booting As Usual Like ReBooting.
Doesn't Seems TWRP Exists
Thank You For Your Help..!
And I Wanted To Change The Port But When I Go To Nearby Service Centers They Are Not Seem To Be Right...!
They Told Me To Reset But I Can't Do It.
Whenever I Click On Factory Resett It Just Reboots
I Can't Reset My Phone.
But The Service Guys May Not Know About The Problem
I Have To Send It To A Samsung Repair Center