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
Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app
hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.
Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."
Tried a different port? Tried second different port with a different USB cable?
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?
On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.
Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app
Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks
I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app
Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!
Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?
The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?
hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.
Android users need help with my phone! I am trying to manually turn on USB debugging (to access files on phone through update thru ADB mode in recovery options, I can install the driver for the phone but won't work until USB debugging is turned on) while my phone cannot boot into the OS. Is there a secret way to turn on USB debugging through recovery mode? (I do not want to wipe the data, and phone unfortunately is not rooted)
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
rootSU said:
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main issue is that I am trying to retrieve my non backuped data on the phone and the phone itself will not boot into the Android OS.
I have looked into unlocking the fastboot/bootloader but it will wipe the data which would be pointless.
The data on the phone is more critical to me than the phone itself (and yes I was dumb enough to not back it up, didn't expect a flagship phone less than a year to crash on me, but I have learned for next time).
I am looking for any possible way to retrieve the data. I have tried to access the phone from the computer but I cannot access it since USB debugging is turned off and the phone is not rooted or doesn't have any other modifications.
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Y is it non bootable?
Sent from my Android 5.0 Nexus 5
You are stuck. Stock recovery, locked bootloader, and OS will not boot. As RootSU mentioned, USB debugging has nothing to do with this. Stock recovery will not connect to adb.
Unless you can get the phone to boot looks like data is lost. Sorry.
Yoda8232 said:
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Click to expand...
Click to collapse
No.
Yoda8232 said:
didn't expect a flagship phone less than a year to crash on me
Click to expand...
Click to collapse
Expect it from every electronic device. Especially expensive and complicated ones.
So I actually had warranty left from Google (bought directly from Google) and was going to RMA it but I decided not to because the data on there is important to me and worth more than the phone itself (yes I should of backuped everything but oh well what can I do now). And I bought a new phone so this Nexus 5 will be my little side project to try and revive it; somehow.
I will try to keep going at it, I have small programming/coding skills but it would be nice to find a way to open up the USB debugging option on the locked stock phone somehow that doesn't bootup.
Any suggestions on where I should start to start testing different "procedures"?
I rooted my phone with Kingroot and wanted to switch it to Super User so that it would not unroot every time I rebooted.
When I switched it to Super User it told me to uninstall other Root Managers so I clicked Uninstall. It got stuck on uninstalling so I rebooted my device thinking I could just update the binary when my device rebooted. Now I am stuck on bootloop and I never downloaded CWM or TWRP. I have already tried factory reset and cache wipe to no avail. Please help I just bought this phone and honestly have no idea what I'm doing.
Just going to buy a new phone. Never touching anything root again. Wow. Something so silly just costed me $500 dollars.
I want to say I can use Odin on a windows computer to flash the original stock rom back into it but I don't have USB debugging on in my phone so something tells me that's a long shot and a giant headache. going to take it to a phone repair shop in town and see what they say. this sucks.
triiuzii said:
I'm not sure, but I don't think you need usb debugging enabled. I've flashed back to stock roms before without enabling it (on other phones).
Click to expand...
Click to collapse
darknaio said:
@triiuzii You are correct, you do not need USB debugging turned on as I forgot to turn it on once when testing root options on the j3, and I was still able to flash stock firmware through Odin. Odin is its own separate system to boot into. I don't think it's dependent on other settings. I think USB debugging is only for ADB. I could be wrong but this is just from my personal experience.
Click to expand...
Click to collapse
Please read the Sticky threads for XDA Assist.
You are not authorized to respond here.
The_Merovingian
Forum Moderator
gsprague16 said:
I want to say I can use Odin on a windows computer to flash the original stock rom back into it but I don't have USB debugging on in my phone so something tells me that's a long shot and a giant headache. going to take it to a phone repair shop in town and see what they say. this sucks.
Click to expand...
Click to collapse
Hi
As mentioned by others, you do not need usb debugging to odin flash in download mode.
This is fixable if you have the right firmware. Apologies for the late reply.
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