Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 3.185 will install this ROM successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated. I have also tried other Odin versions including 3.07.
Thank you!
jvaldez33 said:
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 185 will install this rom successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated.
Thank you!
Click to expand...
Click to collapse
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Note II Won't boot.
dragonstalker said:
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Click to expand...
Click to collapse
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Warranty costs if phone has been rooted
jvaldez33 said:
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Click to expand...
Click to collapse
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
jvaldez33 said:
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
Click to expand...
Click to collapse
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
miketoasty said:
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Update on events
mikelikesbikes said:
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I have been in the IT business for nearly 25 years and have seen many problems resolved if you have the time and desire to put forth the efforts to investigate the problem every day with a clear head. With that being said I for some unknown ADD moment and decided I wanted to troubleshoot my sons girlfriend's Note II that was having problems. Now here I am wrestling with a problem like a drug addict looking for their "next fix". I am very stubborn and extremely capable of diagnosing hardware and software problems but this one truly has me stumped!
With this being a problem I decided to purchase another Note II off EBay to experiment with and was listed with similar problems, Red Light and wouldn't boot.. I figured for $125 the worst that could happen is I could disassemble it and part out the LCD/Digitizer and recuperate my investment. There are some problems I like researching and resolving and this is one. I personally believe the problems on both Note II's may both related to the charging board based on the information on the following post on another forum: http://forum.xda-developers.com/showthread.php?p=45678812#post45678812. I will elaborate a little more shortly.
Let's go over my three day 50 hour marathon. Here is the only download that successfully downloads but the phone will only splash the "GALAXY NOTE II" screen and turn off after a successful install. I have downloaded Odin 3.185 and 3.07 and get the same results:
sch-i605-16gb.pit
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
Unless the problem resides on my laptop I think I have eliminated the issue of having a good cable(s) by using official Samsung cables, NEW RocketFish cables and they all seem to work fine for viewing and transferring files via USB. I also have an external battery charger and can guarantee an excellent charge on the battery(s). The current files I was recommended to use came from a single Zipped file: GalaxyNote2UnlockVerizon. Please let me know if there are a different set of files I should be using?
Unless I have downloaded the wrong files? I have attempted to install the following bootloader with Odin versions 3.07, 3.13 and 3.185 and they all fail: BootloaderBaseline2.tar.md5. All I know at this moment i am stuck at a point that I have the Note II in a state that will not allow me to boot.
Lets discuss some hardware issues that I need to explore a little further. Since I have a spare phone to test with I thought I would swap logic/motherboards and see if I had any different results. Unfortunately they are exactly the same on both Note II's. Now comes an interesting issue I stumbled upon. When I VERY CAREFULLY reassembled it on an ESD Mat I somehow dislodged or did not securely fasten the display cable to the logic board and when the power was pressed the phone seemed to start booting but there was no display. The sound and the blue light came on normally. I had hoped the original ROM was now installing. I powered off the phone, removed the battery and disassembled it to discover my mishap, so I reconnected the display cable and reassembled the phone only to see the original problem was still present.
Has anyone else had a charging port issue that caused similar problems? I was planning on ordering a new charging port off Amazon today just to try. Any additional information would be greatly appreciated.
Thank all of you that contribute to this site. It is amazing how many problems can be resolved when great minds are put together.
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
No Red Light
droidstyle said:
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
Click to expand...
Click to collapse
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
jvaldez33 said:
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
Click to expand...
Click to collapse
look for a n7100 tar, or maybe "I think, can't remember" there was a stock tar in the I605 mega roll thread somewhere. flash one of them. Try not to use the kies tar as i've had problems with them being corrupted before. Know you've tried both the methods already. Just a suggestion in case you have not. Also check and make sure you have the right pda file.
Related
I've been trying to convert the firmware on my M250S to I9100. I've followed the guide to the letter and all the drivers are installed as well as Kries. I also made sure Kries was inactive while Odin was up. This is how far I get before it fails.
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If anyone has any ideas I would appreciate it. I've tried everything I can think of including using different firmwares, pits, as well as versions of Odin. That's as far as I get before it fails.
How are you trying to do it? As I recall (I don't have an M250 so didn't pay crazy attention) there's two ways to convert one to an i9100. One involves Odin failing intentionally. Although, the method involving a pit file doesn't intentionally fail. If you're flashing pits and they're failing that's definitely not good... Potential brick.
Search for a guide in the s2 general section, I read one a couple weeks back which members were using with success.
You can also click the link in my signature and follow the steps there. As you're not doing a 'regular' Odin flash bear in mind some things will be a little different.
Sent from a galaxy far, far away
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Edit: I tried another computer and it worked flawlessly. So now I'm running on i9100. Although I'm having a few issues. It doesn't show my battery charging when the usb is plugged in. Also when I shut down my phone it doesn't completely shut down. It goes to a screen with a green battery. This actually happened before but I thought perhaps changing firmware would fix it. Before this the device would come back on automatically when I tried to shut it down and I read it could be the usb port so I cleaned the usb port with alcohol.
Slywolf15 said:
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Click to expand...
Click to collapse
Ah so it may not be a case of what you're trying to do, it might be a case of how the flash is set up/what hardware (pc, cable etc) you're using. In that case, use the link in my signature to troubleshoot it. Perseverance is key. Also have a look here : http://forum.xda-developers.com/showthread.php?p=45131292
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
ZivC12 said:
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
Click to expand...
Click to collapse
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Slywolf15 said:
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Click to expand...
Click to collapse
it happened to me with bad uk unbranded rom, try to flash new rom, if you cant turn on the phone switch battery
How it started:
A pop message appears asking to format the phone, I accidentally hit okay, after 10 seconds I realized it, I immediately stopped the process by hitting the back button which caused my phone to go blank screen and freeze. so I pressed and hold power button, and the phone shuts off turns back on then it get stuck on the Samsung Logo/screen and won't go through no matter how long I wait.
So with that said I may have corrupted my Operating System so I went online to try to look for solutions to recover my Note.
i have downloaded Odin v1.85 and v3.07
i have downloaded the latest OS Jellybean from samsung:
(KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5)
i have downloaded the latest USB software and currently using the original cable that came in the box.
I open Odin v1.85 on my Windows 7 Ultimate Desktop
i put my phone in Odin download mode (power + volume down)
I pressed volume up
I plugged in my phone to the USB
I clicked start
and then I get stuck
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.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> amss.bin
<ID:0/005> NAND Write Start!!
Please see my screenshot as attachment.
Please help!
Thank you!
http://forum.xda-developers.com/showthread.php?t=2240096
okay thank you i am reading it now.
i will report back with the outcome.
thanks once again.
okay before i go further if you look at my attachment
first box says "MODEM"
is this normal?
i saw a vid on youtube shows "SYSTEM"
I have read your guide and installed the latest samsung USB driver
I rebooted my computer opened ODIN as admin
followed instructions and i am back to my original post
i think it has something to do with the fact mine shows "MODEM"
this is what i'm talking about.
the difference is on this pic it shows "SYSTEM"
while mine says "MODEM"
does that mean my phone can no longer be recovered?
Am I missing something here? seems like I have a more technical issue/problem other than common Odin problems.
any help would be appreciated.
What it says is what yrs currently flashing. That's just where it's getting stuck
studacris said:
What it says is what yrs currently flashing. That's just where it's getting stuck
Click to expand...
Click to collapse
so is there any solution to this?
i tried it over again on another PC (Laptop)
i still get the same error where I get stuck:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> amss.bin
<ID:0/003> NAND Write Start!!
stuck here... no matter how long I wait i have been up all day long and found no solution online
I will send $10 paypal donation to the website or to somebody that can help me revive my phone back to normal.
i am that desperate now. i have been up for almost 12 hours trying everything i could.
i am currently looking for a .pit file for Samsung Galaxy Note AT&T SGH-i717 cannot find it anywhere!
Are you using the same .tar everytime?
Try another package and see what happens.
Or... just flash a twrp.tar and just flash a custom Rom on that thing.
studacris said:
Are you using the same .tar everytime?
Try another package and see what happens.
Or... just flash a twrp.tar and just flash a custom Rom on that thing.
Click to expand...
Click to collapse
Yes: KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5
i'll download an older version (ice cream sandwich)
i have not tried twrp.tar nor custom ROM
can you point me to a link to DL it?
If another stock package doesn't work here's Twrp
http://forum.xda-developers.com/showthread.php?t=1647575
Then you put a custom Rom of your choice I your sdcard and flash that within recovery.
studacris said:
If another stock package doesn't work here's Twrp
http://forum.xda-developers.com/showthread.php?t=1647575
Then you put a custom Rom of your choice I your sdcard and flash that within recovery.
Click to expand...
Click to collapse
tried it i'm still stuck.
please see screenshot
are you running Odin as admin?
as long as you can still get into download mode and have odin recognize you, you are in good shape. Dont do something to put yourself in qualcomm download mode. Else, you will be sending your phone to be jtagged. . .
In my guide it mentioned trying different cables and cleaning the usb port.
Have you taken those steps?
sinasiadat said:
are you running Odin as admin?
as long as you can still get into download mode and have odin recognize you, you are in good shape. Dont do something to put yourself in qualcomm download mode. Else, you will be sending your phone to be jtagged. . .
Click to expand...
Click to collapse
yes
studacris said:
In my guide it mentioned trying different cables and cleaning the usb port.
Have you taken those steps?
Click to expand...
Click to collapse
yes tried 3 diff cables and tried 4 MB ports and 3 laptop ports
I meant cleaning the port on the device itself
jeffcarp003 said:
yes tried 3 diff cables and tried 4 MB ports and 3 laptop ports
Click to expand...
Click to collapse
what is device manager showing you when your phone is plugged in? what does it enumerate as . .
do you have a copy of QPST? (you work for qualcomm right?)
I Hard Bricked Galaxy note i7i7
Hello
I was flashing a kernel in order for this jellybam rom to work.So when i put my phone into custom recovery mode and installed the custom kernel through custom recovery a quick message appeared and my phone just shut off. My phone hasn't turned on since and i have no clue to unbrick my phone. I talked to a guy at att and he said that he unbricked his hard bricked phone without a jig or a jtag is that possible?
jeffcarp003 said:
I have read your guide and installed the latest samsung USB driver
I rebooted my computer opened ODIN as admin
followed instructions and i am back to my original post
i think it has something to do with the fact mine shows "MODEM"
this is what i'm talking about.
the difference is on this pic it shows "SYSTEM"
while mine says "MODEM"
does that mean my phone can no longer be recovered?
Am I missing something here? seems like I have a more technical issue/problem other than common Odin problems.
any help would be appreciated.
Click to expand...
Click to collapse
Sounds like corrupted download. Look for another source and let me know how it goes.
Sent from my XT894 using Tapatalk
I have a US SPH-D710 Sprint Samsung S2.that was working OK on ICS 4.0.4. I decided to upgrade to JB via Kies, following the procedure discussed at the official Samsung page on us on support at SupportOwnersFAQPopup.do?faq_id=FAQ00052384&fm_seq=60310 (sorry, I cannot post links)
I had to install Kies, which was not previously installed. It installed OK. Everything started out well and the phone went to 98% or 99% and then the flash failed. Power cycling, the phone came up with a complaint
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I did recovery mode, to the same effect. I then tried the Simple Upgrade tool, to the same effect. It always got to about 98% or 99% and then failed, giving no information, just a failure..
I uninstalled my anti-virus completely (as it was old anyway and it's time to buy a new license) and tried again. Same thing. The simple downloader fails with "Error Occurred! Cancel Download!!"
Then, I went to QBKing and followed a link from qbking77's web page at how-to-root/root-the-samsung-epic-4g-touch/ to a thread at sxtpdevelopers where I downloaded SPH-D710_GB27_1014481_Rooted_Restore.exe and it fails without giving any reason at "hidden"
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> boot.bin
<ID:0/006> cache.img
<ID:0/006> data.img
<ID:0/006> factoryfs.img
<ID:0/006> modem.bin
<ID:0/006> hidden.img
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
No complaint at all, just the above. I have tried multiple times with different USB ports and different USB cables. I have successfully flashed/rooted/Odin'd other Samsung phones from this PC before. It's 64-bit Win7. This specific phone has never previously been rooted or flashed. It was on FL24.
The phone goes into download mode just fine, but is otherwise useless. In download mode, the phone says:
ODIN MODE
PRODUCT NAME: SPH-D710
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
What can I do to bring this phone back to life?
I got it working
I went into my office and, using a computer appropriate for this use there, followed exactly the same steps with the same file, for the simple download tool this time, and using a third micro-USB cable, and it worked on the first try. Go figure. This was after trying various different things for about six hours at home, on my Win7 laptop that has worked many times before for other Samsung phones (an Epic 4G and an S4).
ekuns said:
I went into my office and, using a computer appropriate for this use there, followed exactly the same steps with the same file, for the simple download tool this time, and using a third micro-USB cable, and it worked on the first try. Go figure. This was after trying various different things for about six hours at home, on my Win7 laptop that has worked many times before for other Samsung phones (an Epic 4G and an S4).
Click to expand...
Click to collapse
I think that the problem was that you didn't installed the correct drivers on your windows 7 laptop :fingers-crossed:
Or the file was corrupted, and when you downloaded it in your office, the download of the stock rom was succes full
KingOfDope said:
I think that the problem was that you didn't installed the correct drivers on your windows 7 laptop :fingers-crossed:
Or the file was corrupted, and when you downloaded it in your office, the download of the stock rom was succes full
Click to expand...
Click to collapse
Definitely could have been any of those. I was just confused as I'd successfully used Odin on that laptop with several other Samsung phones, both newer and older than the S2. And also because it always got to 98% or 99% before it failed. I think this tells me I need another Win 7 box at home, for troubleshooting this kind of problem.
Maybe look here
Sent from my SM-T210 using xda premium
theunderling said:
Maybe look here
Click to expand...
Click to collapse
I didn't realize that the Sprint version of this phone was so different from the non-Sprint version (nor that this forum was for the non-Sprint version). I found the forum you referenced, and will direct all future questions for this phone over there. Thanks for the pointer.
Ok,I think theres maybe 20 odd different ones.Someone could think youve a standard s2 and give wrong info based on that.
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Which version of ODIN did you use? What kind of file(s) were you trying to flash?
Sent from my GT-I9300 using Tapatalk
I'm not sure but think it was Mobile Odin 3.65 and I was trying to flash CWM touch from xda.
Additionally, I think my battery charge may now be low after many attempts to recover it but will that matter bearing in mind I'm using Odin on my PC and the phone is connected to the PC by USB cable?
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
JJEgan said:
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
and it stops there
matrixmainframe said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
and it stops there
Click to expand...
Click to collapse
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
JJEgan said:
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
Click to expand...
Click to collapse
Kies is not installed on my computer and I have tried Odin versions 1.83, 1.85, 3.04, 3.06, 3.07 and 3.09.
I have also tried 'Samsung_USB_Drivers_1.5.27.0.exe' and 'SAMSUNG_USB_Driver_for_Mobile_Phones.exe' and remembering to uninstall then reboot and then install.
On one occasion it got as far as (can't remember the exact words) "Get PIT Mapping" but then just stopped there.
I cannot believe I have done anything other than corrupt the CWM recovery because all I did was try to flash CWM Touch and as soon as I pressed OK the screen went black with the word "Samsung Galaxy SIII GT-I9300". Those words just stay there because since then I can't switch the phone off. I thought that if I just reflashed CWM via Odin on my computer I would be able to get back into recovery mode and just restore my backup.
Appears I am mistaken and have ruined a very new and vey expensive phone.
The only other thing I seem to recall is that before I tried the Mobile Odin flash the battery was below 50% charge but I'm not sure if that's relevant?
This is usually a wrong file flash symptom .
JJEgan said:
This is usually a wrong file flash symptom .
Click to expand...
Click to collapse
Do you mean I'm trying to flash something I shouldn't?
Initially I tried to flash CWM Recovery but then decided just to try and get it back the way it was by trying to flash Android 4.1.2 again.
The file I have been using is "KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5" which I believe is from Sammobile and which is, I believe again, the ROM that the Galaxy S3 comes pre-installed with. Do you think it worthwhile me trying some other ROM?
I have been doing a lot more web research and some say that the battery charge should be more than 80%. Does this matter?
Won't the battery have been charging all the while the phone was plugged into into the Computer via the USB lead?
If I buy a separate charger and charge my battery to 100% do you think the Odin reflash will work then?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
llcoolveer said:
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
Click to expand...
Click to collapse
Nice to know I'm not alone but sorry you're having the same problem. Have sat down to do some more web searching and will let you know if I find a solution
Service centre new motherboard .
JJEgan said:
Service centre new motherboard .
Click to expand...
Click to collapse
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
llcoolveer said:
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
Click to expand...
Click to collapse
Please can you tell me what is "OG Recovery"?
Thanks
matrixmainframe said:
Please can you tell me what is "OG Recovery"?
Thanks
Click to expand...
Click to collapse
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
llcoolveer said:
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
Click to expand...
Click to collapse
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
matrixmainframe said:
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
Click to expand...
Click to collapse
I couldn't also....only when my battery was full charged....:good:
Succes....
The end
Okay, I started this thread so will end it now as follows:
1 Thank you to all those who offered help/advice/suggestions.
1a Some people do not read posts properly because even though I had specifically stated that I could not get into recovery mode some people proceeded to tell me to go into recovery mode and restore my rom.
2 Whilst I have recovered the full use of my phone I can no longer root it but that's ok because at least I have a phone that is comparable to the vast majority who choose not to root.
3 I will explain how I rescued it but obviously I don't really understand what the result is other than a usable phone so please don't copy.
4 Whilst I have no doubt one could damage a motherboard, that could only be done with very specialist software that most people would not have so the advice of some that I needed a new motherboard was ill informed. If you don't know the answer don't offer an unhelpful answer. Recommending a new motherboard is like a motorist taking his car into a garage with a blown fuse and the mechanic saying the only cure is a new car.
5 After a lot of research I found one lone website that explained that from July 2013 Samsung introduced a change to their ROMs which introduced an efs 2 file. Additionally it appears that once you have flashed/upgraded to an efs2 ROM you cannot then go back to an efs ROM.
6 This is above my understanding but I do know I did go from efs to efs2 and when I then encountered a problem I thought it a good idea to go back to my original (efs) ROM which I now believe caused my problem.
7 I did not know if I had found the answer but as I believed my phone was a paperweight at that point anyway I had nothing to lose and downloaded the GT-I9300.pit file and flashed with repartition selected. I then flashed Android 4.3 knowing it would be an efs2 ROM and my phone is now working again.
8 However, although my phone is now working again, I find that I cannot install a custom recovery nor can I root the phone but that is a small price to pay to have a brand new S3 working again.
9 Whilst it may not be wise to mess about with the pit file, it seems nothing can be lost to give it a go because even if it doesn't work you can still go for the new motherboard option happy in the knowledge you have tried everything.
10 I may start a new thread for advice on that matter but for the time being I'm just relieved to have my phone back and I stress again that it did work for my specific problem and whilst it might work for you please only do it knowing it may not work for your problem.
Hello,
I have a Verizon Samsung Galaxy S4 which came stock running 5.0.1 lollipop. I managed to root the phone with KingRoot and flashed a custom rom with FlashFire with no issues at all. My main goal was to get Xposed Framework installed. I was able to flash the Xposed sdk-21 arm file with FlashFire and it seemed to install properly but I couldn't ever get the Xposed app to install properly afterwards. So I then decided to uninstall the Xposed sdk-21 arm with a Xposed uninstaller file from the same source which had to be flashed and that's when all the trouble began.
My phone rebooted and got stuck at the Samsung splash screen. I had tried rebooting several times. Firstly I went into stock recovery and tried wiping cache partition to no avail. Secondly I tried to do a factory restore via stock recovery and that was a no go. Still stuck at Samsung splash screen upon boot up attempt. I then decided it was probable best if I had just started from scratch. So I downloaded the stock I545VRUGOC1 rom along with the Pit file and tried flashing that with Odin v3.09. That was a huge fail. Odin went through the process all the way to about 90-95% and wouldn't go any further. I had to keep pressing start after many failed attempts to get to that point.
Here's what I get from Odin now:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUGOC1_I545VZWGOC1_CL4584173_QB451701 6_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I can no longer get into stock recovery on the phone at this point. I get this message when trying to enter recovery:
Software Update Failed
Your device didn't update
successfully. Use the Verizon
Software Repair Assistant on a
computer to repair your device and
complete the update.
I CAN get into download mode at the very least. Maybe there's still hope? I'm about cross-eyed and at wits ends trying to find a working solution. Any and all help is much appreciated.
Thanks
Okay, so I came across a Brick Fix .tar (boot disc image) file that I was able to flash successfully with Odin 3.09. I can now get back into system recovery. I still cannot get the phone to boot normally. It only goes to the Samsung Galaxy S4 splash screen. I'm currently trying to figure out if I am able to do an ADB sideload.
Can anyone point me in the right direction to the proper adb files or programs?
First, redownload it, unless you confirmed the md5s...
Second, try different USB ports.
Third, a different USB cable... Some work, some don't...
The OEM samsung cable works best, but I know for sure my monoprice cable for 2 bucks works nicely... Odin is reaaalllly picky..
Really, if it fails, those are the three major things 99% of people have problems with.
XxD34THxX said:
First, redownload it, unless you confirmed the md5s...
Second, try different USB ports.
Third, a different USB cable... Some work, some don't...
The OEM samsung cable works best, but I know for sure my monoprice cable for 2 bucks works nicely... Odin is reaaalllly picky..
Really, if it fails, those are the three major things 99% of people have problems with.
Click to expand...
Click to collapse
Holy wow! First off I just want to say thanks to you for chiming in! Apparently Odin didn't like the stock cable that came with the phone. I used my old Motorola Droid Bionic usb cable, switched usb ports, and flashed the stock 5.0.1 rom with Odin v1.85. The best I could do with Odin v3.09 was about 75% complete before it failed. I've been working on this literally all day (off work today) google search after google search . Thank you so much! :good:
Btw I flashed the stock rom I found here http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-5-0-1-lollipop-oc1-t3174850
Huh. Odin prefers the OEM cord, but whatever works works.
I don't know what it is but I also used my droid bionic cable to charge my galaxy s3 because it works a heck of a lot better than the stock cable. I bought my galaxy s4 from ebay as a manufacturer refurbished phone so that my have something to do with the cable provided. My phone is black but it came with all white oem accessories. I ordered my galaxy s3 from ebay brand new a few years back and it is black and came with a black oem charger. Not sure if any of that makes a difference or not but they are Samsung brand cables. I think Motorola may have better charger/data cables imo.