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
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 tried rooting my 4.1.2 Android version Verizon Samsung Galaxy S3 using this method: phonerebel(DOT)com/how-to-root-verizon-samsung-galaxy-s3-4-1-1-install-cwm-recovery/
The rooting fully worked, no problems, and then I edited three lines in my build.prop file in order to install a 3rd party app. Then I restarted by phone. Now, after the GSIII logo comes up, the screen goes black and the notification light softly glows.
I put it into manual mode to check for backups, and it cannot find any that I've made. I do however have a backup of the build.prop file separate from the phone
My basic question is, can I edit or replace my phone's system files from my PC even if my phone won't fully boot past the Samsung and SIII splash screens? My computer detected my phone being plugged in, but Android commander can not find it and open it. Is there another way? I do not want to have to resort to a system restore.
Thank you.
ZachTheCommie said:
I tried rooting my 4.1.2 Android version Verizon Samsung Galaxy S3 using this method: phonerebel(DOT)com/how-to-root-verizon-samsung-galaxy-s3-4-1-1-install-cwm-recovery/
The rooting fully worked, no problems, and then I edited three lines in my build.prop file in order to install a 3rd party app. Then I restarted by phone. Now, after the GSIII logo comes up, the screen goes black and the notification light softly glows.
I put it into manual mode to check for backups, and it cannot find any that I've made. I do however have a backup of the build.prop file separate from the phone
My basic question is, can I edit or replace my phone's system files from my PC even if my phone won't fully boot past the Samsung and SIII splash screens? My computer detected my phone being plugged in, but Android commander can not find it and open it. Is there another way? I do not want to have to resort to a system restore.
Thank you.
Click to expand...
Click to collapse
You could adb push the build.prop to /System but that would only work if you had USB Debugging enabled in Developer Settings. If you don't recall enabling that you could try adb and check if it will connect to your device. If it doesn't, then you need to do a system restore OR dirty flash a rom in recovery if you rooted AND unlocked your bootloader.
SlimSnoopOS said:
You could adb push the build.prop to /System but that would only work if you had USB Debugging enabled in Developer Settings. If you don't recall enabling that you could try adb and check if it will connect to your device. If it doesn't, then you need to do a system restore OR dirty flash a rom in recovery if you rooted AND unlocked your bootloader.
Click to expand...
Click to collapse
I am 100% certain that I have debugging enabled. I've never disabled it. However, I do not know how to use abd. That is something I will have to install and figure out.
I assume that pushing the file through abd is the "sideloading" referred to in manual mode, and that a "package" can be any appropriate file type.
SlimSnoopOS said:
You could adb push the build.prop to /System but that would only work if you had USB Debugging enabled in Developer Settings. If you don't recall enabling that you could try adb and check if it will connect to your device. If it doesn't, then you need to do a system restore OR dirty flash a rom in recovery if you rooted AND unlocked your bootloader.
Click to expand...
Click to collapse
Dude he has 2 threads saying the same thing plus both in the wrong section. I gave him a possible solution on the first one I saw.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
jmxc23 said:
Dude he has 2 threads saying the same thing plus both in the wrong section. I gave him a possible solution on the first one I saw.
Click to expand...
Click to collapse
Oh, man now I'm seeing that since Kenny moved this thread lol I appreciate you getting the OP all fixed up.
Sent from my SCH-I535 using Tapatalk 4
Hello,
I have a tablet that has recently stopped booting. The manufacturer does not provide a firmware rom, nor have I been able to recover it any other way. I feel like I have been running in circles in researching ways to recover it (but I have learned alot). I think that I could recover the tablet if I could install a more flexible recovery manager, such as CWM or TWRP. However, to my knowledge, the tablet must be rooted first in order to install these custom recoveries. So that brings mt to my question: How can I root a tablet that won't boot? I have heard many good (and a few bad) things about Kingosoft Rooter and other root methods. However, even Kingosoft requires the tablet to have USB debugging enabled. Unfortunately, I did not have this enabled before my tablet crashed. So:
1. Is it possible to root my tablet that won't boot?
2. Is it possible to enable USB debugging on my tablet that won't boot?
3. Is there any other way you can think of to get this tablet running?
By the way, the tablet is a RCA RCT6378W2 tablet. I can access the stock recovery (android system recovery <3e>, but I can't seem to make it do anything worthwhile. Any ideas? Thanks!
1. You can't root because the tablet must be on
2. You can't enable adb debugging because the tablet must be on
3. I guess that your tablet is a made in china tablet, so there should be a devices that have same or similar characteristics, and maybe there is a stock rom for those devices
Good luck for your tablet :good:
jeremyb234 said:
Hello,
I have a tablet that has recently stopped booting. The manufacturer does not provide a firmware rom, nor have I been able to recover it any other way. I feel like I have been running in circles in researching ways to recover it (but I have learned alot). I think that I could recover the tablet if I could install a more flexible recovery manager, such as CWM or TWRP. However, to my knowledge, the tablet must be rooted first in order to install these custom recoveries. So that brings mt to my question: How can I root a tablet that won't boot? I have heard many good (and a few bad) things about Kingosoft Rooter and other root methods. However, even Kingosoft requires the tablet to have USB debugging enabled. Unfortunately, I did not have this enabled before my tablet crashed. So:
1. Is it possible to root my tablet that won't boot?
2. Is it possible to enable USB debugging on my tablet that won't boot?
3. Is there any other way you can think of to get this tablet running?
By the way, the tablet is a RCA RCT6378W2 tablet. I can access the stock recovery (android system recovery <3e>, but I can't seem to make it do anything worthwhile. Any ideas? Thanks!
Click to expand...
Click to collapse
Wipe cache and reboot and when it doesn't work do you have to try factory reset.
Bink Feed said:
Wipe cache and reboot and when it doesn't work do you have to try factory reset.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions.
@ bink feed - Thanks for those recommendations. Those are the normal recommendations that should be given to most people. Unfortunately, I have already tried both of those options with no success. It seems that many, many people are running into this problem. It makes me wonder if the recovery partition is corrupt or if some system files were somehow corrupted. The "wipe cache" option and "factory reset" option both perform successfully according to the recovery system, but they do not fix the problem with the tablet not booting. I apologize for failing to mention that I have tried these options. If you have other ideas, please let me know.
@ kfarhan57 - Thanks for the suggestion. This seems like a good idea and it is something I have attempted to do. Problem is, I don't know precisely what similarities must be present for this to work. I have tried using ROMs from other tablets that share the same processor and motherboard, but have not had any success. They seem to always fail the verification process. I have very, very little experience in all of this, so it's always possible that I am not doing it correctly too. Do you know of anyone who has successfully done this? (Someone who has restored on device with a firmware from a similar device). If so, I'd like to ask them how they did it. Here is what I have tried:
1. Boot device into Android Recovery System.
2. Select "Apply update from ADB"
3. Connect the tablet to PC using USB cable
4. Load up Cmd terminal in Windows, navigate to folder containing ADB.exe
5. Type in "ADB sideload filename.zip"The only thing that I have successfully sideloaded (and passed verification with) has been 3 small firmware updates for my tablet. Unfortunately, they are minor updates and do not restore the Operating System or ability to boot into the OS. Presently, I have been toying with the idea of merging one of these small firmwares that pass verification with the factory OS firmware from a similar device. I don't know if this is even possible, and if it is, I probably lack the knowledge needed to do it. If anybody reading this post has a suggestion, please let me know! BTW, one other thing I forgot to mention is this- I have the files copied from a working tablet of the same model. I have the boot.img, recovery.img, system.img, and virtually everything from his device... I just don't have a clue what to do with it. Thanks again. Hope to hear back from one of you!
So this is my first post on XDA, due to the lack of information on this particular device. Here I'll try to explain how I managed to root this device after trying several methods available here and all over the web. First I'll explain what didn't work:
VROOT (*)
Framaroot
Motochopper
SRS Root
MTK Toolkit
Nearly every solution on the web
After trying every method above, I noticed none of them were working. They all were giving false positives. No ROOT at all. I was kinda frustrated, 'cause I had followed every instruction possible, without success. I double checked my PC drivers, and I noticed something odd: Every time I changed the USB connection type on the L50, Windows installed different drivers for the device. I'm saying this was odd because I installed the drivers from LG drivers pack, so I was a bit confused. So, after Windows Installed the drivers for MTP, Modem, PTP and LG mode, I tried VROOT and... VOILÁ! I had ROOT:laugh::laugh:
So here are the steps I followed, and the tools I used:
Download VROOT (a.k.a. as IRoot) from w w w. mgyun. c o m / en / getvroot (without spaces)
Enable DEBUG MODE (Surf the web if you don't know on how to do it).
Plug your device to your PC and wait until Windows Installs the drivers for the connection type.
Without unplugging the device, Change the USB connection type to the next one. Wait 'till windows finishes installation.
Repeat the previous step untill you finish with all connection types.
Check Device Manager for missing drivers. If you have some missing, repeat steps above.
Open VROOT/IROOT and plug your device to the PC. Follow on-screen instructions and wait.
ENJOY!
Now, I have to find a Custom Recovery that works with L50... so if you guys know where I can get one, I'll appreciate your help.
Your Thread will be moved to appropriate Section.
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
someone know how i can do a nandroid backup on LG L50 ?
Thank you so much. Worked on D213AR
Can you confirm if there is a way to unlock NFC hidden option on my phone?
jam66 said:
someone know how i can do a nandroid backup on LG L50 ?
Click to expand...
Click to collapse
If you managed to get Root (with the steps described on the OP) You can use Titanium Backup.
THE Ghost2 said:
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
Click to expand...
Click to collapse
same for me i made cwm for it cant boot to it because it has locked boot loader
So is it possible to root the phone with the official rom?
Or am i missing something?
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.