Database Develop

[Q] Captivate Soft Brick - Need a rooted Odin solution.

Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.

if he can access recovery, try wiping everything thru recovery then start again

Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.

What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)

@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.

You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.

REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament

Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others

- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.

viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App

Bet this can't be fixed

No firmware and USB problem
I have a large problem, my wifes galaxy s won't go by the first screen (says GALAXY S GT-I9000)
So i thought i'd fix it using odin using the 3 button combo. But that isn't working anymore.
Luckily i have a usb jig which gets me to the download mode ...... but !
When i connect the pc cable (tried 2 OE samsung ones) i get device not recognized so i can't use odin to fix it.
What can i do, or do i have to send it to a repair centre to be resurrected ?
I have searched and searched but not found any topics with the same issues i have on her phone.

Need a bit more info i.e were you flashing the phone??if so which rom?

Then phone was playing up so i flashed darkys 10.4.2.
However the usb connection wouldn't work so i flashed it to standard JVT
using mobile odin.
Then i rooted it and went to go into recovery mode and it wouldn't turn on.

I tried to help the gentleman , but no luck . From what he told me , phone turns on after battery insertion , and It is not recognised by usb => so odin not usable .

If you can get to download mode but the phone isn't recognized by your computer then i'd say it's a driver issue. Install your phone's drivers again. To do that, just installing kies is enough BUT be sure to open task manager in windows and kill any process that has kies in it's name before opening odin.
If that still isn't flying i'd try using different USB ports and even with a different computer.
Extra advice:
- try not to flash bootloaders for now. That means picking a rom that has no bootloaders included but matches your phone's current bootloader. If you were using gingerbread flash a gingerbread rom, if you were using froyo, flash a froyo rom.

phone not starting up past first screen (GALAXY S GT-I9000 in white on black screen), phone not recognized neither by pc nor laptop ( usb drivers installed ) , phone turns on after battery insertion without pressing anything.

This manual is from a German board
Take the battery out, then hold the 3 keys combo for download and put the battery back on. Now you should start the download mode.
If not, then try it with a jig.
Good luck!

GOT A JIG. WORKS FINE.
But pc wont recognize it !!

Have you double checked that you have the right drivers installed? I know you have to use the Nexus S drivers for CM9, not sure about Darky's ROM.

Drivers
Download drivers 64 bit | 32 bit from here and install.

It is NOT the drivers as my other galaxy s connects fine every time.
Drivers have been removed and installed repeatedly.

I would suggest a different computer, maybe a different cable. I have this same issue with my infuse, hope you get this resolved.
Sent from my Desire HD using XDA App

Already tried that as well

You could try Adam outler's unbrickable mod.

Pasted from other thread:
I just wrote a wall of text b4 and my browser crashed GG
Well, here we go again, i will only tell what I did/the process
I did a nandroidbackup, then i wiped all data (data+cache+dalvik), installed CyanogenMod 9 (Build 16), it rebooted automaticly, so I entered recovery again, installed Google Apps from there, wiped data and cache (no dalvik), rebooted.
Ended up looping at the Samsung screen (not animation), and I couldnt do the 3-button-combo, so the NANDroid backup is useless.
I can enter the download thing, but i dont even know what it does.
Tried plugging it in the charger (after letting it dry out during the night), and only the loop thing appears. Cant do anything.
I see that theres something called odin (Since my download thing is working (VolDown+Home+Power) if its that you mean.
If its possible to fix my phones state, please tell me how, since I startedrooting, flashing and stuff yesterday (Gotta start at some point) and followed HDTechVideos tut (On his website)

woolf clubs said:
You could try Adam outler's unbrickable mod.
Click to expand...
Click to collapse
I have nowhere near enough ability for that. Pity though.

Your problem is most likely the USB port. Maybe cleaning it might help. It happened to me for a few months then when I got the S2 I stopped using it. Began to use it as my home 3g wifi modem and kept it on charge the whole time. A few weeks later tried connecting it to the computer and it worked first go. Ever since it has worked perferctly. I suspect the problem possibly started by a rain drop getting into the port.
Mind you, even when it wasn't being recognised by the PC, I would constantly connect, remove, reconnect, reboot PC and phone etc and it would sometimes get recognised. Other times it wouldn't connect but Odin still recognised it.
Sounds silly but try leaving it on charge as I did and maybe, just maybe you'll be lucky like I was.
Sent from my GT-I9100T

Well as of today it is away to the O2 repair centre.
Its under warranty (unless the find out it was rooted etc) so fingers crossed.

Well had a text back today to say my phone has been despatched, so here is hoping that its fixed.

It came back from the repair centre yesterday with a note saying a part had been replaced,
no costs for me, yippeeeeeeee.

[i9000b] BSOD - Phone ! Computer Screen

I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.

If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.

KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below

k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.

I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]

KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah

Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!

KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help

[Q] After rooting phone is not starting, please help...

Hi,
I have Samsung Galaxy S I9000 running Ginger Bread.
I wanted to upgrade my phone to Ice Cream Sandwitch or Jelly Beans. In order to do it, I started with below steps to root my mobile.
1. Installed latest Clockwise Mode application into my phone.
2. Installed Odin3 v1.7 in my laptop.
3. Downloaded CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1.tar on my laptop.
4. Started Odin first.
5. Disconnected mobile and started in download mode with Volume Down + Home Button + Power Key.
5. After starting the download mode, connected mobile to laptop using the USB.
6. Keep all the default values in Odin3 i.e. Re-Partition option unchecked, Auto Reboot and F-Reset Time option enabled. Selected tar file CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1.tar in PDA option.
7. Connected mobile and it detected ID Comm [Highlighted in Yellow].
8. Finally click on Start button.
After starting the process was completed and Yellow color changed to Green one, phone was auto reboot.
But after reboot it is just stuck on start of screen and not going ahead. I wait for 2 hours but still not working.
Could you please help me how I can solve this issue now?

Did you try to pull battery out and restart the phone again?
Do you still can go in CWM with 3 button combo again?
If yes then try to flash a ICS or JB kernel (depending on what ROM you finally want to have on your phone) via CWM and then go in advanced and restart recovery (if available), otherwise just try to flash the rom.zip on top.
If CWM is not possible, the go in download mode an falsh a tar version of kernel via ODIN.
Here are different semaphore kernels for each android version:
http://78.46.194.137/downloads/gt-i9000-ics
http://www.semaphore.gr/downloads/gt-i9000-jb
For ics it should work after 1. flash, but for JB you have to flash it 2 or even 3 times, if after restart phone does not boot. Then battery out again, start in recovery and flash zip again.
Good luck and good success .

I think, at this position, installing a new gingerbread stock ROM will be preferable. Try installing XXJVU. Then root with cwm and install any slim bean version in case you are interested to use jelly bean.
Sent from my GT-I9000 using xda app-developers app

Sure that will be the best way....but my suggestions do not take much time, so why not give them a try .
But if its not going, then a restock is the best you are right:
What I always do for restock is using slappys rescue kit.
Unzip it and flash the Rom via Odin. There is everything, also a txt file with a guide included.
http://forum.xda-developers.com/showpost.php?p=29114573&postcount=2
If you want to have slim rom then its recommended to flash CM9 first or flash a modem afterwards via cvm, because slim does not have a modem included.
And/Or just follow the installation guides/recommendations from the single ROM Threads.

Thanks Guys for your help.
My issue is resolved with below post.
http://forum.xda-developers.com/showthread.php?t=1809098

phone not starting
guys i cant start my phone....even the three buttons ar not working...it is just loading and loading....help please
model-gt-s5830i

viral1999 said:
guys i cant start my phone....even the three buttons ar not working...it is just loading and loading....help please
model-gt-s5830i
Click to expand...
Click to collapse
You are here in totally wrong section: this is a i9000 help thread section. Hopefully you didn't flash a i9000 rom, otherwise your phone is hard bricked.
tetakpatalked from Nexus 7 flo

Me 2: It was from low battery in my case
I had similar problem when rooting my Samsung Galaxy S5 smartphone with Odin3. After rooting with a success message my phone was showing just the Samsung Logo each time I was trying to turn it on without loading OS. I googled and directed here and connected my phone to the charger as its mentioned in a link you provided which solved your problem. It turned on automatically after a few minutes while of charging and when turned on it was charged approximately 40%.
As I was very afraid my phone got serious harm at first I hope this maybe a sedative probability for duds really worry about what happened to their smartphone.

I rooted my phone le tv without pc bt after rooting it is not starting pls help me how to start my mobile again

Imbhavya said:
I rooted my phone le tv without pc bt after rooting it is not starting pls help me how to start my mobile again
Click to expand...
Click to collapse
What exactly did you do, which phone model and what does it display now?
Sent from my A0001 using Tapatalk

Note 4 Dead after Update won't power on

I recently did the latest update to my T-mobile Note 4 upon updating the phone, the phone was in a constant boot loop and finally installed the update to the device. Upon installing the new software update to the phone it began the reboot loop and eventually started up I received one text message and it began to loop again and now it will not turn on. None of the button combinations will turn the phone on it is not accepting a charge either. I put the battery in another note 4 and it works fine and shows 79 percent of the battery is charged. What can be done to get the phone to wake up out of it's current state most of the pictures were salvaged with drop box, but it did not update from a family funeral yesterday with several pictures and those are important. Has anyone had this issue before and what was done to fix it?

nigafied45 said:
I recently did the latest update to my T-mobile Note 4 upon updating the phone, the phone was in a constant boot loop and finally installed the update to the device. Upon installing the new software update to the phone it began the reboot loop and eventually started up I received one text message and it began to loop again and now it will not turn on. None of the button combinations will turn the phone on it is not accepting a charge either. I put the battery in another note 4 and it works fine and shows 79 percent of the battery is charged. What can be done to get the phone to wake up out of it's current state most of the pictures were salvaged with drop box, but it did not update from a family funeral yesterday with several pictures and those are important. Has anyone had this issue before and what was done to fix it?
Click to expand...
Click to collapse
A few questions I would ask to be able to help would be:
Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?
Are you rooted or stock?
When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.
If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.

Modzilla44 said:
A few questions I would ask to be able to help would be:
Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?
Are you rooted or stock?
When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.
If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.
Click to expand...
Click to collapse
All stock the last update performed was for that security hole android had on the android 5.1.1. What I mean is that during the install the phone kept restarting and restarting and then it installed the updates and went to the home screen. When it reached the home screen it showed me one text and I went on charging the phone thinking it was normal woke up this morning the phone was off yet the battery still has 79 percent when placed in another note 4 phone. I tried plugging into the pc the phone isn't recognized because it does not turned on it says unrecognizable usb device and I installed the latest samsung drivers as well I've tried those button combinations as well as pulling the battery. I'm wondering if the update corrupted something prohibiting it from booting it doesn't take a charge either when connected to the wall it's almost like the phone is in a stale state.

nigafied45 said:
All stock the last update performed was for that security hole android had on the android 5.1.1. What I mean is that during the install the phone kept restarting and restarting and then it installed the updates and went to the home screen. When it reached the home screen it showed me one text and I went on charging the phone thinking it was normal woke up this morning the phone was off yet the battery still has 79 percent when placed in another note 4 phone. I tried plugging into the pc the phone isn't recognized because it does not turned on it says unrecognizable usb device and I installed the latest samsung drivers as well I've tried those button combinations as well as pulling the battery. I'm wondering if the update corrupted something prohibiting it from booting it doesn't take a charge either when connected to the wall it's almost like the phone is in a stale state.
Click to expand...
Click to collapse
Have you tried installing Kies on your PC to see if it can detect it? I believe it has a couple special options for detecting and repairing corrupted stock updates. http://www.samsung.com/us/support/owners/app/kies

Modzilla44 said:
Have you tried installing Kies on your PC to see if it can detect it? I believe it has a couple special options for detecting and repairing corrupted stock updates. http://www.samsung.com/us/support/owners/app/kies
Click to expand...
Click to collapse
I haven't tried kies I tried smart switch though and the phone wasn't detected I'll try kies as well. I'll be back with an update appreciate the help.

Kies didn't work because the phone can't be recognize by the program the computer makes a noise knowing when the phone is connected but the screen on phone doesn't turn on I can't even get it to boot up or accept a charge and the battery is nearly full given that I put it in another phone to check. I've tried even starting the phone up with no battery using direct charger as primary source but it didn't work. I'm not sure how the update fried my phone, but I'm going to be losing some important pics drop box didn't sync yesterday during a family funeral.

That is just really ****ty luck. They say there is always a small chance that flashing anything can cause epic partition disasters. If kies is detecting it but saying it's unable to connect then I'd say the phone is toast. You might be able to get Odin to recognize it and reflash the entire ROM, but that would obviously destroy any data you had on the device previously. Might look into doing an adb pull or backup but being realistic with expectations, I'd say the chances of them working considering what you've done is minimal.
Since you're on stock anyways I'd just go warranty exchange it if you can. Not worth dicking around with Odin if you are stock.
Sorry I couldn't be more help but I would take this opportunity to seriously get yourself a cloud based automatic backup so you don't have to worry about these things anymore. I had something similar happen to me and I lost all my data and now it all syncs to my ex_sdcard and Dropbox haha..can never be too sure
Sent from my SM-N910T using Tapatalk

Yeah I never flashed anything it was an over the air update basically that went bad. The last time I flashed software using odin I didn't lose any of my information it stayed on the internal memory and was there still. It truly is sad they roll out an update over air and it bricks your phone makes no sense.

Modzilla44 said:
A few questions I would ask to be able to help would be:
Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?
Are you rooted or stock?
When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.
If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.
Click to expand...
Click to collapse
I have gotten the phone to turn on randomly it turned on and is now regularly turning on however it is still in a bootloop will not allow me to enter recovery I can enter custom OS have tried to root but it flashes and does not stick with phone for the custom recovery I'm not sure what I can do now that the phone turns on any suggestions?

When trying to root or enter recovery I get recovery is not Seandroid enforcing set warranty bit recovery and boot loop

Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
Sent from my SM-N910T using Tapatalk

Modzilla44 said:
Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I have a t-mobile 910T note 4. I will try kies again not sure what my bootloader is or was I'm just trying to do what ever i can to preserve the data on phone will flashing stock again delete the internal I know with root with my other note 4 it didn't. This phone was never rooted the over the air update boot looped the phone

I would definitely try using kies or even adb from command to see if you can pull the data from it. Flashing a full firmware will wipe all data Yeah so I'd use that as a last resort
Sent from my SM-N910T using Tapatalk

Not to sound stupid what's an adb command

Modzilla44 said:
Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
On this forum I have found just the bootloader available to down load if I download the full rom is it going to wipe the internal memory here is the link I'm referring to http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I think I might have it figured out just need clarity on if flashing just the bootloader will do the trick I also got a set warranty kernel on boot last time as well.

If it were me I'd install the following:
Twrp custom recovery : https://www.androidfilehost.com/?fid=24052804347792887
Make sure you have latest drivers from Samsung. Flash twrp and see if you can boot into recovery and then either wipe cache or flash a bootloader zip from there. At the very least you could pull files from it once in recovery
Sent from my SM-N910T using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:10 AM ----------
If that doesn't work then I'd read this guide on adb setup and commands. It seems daunting at first but incredibly useful
http://forum.xda-developers.com/showthread.php?t=2225405
Sorry I'm a bit short on explanation I'm just short on time. If you need anything more specific in terms of clarification don't hesitate to ask.
Sent from my SM-N910T using Tapatalk

I would visit your local tmobile store and have them look at it. Besides smartswitch they have a program they can run and possibly restore your phone before it gets totally borked up.
This could help justify rma with Samsung.
Pp.

My phone was dead. I used the original note 4 cable and it worked like a charme was able to odin to stock (new firmware) and root. I dont see any way out other than loosing all data
Sent from my SM-N910T using Tapatalk

This is what I see when I flash the root or recovery every single time. I know if I can get the recovery on the phone I can get the pictures on to my pc because I had a phone that was android locked that I did myself and rooted recovery and was able to get the pc to see and transfer files to pc so why is it showing this image am I doing something wrong?

PanchoPlanet said:
I would visit your local tmobile store and have them look at it. Besides smartswitch they have a program they can run and possibly restore your phone before it gets totally borked up.
This could help justify rma with Samsung.
Pp.
Click to expand...
Click to collapse
They don't have that machine any more I use to work at t mobile that machine was a joke by the way I'll be able to get a replacement it's the funeral pictured that are most important to me they didn't sync to drop box for some reason and that's my main reason for trying to get the phone working. I've flashed everything I've been told to flash I still get the boot loop and the stupid se android reinforcing set recovery or set kernel etc currently it's recovery if I try to initiate recovery via the buttons it just boot loops