[Q] Recovery Loop using Kingo - T-Mobile Samsung Galaxy Note II

Hi there
I have a 900W8 note 3. I upgraded to the newest firmware via kies. it worked perfectly then i wanted to root it.
Instead of using Odin i used Kingo and now my phone is stuck on a recovery loop.
I try and access recovery up+home+ power and nothing happens it simply keeps looping
I can access download down+power+home.
any suggestions how i can get out of this?
Do download the latest version of Odin and select PDA of the recovery? and leave all other settings intact?
currently i am downloading sammobile.com firmware for my phone
Thank you!
I just noticed i posted this under note 2. i do apologize

MacProoo said:
Hi there
I have a 900W8 note 3. I upgraded to the newest firmware via kies. it worked perfectly then i wanted to root it.
Instead of using Odin i used Kingo and now my phone is stuck on a recovery loop.
I try and access recovery up+home+ power and nothing happens it simply keeps looping
I can access download down+power+home.
any suggestions how i can get out of this?
Do download the latest version of Odin and select PDA of the recovery? and leave all other settings intact?
currently i am downloading sammobile.com firmware for my phone
Thank you!
I just noticed i posted this under note 2. i do apologize
Click to expand...
Click to collapse
I got into the SAME situation with my Note 2 when i tried to use goomanager (BOOOOO!!!) to install either CWM or TWRP (cant remember which now).
I downloaded the correct stock rom for my device from sammobile and used Odin to flash it to my phone and everything came good.
God knows what happened with the goomanager business - perhaps I was supposed to make some obvious selection in goomanager like clearing caches or some damned thing - the tech geeks who put instructions together tend to miss "obvious" steps sometimes. "Make sure you're familiar with rooting etc." often means "make sure you know enough to not get screwed by steps we miss out in written instructions because to us they're obvious"...

Wobosh said:
I got into the SAME situation with my Note 2 when i tried to use goomanager (BOOOOO!!!) to install either CWM or TWRP (cant remember which now).
I downloaded the correct stock rom for my device from sammobile and used Odin to flash it to my phone and everything came good.
God knows what happened with the goomanager business - perhaps I was supposed to make some obvious selection in goomanager like clearing caches or some damned thing - the tech geeks who put instructions together tend to miss "obvious" steps sometimes. "Make sure you're familiar with rooting etc." often means "make sure you know enough to not get screwed by steps we miss out in written instructions because to us they're obvious"...
Click to expand...
Click to collapse
Seeing that boot loop gave me a heart attack. I flashed recovery and it worked.
Thank you so much!!!
NEVER USE KINGO !!!

Related

[Q] I've messed up terribly. Galaxy S4 Odin firmware flash went wrong.

Okay, so I rooted my phone back in December and had no problems at all with firmware 4.3. I had this app called "Clean Master" I think, so it analyzed my device to clean up "unnecessary" files and such. I go ahead a clean whatever it had "cleaned" and then I noticed that when I went into settings that it started freezing for about a minute or so and had to force close the settings. It also started to restart randomly at times and it got to the point where I just got fed up and looked to the internet. I decided to use Odin to Unroot my phone because at the time that's what I thought was causing the problem. This is where I think (I know) I screwed up. Instead of flashing the stock firmware for the T-Mobile Galaxy s4 I flashed this "GT-I9500-XSE-I9500XXUAME1-ROOTED_MAY4". I think I used this file for rooting but I downloaded so many files to get the rooting to work that I don't remember. This file is neither an .md5 file nor a .tar file. I don't know what I was thinking and I regret the decision. I started the transfer of whatever file that was to my phone using the Custom ROM download screen, and it only took about 4 seconds and said it passed. It reboots but ever since has been stuck on the Samsung Galaxy s4 screen. Recently it now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I've tried connecting the device via Kies but IT DOES NOT CONNECT. I'm beginning to think that I've just completely destroyed the phone and will be needing to by another. Any help would be much appreciated. I've tried everything I know. I've wiped the cache, wiped the data and factory reset the phone, but it won't reboot correctly. I'm stuck people. What can I do?
Can you get into download mode?
Sent from my SGH-M919 using XDA Premium 4 mobile app
The Sickness said:
Can you get into download mode?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can get into download mode yes.
re:
NEKTAR11 said:
I can get into download mode yes.
Click to expand...
Click to collapse
#1: Find the Odin flash rom/firmware for your phone and load Odin with it.
#2: Put the phone into download mode.
#3: plug usb cable into phone and computer.
#4: after you see [COM:xx] light up click START in Odin.
#5: when it gets done flashing let it reboot, have patience.
Forget all about these cleaning utilities, you can do all the cleaning
you want once the phone works properly and once it's rooted.
Only use CF-Autoroot to root the phone for best and trouble free results.
Here is the direct download link for CF-AutoRoot:
http://download.chainfire.eu/328/CF-Root1/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
Good luck!
Misterjunky gives good instruction, if you can get into download mode your phone can be resurrected. In my early days of flashing, I thought I had created an expensive paperweight but the guys on here saved me. One thing, you may have to do a factory reset in stock recovery to get your phone to boot. Happened to me a couple of times.
Good luck.
Flash until you brick!
Ok, so I'm pretty sure I have the right Odin flash firmware, but it all goes really fast and after "aboot.mdn" it stops and it says FAIL. Ok so I tried the md5 file that came with the download and it went through fine, but It's still stuck on the Samsung Galaxy S4 screen. Do I need to restart the system now and try the firmware file?
NEKTAR11 said:
Ok, so I'm pretty sure I have the right Odin flash firmware, but it all goes really fast and after "aboot.mdn" it stops and it says FAIL. Ok so I tried the md5 file that came with the download and it went through fine, but It's still stuck on the Samsung Galaxy S4 screen. Do I need to restart the system now and try the firmware file?
Click to expand...
Click to collapse
Have you done a factory reset?
Sent from my SGH-M919 using Tapatalk
serio22 said:
Have you done a factory reset?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I've done it more than I can count, yes.
re: do this next.
NEKTAR11 said:
I've done it more than I can count, yes.
Click to expand...
Click to collapse
Flash this TWRP custom recovery in ODIN then go into recovery mode and
do a full wipe, data, system, dalvik cache, cache and do a Factory Reset.
Here is the direct download link for the Odin flash TWRP recovery:
http://techerrata.com/file/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Once that's done go into download mode and flash the
stock official M919 4.2.2 firmware (tar/md5) file.
Good luck!
SO I went into recovery mode, but it stays on the "teamwin" screen.
Pull the battery out of the phone, then put it back in and try to boot into recovery again. Sometimes, the recovery will hang like you described. You might have to repeat this process again and again until you get into the main menu of the recovery.
Okay, so I'm sure I'm doing everything right. I flashed the twrp recovery it restarts my phone. I held the power key, home key, and up key on the phone and released the power button when it shows the text on the top left showing that it is going to start recovery. It goes to a "teamwin" screen but freezes there. Truthfully, do you think I will be able to recover my phone, or will I need to send it in to samsung and pay 70 dollars plus the damages?
Misterjunky said:
Flash this TWRP custom recovery in ODIN then go into recovery mode and
do a full wipe, data, system, dalvik cache, cache and do a Factory Reset.
Here is the direct download link for the Odin flash TWRP recovery:
Once that's done go into download mode and flash the
stock official M919 4.2.2 firmware (tar/md5) file.
Good luck!
Click to expand...
Click to collapse
Do you think the reason why I can't flash the firmware is because I upgraded to 4.3 and it brought KNOX onto the phone?
NEKTAR11 said:
Okay, so I rooted my phone back in December and had no problems at all with firmware 4.3. I had this app called "Clean Master" I think, so it analyzed my device to clean up "unnecessary" files and such. I go ahead a clean whatever it had "cleaned" and then I noticed that when I went into settings that it started freezing for about a minute or so and had to force close the settings. It also started to restart randomly at times and it got to the point where I just got fed up and looked to the internet. I decided to use Odin to Unroot my phone because at the time that's what I thought was causing the problem. This is where I think (I know) I screwed up. Instead of flashing the stock firmware for the T-Mobile Galaxy s4 I flashed this "GT-I9500-XSE-I9500XXUAME1-ROOTED_MAY4". I think I used this file for rooting but I downloaded so many files to get the rooting to work that I don't remember. This file is neither an .md5 file nor a .tar file. I don't know what I was thinking and I regret the decision. I started the transfer of whatever file that was to my phone using the Custom ROM download screen, and it only took about 4 seconds and said it passed. It reboots but ever since has been stuck on the Samsung Galaxy s4 screen. Recently it now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I've tried connecting the device via Kies but IT DOES NOT CONNECT. I'm beginning to think that I've just completely destroyed the phone and will be needing to by another. Any help would be much appreciated. I've tried everything I know. I've wiped the cache, wiped the data and factory reset the phone, but it won't reboot correctly. I'm stuck people. What can I do?
Click to expand...
Click to collapse
Are you sure some other people have tried this file on a t-mobile variant? because GT-I9500 is indeed for a galaxy s4, but it's for the octa chipset, which is completely different from the t-mobile variant of the s4 since the t-mobile version is similar to GT-I9505, which is a quad core instead of a octa core
Just to give you guys a heads-up, I fixed my phone, but not by the ways you guys suggested. Not that I'm ungrateful, I am very happy you all took the time to help me out and I appreciate the suggestions. Thank you so much.
Oh and I fixed it by going into kies, clicking on "tools", "firmware upgrade and initialisation", and proceeded to follow the steps and type in my Model name and Serial Number.Fortunately they had the ability for my phone to return it COMPLETELY stock.
Thank you!
NEKTAR11 said:
Just to give you guys a heads-up, I fixed my phone, but not by the ways you guys suggested. Not that I'm ungrateful, I am very happy you all took the time to help me out and I appreciate the suggestions. Thank you so much.
Oh and I fixed it by going into kies, clicking on "tools", "firmware upgrade and initialisation", and proceeded to follow the steps and type in my Model name and Serial Number.Fortunately they had the ability for my phone to return it COMPLETELY stock.
Click to expand...
Click to collapse
OMG thank you for this. I actually registered just to thank you for this, I thought I was totally boned.

[Q] galaxy s3 I747 wont boot past Samsung Galaxy s3 Logo, Did i brick my phone???

I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.

[HELP!] Odin Firmware flash failed at hidden.img. Stuck in DL Mode. T700. Plz Help Me

Hi Everyone,
I am a new owner of a soft-bricked SM-T700. I am feeling very down and need some advice. I will be as thorough as I possibly can and I would truly, truly appreciate some help and advice from you kind folks. This is the first time I have had a bricked device out of my many Android devices.
My PLAN:
-Root
-Custom Recovery
-Nandroid Backup
-Backup EFS
-Flash stock western country firmware
What HAPPENED
Today I bought a wifi T700. I bought it in my hometown, which is China. Whenever I buy a new Android device in China my first action is to ensure it doesn't have any hardware/warranty issues. I then go about reflashing a western firmware so I can use Google services.
1) First I rooted using CF-Auto Root. That worked fine. I confirmed that I had root using an app called root checker.
2) I then attempted to flash TWRP recovery by following the instructions here: http://teamw.in/project/twrp2/238
- First I tried flashing the .tar file using Odin. As soon as I hit 'Start' Odin froze and I got the Windows error saying "Odin Downloader Has Stopped Working", asking to close the program. I close the program. I tried this several times then rebooted. It seemed as though the phone booted fine.
- I then tried using their own software, TWRP manager, here: http://jmzsoftware.com/twrp-manager-4. This app just crashed every time I booted it. I submitted an error log.
- I then tried using 'Flashify' as suggested by someone here on XDA. Once I did that it said flashed successfully and would I like to reboot. I said yes. This is when my troubles started.
3) Upon reboot it immediately booted into a sparse looking 'Download Mode' screen, all in English (the normal one on mine has some Chinese too) without the volume button options to reboot or continue. It just went straight into this screen.
After trying to reboot the phone using several power button holds and key combinations, it appears I am stuck in this screen, so I thought I had no chance of doing a NADROID backup as originally planned, so I decided to try my luck and flash the western firmware.
I tried to flash the version of the firmware provided here: http://forum.xda-developers.com/showthread.php?t=2798835
http://www.androidfilehost.com/?fid=23501681358556680
It got all the way through the install until it hit the hidden.img and then failed. I've attached a screen capture.
A few notes;
I have tried using two different USB cables (the one that came with it, and the one that came with my HTC One). I have tried several USB plugs, including the one in the back of my PC. I allowed Odin to do it's MD5 check and it said the file checks out.
I have tried using the Kies emergency Firmware recovery. Pffft! As it that was going to work. Damn Kies.
I sound like I've still got my sense of humor, but actually I am really cut up about this. It is so much money for a tablet and now it is useless unless I can get s firmware that will flash.
I don't have my stock Chinese firmware. That is T700ZCU1ANF4/T700CHN1ANF4/T700ZCU1ANF4/T700ZCU1ANF4 (CHN).
Questions:
Does anyone know where I could find the stock Chinese firmware to try flashing back to that?
Does anyone have the .PIT file and instructions on how to flash that, because I have read in other threads that it solves the hidden.img problem.
Does anyone know why this may have happened and have any alternative suggestions?
Could it have been the TWRP that actually caused this? The thread here indicates others aren't having trouble. Why would it have frozen for me?
I will try anything at this point. I am desperate.
Thanks so much in advance. Please come through XDA! Please come through Galaxy Tab S owners!!!!!!
-------------------------------------------
CLOSURE EDIT: I managed to flash Australian firmware, after reinstalling Kies, uninstalling and reinstalled the device drivers. I also made sure all Kies processes were killed before flashing with Odin.
For people in a similar situation I would urge them to have patience and keep trying to flash stock firmware.
Private Message UpInTheAir and see what he thinks.
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
The program crashing is when you should back off from trying to flash. Reassess what you did and what happened and if it's failing at a point flash the stock back before rebooting.
Continuing blindly was the problem. On something as expensive as a tablet never continue past a point where something goes wrong without reflashing back to stock and starting again.
As eousphoros said Use heimdall and flash a recovery.
Good luck.
eousphoros said:
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
Click to expand...
Click to collapse
Hi All,
Thanks for taking the time to reply.
You are certainly right that it is my fault and I should have stopped at some point and reassessed what was happening.
Can you please give me some more information about the steps you have offered? I am researching heimdall now, but if you could give some steps or advice that would be much appreciated.
It's probably going to be difficult because I assume we are in different timezones. I will persevere and try to get this worked out.
I have downloaded Heimdall and understand that it is an alternative to using Odin.
I currently have three questions about Heimdall.
1. Do I need to do the install drivers step if I have already installed the drivers for my device? Is this some step that actually replaces the current drivers with ones that are required for Heimdall to operate? I ask them because when I list USB devices, my tab is not shown up as Samsung Composite Device. It is actually shown as two separate entries, looking like generic USB entries.
2. Do I need to have a valid PIT file in order to run a custom Heimdall flash?
3. Which partition should I select if/when I run the Heimdall flash?
I'm dying a little inside every time I look at my tablet
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
eousphoros said:
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
Click to expand...
Click to collapse
First of all, let me just say that OH MY F#@$ING GOD I THINK THE NIGHTMARE IS OVER!!!! I managed to flash the Australian Firmware successfully. It has now booted fine, I have factory reset and I am in the process of setting up the device afresh.
Having said that, when I do come to reroot and install a custom recovery, I will definitely take a look at yours. Was this here 12 hours ago? I looked and couldn't find anything about CWM except for a short thread and an unofficial port. I have never tried TWRP before and I will avoid it like the plague in the future. I have NEVER had trouble with CWM.
When (if ever) I get the nerve up to give this another go, I will try your CWM.
Thanks again.
I am so relieved right now.....
And make a Nandroid first this time
Hey,
I had the exact same issue with my Galaxy Note 8, every time I tried to install European or custom Rom.
The only way to get the tab back was to flash with the Chinese firmware. You may find it easily on Baidu.
Since it happened also with a note 2 and note 3, I stopped buying Android device in China... Unless you can make sure that you buy a model coming from HK.
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
ky3bmu4 said:
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
Click to expand...
Click to collapse
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
ky3bmu4 said:
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
Click to expand...
Click to collapse
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
pierrotee said:
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
Click to expand...
Click to collapse
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
ky3bmu4 said:
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
Click to expand...
Click to collapse
Cool! So do you now have root and custom recovery?
pierrotee said:
Cool! So do you now have root and custom recovery?
Click to expand...
Click to collapse
Yeah))
TWRP installs OK via TWRP Manager
I installed TWRP Manager, selected 'klimtwifi' as the device, and it successfully installed TWRP 2.7.1.1 without a hitch.
From TWRP I then immediately performed a nandroid backup of everything but the caches to my microSD card and encountered no problems.
The last step was to enable writing to my microSD card by installing NextApp SDFix.
My SM-T700 is bricked as well and I tried to flash a custom recovery with Heimdall on Mac but it gave me the Error "Claiming Interface failed". Seems like you really need the pit.

[Q] N7100 stuck at boot screen after flashing stock 4.4.2

Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
I am having similar problem.
Tried to flash the TWRP Recovery from THIS via Odin.
Still phone isn't going past the Galaxy Note II logo.
Sidz4u said:
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
Click to expand...
Click to collapse
Thanks for the reply.
It processes OK and Odin says 'Pass!', but then it automatically restarts and gets stuck at the boot screen again. Still can't boot into recovery mode.
AliverMD said:
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried that, but unfortunately it just does the same thing ....
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
devrog17 said:
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
beardyweirdy said:
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
Click to expand...
Click to collapse
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
devrog17 said:
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
Click to expand...
Click to collapse
Just tried, but to no avail again. Thanks anyway. Anybody else got any suggestions as to what I might try? I'm starting to lose hope a bit here
Try to boot in recovery and do a factory reset
devrog17 said:
Try to boot in recovery and do a factory reset
Click to expand...
Click to collapse
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
C
beardyweirdy said:
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
Click to expand...
Click to collapse
Just to close this thread off, I've now paid to get the phone sorted at a local shop. Took them a while (think their first level support just tried all the things I'd already done), but their occasional staff member and all round guru managed to get it sorted. I don't know what he did as I didn't get the chance to speak to him. Cost me £30.

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

Categories

Resources