Hi everyone, I ran into a serious problem today with my S6 G920F. I was running stock android 7 with Magisk and TWRP installed, I flashed the firmware using Flashfire from the Google Play store.
This morning the phone decided it would stop charging, a problem I faced with Android M. Anyway I reflashed the firmware package but this time i chose NOT to select the options to inject supersu and save my custom recovery, thinking that I could get it back to stock and re root it from there.
The phone previously would not boot if either Magisk or SuperSu was not installed (after i rooted it), it would just endlessly loop. Unfortunately this was the case after i flashed the firmware .
I assumed it would be a quick fix as I could just use Odin to flash the stock firmware . Unfortunately I was wrong again: my computer gives me an error message "USB Device Not Recognized" no matter how many times I uninstall and reinstall the Samsung Driver, Odin wont detect the phone either. Even Smart Switch is at a loss. The phone is currently plugged into my PC and is charging normally, I CAN boot into stock recovery and download modes.
SOMEBODY PLEASE HELP!! :crying::crying::crying:
Seems very obvious now but I found the solution I found the original cable that came with the phone; plugged it into the PC and just like that the computer registered that it was a Samsung devices and started installing drivers right away, seems like the P8 Lite cable I was using isnt a data cable?
I was able to flash TWRP using Odin and flashed Magisk using TWRP. All is well
Related
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
kitchenspoon said:
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
Click to expand...
Click to collapse
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
erica_renee said:
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
Click to expand...
Click to collapse
Hi, cheers for the response,
I have tried all of what you have said but unfortunately no PC will see my device, not even an "unrecognized device". I have access to android system reocvery <e3> and Download mode (Odin) but the pc just won't recognized, tried new leads and so forth, nothing.
Okay so some of you might know that there is a ram management fix for the Samsung S6 by editing the build.prop file. I tried doing it and my phone went into a boot loop(it just repeatedly show the white text of SAMSUNG GALAXY S6). My phone is rooted by the ping pong method which doesn't trip knox. The last 2 things I want to do is go to a samsung store or flash a stock rom which wipes my data.
I saw a video that you can fix it by using adb. However, when i plug my phone in my pc while my phone was in recovery mode, the pc doesn't detect. But if my phone is in Download or just its boot loop mode, the pc detects but it often says "Your last device is not recognised or malfunctioned" or something like that. Yes I do have drivers installed including Kies3.
All I want to do is just to fix my s6 build.prop file without
1. Tripping the knox,
2.Not visiting the samsung store
3.Factory resetting my phone and flashing a new rom.
Please help. Thanks
*********EDIT***********
I found out that you can flash a zip file that restores the build prop file here:
http://forum.xda-developers.com/show....php?t=2212168
It's one of the replies to the post.
But I'm an odin noob so... how do you flash it???
***********EDIT AGAIN*********************
Okay... soooo I'm stuck now. I can't even get my s6 to connect to my pc. It just says usb device not recognised.
I already tried:
-Redownloading samsung usb drivers.
-Installing Kies3
-Installing Smart Switch then clicking more and reinstalling usb drivers.
-Using different port.
-Using different wire.
-Blowing into port and phone port to clear debris.
Help :/
I'm completely hopeless, and all I can count on are good people from XDA to help me.
I bought a new Samsung Galaxy S6, T-Mobile version [G920F], running Android 5.1.
I used this tutorial:
http://www.droidviews.com/root-samsung-galaxy-s6-and-install-twrp-recovery-all-models/
I enabled USB Debugging, downloaded latest Samsung USB drivers.
First I successfully installed TWRP 2.8.7.1, and meanwhile copied the SuperSU.zip to my device.
I had successfully entered TWRP, went to Install, and selected teh SuperSU file. It said it was done, so I went ahead and restarted my device.
Immediately, I noticed that the device was stuck on the boot logo (Galaxy S6 + Powered by Android screen).
And for some reason, when I connect the device with USB to mc PC, Windows says it's "damaged or undetected", something of that sort.
Luckily, I can still detect it in ODIN.
I might mention that I can still enter TWRP & Download Mode from the Bootloop.
I'll give any more information I can, just tell me if there is any hope for me.
Thank you so much.
hey everybody!
i was using my galaxy a3 2017 (SM320FL) for half a year with lineage os (15.1) and flashed the latest build (Lineage 15.1-20180821-UNOFFICIAL-a3y17lte) some weeks ago.
i allways noticed little bugs etc. but all in all it worked for me.
since a week now, the phone won't boot into the system anymore if not connected to charge. i can still boot in download mode and recovery without plugging it in but not into the custom rom. as soon as i deconnect it (when using the custom rom) it reboots and gets stuck at the samsung screen.
that wouldn't be that bad if the usb connection was not dead as well. that happened a few month ago allready. i tried to connect it via odin, kies and smartswitch in download mode and recovery. but nothing. i also reinstalled the drivers via kies. i also flashed "ressurection remix oreo" to check wether it works with different roms but it didnt.
does anybody here have an idea what i can do to make the usb connection work? or is there a possibility to flash the firmware without it?
device SM-320FL
Android 8.1.0
TWRP 3.2.3-0
Bootloader: 0x030c (?)
EDIT: i guess this thread is supposed to be in the device-forum but i'm not able to move it myself am i?
EDIT: the problem turned out to be broken cables. i tried with a third one and usb is working fine.
Hi, I own a samsung galaxy s7, running Superman-ROM and using TWRP recovery. Recently I was mucking around with some friends and decided it would be a good idea to install a ****ty game as firmware (through Lucky Patcher). After asking me to reboot I did and it is now soft-bricked. It says "custom binary blocked by FRP lock". The problem is that both OEM unlock & USB debugging were off, so I cannot connect to my PC. The only thing I can access is Download mode, but I am not able to enter recovery mode to wipe it. I have tried reinstalling both TWRP & Samsung's default ROM through Samsung Odin (I do have USB drivers) and they both fail. Is this fixeable or would I have to give it to a professional?
Thanks in advance, Lucien
This once happened to me and I had to end up wiping everything on my phone with Odin.