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
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.
Hi. I have a Galaxy Note 10.1 tablet. I went to turn it on this morning and it for stuck in a boot loop. all it says it "Samsung Galaxy Note 10.1" and then shuts off. I try and into recovery and the TWRP title screen shows up and then immediately turns off. What should I do?
Try flashing stock rom through odin
Sent from my GT-I9100 using xda app-developers app
raducux said:
Try flashing stock rom through odin
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Is the Stock Rom the same thing as a Stock Recovery? If not, where would I find a Stock Rom and how do I install it?
kyleschepis said:
Is the Stock Rom the same thing as a Stock Recovery? If not, where would I find a Stock Rom and how do I install it?
Click to expand...
Click to collapse
Answer no but it includes stock everything .
Stock roms on the forum or sammobile.com samsung-updates .com .
Would flashing the stock ROM erase everything from the tablet? Is there a way to retrieve the files from it in download mode?
Bootloop - No Recovery Mode
kyleschepis said:
Would flashing the stock ROM erase everything from the tablet? Is there a way to retrieve the files from it in download mode?
Click to expand...
Click to collapse
Hi all,
I have a similar issue to kyleschepis.
I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started a week ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But last week, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I AM able to get into the Odin download mode but CANNOT get into recovery mode no matter what I do.
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00 _user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. The installation in Odin seems to run fine - I get the "PASS" message at the end of the prodedure. But the power + volume up combination does NOT get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for a full week now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Boot loop (soft brick)
robb-x said:
Hi all,
I have a similar issue to kyleschepis.
I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started a week ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But last week, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I AM able to get into the Odin download mode but CANNOT get into recovery mode no matter what I do.
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00 _user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. The installation in Odin seems to run fine - I get the "PASS" message at the end of the prodedure. But the power + volume up combination does NOT get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for a full week now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
I am having near the same experience as rob-x. I have had problems with some files on my SD card missing or arbitrarily renamed. I had the tab on charge and the next day it was looping through the boot screen,
I have tried flashing the firmware with Odin and also CWM, without results. I am unable to boot into recovery, only into download.
Also the only way to turn the machine off is to plug it in to charger then hold the on/off until the screen goes black.
My next plan is to flash the PIT and the firmware at the same time,
tcm13 said:
I am having near the same experience as rob-x. I have had problems with some files on my SD card missing or arbitrarily renamed. I had the tab on charge and the next day it was looping through the boot screen,
I have tried flashing the firmware with Odin and also CWM, without results. I am unable to boot into recovery, only into download.
Also the only way to turn the machine off is to plug it in to charger then hold the on/off until the screen goes black.
My next plan is to flash the PIT and the firmware at the same time,
Click to expand...
Click to collapse
Hi tcm13,
Three weeks later and I am still none the wiser with my Note. It is still caught in the bootloop.
I can tell you that I have tried flashing the PIT and the stock firmware, but in my case it did not help. You are welcome to try. It didn't get any worse, but it did not get any better either. I have also tried flashing the stock German and UK ROMs for the GT-N8010 (mine is the US GT-N8013) with or without the PIT. These both fail fairly early on in the flashing process. But the behavior of the device does not change. Still the same bootloop, stuck at the same place.
Sorry for the bad news. Like I said, in my case flashing the PIT didn't help, but I have read on forums that people did have success with it. So it is definitely worth trying. It doesn't make things any worse, any way.
Let me know how it goes for you.
Ditto, same issue. I can flash a .tar file (I have tried CF-Auto and TRWP) in download mode using Odin but can't get the device into recovery mode.
It is just boot looping to the Samsung GALAXY Note 10.1 screen every 15-20 seconds. Can't even turn the damn thing off to save battery!!
Topazzar said:
Ditto, same issue. I can flash a .tar file (I have tried CF-Auto and TRWP) in download mode using Odin but can't get the device into recovery mode.
It is just boot looping to the Samsung GALAXY Note 10.1 screen every 15-20 seconds. Can't even turn the damn thing off to save battery!!
Click to expand...
Click to collapse
Hi,
I have been able to turn the device off by plugging it in to charge then hold the on/off down until the screen goes dark.
---------- Post added at 08:59 PM ---------- Previous post was at 08:40 PM ----------
robb-x said:
Hi tcm13,
Three weeks later and I am still none the wiser with my Note. It is still caught in the bootloop.
I can tell you that I have tried flashing the PIT and the stock firmware, but in my case it did not help. You are welcome to try. It didn't get any worse, but it did not get any better either. I have also tried flashing the stock German and UK ROMs for the GT-N8010 (mine is the US GT-N8013) with or without the PIT. These both fail fairly early on in the flashing process. But the behavior of the device does not change. Still the same bootloop, stuck at the same place.
Sorry for the bad news. Like I said, in my case flashing the PIT didn't help, but I have read on forums that people did have success with it. So it is definitely worth trying. It doesn't make things any worse, any way.
Let me know how it goes for you.
Click to expand...
Click to collapse
Hi,
I have tried all and every PIT, ROM custom or not, and various recoveries without success.
I presume, as opposed to assume that it is a hardware fault.
Faulty SD card reading, random freezing, crashes and long charging cycles lead me to surmise some basic fault is the cause, also seeing that my device is not the only one to have been stricken.
I have now surrendered my system to the "tender mercies" of the appointed Samsung technicians as my device is still under warranty.
I dislike admitting defeat but I have gone as far as I can without picking up a screwdriver.
Let hear if you have found another alternative.
Hi,
Could you let us know how it went after the service? I had similar problems with my Note 10.1 (n8013) but it seems to have gone away by itself. Had to let the battery die a couple of times a couple of times though, but now I'm running IOKP without a hitch. . Would really like to know what the Samsung service people diagnosed...
Bump
mowgli_writes said:
Hi,
Could you let us know how it went after the service? I had similar problems with my Note 10.1 (n8013) but it seems to have gone away by itself. Had to let the battery die a couple of times a couple of times though, but now I'm running IOKP without a hitch. . Would really like to know what the Samsung service people diagnosed...
Click to expand...
Click to collapse
BUMP : Same behavior here. I was able to upload an older stock ROM via odin but upon rebooting, the behavior persists and I still cannot boot into recovery mode. It would help tremendously if Samsung would pull their heads out of the asses and provide links to firmware but I cannot find an official source for any US version of the Note 10.1 (gt-n8013eavxar).
Side note to the origin of the problem. The tablet I am attempting to recover had never been rooted so I'm ruling out operator error as to how the device became so jammed up.
robb-x said:
Hi all,
I have a similar issue to kyleschepis.
I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started a week ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But last week, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I AM able to get into the Odin download mode but CANNOT get into recovery mode no matter what I do.
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00 _user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. The installation in Odin seems to run fine - I get the "PASS" message at the end of the prodedure. But the power + volume up combination does NOT get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for a full week now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
bro have you found the solution ?
Boot into recovery
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
harrisyn said:
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
Click to expand...
Click to collapse
Thanks a lot for stupid it seams I did that and oala CWM XD.
Im resurrecting my tab from a hard brick so entering recovery is a greate deal for me a few ours ago i could only enter in download mode no at least i have a boot loop and recovery.
It´s factory reset and cache whipe time to get rid of the boot loop
rodrigofantino said:
Thanks a lot for stupid it seams I did that and oala CWM XD.
Im resurrecting my tab from a hard brick so entering recovery is a greate deal for me a few ours ago i could only enter in download mode no at least i have a boot loop and recovery.
It´s factory reset and cache whipe time to get rid of the boot loop
Click to expand...
Click to collapse
great ☺
Envoyé de mon GT-N8010 en utilisant Tapatalk
harrisyn said:
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
Click to expand...
Click to collapse
i tried your way its shows green android logo with blue lines in centre and then next screen it shows is android lying down with its stomach open and red exclamation.
what does that mean >?
Hi.
I'm having a similar issue wih my n8010
Im am unable to boot the tablet, its stuck on the samsung logo, and here it stays untill it runs out of battery.
I cannot enter recovery mode, it will not get past the samsung logo. (I have tried holding down the vollme up key and releasing the power key when the logo apears) Nothing works.
I am able to get into Download mode, and the tablet is also reconized by Odin, But when i try to flash a stock firmware downloaded from Sammobile, It right away sais Fail!
This is the output from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the tablet i get: SW REV. Invalid magic string
I have tried to flash a new recovery using Heimdall and that i can do with no errors, but i canot enter recovery mode.
Am i tryind to flash the wrong firmware fra Sammobile?
Hope that someone can help me to solve this.
NOTE: Before this went wrong i had CM 10.2 Nightly on the tablet, but could not play any videos, so i want to go back to stock. So i connected the tablet to odin and tried to flash the firmware from Sammobile, but it failed, and now, this is where im at.
EDIT: I got the problem solved.. I tried various stock roms from Sammobile, different countries and regions, ended up with a stockrom pointing at Netherlands even tho i live in Denmark, but that one flashed with no errors, and i was able to get past the "Samsung Galaxy 10.1 ) logo, but got stuck at the "Samsung" logo. But i was now able to enter revovery mode (Power + Vol Up) and do a full wipe and the reboot. Now everything works.
A littel bonus question i would like someone to help me understand. When i want to download a Stock Rom from Sammobile, what should i choose? I live in Denmark, but there is no option for that when i am to selct a download from Sammobile.
Another question, can i Select a 4.1.2 firmware and flash that on my Tablet, now that i have the 4.4.2 installed? I hate the new KitKat placement of buttons on the tablet.. Back button in the middle where you cant reach it with your thumb and the drop down menus are a pain.. i hate it.
Will i for example be able to flash this rom : http://forum.xda-developers.com/showthread.php?t=2119547
Or are there some problems with me having 4.4.2 now, and want to go back to 4.1.2?
Please advise.
Thank you in advance.
I am glad it helped several members but unfortunately not me and probably also others with the same issue as ROBX described.
I think it has something to do with hardware, original cable etc. tomorrow I have it flashed at the Samsung shop and see if it works there.
harrisyn said:
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
Click to expand...
Click to collapse
Jrod236 said:
EDIT: I got the problem solved.. I tried various stock roms from Sammobile, different countries and regions, ended up with a stockrom pointing at Netherlands even tho i live in Denmark, but that one flashed with no errors, and i was able to get past the "Samsung Galaxy 10.1 ) logo, but got stuck at the "Samsung" logo. But i was now able to enter revovery mode (Power + Vol Up) and do a full wipe and the reboot. Now everything works.
Click to expand...
Click to collapse
Any one tray this and solve the problem?
Sent from my SM-T805 using XDA Premium HD app
Hi,
I recently tried to root a friend's SM-G900P Samsung Galaxy S5 using Odin v3.07, I used CF-Auto-Root.tar
I got the message: Remain Port .... 0
then: All threads completed. (succeed 1/failed 0)
<ID> Added.
The phone rebooted to this:
Recovery Booting (in blue)
Recovery is not seandroid enforcing (in red)
Set warranty bit: recovery (in yellow)
And a samsung s5 logo
The computer does not recognize the device, so I cant use Odin to use something like philz recovery.
I also cant access download mode or access recovery.
Is there any possible thing I can do?
Is the phone bricked?
wamhax said:
Hi,
I recently tried to root a friend's SM-G900P Samsung Galaxy S5 using Odin v3.07, I used CF-Auto-Root.tar
I got the message: Remain Port .... 0
then: All threads completed. (succeed 1/failed 0)
<ID> Added.
The phone rebooted to this:
Recovery Booting (in blue)
Recovery is not seandroid enforcing (in red)
Set warranty bit: recovery (in yellow)
And a samsung s5 logo
The computer does not recognize the device, so I cant use Odin to use something like philz recovery.
I also cant access download mode or access recovery.
Is there any possible thing I can do?
Is the phone bricked?
Click to expand...
Click to collapse
If you really can't get into download mode, that may be a problem.
Try this:
Unplug from computer
Reboot computer
Pull battery on phone
Put battery back and try Volume DOWN-HOME-POWER. If you get the Download Mode, press Volume UP
Make sure you are using the right CF-Autoroot: http://download.chainfire.eu/408/CF-Root/CF-Auto-Root/CF-Auto-Root-kltespr-kltespr-smg900p.zip (This is for the Sprint S5 on Lollipop.
Hook up phone via USB, make sure you get a blue COM:ID in the upper left side of Odin
In odin, the downloaded file goes into the PDA or AP slot (depending on which version of Odin you're using.
Click start.
Good luck
Dude, thank you.
I was having a heart attack, because this is not my phone. I don't know what was causing issues with the device. I was so wound up, that sometimes a simple restart can fix everything. On top of it the device is now rooted. Thank you!
Okay, so I started onto the dark path of trying to root my phone and I thought it wouldn't be too hard. I am fairly tech savvy, but I have never tried rooting before.
I got my phone successfully rooted using SpaceX-Kernel. That wasn't a problem. However I started trying to use xposed to start adding modules, and I have been working on this for the last 6 hours and I am tired and confused.
My phone started to stop on the Samsung screen and would flash up and down. I was able to turn it off with Power + Volume Down, but it wouldn't actually stay down it would try to reboot after that. I realised I could get to the TeamWin screen if I pressed Volume up + Home + Power quickly enough after the forced off, and I wiped the caches to see if that would help. It did not.
**Then I did something stupid. I did a reformat (which I thought at the time would be a like a factory reset deleting all my apps/files/other stuff) also unencrypted my phone.
**So, finally I am trying to reset it by reinstalling the firmware of 5.1.1 (mostly just cause that's what I have on my computer), but I am getting fails using Odin. The error I am getting currently is
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
How am I supposed to deal with this? My phone also is randomly not recognised by the computer even though I am sure I have downloaded the drivers for this phone.
If anyone could give me any kind of indication on what I should try next I would be so happy. I know there are other threads that are similar to this, but most of what I have been reading to to flash the firmware onto the phone which should give it a fresh restart. ** Are next to the important information.
I have also tripped the knox security. So my warranty is void. I also know that can affect booting. Thanks
You've got it in download mode?
Sent from my SM-G920W8 using Tapatalk
Try another USB cable and another USB port. ODIN is known for failing for stupid reasons, cheap usb cables being one of the top reasons. As a last resort try ODIN on another pc.
Also you should ODIN the latest stock image, sometimes using a version older than you have installed on the phone will fail.