Develop Bugs

[Q] HELP!!!!

I cannot get my phone to boot up. It loads the splash screen and gets stuck there. It doesn't move past that screen. I've tried multiple times going into recovery mode but it won't go. I can get into download mode though. I've tried using Odin 3.07 to reflash the KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5 from the back to stock rar I found here http://forum.xda-developers.com/showthread.php?p=41340941 and I do not know what to do next. I've even tried flashing a recovery tar file I found here http://forum.xda-developers.com/showthread.php?t=2533333. I've also tried removing the battery, replacing the battery (I have a second battery), and even if I power off the device and plug it up to my charger it loads the splash screen and stays there. I've looked around online and found this http://www.note2forum.com/forum/galaxy-note-2-help/1530-troubleshooting-samsung-galaxy-phone-bootloop.html#post20381 but can't even get to recovery mode to do a data wipe. The last thing I was able to do successfully with my phone was get it back to stock so and do the update to 4.1.2 because it was on 4.1.1 and I've seen something called SDS while searching. Is that what happened here? Is my phone able to be repaired? When I'm in download mode the upper left corner shows the following information:
ODIN MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV
I'm doing some serious reaching here because this is my primary phone, and I'm not familiar with PIT files but what I briefly read stated something about identifying which files go to which partition. I have no experience or knowledge of bootloader functions/changes and I've never checked more than auto reboot and reset time in ODIN. Any help is greatly appreciated.
Update!!! OMG I'm so happy to make progress. I flashed in ODIN the 4.3param_tz.tar file found herehttp://forum.xda-developers.com/showthread.php?t=2497994 and it successfully rebooted me into CWM. I will post the results of a ROM restore I'm attempting shortly. I was able to complete a full restore of a previous ROM and my phone is now currently booting up as I type this. Hopefully nothing goes wrong, but I've gotten farther now than I have in the past 5 hours I've been glued to my laptop. Time for a cig and beer.

Assassyn said:
I cannot get my phone to boot up. It loads the splash screen and gets stuck there. It doesn't move past that screen. I've tried multiple times going into recovery mode but it won't go. I can get into download mode though. I've tried using Odin 3.07 to reflash the KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5 from the back to stock rar I found here http://forum.xda-developers.com/showthread.php?p=41340941 and I do not know what to do next. I've even tried flashing a recovery tar file I found here http://forum.xda-developers.com/showthread.php?t=2533333. I've also tried removing the battery, replacing the battery (I have a second battery), and even if I power off the device and plug it up to my charger it loads the splash screen and stays there. I've looked around online and found this http://www.note2forum.com/forum/gal...-samsung-galaxy-phone-bootloop.html#post20381 but can't even get to recovery mode to do a data wipe. The last thing I was able to do successfully with my phone was get it back to stock so and do the update to 4.1.2 because it was on 4.1.1 and I've seen something called SDS while searching. Is that what happened here? Is my phone able to be repaired? When I'm in download mode the upper left corner shows the following information:
ODIN MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV
I'm doing some serious reaching here because this is my primary phone, and I'm not familiar with PIT files but what I briefly read stated something about identifying which files go to which partition. I have no experience or knowledge of bootloader functions/changes and I've never checked more than auto reboot and reset time in ODIN. Any help is greatly appreciated.
Update!!! OMG I'm so happy to make progress. I flashed in ODIN the 4.3param_tz.tar file found herehttp://forum.xda-developers.com/showthread.php?t=2497994 and it successfully rebooted me into CWM. I will post the results of a ROM restore I'm attempting shortly. I was able to complete a full restore of a previous ROM and my phone is now currently booting up as I type this. Hopefully nothing goes wrong, but I've gotten farther now than I have in the past 5 hours I've been glued to my laptop. Time for a cig and beer.
Click to expand...
Click to collapse
Good for you! FYI, I think u can do a wipe through adb (adb wipe) I think. Nothing should go wrong after restoring your nandroid. (BTW, it's not sds.)
P.S. get a good beer and relax.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.

Sadly ...we still can't dump that pathetic Knox bootloader ...yet...but progress is being made...
And if not...we can downgrade and still flash any rom we want...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] SGH-I317 Can't enter recovery mode

I have searched these forums and everywhere else I can find mentioning this problem online, but nothing has worked yet. I'm hoping someone here may be able to point me in the right direction.
I rooted my AT&T Galaxy Note 2 SGH-I317 a couple weeks ago and was messing around and stupidly tried upgrading to 4.3, and now I can't boot and can't enter recovery mode. NOTE: Download mode works just fine, either by manually holding Volume Down/Home/Power or by using a USB Jig, I just can't enter recovery mode by holding Volume Up/Home/Power
I am able to flash just fine with Odin (I have tried version 3.07 and 3.09), it says Pass every time but the darn phone still won't boot and won't let me into recovery mode so that I may clear the cache and get it to boot.
I have tried flashing back to the factory firmware, to which Odin says Pass but still no go on the boot.
I have also tried setting up an ADB connection in Windows 7 (so that I may get the phone into recovery mode without hardware buttons), but since my computer will only recognize the phone when it's in download mode (since I can't boot the phone so Windows 7 will see it like it normally would) ADB won't work.
I'm at my wits end here, does anyone have any clue how I may fix this problem? What's really frustrating is I just bought a Galaxy Gear Watch and about a week later messed up my phone
Thanks, and I appreciate any help you can give me.
EDIT: Forgot to mention something. When I turn the power to the phone on and don't enter download mode, it stays on the Samsung Galaxy Note II screen, and that's all that happens.
Also, this is exactly what my Download screen info says:
FACTORY MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes(6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 1
RP SWREV: A2

Got the phone to finally boot up
I finally got my phone to at least boot up. Although, I still can't get into recovery mode.
I followed this post: http://forum.xda-developers.com/showthread.php?t=2596256 and downloaded this file
It boots, and is currently 4.1.2, however when I try to get to recovery mode, the graphics flicker and the screen goes blank for a couple mins then reboots to the OS.

geekinator said:
I finally got my phone to at least boot up. Although, I still can't get into recovery mode.
I followed this post: http://forum.xda-developers.com/showthread.php?t=2596256 and downloaded this file
It boots, and is currently 4.1.2, however when I try to get to recovery mode, the graphics flicker and the screen goes blank for a couple mins then reboots to the OS.
Click to expand...
Click to collapse
I had a similar issue moving from Jedi to Jedi Master X.
I had to use an older Odin 2.85 to install a CWM recovery(I prefer TWRP UI)
Once I had the CWM I could install Jedi Master X2 and I had to wait about 30 mins for it to get through boot.
I thought I had a good soft brick but eventually I found a combiination of Odin, recovery and Rom to get it to work.
Good Luck

Recovery screen is now up!
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.

geekinator said:
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
Click to expand...
Click to collapse
Update to 4.3 official will fail if you have a custom recovery...
I suggest using the leaked 4.3 we have...
It will give you all of the gear functions....and allow you to keep root and dump the bloat that you don't want...
A best case situation ....IMHO....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...

geekinator said:
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
Click to expand...
Click to collapse
Glad you were able to figure it out... I just had a similar problem because TWRP froze up on me halfway through flashing a ROM. Had to ODIN CWMR back on and flash a ROM... lesson learned... always keep a ROM on your SD card in case your phone soft bricks - if you can get into download mode at least you will be able to work around it!!

I'll give that a try
gregsarg said:
Update to 4.3 official will fail if you have a custom recovery...
I suggest using the leaked 4.3 we have...
It will give you all of the gear functions....and allow you to keep root and dump the bloat that you don't want...
A best case situation ....IMHO....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
Thanks, I'll definitely give that a try.

geekinator said:
Thanks, I'll definitely give that a try.
Click to expand...
Click to collapse
Instead of the leaked you can use the official without locking yourself into the 4.3 bootloader
http://forum.xda-developers.com/showthread.php?t=2589891

hi to all my senior
---------- Post added at 07:25 AM ---------- Previous post was at 07:17 AM ----------
i have problem with my samsung note 2 i317 of white screen of death i tried flashing with many file but no successes it always fail (ODIN) with latest version im able to go to download mode tryed with most of the firmware please help if any body can thankks in adv.
FACTORY MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY:Samsung official
SYSTEM STATUS: Custom
this much it shows on the download mode screen pls help Thanks.

i have problem with my samsung note 2 i317 of white screen of death i tried flashing with many file but no successes it always fail (ODIN) with latest version im able to go to download mode tryed with most of the firmware please help if any body can thankks in adv.
FACTORY MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY:Samsung official
SYSTEM STATUS: Custom
this much it shows on the download mode screen pls help Thanks.

[Q] Rooted Sprint S3 OTA 4.4 stuck on firmware upgrade encountered an issue

Afternoon folks,
I can no longer even get to the Samsung Logo. It boots to what appears to be the download screen and states "Firmware upgrad encountered an issue. Please select recovery mode in Kies and try again." This also shows when I try to boot into the phones recovery screen now.
Kies wont even find the phone when connected and no recovery code is listed...
I have the S3 and it was rooted using Autoroot but no recovery(mistake 1) and this morning I got the notification to do the OTA to 4.4. So in my morning fog I selected to do the update(mistake 2)... all seemed fine and dandy and rebooted and just hung on the Samsung logo.
I have been fighting with this thing half the morning and Odin will recognize it and so I tried to revert back using the L710_SPR_L710VPUCMK3_HOME.tar.md5 file I have from a previous OTA fail going to 4.3 that a buddy helped me get fixed. This problem is a lot worse because I cant even get into the phone whereas last time we could if I recall correctly. Odin gives the Auth fail, and my download screen shows the following:
Current binary: custom
system status: Official ---(currently jacked up really)
Qualcom secureboot: Enable
Warranty Bit: 1
Bootloader RP SWREV: 2
I tried Kies and that says: Error - Device not responding, To resolve the issue, reboot the device.
Please walk a noob through this.. gut feeling Its bricked

Disregard my post please!! Its fixed.
guyver08 said:
Afternoon folks,
I can no longer even get to the Samsung Logo. It boots to what appears to be the download screen and states "Firmware upgrad encountered an issue. Please select recovery mode in Kies and try again." This also shows when I try to boot into the phones recovery screen now.
Kies wont even find the phone when connected and no recovery code is listed...
I have the S3 and it was rooted using Autoroot but no recovery(mistake 1) and this morning I got the notification to do the OTA to 4.4. So in my morning fog I selected to do the update(mistake 2)... all seemed fine and dandy and rebooted and just hung on the Samsung logo.
I have been fighting with this thing half the morning and Odin will recognize it and so I tried to revert back using the L710_SPR_L710VPUCMK3_HOME.tar.md5 file I have from a previous OTA fail going to 4.3 that a buddy helped me get fixed. This problem is a lot worse because I cant even get into the phone whereas last time we could if I recall correctly. Odin gives the Auth fail, and my download screen shows the following:
Current binary: custom
system status: Official ---(currently jacked up really)
Qualcom secureboot: Enable
Warranty Bit: 1
Bootloader RP SWREV: 2
I tried Kies and that says: Error - Device not responding, To resolve the issue, reboot the device.
Please walk a noob through this.. gut feeling Its bricked
Click to expand...
Click to collapse
I fixed the stupid phone, used another post about a issue with the ND8 and downloaded and installed using Odin and it worked.. thank God.

how did you fix
I'm having the same proble, that you had. i sent my phone to Samsung and they would not fix it due to it being rooted. one of my kids rooted it. so im at a lost how to fix it. if you could give me step by step instructions i would greatly appreciate it.
thanks in advance.

dadofas said:
I'm having the same proble, that you had. i sent my phone to Samsung and they would not fix it due to it being rooted. one of my kids rooted it. so im at a lost how to fix it. if you could give me step by step instructions i would greatly appreciate it.
thanks in advance.
Click to expand...
Click to collapse
Hey thanks !!!! I had the same problem trying to go from KK back to JB...Using the ND8 tar file fixed the stuck on firmware upgrade encountered an issue screen..... SUPER THANKS!!!!

dadofas said:
I'm having the same proble, that you had. i sent my phone to Samsung and they would not fix it due to it being rooted. one of my kids rooted it. so im at a lost how to fix it. if you could give me step by step instructions i would greatly appreciate it.
thanks in advance.
Click to expand...
Click to collapse
Here is the post I followed to FIX my same issue. http://forum.xda-developers.com/showthread.php?t=2738533

can you walk me through this
not the most techie type of person...
bruall847 said:
Here is the post I followed to FIX my same issue. http://forum.xda-developers.com/showthread.php?t=2738533
Click to expand...
Click to collapse

which posting did you follow
did you follow the first link in the forum? if so did this restore the phone back to factory settings?
bruall847 said:
Here is the post I followed to FIX my same issue. http://forum.xda-developers.com/showthread.php?t=2738533
Click to expand...
Click to collapse

dadofas said:
did you follow the first link in the forum? if so did this restore the phone back to factory settings?
Click to expand...
Click to collapse
Use the first post. It doesn't take the phone back to factory settings. It upgrades the phone to 4.4. However, it did wipe my system (I had made backups, transfered important stuff onto my external sd, etc). Also, if you have root/custom recovery, you will lose both...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

[Q] Help please Samsung Galaxy S3 unbrick.

Hello Everyone.
Please, I need some help. I was trying to downgrade an ATT Samsung Galaxy S3 from 5.0 to 4.1.1 and try to unlock it.
First, Try to flash with Odin 3.04, Odin 3.07 and Odin 3.09 with the firmware 4.1.1 from Samsung. It always failes.
So I rooted it , installed a team Win Recovery Project 2.6.3.1 and flashed a custom rom based on Android
4.1.2 thinking it will break the bootloader. Nothing.
I tried Emergency Recovery with Kies did not work.
In odin mode:
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcom Scoreboot: Enable
Warranty Bit:1
Bootloader AP SWREV:3
I spent hours on it. I don't know what to do.
Anyone has a idea to help me please?
Thanks you very much in advance.

If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.

audit13 said:
If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.
Click to expand...
Click to collapse
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?

MEEEEEEEE said:
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?
Click to expand...
Click to collapse
If you're on Philz touch, download AROMA file manager and store it on your external SD. You can get it here.
Boot into recovery and flash the file manager like you would install a ROM and it will open the file manager. Once you're up in the AROMA file manager, one of the menu options is to open a console. Once you're up in the console window the following command will tell you what bootloader you have loaded:
Code:
getprop ro.bootloader
That command will work from ADB shell in custom recovery too, if you happen to have ADB and all the drivers set up right on your computer.
What error did you get when flashing with Philz? Was it error 7?

Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?

MEEEEEEEE said:
Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?
Click to expand...
Click to collapse
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.

You may have to try a de-brick image. Status 7 usually occurs when the recovery is out of date.

jason2678 said:
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.
Click to expand...
Click to collapse
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.

MEEEEEEEE said:
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.
Click to expand...
Click to collapse
You did put the battery back in after pulling it for a couple of minutes, right? Looking back at my previous post it was poorly worded.
The fact that you went from working recovery and download to not working on a status 7 is curious. Usually status 7 errors are the developers trying to protect us from ourselves; your recovery is out of date, you are trying to flash a rom that isn't for your phone or doesn't like your bootloader, something like that. When you get a status 7, usually the recovery didn't actually do anything. It failed a safety check and quit. That's what made me wonder if maybe your battery just died.

So you flashed CM11 for the d2lte using the latest version of Philz? Did you flash anything else?

Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.

MEEEEEEEE said:
Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.
Click to expand...
Click to collapse
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"

Yes. The red led is showing when I plugged the device without the battery.
mrrocketdog said:
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse

MEEEEEEEE said:
Yes. The red led is showing when I plugged the device without the battery.
Click to expand...
Click to collapse
pretty positive sign of a brick if thats all you can get. check the link for the "de-brick" thread that i posted. remember that sometimes it takes more than one try , and while one sdcard will work for one phone , it may or may not work for another. just keep trying. good luck.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"

Do I need to get a jig to un-bricked it?

MEEEEEEEE said:
Do I need to get a jig to un-bricked it?
Click to expand...
Click to collapse
nope. read the thread. a de-brick image and sdcard should do it.
"all i can really do , is stay out of my own way and let the will of heaven be done"

A jig would be helpful if the phone boots but you can't get into download mode.

Note 2 stuck at Start Up screen. Please help

My Galaxy Note 2 is stuck at the Start up screen screen. Where its an all black bg and simply says Samsung Galaxy Note II
I have tried using recovery mode, cleared cache, and reset to factory. Neither troubleshoot method worked.
I have tried numerous Odin autoroots. none work. Whenever I try to root it fails. Im guessing it might be because I dont have Dev Debug enable and I cant get into my phone to enable it. because of this issue
I have tried looking for TWRP .tar but every file I download the file is always a .img
The Model of the phone is a SGH-T889 (T-mobile Note II)
I am all out of ideas, and I dont know what to do. I have been search for answers for hours and everytime I think I found a solution it doesnt work.

What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.

ciphercodes said:
What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
Click to expand...
Click to collapse
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin

BramaKnox said:
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
Click to expand...
Click to collapse
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here http://www.sammobile.com/firmwares/download/22863/T889UVUCMK7_T889TMBCMK7_TMB/
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.

I have the same problem as the OP (boots only up to Samsung logo with black bg) but it was not caused by niece downloading games but instead from trying to install jedi masterx2 rom.
I did what ciphercodes recommended and put phone in download mode and odin went through the motions of installing the stock os (in my case version 4.3) but after apparently installing the rom it again booted up to Samsung note II logo in black bg.
luckily I can install either Clockword mod recovery v6.0.4.3 or teamwin v2.8.6.0
The clockword mod recovery can read the external sd card (whereas funnily enough the teamwin can't) and I can attempt recovery from previous backups on cmr or to install a rom from zip file but neither of these work - reboots again to Samsung logo in black background after apparently installing the rom.
both teamwin and cwr mention that they can't mount system and that's probably why no rom is install either using cwr or odin so my guess is that I have to reformat the partitions cause probably efs file is corrupt but I don't know how to do that and I have done extensive search in google but have not found a solution
so ciphercodes if you or anyone reading this can help please reply to this message

ciphercodes said:
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.
Click to expand...
Click to collapse
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.

BramaKnox said:
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
Click to expand...
Click to collapse
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.

koyanishi said:
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
Click to expand...
Click to collapse
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2

BramaKnox said:
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2
Click to expand...
Click to collapse
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox

koyanishi said:
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
Click to expand...
Click to collapse
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*

BramaKnox said:
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
Click to expand...
Click to collapse
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo

koyanishi said:
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
Click to expand...
Click to collapse
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do

BramaKnox said:
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do
Click to expand...
Click to collapse
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.

koyanishi said:
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.
Click to expand...
Click to collapse
Yeah the warranty is expired. and I have tried recovery mode. thats actually the first step before trying to apply a firmware. So recovery hasnt worked either. Guess I will just have to get a new phone. thank you all for oyu help tho. I apperciate it

I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..

Double0EK said:
I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..
Click to expand...
Click to collapse
From my knowledge the other person who first replied gave me 4.3 firmeware fild link. But in the chances of it could u provide me with a link to a 4.3 firmware u believe will work, because all the ones I found have not worked