Hello, I have Galaxy SII, SGH-I777 w/AT&T. When i turn on the phone i get black screen that says "Samsung Galaxy SII". I can't get passed this screen. The only other thing i could do is hold up/down volume & power button that takes me to a screen where i'm giving 2 options, continue or cancel. Click cancel, i'm back at black screen. Click continue it takes me to "ODIN MODE" and says downloading. No clue what it's downloading but it's stuck at this screen now. I'm not very techy w/phones, not sure if there's a simple solution. Phone is factory OS, i never installed anything outside of what AT&T pushed through software upgrades. Please help!
When you press continue and get the screen that says downloading, your phone is in download mode, which means it is ready to receive new firmware via Odin. Since all you can get is either download mode or the black screen when you use the button combination that should take you to recovery, that means that the firmware has become corrupt in some way. The only way to fix this is to re-flash the stock firmware using Odin. Please read through some of the guides that are linked in my signature. That should give you enough basic information to flash back to stock. If you have any questions along the way, feel free to ask them here.
I followed steps in this link - step #2. http://forum.xda-developers.com/showthread.php?p=18630030#post18630030. When i got to this step "Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot." - instead of PASS, i got a red FAIL. Seems like i can't even get it to to flash?
ytka98 said:
I followed steps in this link - step #2. http://forum.xda-developers.com/showthread.php?p=18630030#post18630030. When i got to this step "Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot." - instead of PASS, i got a red FAIL. Seems like i can't even get it to to flash?
Click to expand...
Click to collapse
Since you are running stock ROM & kernel, if you've ever performed a factory reset or wipe on your phone then you may have an emmc superbrick on your hands.
Sorry, i'm not very savvy with the tech language, what does this emmc superbrick mean? Is my phone done and i should get a new one?
ytka98 said:
Sorry, i'm not very savvy with the tech language, what does this emmc superbrick mean? Is my phone done and i should get a new one?
Click to expand...
Click to collapse
What AJ Newkirk says is a possibility, but not definite. If the phone does have damage to the emmc memory, then yes, you would probably have to get a new phone. I only ever saw two reports of emmc memory damage reported here, and only one of them was even close to conclusive, so the likelihood that your phone has some other issue is quite good.
Do you know what version was currently on the phone? The latest version pushed out by AT&T is 4.0.4 (UCLL6). Also, did you ever perform a wipe data/factory reset at any time? And finally, please describe the circumstances surrounding the phone's failure to boot. We'll try to help.
Thanks this helps! I want to say i had the latest version, to be honest i don't recall but deferentially 4.something. I did a factory wipe a few months ago and then restored back up from Klies. I really don't know how/why it failed, i was charging it and texting infrequently. at some point i looked at the phone and saw the black screen. that was pretty much the end of it.
ytka98 said:
Thanks this helps! I want to say i had the latest version, to be honest i don't recall but deferentially 4.something. I did a factory wipe a few months ago and then restored back up from Klies. I really don't know how/why it failed, i was charging it and texting infrequently. at some point i looked at the phone and saw the black screen. that was pretty much the end of it.
Click to expand...
Click to collapse
If you were flashing the UCKH7 downloaded from that guide, try flashing the latest 4.0.4 firmware instead. You can get it from the download repository.
Also, after you open Odin on your desktop, enter download mode the usual way: with the phone off, hold down vol+ and vol- (but not power) while plugging in the usb cable.
Am i doing this right? i downloaded and extracted I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 then used Odin3 check PDA and ran...got a FAIL and info below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Removed!!
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
ytka98 said:
Am i doing this right? i downloaded and extracted I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 then used Odin3 check PDA and ran...got a FAIL ...
Click to expand...
Click to collapse
Yes, but it appears that you may have Nand read/write corruption. (Not actual physical damage to the memory, but just corruption that needs to be reflashed.)
Here are the steps:
1) Flash kernel as PDA in Odin.
2) Flash the full stock package again as PDA in Odin.
If that is not successful then:
3) Download the Bootloader. Flash it as PDA in ODIN. Without ticking Re-Partitioning.
4) Flash kernel as PDA in Odin.
5) Flash the full stock package again as PDA in Odin.
I believe you can flash either a custom kernel or the stock kernel to clear the nand r/w corruption, but the problem is there are not many kernels packaged as tar available. I don't know whether flashing a Gingerbread kernel and then coming back with the ICS stock will clear the problem, but since the only kernel tar I know of is Gingerbread, why don't you try that first. If that doesn't work, I can package up an ICS kernel for you to use, but you'll need to be patient since I am pretty busy right now.
Download the Siyah 2.6.14 Gingerbread Kernel. From the line that says download, choose the TAR version. Flash that is step 1 and then the UCLL6 tar md5 package you used before in step 2.
Thanks so much for all the help. But at this point i can't even get past the initial black screen to and go into the "download" mode when i press up/down volume and power.
ytka98 said:
Thanks so much for all the help. But at this point i can't even get past the initial black screen to and go into the "download" mode when i press up/down volume and power.
Click to expand...
Click to collapse
Pressing all three buttons does not take you to download mode, it takes you into recovery mode. To enter download mode: (as I posted in a previous post in this thread) with the phone off, hold down vol+ and vol- (but not power) while plugging in the usb cable.
I ran SiyahKernel v2.6.14 TAR and got this response:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I then ran I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5.7z and got this response:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
i777 UCKH7 sbl.tar and this happens:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have the device already plugged in and in download mode when you start Odin? Try unplugging and plugging the device back in with Odin open.
Sent from my SGH-I777 using xda premium
Odin was open when i plugged the device in. I unplugged after every file I ran and plugged in again, without closing Odin.
Same boat
I am in the same boat. I will admit that i rooted my phone, and yes, selected a factory restore and now i am in this noob-predicament. Now I cant get the phone to communicate with ODIN. I have tried the jig with no avail. My phone displays:
"ODIN MODE
Product Name: SGH-I777
Custom Binary Download: YES (5 counts)
Current Binary: Custom"
When I use the Jig, the only display that changes is ODIN MODE changes to FACTORY MODE
Hoping for a cure...
Thanks for the help!!!
I had the same problem "can't open com port" until I used the original Samsung cable. I tried unsuccessfully for hours until I read that somewhere. With the right cable, it worked immediately.
Sent from my SGH-I777 using Tapatalk 2
ytka98 said:
Odin was open when i plugged the device in. I unplugged after every file I ran and plugged in again, without closing Odin.
Click to expand...
Click to collapse
To answer your earlier question, "Am I doing this right?" Look at the following complete instructions for Odin and follow as described. Attempt to flash the Siyah kernel tar (Step 1 in the previous post.)
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
Step 5) in this sequence will complete only if you have the correct drivers installed. Let us know how it goes, or which step is unable to complete.
If you get through all 10 steps and you still get the com port error, then try a different cable, or a different usb port, or even a different computer. If you have a desktop computer, you must use the usb port on the back, one that is connected directly to the motherboard.
Awesome, very detailed thank you very much, worked like a charm! i loaded "Siyah 2.6.14 Gingerbread Kernel file to PDA. Now i'm at step 10, i see green bar advanced, says "Kernel" right above it. Now i see the following message for the last 10 minutes:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sign "Kernel" above green turned red and now says "Fail"
ytka98 said:
Awesome, very detailed thank you very much, worked like a charm! i loaded "Siyah 2.6.14 Gingerbread Kernel file to PDA. Now i'm at step 10, i see green bar advanced, says "Kernel" right above it. Now all the buttons on the screen are grayed out and i see the following message for the last 10 minutes:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
The phone still says "downloading...do not turn off target!!" . what's my next step?
Click to expand...
Click to collapse
If your problem is nand r/w corruption, you need to get a kernel to flash successfully as the first step, before you flash the complete package. The flash should complete in under 10 minutes, so it sounds like it's not going to complete. I could put the 4.0.4 stock kernel into a tar for you to try to flash to see what happens. Before I do that though, I need to find some additional information about the boot loader flash. I probably won't be able to get back to you before tomorrow.
Related
I have a Samsung S3 on O2 (UK). Yesterday I got a system update notification and I downloaded and installed the update (it was quite big, about 300MB). There were no issues during the install and it restarted fine when it finished, however about an hour later the phone just restarted itself on its own (it was in my pocket) and then just kept looping the restart process over and over. I couldnt get the phone to get passed the logo screen. I tried removing the battery, sim card, etc but nothing helped. I read in a post here to try to use the "Recovery Mode" to restart the device. I did that and it worked, I was able to get the phone started again, but about half an hour later it did exactly the same thing but this time I couldn't get into recovery mode anymore! I read a few more posts on this forum and it looked like the update had soft bricked my phone. I could get the phone into download mode so I thought I would try using Odin to re-install the stock firmware. I followed the instructions on the post to the letter, downloaded the correct firmware from Samsung, installed the USB drivers for the phone but when I tried to use Odin it just said the the update failed. Now when I turn on the phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I have read a few posts on suggested work arounds but no matter what I try Odin always just gets stuck on "Nand Start Write!!!". I have tried re-installing the USB driver, using a different cable and even a diff computer but always the same.
Can anyone help? This is really annoying. I have never tried to do a root or mess around with the phone so it seems really odd that something like this would happen following a standard update
P.S These are the instructions I followed when I tried to re-install the official firmware - http://forum.xda-developers.com/showthread.php?t=1671969
Boot to recovery factory restore then flash stock firmware via Odin .
jje
JJEgan said:
Boot to recovery factory restore then flash stock firmware via Odin .
jje
Click to expand...
Click to collapse
Its not letting me boot to recovery mode anymore. I can boot to download mode but when I try to boot to recovery mode it just keeps looping the startup screen which at the moment is the error message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Then flash a stock ROM image through Odin
You only need to boot into download mode for odin download the relevant firmware package and odin when you connect it via usb in download mode you will notice the first com port on odin turn yellow to indicate a device is connected
Do a search for detailed instructions buddy
Sent from my GT-N7000 using xda app-developers app
ascottuk said:
You only need to boot into download mode for odin download the relevant firmware package and odin when you connect it via usb in download mode you will notice the first com port on odin turn yellow to indicate a device is connected
Do a search for detailed instructions buddy
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Hmmm. When I connect the phone it makes the sound in Windows that the phone has been connected but then in Odin the com port is blue not yellow. Does that mean that it has not detected the phone properly?
Glebun said:
Then flash a stock ROM image through Odin
Click to expand...
Click to collapse
This is the message I get in Odin when I try to flash the stock firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIH_I9300O2UDLI3_I9300BWDLI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
You need a service centre with that comment Nand Start Write! .
jje
Yeah, you probably have corrupted NAND :/, take it for warranty repair, they will replace the mainboard. :thumbup:
Sent from my GT-I9300 using xda app-developers app
A few moments ago I was trying to flash the stock ICS firmware to my SGH-I757M using Odin3 v1.85.
But, I made a serious mistake. I didn't notice that "Re-Partition" was checked for some odd reason. The flash failed.
I then restarted Odin and put my phone back into download mode and proceeded to try to re-flash the stock firmware.
It failed yet again.
This is the log from Odin:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I757MUGLH2_I757MOYCLH2_I757MUGLH2_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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone now shows the following error: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried flashing just CWM and that won't work either. Kies also does not connect to the phone.
CharlieMPK said:
A few moments ago I was trying to flash the stock ICS firmware to my SGH-I757M using Odin3 v1.85.
But, I made a serious mistake. I didn't notice that "Re-Partition" was checked for some odd reason. The flash failed.
I then restarted Odin and put my phone back into download mode and proceeded to try to re-flash the stock firmware.
It failed yet again.
Click to expand...
Click to collapse
See if this helps
ysrini said:
See if this helps
Click to expand...
Click to collapse
So, I read through the guide and it does not refer to the SGH-I757M.
Is there something that I'm missing? I don't want to further my issue.
I bricked my SGH-i757m galaxy s2 hd lte
I tried to install Cyanogenmod 10 onto my sgh-i757m but it seems I may have used the wrong links to download the .zip files. I followed standard procedure in recovery mode (factory reset, clear cache) and instead of rebooting my phone just turned off. I had plenty of battery life (over 50%) and I cannot even start recovery mode!
No download mode, no recovery & no signs of life from phone ? Try a jig (highly unlikely to work). Also try King Rat's 'hotboot' method to try & jump start the phone (search). Otherwise, service centre for motherboard replacement or perhaps try a JTAG repairer (assuming it can be JTAG'd).
After looking at many XDA pages and other android related forums I have not found a problem to my solution which has left my phone unusable for two months.
My phone is stuck at the Samsung boot screen, it is not looping, it just stays there when the phone turns on - indefinitely, I CAN enter both recovery mode and download mode (a lot of people with similar problems cannot enter recovery) but when attempting to flash anything at all I get a NAND write start failure regardless of the cable, computer and version of Odin I use. I have attempted to use a few PIT files but these get stuck at the "REPARTITION" stage and I am forced to unplug the phone to try again. The phone is rooted and I cannot as many of you will know send it back to Samsung (still in warranty) due to the flash counter being greater than zero.
If there is any further information required please ask.
hawkar13 said:
After looking at many XDA pages and other android related forums I have not found a problem to my solution which has left my phone unusable for two months.
My phone is stuck at the Samsung boot screen, it is not looping, it just stays there when the phone turns on - indefinitely, I CAN enter both recovery mode and download mode (a lot of people with similar problems cannot enter recovery) but when attempting to flash anything at all I get a NAND write start failure regardless of the cable, computer and version of Odin I use. I have attempted to use a few PIT files but these get stuck at the "REPARTITION" stage and I am forced to unplug the phone to try again. The phone is rooted and I cannot as many of you will know send it back to Samsung (still in warranty) due to the flash counter being greater than zero.
If there is any further information required please ask.
Click to expand...
Click to collapse
Which recovery?
What else does it say in Download mode?
wangdaning said:
Which recovery?
Click to expand...
Click to collapse
CWM recovery
rootSU said:
What else does it say in Download mode?
Click to expand...
Click to collapse
Here is the log from Odin v3.07 using a stock rom:
==================================================================================
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXEMC2_I9300OXAEMC2_1042335_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
==============================================================================================
Service repair Nand damaged .
jje
Sorry, I meant on the phone screen
Sent from my GT-I9300 using Tapatalk 2
Did you get any further with this? I can't get into recovery mode but download mode is showing the product name correctly, unlike with many of the others. Is all hope lost for my NAND / Phone?
velkrosmaak said:
Did you get any further with this? I can't get into recovery mode but download mode is showing the product name correctly, unlike with many of the others. Is all hope lost for my NAND / Phone?
Click to expand...
Click to collapse
Try flashing a recovery with Odin or reflash stock ROM
slaphead20 said:
Try flashing a recovery with Odin or reflash stock ROM
Click to expand...
Click to collapse
Tried that, but Odin fails when it gets to start writing to the NAND. Any other ideas?
velkrosmaak said:
Tried that, but Odin fails when it gets to start writing to the NAND. Any other ideas?
Click to expand...
Click to collapse
Requires a new motherboard .
jje
I installed cyanogenmod a few months back and last night I tried to remove it, in the end I ended up with no rom with default recovery/modem/kernel adb refuses to work on my computer so no luck with sideloading and my phone also wont read my internal SD card. I can't unlock my bootloader since there isn't a ROM? Not really sure on that one, but so far no luck with auto bootloader unlockers. And I can't use Kie's because it's not a supported device since I changed things? and using Odin to install a ROM because they freeze while connecting to device.... Anyone have some ideas?
This is what I get from pretty much everything I tried to flash, this was CF auto root
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
and it freezes there
With adb I tried following a guide to flash ROM on to my phone
Download this mini-sdk package and extract it to c:\mini-sdk
Rename the custom ROM package you want to flash to "rom.zip" and copy it to c:\mini-sdk
Connect your device to the PC
Boot your device in recovery mode
Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:
cd /d c:\mini-sdk
adb shell
mount /data (error might mean that /data partition is already mounted)
on Android 4.2 and above: mkdir -p /data/media/0
but I get stuck at "adb shell" with error: device not found (again the device is showing up connected on my computer)
McNiiby said:
I installed cyanogenmod a few months back and last night I tried to remove it, in the end I ended up with no rom with default recovery/modem/kernel adb refuses to work on my computer so no luck with sideloading and my phone also wont read my internal SD card. I can't unlock my bootloader since there isn't one... And I can't use Kie's or Odin to install a ROM because they freeze while connecting to device.... Anyone have some ideas?
Click to expand...
Click to collapse
A little sparse on details here...
How did you try to remove CM?
How do you know that your phone can't read the internal storage if it is not booting up?
Also, there certainly is a bootloader on your phone.
If Odin is freezing, this is going to be an issue with one of the ports, the cord, or the computer.
es0tericcha0s said:
A little sparse on details here...
How did you try to remove CM?
How do you know that your phone can't read the internal storage if it is not booting up?
Also, there certainly is a bootloader on your phone.
If Odin is freezing, this is going to be an issue with one of the ports, the cord, or the computer.
Click to expand...
Click to collapse
Sorry, I tried to add more detail, but was blocked by the spam filter since I'm a new user. I was quite tired as well after trying to fix it for 6+ hours... I'll try to give you as much information as I can.
I tried to remove it by installing the Kernal/Recovery and modem, and figured I could add the ROM in later.
My device will get to the recovery screen, but since it's not an unlocked bootloader my theory is that's why odin doesn't work, but I can't unlock my bootloader since there's no ROM?
There is nothing wrong with the ports or the cord I can get the device to show up and stay on the computer and was able to use odin just fine up until now. My problem with Odin is it gets stuck when I get here, mind you CF-Autoroot isn't the only thing I've tried to flash, I've tried TWRP and CWM, but since neither will work with out being unlocked, I have to find a way to unlock the bootloader.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
I was originally using CWM, but since I flashed the Recovery for the stock it removed CWM?
and to be clear my phone will start in recovery mode and dowload mode, but I can't actually recovery a back up since it can't communicate with the SD card...
The status of the bootloader definitely does not have anything to do with Odin not working. The tool is meant to flash firmware to stock phones as well. You need to follow this:
http://forum.xda-developers.com/gal...-ucucne5-mj4-stock-odex-t2802189/post53841080
So I was trying to unroot my phone, to be able to play that new mobile nintendo game of all things and in the process of that got myself stuck in a boot loop, with my wits I tried on my own to get my phone out of the loop. With the TWRP recovery thing in hand I had mangaed to complete wipe my device I think. So now, it will load up to the sprint screen and sit there. I can boot up into TWRP and into the download mode; I don't think I can boot into the stock recovery thing. I tried to use Odin to get a OS onto my device but it said this "<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
And on my phone it had said
SW REV CHECK FAIL DEVICE 3 BINARY 1
Please help me on this, I would rather not just have a soft bricked phone out of my own stupidity.
also not really sure what fastboot is but I don't think I can access it, When i try to hold the power vol up, down. It just turns the phone off (?) and shows the battery charging.
If you can go into recovery mode you just adb push a rom from your pc.
http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
StillLiam said:
So I was trying to unroot my phone, to be able to play that new mobile nintendo game of all things and in the process of that got myself stuck in a boot loop, with my wits I tried on my own to get my phone out of the loop. With the TWRP recovery thing in hand I had mangaed to complete wipe my device I think. So now, it will load up to the sprint screen and sit there. I can boot up into TWRP and into the download mode; I don't think I can boot into the stock recovery thing. I tried to use Odis to get a OS onto my device but it said this "<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
And on my phone it had said
SW REV CHECK FAIL DEVICE 3 BINARY 1
Please help me on this, I would rather not just have a soft bricked phone out of my own stupidity.
Click to expand...
Click to collapse
When i did this go into twrp and clear delvik. Cache. System
Sd card. And usb check em all coach.
Do it then reboot system and quickly press (power - volume down - and menu key all at once. Download a completely stock rar and install it using odin .
The id005 thing is all good . Dont mess with settings jusy navigate to .tar and flash
ilqs said:
If you can go into recovery mode you just adb push a rom from your pc.
Click to expand...
Click to collapse
As I had said up there I cant boot into recovery mode, whenever I try to my phone just boots into TWRP.
bipolargroup said:
When i did this go into twrp and clear delvik. Cache. System
Sd card. And usb check em all coach.
Do it then reboot system and quickly press (power - volume down - and menu key all at once. Download a completely stock rar and install it using odin .
The id005 thing is all good . Dont mess with settings jusy navigate to .tar and flash
Click to expand...
Click to collapse
I'm not sure I can get a rom in there through Odin, As I had posted up there whenever I tried to do that it gave me that error.
I would really appreciate some help here, been over 12 hours of me trying to fix it on my own. To no avail.
try samsung smart switch. it will download the original firmware that came with the phone and flash it for you..
success123 said:
try samsung smart switch. it will download the original firmware that came with the phone and flash it for you..
Click to expand...
Click to collapse
How do I do that? Does it require my phone to boot?
as digital tumbleweed passes through
StillLiam said:
As I had said up there I cant boot into recovery mode, whenever I try to my phone just boots into TWRP.
Click to expand...
Click to collapse
Did you see the link? If you can access TWRP you are good. Just follow the guide.
StillLiam said:
How do I do that? Does it require my phone to boot?
Click to expand...
Click to collapse
http://samsungsmartswitch.org/ download it from here. put your phone into download mode and follow the steps
download it from here. put your phone into download mode and follow the steps[/QUOTE said:
I tried using Smart Switch and it didn't recognize my phone. I had tried putting my model number and serial number in on it too in the emergency software thing, didn't recognize it.
Click to expand...
Click to collapse
Shooot. Well id do this if you can still get into twrp you really are safe. Click on twrp and i think under Home advamced. Find the fix file permissions. Do it "JUST IN CASE" .i had this happen to me
Then folllow the post here at this link
Click Me Stock Firmware This worked for me when i was Bricked .No os . No nothing . What do you have to lose
ADB Sideload in worst case
Your last but 100% working hope once executed the right way will be the use of ADB Sideload within TWRP which is your obvious recovery. You will need either a SDcard (not for S6 and Edge), a USB with a direct usb cord, or a PC with USB cord to do this. For PC you will need the ADB SideLoad drivers for your phone model to be installed on your PC. Once installed you can connect your phone via USB to your PC and run the ADB SideLoad executable which will run in a CMD window. I don't know the exact commands anymore, but long story short, you want to push the OS install package (Self-installing OS NOT WITH CUSTOM INSTALL MENU) to your phones internal memory which after you'll need to execute by using TWRP. This i have done myself after i hard bricked my S6 edge the first day i got it. I used (by accident) Nand Erase including every other erase to get it back to work which just only put me to more trouble having me to use ADB SideLoad. I hope this bare information helps you out since i can feel the pain you are going through having to know you may have permanently lost your phone lol... Report back if it helped or if you need any more information regarding ADB SideLoad.
- GhostGurio
Try some other original cable. N try flashing via odin.
Also there sometimes u need to flash with pit file. Not sure though.
I had same problem with my s4. Failing at nand write.
In my case cable thing worked.