Develop Bugs

help - I did something bad

I know I didn't brick my phone because I can still get into bootloader. I've tried to connect to Odin (several times following instructions to remove battery, restart pc, etc) and Odin won't recognize phone in bootloader. I was trying to update to gingerbread 2.3.5 using Odin and it got stuck. it said 'writing, wait 2 minutes' and I waited 8 mins and it never did anything. was I just inpatient? Now when I try to restart my phone it tells me manual files were installed and to hit the OK button. I have no OK button and I've tried all the screen buttons and the 3 hardware buttons to select 'reboot' as instructed per the phone and none work. So I pull the battery and start the vicious cycle all over again. I've been searching and searching (for the past 2hrs) trying to solve this on my own and I'm stuck. I need this phone as it's my work phone and I just got it Friday! (owned by me, not my company thankfully!) please help. thank you.

lol looks like u got urself a sweet paperweight haha. 1st of all make sure u have all the drivers installed, secondly it might be ur usb cable too

klyang88 said:
lol looks like u got urself a sweet paperweight haha. 1st of all make sure u have all the drivers installed, secondly it might be ur usb cable too
Click to expand...
Click to collapse
I could previously connect to Odin so I wouldn't think it was the drivers or the cable. I hope I didn't really brick it! I can't afford a new one! booo

nursemm05 said:
I could previously connect to Odin so I wouldn't think it was the drivers or the cable. I hope I didn't really brick it! I can't afford a new one! booo
Click to expand...
Click to collapse
have u tried a different usb plug in hole?

Pulling the cable on a Odin flash is the quickest way to ruin your phone. Should have left it plugged in and looked around real quick for an answer.

klyang88 said:
have u tried a different usb plug in hole?
Click to expand...
Click to collapse
I have and another computer. still no luck. Won't recognize it.
tenaciousj said:
Pulling the cable on a Odin flash is the quickest way to ruin your phone. Should have left it plugged in and looked around real quick for an answer.
Click to expand...
Click to collapse
doesn't help to tell me what I should've done. Is this fixable or not?

nursemm05 said:
I have and another computer. still no luck. Won't recognize it.
doesn't help to tell me what I should've done. Is this fixable or not?
Click to expand...
Click to collapse
if u can still get into odin mode, then yes it should still be fixable

The only thing I can think of as I have never seen this B4. try holding power down,it takes awhile but it should reboot. I will try to get ahold of more info for you. No promises though. But rule of thumb Be patient.
One last thing where did you get the update from? ie 2.3.5. It helps to know what you were trying to flash.

Indrid Cole said:
The only thing I can think of as I have never seen this B4. try holding power down,it takes awhile but it should reboot. I will try to get ahold of more info for you. No promises though. But rule of thumb Be patient.
One last thing where did you get the update from? ie 2.3.5. It helps to know what you were trying to flash.
Click to expand...
Click to collapse
just tried that and it gives me the same screen I was getting when I just pressed the power button to turn on. then it says to press OK to reboot and none of the buttons work to reboot.

nursemm05 said:
I know I didn't brick my phone because I can still get into bootloader. I've tried to connect to Odin (several times following instructions to remove battery, restart pc, etc) and Odin won't recognize phone in bootloader. I was trying to update to gingerbread 2.3.5 using Odin and it got stuck. it said 'writing, wait 2 minutes' and I waited 8 mins and it never did anything. was I just inpatient? Now when I try to restart my phone it tells me manual files were installed and to hit the OK button. I have no OK button and I've tried all the screen buttons and the 3 hardware buttons to select 'reboot' as instructed per the phone and none work. So I pull the battery and start the vicious cycle all over again. I've been searching and searching (for the past 2hrs) trying to solve this on my own and I'm stuck. I need this phone as it's my work phone and I just got it Friday! (owned by me, not my company thankfully!) please help. thank you.
Click to expand...
Click to collapse
Of the responses so far, I'd start with a new microUSB cable. Whether the current cable worked 30 seconds ago or not, that could certainly be a potential issue, might as well rule it out.
After that, a few things to consider:
1) Can you get into recovery? [Hold Vol. Up] + [Power] for as long as it takes to get to the recovery screen (anywhere from 15 seconds to two minutes of solid holding.) If you can get to recovery, you are going to be in business. If after 120 seconds it hasn't gone into recovery, move on.
2) In your post, you refer to "bootloader", technically correct, but want to make sure you are referring to Odin download mode. The whole "instructions to remove battery, restart pc, etc" throws me off, you shouldn't have to do any of that. Just to make sure, what you want to do is:
Start up Odin 1.85 on your PC
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] + [Vol. Dn] until confirmation screen appears
Press [Vol. Up] to enter Download mode
Connect USB cable to the phone and then to the PC
ODIN should show COM port in first slot
3) If you can successfully get into ODM and the COM port in the first slot lights up, you are golden. Follow the rest of the steps here and you are all set to move forward or hang out from that point.
4) "I was trying to update to gingerbread 2.3.5 using Odin and it got stuck. it said 'writing, wait 2 minutes' and I waited 8 mins" I'm thinking maybe you flashed with Bootloader, Phone or CSC selected rather than PDA in the Odin menu. If that is the case you should still be able to get into ODM as shown above.

Just_s said:
1) Can you get into recovery? [Hold Vol. Up] + [Power] for as long as it takes to get to the recovery screen (anywhere from 15 seconds to two minutes of solid holding.) If you can get to recovery, you are going to be in business. If after 120 seconds it hasn't gone into recovery, move on.
Click to expand...
Click to collapse
yes, that is where it tells me media files have been installed and to press OK to reboot the phone (and other options to wipe data, cache, etc). It is not CWM recovery.
2) In your post, you refer to "bootloader", technically correct, but want to make sure you are referring to Odin download mode. The whole "instructions to remove battery, restart pc, etc" throws me off, you shouldn't have to do any of that. Just to make sure, what you want to do is:
Start up Odin 1.85 on your PC
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] + [Vol. Dn] until confirmation screen appears
Press [Vol. Up] to enter Download mode
Connect USB cable to the phone and then to the PC
ODIN should show COM port in first slot
Click to expand...
Click to collapse
Yes, Odin mode by doing what you said. I was referring to what to do if Odin won't connect. Remove battery, restart PC and try to reconnect to Odin
3) If you can successfully get into ODM and the COM port in the first slot lights up, you are golden. Follow the rest of the steps here and you are all set to move forward or hang out from that point.
Click to expand...
Click to collapse
therein lies the problem, I can't get the first slot to show yellow to show it's connected.
4) "I was trying to update to gingerbread 2.3.5 using Odin and it got stuck. it said 'writing, wait 2 minutes' and I waited 8 mins" I'm thinking maybe you flashed with Bootloader, Phone or CSC selected rather than PDA in the Odin menu. If that is the case you should still be able to get into ODM as shown above.
Click to expand...
Click to collapse
yes. I followed these instructions -
Check only Re partition, Auto reboot & F. Reset time in option
Put the files like this in Odin:
PIT = u1_02_20110310_emmc_EXT4.pit,
PDA = CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5,
PHONE= MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5,
CSC = GT-I9100-CSC-MULTI-OXAKI3.tar.md5
Hit the start button and process will begin

just tried another cable, no joy.

nursemm05 said:
yes, that is where it tells me media files have been installed and to press OK to reboot the phone (and other options to wipe data, cache, etc). It is not CWM recovery.
Yes, Odin mode by doing what you said. I was referring to what to do if Odin won't connect. Remove battery, restart PC and try to reconnect to Odin
therein lies the problem, I can't get the first slot to show yellow to show it's connected.
yes. I followed these instructions -
Check only Re partition, Auto reboot & F. Reset time in option
Put the files like this in Odin:
PIT = u1_02_20110310_emmc_EXT4.pit,
PDA = CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5,
PHONE= MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5,
CSC = GT-I9100-CSC-MULTI-OXAKI3.tar.md5
Hit the start button and process will begin
Click to expand...
Click to collapse
"GT-I9100-CSC-MULTI-OXAKI3.tar.md5"? Aren't you on the E4GT? So flashing all of these files for an international SGSII would be the first issue. What forum did you get these from?
This might be a big issue afterall. Get back to me on where you got the files and I'll see if I can come up with something in the meantime.
EDIT: One thing that will work for sure, but you'd have to wait for it to come in is a $2 jig. Once you get it, you'll back in business in less than 2 seconds. Mine took 5 days via standard shipping. You could do expedited shipping if you need it faster. In lieu of that, I will keep thinking about what you can do tonight.
EDIT 2: I know you said that you have driver's installed an all, but if you downloaded them where you got those files, they might not be what you need for this phone. You might try going to the E4GT Auto Root thread and get everything you need to start fresh from there.
Then/or try this again:
Disconnect phone, and remove battery (wait 30 -60 seconds or so).
Re-insert the battery and power the phone as I noted before by simultaneously pressing and holding [Power] + [Vol. Dn] until confirmation screen appears
Press [Vol. Up] to enter Download mode
Make sure NPS and KIES are NOT running IMPORTANT
Start up Odin v1.85
Keep trying to connect the phone to get a COM port lit. If it's not working, try changing USB ports. Try every port on your PC.
Keep trying, I've seen odin fail to recognize phones over and over and then
suddenly recognize it out of nowhere.

Just_s said:
"GT-I9100-CSC-MULTI-OXAKI3.tar.md5"? Aren't you on the E4GT? So flashing all of these files for an international SGSII would be the first issue. What forum did you get these from?
This might be a big issue afterall. Get back to me on where you got the files and I'll see if I can come up with something in the meantime.
Click to expand...
Click to collapse
oh crap! I just saw the GT-I9100 and thought I was good. I don't remember when I got them originally but just found it again here

Just_s said:
EDIT: One thing that will work for sure, but you'd have to wait for it to come in is a $2 jig. Once you get it, you'll back in business in less than 2 seconds. Mine took 5 days via standard shipping. You could do expedited shipping if you need it faster. In lieu of that, I will keep thinking about what you can do tonight.
Click to expand...
Click to collapse
this will work even though I can get into odin download mode? I can wait a few days instead of buying a new phone if it will really work!

nursemm05 said:
this will work even though I can get into odin download mode? I can wait a few days instead of buying a new phone if it will really work!
Click to expand...
Click to collapse
Yes, the jig should definitely work and it is a good idea to have one around anyway, just in case you ever need to go back to stock to return the phone or something.
But I am certain you can fix it at home in the meantime. I just need to remember or find how.

Just_s said:
Yes, the jig should definitely work and it is a good idea to have one around anyway, just in case you ever need to go back to stock to return the phone or something.
But I am certain you can fix it at home in the meantime. I just need to remember or find how.
Click to expand...
Click to collapse
I am going to order one just in case but in the meantime, going to try one more time to get Odin to cooperate then I'm done for the night. Sadly work calls tomorrow and I can't do any of this on my work computer either thank you SOOO much for all your help!

nursemm05 said:
oh crap! I just saw the GT-I9100 and thought I was good. I don't remember when I got them originally but just found it again here
Click to expand...
Click to collapse
Yeah, definitely not the right files for our phone, but don't worry, yet, I think you can recover from this. The fear is that the radio is borked as those are GSM phones and we are a CDMA phone. I haven't really read much about this issue, but I know it has happened to others. If you have time, you might search around for something like "oops, flashed SGSII GSM files on my E4GT CDMA phone" or something like that and see if anyone else figured out the fix.

I did not think there was a update to 2.3.5 for the epic 4g touch. I thought only the European versions received that update. The only update I know of for our phones was 2.3.6.
Plz link or direct where you downloaded this update you flashed. If it is the European update you will need to install the drivers for that model for Odin to recognize your phone. Then reflash the proper update.
---------- Post added at 10:18 PM ---------- Previous post was at 10:14 PM ----------
Indrid Cole said:
I did not think there was a update to 2.3.5 for the epic 4g touch. I thought only the European versions received that update. The only update I know of for our phones was 2.3.6.
Plz link or direct where you downloaded this update you flashed. If it is the European update you will need to install the drivers for that model for Odin to recognize your phone. Then reflash the proper update.
Click to expand...
Click to collapse
Wow bythe time I typed this all is revealed. The 2.3.5 was the giveaway.
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
Indrid Cole said:
I did not think there was a update to 2.3.5 for the epic 4g touch. I thought only the European versions received that update. The only update I know of for our phones was 2.3.6.
Plz link or direct where you downloaded this update you flashed. If it is the European update you will need to install the drivers for that model for Odin to recognize your phone. Then reflash the proper update.
---------- Post added at 10:18 PM ---------- Previous post was at 10:14 PM ----------
Wow bythe time I typed this all is revealed. The 2.3.5 was the giveaway.
Click to expand...
Click to collapse
It should not kill your radio. I fixed a buddys phone that kinda did the same thing. Main thing is get the drivers for the euro sgs 2. Then Odin should see your device. Then use just s's guide from there.
One last thing the jig is not be needed. You can already get into download mode. Your phone is ready for flashing. What you need are drivers for the the computer to recognize your phone.

Indrid Cole said:
...the European update you will need to install the drivers for that model for Odin to recognize your phone. Then reflash the proper update.
It should not kill your radio. I fixed a buddys phone that kinda did the same thing. Main thing is get the drivers for the euro sgs 2. Then Odin should see your device. Then use just s's guide from there.
Click to expand...
Click to collapse
Yep, this is exactly right.
@nursemm05 you need to find and install the drivers for the phone who's files you flashed. Make sure you know where you save the driver files and where they are installed. In fact, make a backup of your system so that you can restore your PC after you get your ET4G back to good.
Once you can get back into Odin, flash the tar file (singular) that I linked to and you will be back at stock. Then you can hit the other links and you will be very happy with your new setup.
Then do a system restore on your PC to before the i9000 driver's were installed and you should be back to good there as well.
Good luck!

Black screen, no fastboot

I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..

If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59

Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.

The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/

freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...

Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.

freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...

familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone

freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^

familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.

freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^

[Q] Samsung t989 Galaxy S II - Bootloop HELP please :(

I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!

still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?

phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.

zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.

If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?

JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.

sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!

dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know

sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.

JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.

sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.

JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!

sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:

(FIXED) Samsung Galaxy Tab S 8.4 will not fully boot up.

I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~

It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.

edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?

AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)

edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)

KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.

edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.

AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.

edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~

Think ive killed it :/ Tab S2 T813

ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas

You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today

Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!

Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........

thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/

Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....

stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony

one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??

if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again

In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/

RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!

will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.

Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.

swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.