Database Info

Listening to music - Bam constant reboot loop

I'm rooted, permanently sideloaded and running unhelpful kernel. My phone has been fine other than getting progressively slower. I also have build 1007. Today I was listening to music and my antenna disabled with no signal. I tried rebooting after flight mode on/off didn't work and BAM I can't get past the Galaxy S screen. I can get into clockwordmod loader but I'm not sure what to do from here. I did a backup of my current rom.
Ideally I just want to be able to mount my internal sdcard and grab my pictures then just flash back to stock or upgrade to a new ROM, something I have yet to do. My phone doesn't seem to want to mount, any help?

Try to restore your backup in clockwork
You will not lose your pictures with a odin flash unless you master clear

Going to restore my backup from today and then try one from Jan 30th if that doesn't work.
I downloaded Odin to get ready just incase. When I enter download mode through clockwork and fire up Odin nothing seems to happen when I click start, just "All threads completed. 0 succeed 0 failed"

MikalCarbine said:
Going to restore my backup from today and then try one from Jan 30th if that doesn't work.
I downloaded Odin to get ready just incase. When I enter download mode through clockwork and fire up Odin nothing seems to happen when I click start, just "All threads completed. 0 succeed 0 failed"
Click to expand...
Click to collapse
After you enter download mode, plug in the phone. You should see on of the fields in Odin turn yellow, this means it picked up the phone. If it doesn't turn yellow you may need to install the drivers.

Odin should be open first
Pull battery, sim, and ext sd
Hold volume up and down
Plug in usb
Odin should have field turn orange
Click start

[Q] Serenity KK4 questions

So i have been looking through the pages, and cannot find anything pertaining to what i am looking for. I am new to ROM's and i cant find a explanation on how to install it, or flash it rather. I saw the part that said installation which has:
- Make sure you're on Gingerbread I897 Bootloaders
- If you are on EXT4, convert back to RFS (disable lagfix)
- Flash a CWM KK4 kernel
- Flash serenity zip file
- First boot takes some time
My phone is a Captivate rooted, and have tried installing roms with ROM manager, to no success because it says to reboot into ClockworkRecovery, but i have followed every instruction in the book to get to CWR but it still takes me to the stock recovery menu.
I have been at this for about two weeks looking at forums and everything to figure out how to do it on my own, but i really have given up because i have no clue.
Thanks in advanced for any advice.

So rooted & stock? Some thoughts
You need Samsung usb drivers.
adb for PC command line controls:
http://www.xda-developers.com/android/adb-easy-tutorial/
In Settings>Applications>Development toggle USB debugging on.
Use ODIN [1.85] once you put it in Download mode:
http://forum.xda-developers.com/showthread.php?t=1365805
Download mode: use adb command: adb reboot download
Bootloaders via ODIN [has its own odin copy]:
http://forum.xda-developers.com/showthread.php?t=1129821
Flash a tar of Corn 6.0.3 kernel via ODIN. This comes with its own CWM version:
http://forum.xda-developers.com/showthread.php?t=1294477
Always have a way to get back to stock if things go wrong:
http://rum.xda-developers.com/showthread.php?t=731989

Ok, so got it into download mode.
I open ODIN, but im not exactly sure what to do from there, so i tried opening ODIN then using the bootloaders.
I ran the bootloader program, went through that, it said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
dont know if im doing something out of order, but clicking start in ODIN itself doesnt do anything.
Thanks in advanced!

Buckli39 said:
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
sequence:
1.Run the Odin with built in bootloader code.
2. Phone in DL mode
3. Attach to USB. Odin will then get a yellow box indicating some com port.
Yellow com port box or it will do nothing! Perhaps you ran Odin with the phone already in DL mode & usb connected?
Sequence matters: If you used adb to get into DL then with Odin already open it should recognize it [20 seconds?]. I use a jig from MobileTechVideos $7 to get into DL, only then I usb connect to PC with Odin already running/waiting. Using adb is functionally equivalent. As the phone reboots it is not actually "connected". Once the reboot to DL happens the connection to PC is restored.
My Odin/Bootloader one-click program reports: " <ID:0/012> Added " with a yellow box with " 0:[COM12] "
4. choose Start. A green bar progress will indicate the 'progress'. It will reboot the phone.
5. You can close Odin after the "all thread completed", it will indicate a reset. Safest to wait for the reset/reboot.
It should have read: <OSM> All threads completed. (succeed 1 / failed 0)
This is just as directed on the link to the Bootloader one-click program [odin variant]
You only need the basic Odin[1.85] when flashing the Corn 6.03 tar file. In theory if one had the tar file for the bootloaders one could use the basic Odin for it, but here the bootloaders are already packaged in with an Odin executable.

okay, so i did exactly the sequence you told me, run odin/bootloader, phone into DL, then connect to usb.
I do not get the yellow com port until after i turn my phone off, out of DL mode, and back into reg mode. then it recognized it and says "Added!". i go back into DL mode and it says its disconnected ( i also waited 20 min just to make sure it didnt come back as added )
And you had said "Once the reboot to DL happens the connection to PC is restored." it is exactly the opposite, once it reboots to DL the connection seems to be severed.
If i hit start when it is present and not in DL mode but has the yellow com, it just fails anyway.

Buckli39 said:
I do not get the yellow com port until after i turn my phone off, out of DL mode, and back into reg mode. then it recognized it and says "Added!".
And you had said "Once the reboot to DL happens the connection to PC is restored." it is exactly the opposite, once it reboots to DL the connection seems to be severed.
If i hit start when it is present and not in DL mode but has the yellow com, it just fails anyway.
Click to expand...
Click to collapse
Connecting when in Normal use mode will always have Odin responding Yellow/ComPort. And yes Start will do nothing unless in DL.
I tested my sequence. Odin/Bootloaders running, PC: adb reboot download, and it did fine giving YellowBox/ComPort. Never usb disconnecting physically, only functionally as it reboots. So I dont know. I do know that sometime DL mode goes stale. Phone unresponsive if one does not take fairly prompt action. That is I cannot put in DL and put aside for 5min. If I had to do this then I would need reboot into DL again.
For the Kernel you can transfer the Corn6.03 [zip CWM version] file to some directory in the internal SD card [ not the one inserted by "you"]
Then you could use "adb reboot recovery" but the stock recovery is very limited, and it wont let you flash the kernel in recovery. Unless you first save a CWMR 3 file as update.zip on the internal sd. This was how you rooted? There is some reason stock recovery forces you to do the flash from update twice, the second time puts you in the CMW3 program[green menu, no longer blue?] where you can then flash the kernel. Look for old links/threads to the old CWM zip file.
Let me get back to you on the BLs & perhaps a link to the old CWM3.

i will keep on trying to get the DL mode to be connected, and I rooted via the super one click root program, was told it would be the easiest and fastest way
Okay so i was digging around and found some reasons why it wasnt reading my device, and i got it. i got odin to flash the file, waiting for it to start my phone back on, atm it is stuck on the att screen. i shall wait a bit and report

okay i have let it attempt to reboot by itself for about 20 minutes, all it is doing is loading to the att screen, staying there for a sec, then the screen goes black, the the att screen pops up again.. it has just been repeating that since my last post

so something messed up. i wanted functionality until you could help me out, so i was doing the last link you sent me to restore it to stock. Did that, and now it wont even turn on or get into DL mode, the only thing i can get onto the phone is:
RST_STAT =0x1
PMIC_IRQ1 =0x3c
PMIC_IRQ2 =0x0
PMIC_IRQ3 =0x0
PMIC_IRQ4 =0x0
PMIC_STATUS1 =0xc0
PMIC_STATUS2 =0x2c
Moden booting...
End modem booting.
Now start usb upload.
*
okay maybe i should wait to post, i finally got it into DL mode and installed stock rom

Buckli39 said:
...
okay maybe i should wait to post, i finally got it into DL mode and installed stock rom
Click to expand...
Click to collapse
DL mode can get scary. So many threads warn the user "I'm not responsible for your bricking your phone". Early on I spent a couple of days stuck, "soft bricked". Here too I only tell you what has worked and still works for me.
As you used the link/thread for flashing to stock that I listed perhaps you will have an easier time now.
Then select Settings >> Applications >> Development and tick "on" USB debugging [must disconnect usb cable first]
Now perhaps you can do the Odin work. I looked for where [link/thread] I had found it to no avail so I attach BLs and what I use for CWM3 and rooting. Until now I had preferred passing a thread where you could use others vetted sharing, rather than 'just my copies' of these. BL file can be used in normal Odin. The other two should be named update.zip and placed in the internal SD and flashed in Recovery. [adb reboot recovery].
On to Corn6.3 [CWM safer?] and Serenity 6.0 and subsequent & extras in Recovery.

[Q] tab 2 7.0 P3110 stuck at Samsung Tab 2 7.0 screen unable to boot to recovery

Please can you help I bought this samsung tab 2 7.0 P3110 with it only powering on to the samsung tab 2 7.0 logo screen.
I am unable to get to recovery screen using the power and the vol up button all this does is power it off even if I hold for over one minute.
I can get to the download screen (power and vol down doing so is easy as it works) I have been able to use odin (failed many times) and download firmwares.
Last night I was able to download and gain a pass in Odin for CF-Auto-Root-espressowifi-espressowifixx-gtp3110 this I ran fist then 4.1.1 P3110XXCLK7_P3110OXACLK7_BTU. the problem after that is when odin tells it to reboot it hangs at the logo screen everytime. I have tried without the reboot and reboot manually it staill hangs.
is it a bootloader problem? corrupted partition? I think it needs the whole boot process reinstalled or rewritten if someone knows how
I am not looking for a custom rom All i want it to do is to power on into the stock recovery and to power on into the sofware by using something that works either by reformat or re partition the tab to get that part of the tab working before looking at firmware. sometime I have seen write fail when in odin.
simple instructions for how to get it back is all I am looking for.
I have browsed your site and watched youtube for hours no light at the end of the tunnel
thanks in advance for your help

tab 2 7.0 P3110 stuck at Samsung Tab 2 7.0 screen unable to boot to recovery
tab2noob said:
Please can you help I bought this samsung tab 2 7.0 P3110 with it only powering on to the samsung tab 2 7.0 logo screen.
I am unable to get to recovery screen using the power and the vol up button all this does is power it off even if I hold for over one minute.
I can get to the download screen (power and vol down doing so is easy as it works) I have been able to use odin (failed many times) and download firmwares.
Last night I was able to download and gain a pass in Odin for CF-Auto-Root-espressowifi-espressowifixx-gtp3110 this I ran fist then 4.1.1 P3110XXCLK7_P3110OXACLK7_BTU. the problem after that is when odin tells it to reboot it hangs at the logo screen everytime. I have tried without the reboot and reboot manually it staill hangs.
is it a bootloader problem? corrupted partition? I think it needs the whole boot process reinstalled or rewritten if someone knows how
I am not looking for a custom rom All i want it to do is to power on into the stock recovery and to power on into the sofware by using something that works either by reformat or re partition the tab to get that part of the tab working before looking at firmware. sometime I have seen write fail when in odin.
simple instructions for how to get it back is all I am looking for.
I have browsed your site and watched youtube for hours no light at the end of the tunnel
thanks in advance for your help
Click to expand...
Click to collapse
forgot to add the above was using Odin 3.07 and laptop is win 7. did try pc on xp and failed loads.

tab2noob said:
forgot to add the above was using Odin 3.07 and laptop is win 7. did try pc on xp and failed loads.
Click to expand...
Click to collapse
I am not too sure about the partition/repartition thing, but I think you should use said Odin to flash CWM 6.0.45. It doesn't mean you have to install a ROM, but try attempting a factory reset (at this point, not being able to boot up, you might need to use Cwm to create some sort of backup).
However, I suggest waiting until you receive more than one reply, as I may be wrong

For going into recovery, try holding the buttons at the same time. When you see the first samsung bootscreen, release the power button and continue to hold the other button.

jccarbon said:
I am not too sure about the partition/repartition thing, but I think you should use said Odin to flash CWM 6.0.45. It doesn't mean you have to install a ROM, but try attempting a factory reset (at this point, not being able to boot up, you might need to use Cwm to create some sort of backup).
However, I suggest waiting until you receive more than one reply, as I may be wrong
Click to expand...
Click to collapse
Hi thanks for your suggestion. I am thinking until I can get to the recovery screen putting on firmware isnt getting tab into recovery

tab 2 7.0 P3110 unable to boot into recovery or past samsung tab 2 7.0 screen
swrght13 said:
For going into recovery, try holding the buttons at the same time. When you see the first samsung bootscreen, release the power button and continue to hold the other button.
Click to expand...
Click to collapse
Thanks for your reply I probably didnt explain myself. I have always been holding down the power and the vol up button at the same time.
I have access to another tab 2 7.0 P3110 that is working in stock mode (a trusted friend allowed me to check how to get to the download and recovery screens ) I have noted the time it takes to boot into recovery from power off and from the samsung tab 2 7.0 screen and also going into recovery from the download screen. mine dont do any it just goes to the download screen or power off. the screen is black no life lol.
just a thought I dont think it actually powers off although the screen is black because I left it for over 10 hours I felt the back and it was warm battery was low as I couldnt power it on it was fully charged when I tried to get into recovery 10 hours earlier.
will try to explain one step at a time
because of the problem I am thinking I have to start from scratch instead of jumping into the middle of what is already possibly corrupt files. (I have probably built a house out of my bricked Tab)
1. what do I have to do to get a totally clean 8gb space for recovery and firmware to go onto?
2. what has to be installed via Odin to get to recovery (can recovery be tested on its own before the firmware is installed)
3. I have tried a PIT file before all I had was 0 completed and 0 failed???? is that good or bad? didnt see a PASS at the top left. did I have the correct PIT file?
4. are PIT files dependant on which version of Odin I run or recovery or firmware? if they are can someone point my in the right direction for everything that is compatible with each other
I read on this forum of splitting the MD5 files into bootloader pit by extracting it twice I tried that in winRAR I only had one chance it left a tar.md5 file which is the file I used to upload in Odin.
Thanks again for everyones help

2. You need to install Clockwork Mod Recovery version 6.0.4.5. It can be found in the development forum, made by Android-Andi
As for the rest, I'm not familiar

jccarbon said:
2. You need to install Clockwork Mod Recovery version 6.0.4.5. It can be found in the development forum, made by Android-Andi
As for the rest, I'm not familiar
Click to expand...
Click to collapse
I have tried the above it passes and reboots to samsung tab 2 7.0 and thats as far as it goes. I waited 15 minutes no change tried the usual to get into recovery not happening. went back to download screen and ran gtab2P311x8g.pit below is a snippet of the important bits from Odin output screen bottom left I had auto reboot, repartition and f reset time all selected
set pit file
get pit for mapping
theres no pit for mapping
all threads completed succeed 0 failed 1
I have also ran philz touch 6.008 universal root also pass with reboot and without reboot
all tar md5 files installs and with a pass reboots but no blue bar on the bottom of download screen and no access to recovery screen.
I think the internal 8gb memory needs to be wiped and partitioned.
maybe someone can tell me how to extract all the files that are needed to get the os onto the tab from the tar md5 file like the partition, recovery and bootloader etc and the order of installing in Odin

tab2noob said:
I have tried the above it passes and reboots to samsung tab 2 7.0 and thats as far as it goes. I waited 15 minutes no change tried the usual to get into recovery not happening. went back to download screen and ran gtab2P311x8g.pit below is a snippet of the important bits from Odin output screen bottom left I had auto reboot, repartition and f reset time all selected
set pit file
get pit for mapping
theres no pit for mapping
all threads completed succeed 0 failed 1
I have also ran philz touch 6.008 universal root also pass with reboot and without reboot
all tar md5 files installs and with a pass reboots but no blue bar on the bottom of download screen and no access to recovery screen.
I think the internal 8gb memory needs to be wiped and partitioned.
maybe someone can tell me how to extract all the files that are needed to get the os onto the tab from the tar md5 file like the partition, recovery and bootloader etc and the order of installing in Odin
Click to expand...
Click to collapse
Help needed anybody somebody.
I have tried with Heimdall and ADB not working. Now back to Odin

tab2noob said:
Help needed anybody somebody.
I have tried with Heimdall and ADB not working. Now back to Odin
Click to expand...
Click to collapse
Am now running with Odin 3.07 and CF Auto Root espressowifi....md5
it all run through with pass at the end. It doesnt show the blue line running across the bottom of the download screen on the tab. I have never seen this in all the 20 + times I have tried with Odin. All the you tube vids show this as part of the installation process. If I have auto reboot on the tab reboots when Odin send the request to the tab to reset.

tab2noob said:
Am now running with Odin 3.07 and CF Auto Root espressowifi....md5
it all run through with pass at the end. It doesnt show the blue line running across the bottom of the download screen on the tab. I have never seen this in all the 20 + times I have tried with Odin. All the you tube vids show this as part of the installation process. If I have auto reboot on the tab reboots when Odin send the request to the tab to reset.
Click to expand...
Click to collapse
ADB devices does not attach itself to the tab. ADB just says its waiting for device when in download mode and fastboot returns nothing. I think its because I am unable to run USB debugging due to no firmware.
Is there a way to get into the tab if theres no os?
I have taken the back off thinking the volume or power key might be faulty, there not. Pressing the power button and the up vol does nothing apart from putting the tab in a reboot loop or power off. I can get into download mode no prob. I have tried pressing the up and down vol keys with the power button to try to put the tab into shock no change.

I was searching the forum for a similar problem as mine.
And you have the exact same problem as I do.
At some point when I used Odin 3.07 and flashing an official firmware from samsung I got past the first boot screen.
But right after that it shows an android robot with a dedacahedron in front of it showing an animation and a loading bar.
Soon I discovered the next loop, since this animation would loop over and over again.
Now I waited for the battery to run out and charge it up till its full.
By the way:
When the tablet is off and I plug it in with the original cable and charger the tablet shows the battery icon, but it doesnt show the charging animation. The battery icon shows a "waiting" circle. So I cant really see if its charging or not.
Have you had any progress?
Would be so awesome to fix this, this galaxy tab is not mine. Its my brothers and I broke it by trying to root it and install cwm xD

Eureka
Dude I totally got into recovery mode.
I downloaded CWM (clockwordmod) 6.0.1.1 SuperSU 0.96 Busybox 1.2.0.2 md5 file.
You can find it here:
http://forum.xda-developers.com/showthread.php?t=1880010
In the first post there are attached files.
The right one is in that list.
Then I tried flashing it with Odin3 Version 3.09
I googled for a newer version of Odin and found this version 3.09
First time rebooting didnt work.
But the seccond time I succesfully got into CWM recovery.
Hope this works for you 2!
Cheers.

Amlan90 said:
Dude I totally got into recovery mode.
I downloaded CWM (clockwordmod) 6.0.1.1 SuperSU 0.96 Busybox 1.2.0.2 md5 file.
You can find it here:
http://forum.xda-developers.com/showthread.php?t=1880010
In the first post there are attached files.
The right one is in that list.
Then I tried flashing it with Odin3 Version 3.09
I googled for a newer version of Odin and found this version 3.09
First time rebooting didnt work.
But the seccond time I succesfully got into CWM recovery.
Hope this works for you 2!
Cheers.
Click to expand...
Click to collapse
Thanks for the detailed guide and everyone's responses.. I was SOL also and re-flashing CWM helped get me back to where I can flash again.

Samsung galaxy S6: Recovery is not seandroid enforcing

I tried to root my sgs6 with an CF auto root. This didn't work because after the first reboot of my Phone I got the message:
"Recovery is not seandroid enforcing"
I've been looking on the internet and have seen several options which didn't work, including:
- Getting into recovery mode (home + on/of button + volume UP). This doesn't work somehow.
- Try to install stock firmware.
- Retry the same root
- Try a different root.
Also; connecting via Kies/Smart Switch gives me the reply that the S/N isn't valid. This however, is not true.
The biggest problem that I seem to have is connecting my phone to my computer properly. And I can't turn on 'USB debugging' anymore (I turned it on when I started with my root).
So maybe my first question is: How can I get my phone to connect with my computer properly?
And after that; How can I fix the failed root.
Additional info:
Model name: SM-G920F
Android 5.1.1. before I tried to root my phone.
If additional information is required, please let me know.
Thanks in advance.

Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/galaxy-s6/help
The experts there may be able to help. Good luck.

Not an expert, but I've got the same message in the top left corner on the bootscreen after installed TWRP trough Odin and flashing adam-kernel.
Does not interfere with my phone working though. Even SmartSwitch still recognises it. Maybe wrong version of autoroot?

We found the solution:
We downloaded the original stock firmware and installed it through odin. Some things we encountered during the solving:
- It failed on the hidden.img
- We had to extract that file and load it seperatly through odin.
At that point the phone kept resetting, but after removing the cable from the computer and charging it with the normal charger it booted like normal again. The android sign (which we saw before but the phone went rebooted all the time) stayed in the screen and after a couple of minutes it started installing.
After 10-15 minutes the phone worked again!
Tnxs for your efforts!

Stuck at Boot Logo and no Recovery Mode

Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated

Hi, I too have similar issue. Would like to know how you got it resolved.

tanzeeb210 said:
Hi, I too have similar issue. Would like to know how you got it resolved.
Click to expand...
Click to collapse
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue

oscar_ferreiro said:
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
Click to expand...
Click to collapse
its seems like battery issue more for me than the board!
you should replace or disconect her first before selling the device... could worth the try...

oscar_ferreiro said:
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Click to expand...
Click to collapse
Same issue here, any idea to solve that? (I'm Brazilian, sorry for some typing wrong)
I don't opened the device (yet), but if is a battery issue, someone tried to fix?
My device is SM-G920I, i tried to flash this FW: G920IDVU3FQD1_G920IXSA3FQC3_XSA without sucess, i will try with a "pit" file that i've found here on XDA and update here, but until the moment, the problem remains
Update: The PIT file does not solved the problem, after this I decided to open the device and swap the battery, but the problem remained, i'm buying a new board today, i think this board can't be saved

I've had similar problem with my Note4. It would sucessfuly apply firmware via Odin but refuse to boot. (tried multiple times)
I then did a flash via SmartSwitch (takes forever) but the phone worked again.

any update for this ? i have the same issue

Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Could someone please help!

bestfootie said:
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Click to expand...
Click to collapse
Had to come back and add on to my previous post - I sorted it. It was simply a driver issue... Make sure you download all the correct Samsung USB Drivers people if you're having similar issues...
I finally restored my Android to Stock Android (albeit the latest Android system 7.1).