Develop Bugs

[Q] SGS2 Odin Question

During an attempt to flash a rom using odin to my rooted sgs2, odin crashed and closed before it was finished. I tried restarting odin, wouldnt see phone.
Removed battery from phone, reconnected to odin and tried using the one click odin to reflash back to stock. Also tried using odin with other roms to flash back.
Heres my problem.
When i power on the phone, it says the Galazy S2 i9100 for a few seconds, then just turns off.
I can open odin, or odin one click, plug in phone, shows me yellow w/com and added. I click start, it gets to Setupconnection and then just sits there.
I have tried
- Different roms and both one click and normal odin.
- Different usb cables
- Different usb ports
- Multiple computers
Is there any way to get past this? God i hope someone can either point me somewhere or help me out.

Reinstall Samsung Kies to your laptop or pc so the proper drivers are re-installed. Once complete with that install, plug your phone into the pc and put the phone into USB mode, hopefully the pc will recognize your phone and install the NEW DEVICE drivers after a few moments. Depending on your pc, sometimes it takes many seconds for your pc to recognize and bring up the drop down menu for the newly recognized drive. BE PATIENT. If the pc does recognize your phone, start Odin again. If Odin also see's your phone, which it now should, you should see a COM:# connection in the ID:COM box of Odin. Doesn't matter what COM # is, as long as something is there. You can now use Odin because it see's your phone. Once you start Odin flashing, make sure not to disconnect anything until you see the upper left GREEN PASS box in Odin. Once its GREEN with PASS in that box, you're finished. You can d/c your phone from the pc and the phone is probably rebooting anyway.
OFC, if your phone will not stay power'd up, all of the above is for nought. Wish I could be more helpful.
Keep in mind that I do not intend to insult intelligence but everyone has limits in experience and I always try to explain in the simplest way I can. No disrespect intended.
Good Luck!
R

Thanks for the reply,
How am i supposed to put the phone in usb mode when i cant boot it?

That does create a problem, I would do some research on a USB Jig for your phone. Search at eBay for: Samsung Galaxy S2 Epic 4G Touch USB Jig
I'm not sure if this will help a phone that will not power up but it does have its uses for Root'd phone especially using Odin to flash and to remover that nasty YELLOW Triangle that comes from ROOT ROMS that are unsign'd.
Wish I could help you further.
R

Scribes said:
Thanks for the reply,
How am i supposed to put the phone in usb mode when i cant boot it?
Click to expand...
Click to collapse
Try to put in download mode if not try a jig ... If that fails it's sprint or jtag
Sent from my SPH-D710 using xda premium

It does power on, basically shows the sgs boot logo (black backgroud w/ white text) then goes dark, but its actually still on cause it gets hot.
I can get it into download mode and i can get it into the android recovery.
Theres gotta be a way to recover with an update.zip from the android recovery via the sd card........

There you go, you have two of us saying about the same thing. Just make sure you get the correct JIG if you go that route. It's like $2.00 and arrives from China in like 2 weeks.
http://www.ebay.com/sch/i.html?_fro...e+for+Samsung+Galaxy+S2/i9100/i9000/T959/i897
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
humm, an idling phone shouldn't get hot. That tells me you've got something going on. I think you just progress'd passed my pay grade my friend.

Heres another thing, as i mentioned in my first post.
The boot logo says i-9100....
and this is a sprint phone, isnt it a d710?
So im gussing in my late night haze i screwed myself by loading an i9100 rom/bootloader/whatever the hell that is.

Samsung calls it: I9100
Sprint calls it: SPH710
We call it: Epic 4G Touch

I see, so thats not the problem?
Im just gonna keep posting here while i mess with this incase i trigger someones mind for a fix.
(picture was here apparently i cannot post an external link yet. Was just a picture of device manager and odin sitting at SetupConnection)
The only way to get odin to see my phone, is if i open odin, put phone in download mode, plug phone in, then uninstall the com port via device manager, reinstall it. When i rescan for hardware changes, odin goes yellow as seen in the picture, i click start, then it sits at SetupConnection all day, so im guessing its losing the connection after it finds it.
My only solution here is via usb card i think, but i cant find a signed package. Cant someone just pull theirs from a stock phone? Why wouldnt that work?

Well, if you can get Odin to work, unroot to full stock with this:
http://www.megaupload.com/?d=ISD9AOP0

Right, getting odin to work is the real problem though i think.
Stuck at SetupConnection forever
This is super frustrating... going without a phone is impossible, work emails, texts, calls, ahhhh

..and there is no way to completely reload the entire phone using an update.zip off the sd card, one that is signed?
I know i used to do that on my droid, and all though i know this is a totally different game, i still have android recovery, one would think it would be possible if the package was signed. unsigned ones just fail, but at least i can attempt to run them from there.
If someone can find a way to do that, and it works for my phone, i will paypal $50

Let me see what I can find for ya....
I have searched two different Forums for a flashable unroot to stock with NO luck. Everything I found requires Odin. Sorry Buddy.

Correct me if I'm wrong but isn't the i-9100 a whole different phone??? Looking at the specs and release date I would believe so. Sounds like he did an ics update for a phone that wasn't the Sph-d710 or something..
http://www.gsmarena.com/samsung_i9100_galaxy_s_ii-3621.php
Sent from my SPH-D710 using XDA App

not sure, all I know it by is: SPH 710
~ via My Epic 4G Touch & XDA'a app ~

Have you tried just flashing a kernel only in Odin
Sent from my SPH-D710 using xda premium

You tried flashing ICS on your phone, didn't you? B/C I'm pretty sure that's why you are seeing I9100 while booting up. If that is the case, do a search here as there are multiple people who have done this, and none of them have been able to fix it.
Sorry, your only solution is exchange at Sprint if you can, or JTAG.

help
beezar said:
You tried flashing ICS on your phone, didn't you? B/C I'm pretty sure that's why you are seeing I9100 while booting up. If that is the case, do a search here as there are multiple people who have done this, and none of them have been able to fix it.
Sorry, your only solution is exchange at Sprint if you can, or JTAG.
Click to expand...
Click to collapse
does not mean he flashed ICS when you odin a kernel that is not signed ie with CWM you will get yellow triangle and it will say i9100 too ..... so does not mean he flashed ics ... if odin sees the phone on a com port he probably didnt .... try flashing a working kernel from our phone

I did attempt to flash ICS. I could find where i got it, but it was supposedly for the Epic 4G touch, aka sprint sgs2 variant.
I am a network and systems admin, i should have known better. I jumped the gun and got ahead of myself. I have rooted and put roms on the og droid, and the droid x, samsung is a different beast all together.
However, i went in to sprint the day after i did this, they looked at it, no insurance, no replacement warranty, they didnt ask me anything, and THEY determined it was a factory defect , they had me sign a sheet that said "After researching found phone to be a factory defect and the solution from SPRINT is to replace the phone. $37.41, and 22 hours later i had a brand new SGS2 in my hand.
They hadnt sent my phone in yet. I honestly am not sure if they are going to be able to tell if i did anything to it or not, i may have just hosed the bootloader enough that odin wont connect, so they probably will have to use something like jtag in house to reflash it, or replace the chip or whatever they do. Even so, if they do see that i was messing with it, and say it voided my warranty, i have a signed receipt showing my payment and agreeing to pay for the replacement at $37.41, and that THEY determined the flaw. My brother in law is a lawyer, so i asked him, because i was curious if they would look at my phone at the service center or hub or whatever, and determine it was my fault. He assured me they could try, but it would all fall back to the employee who had me sign the agreement, so even if they dont like what i did, they are beyond doing anything about it.
I doubt they will even notice it, im sure they will try to boot it, then just flash it or however they do it.
Either way, im not worried anymore.
So...someone wanna point my idiot ass to an actual good rom, with a good method, that works for my phone? lol. I cant stand touchwiz, huge icons and cant replace them ....wtf is that all about.

WARNING: Flashing Fonts, bootloaders, or themes

This thread is here to inform people that if they try to flash anything through rom tools of any type they might "brick" or "soft brick" their phone or have a bootloader loop with samsung logo as I do. As of right now I am working on unsoftbricking my phone because I tryed flashing fonts and a bootloading screen. While the chance there is that it will softbrick vs flashing successfully.since I had several flash fonts go off without a problem and just never stuck, I assumed everything was ok. After deleting my current rom and going back to my stock rom i thought back at what steps i took to arrive at my bootloader loop it was after a few apps I downloaded from the market.Oden Flasher (not saying in anyway that was the cause) was one of them (blue android with black lighting down the middle). Now I am unsure if this is the "root" cause (pun intended, for those that think im talking about root access im not its just a joke). I am tyring to load a stock rom ATM via "Samsung Galaxy S3 ToolKit v2.3.0". So far no luck and it still stays at the samsung screen. I can get into Odin mode and get into recovery mode. when i try to manually load a rom i get e: signature verification failed and it aborts install. the only answer i have found was from an s2 device to basically create and load a temp recovery made by adb programing. I beleive i can do it but i havent seen anything on the SIII device for sprint and really dont want to try it unless i know that is the right way to go. Ill keep everyone posted so if they have or had the same problem this might be an answer. I will gladly take advice from someone with the right knowlege please. Thank you.
***UPDATE*** IM STILL LEARNING AND I HAVE CONTINUALLY SEARCHED THESE FORUMS FOR ANSWERS UNSURE OF.
***UPDATE*** INSURE YOUR PHONE!!!
I was finally able to recover a new phone. Sprint was actually the one that suggested this to me...
If you screw up your phone and don’t have insurance to replace the one bricked or soft brick revert back to a prior model phone that you used past before your Samsung galaxy s3. Then activate your old phone. Activate insurance when you complete activation wait a day or two and bring in the one you messed up and have it replaced by acting as if you have no idea what happened. Tell them a friend that used to work for sprint tried to fix the phone and you have no idea if it was rooted or have any clue what root is and that he was using Odin to try and fix it (ONLY if they ask it was ever rooted even then you should act as if you have no clue). They should replace the device. This is not 100% guarantee but it worked for me. For all of you who messed up like I did I hope this information helps you acquire a new or factory refurbished phone. Good luck. I have made sure to back up every aspect of the phone as I was excited to receive this new device I knew nothing about and realized out of my own stupidity I only did a nandroid back up and it would never flash back because of careless mistakes and greedy want to have another cool rom all the time.
Thank you to all of you who devoted some time to help me with my stupidity!

I'm trying to figure out why you were trying to use Rom toolbox to change your boot logo.........
You clearly got this screen before it let you attempt changing it.....which device did you choose???

Rom toolbox is a very noob friendly way of doing small mods and the ONLY thing that is going to brick you under the "interface" menu is going to be the boot logo changer, and you STILL have to intentionally select a device you are not using to do it........
^^^Add that info to your OP so everyone knows you tried to flash it even tho it clearly shows not S3 compatibility
---------- Post added at 01:57 AM ---------- Previous post was at 01:53 AM ----------
Did you notify the app developer of his app shortcomings before attempting to chop into his revenues????
NOT VERY COOL MAN....:what:
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Did you notify the app developer of his app shortcomings before attempting to chop into his revenues????
NOT VERY COOL MAN....:what:

Put phone in download mode
Flash stock Odin
Done
And don't use the term brick....a brick is a useless lump of mass that has no power.
If you really have to use it...yours would be what some call a soft brick.
Sent from my SPH-L710 using xda app-developers app

I'm fairly certain if you flash anything using anything that can flash, you Might brick your device. Unless you know what your doing and even then **** happens.
Sent from Pluto.

Thanks for the info. It didn't brick my phone, but flashing a font from room toolbox cause my S3 to freeze at the boot logo, and I had to flash my back up
Sent from my SPH-L710 using xda premium

18th.abn said:
I'm trying to figure out why you were trying to use Rom toolbox to change your boot logo.........
You clearly got this screen before it let you attempt changing it.....which device did you choose???
Click to expand...
Click to collapse
no. I did not use that or get that screen. i never had that option and i never would have selected a device that was not of the same origin.

00mred00 said:
Put phone in download mode
Flash stock Odin
Done
And don't use the term brick....a brick is a useless lump of mass that has no power.
If you really have to use it...yours would be what some call a soft brick.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
done that nothing has happend. so when i finally was able to get back into my bootloader (after i have already restored it by flashing a boot image... even though i apperently dont know how to do that) everytime i tryed to manually flash the rom i got a sig ver fail. Im having a hard time trying to get a soft brick (sorry for the confusion im not good on terminologies) ive researched and come up with an answer from the s2 device when it comes to verification but i feel its a bit risky by loading a temp boot and then restoring cwm boot (actually making a temp bootloading program looks fun to me and plausable) but learning how to do all this is fun and experimental since i cant find a single post on what to do about my situation. im not just doing it to do it. i could just go buy a new phone but Im doing all this to learn it. i would appriciate it if people would stop harrassing me and just help me since i am willing to learn.

pitbull292006 said:
Thanks for the info. It didn't brick my phone, but flashing a font from room toolbox cause my S3 to freeze at the boot logo, and I had to flash my back up
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
your welcome. I do appologize since ive used the wrong terms. but that is exactly what happend to me and nothing i have tried or what i have researched has worked. ive tryed to flash my back up and i cant get it to work i just hangs. i tryed flashing a custom flash to get adb access and i still cant flash my backup. Ive flashed a few times using font flashes but everytime i tryed it i always restored my main back up first

Speedin07si said:
I'm fairly certain if you flash anything using anything that can flash, you Might brick your device. Unless you know what your doing and even then **** happens.
Sent from Pluto.
Click to expand...
Click to collapse
yes i am aware. that is why i am about to go into adb on my own and write out manually. I know how to do that. its just i dont know what to do to get it back. this is my problem. but i want to learn this stuff because i like doing it.

How the heck are you guys messing up switching fonts with RomToolbox. Never once had an issue and have changed it about once a week as the rom i'm on updates.

If you ODIN'd back to stock, it should work.
Did you ensure that everything got flashed in ODIN? Make sure you're flashing system, data, user data, boot/kernel etc.
Then repartition in Odin and flash those again.
It should work after rebooting. If it doesn't, I suspect its hardware failure and that you can get it replaced by going into the store.
Sent from my Sprint SGS3

yousefak said:
If you ODIN'd back to stock, it should work.
Did you ensure that everything got flashed in ODIN? Make sure you're flashing system, data, user data, boot/kernel etc.
Then repartition in Odin and flash those again.
It should work after rebooting. If it doesn't, I suspect its hardware failure and that you can get it replaced by going into the store.
Sent from my Sprint SGS3
Click to expand...
Click to collapse
yes. odin even said pass and it was green after all was completed. at this point I was starting to think it was hardware related and was going to reset the counter before turining it in for factory warrenty.

Thread cleaned
A little ribbing and fun when someone screws up is fine
But outright flaming and disrespect will NOT be tolerated
Thank you for your cooperation
Friendly Neighborhood Moderator

kennyglass123 said:
Thread cleaned
A little ribbing and fun when someone screws up is fine
But outright flaming and disrespect will NOT be tolerated
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
thank you! most appriciated

VenomousViper said:
yes. odin even said pass and it was green after all was completed. at this point I was starting to think it was hardware related and was going to reset the counter before turining it in for factory warrenty.
Click to expand...
Click to collapse
That seems like a solid course of action. Make sure you play dumb when you bring it into the store - Just say you left it on your nightstand, the charger wasn't plugged in, but it still wouldn't get past the boot screen in the morning.
The regular procedure is that they take out battery, reboot, check water damage, etc. without actually going into Download Mode.

Well... tbh I dont understand nothing. But try to abd install twrp2 instead CWM. And try to flash any ROM you have in your phone.
Sent from my phone...

Pull battery, reinsert, press and hold (in this order) vol (+), physical home button, then power. Hold all 3 until screen blinks a couple times, let off of power button but continue to hold vol (+) and Home. If you have a custom recovery, this should get you there.......
Problem being, if like u said in op you also flashed a boot logo(splash screen)different than boot animation - the boot logo is earlier in the boot process than recovery and when it gets corrupted, recovery options don't apply because the device won't be able to access it since the boot process is corrupted before the recovery
If it was ONLY a font that got you here, then you WILL be able to access recovery. Fonts are flashed to the /system partition, and if there in a problem , /system is the final step in the boot process and CANNOT NO-WAY cause ANY harm early enough in the boot process to prevent you from accessing recovery. So give it a try.
---------- Post added at 06:34 AM ---------- Previous post was at 06:21 AM ----------
The pic shows ROM toolbox font installer- highlighted is the default location for flashing the fonts
Below is root explorer showing the s3 filesystem fonts are in the correct directory as set as default for ROM toolbox.
So like I was saying, if it was just a font this is a very simple fix for you. Boot into recovery, flash a ROM which formats and writes /system, fixing any kind of error that installing a font could have caused

Personally if you have certain fonts you like to flash and after a successful change of fonts with what ever apps you use. I would then create a zip file with your fonts to flash in recovery when changing roms. Its what I have done without issue. I have even added the fonts folder to gapps for easy install

18th.abn said:
Pull battery, reinsert, press and hold (in this order) vol (+), physical home button, then power. Hold all 3 until screen blinks a couple times, let off of power button but continue to hold vol (+) and Home. If you have a custom recovery, this should get you there.......
Problem being, if like u said in op you also flashed a boot logo(splash screen)different than boot animation - the boot logo is earlier in the boot process than recovery and when it gets corrupted, recovery options don't apply because the device won't be able to access it since the boot process is corrupted before the recovery
If it was ONLY a font that got you here, then you WILL be able to access recovery. Fonts are flashed to the /system partition, and if there in a problem , /system is the final step in the boot process and CANNOT NO-WAY cause ANY harm early enough in the boot process to prevent you from accessing recovery. So give it a try.
---------- Post added at 06:34 AM ---------- Previous post was at 06:21 AM ----------
The pic shows ROM toolbox font installer- highlighted is the default location for flashing the fonts
Below is root explorer showing the s3 filesystem fonts are in the correct directory as set as default for ROM toolbox.
So like I was saying, if it was just a font this is a very simple fix for you. Boot into recovery, flash a ROM which formats and writes /system, fixing any kind of error that installing a font could have caused
Click to expand...
Click to collapse
Thank you for your advice. Ill try that before I turn it in. If i dont have insurance they will still replace it if i act dumb right? Just incase I will make sure i have insurance before going in. Thanks for helping me everyone with my screw up i never had this issue with HTC evo's and ive rooted, and flashed 2 of them and other HTC varients with out an issue. this is the first samsung and i cant figure it out on my own!
I continue get e: signature verification failed every time i try to load my recovery image, stock sprint imgs (every official one i can find), and still get the message every time. Ive never had this issue with HTC.

S3 won't boot - black screen

Hey folks,
I was trying to flash a custom kernel (Phenomenal Extreme 4.0) from Clockworkmod on a rooted stock 4.1.2 rom and kernel. I placed the zips on my sd card, then flashed, but it was unsuccessful. Then, when I rebooted from CWM's main menu, the phone went dead. Nothing worked, no buttons, no nothing. Any combination I tried failed, from a simple reboot, to reboot into recovery, to a reboot into download mode. Took battery out, and placed it back in, still nothing.
I'd appreciate any help you can give me! If there's anything like a factory cable, that is still better than nothing. I think I bricked it, and no warranty (Samsung's 3 month is quite short). When I plug the phone in, the laptop responds with a sound but it's not the usual sound when you dock the device. A balloon says that device driver installation failed. Then nothing happens. In any case, I rooted it and there's a flash counter of 1 on it, even if I'm running stock everything. Again, I appreciate any help!

seokhun said:
Hey folks,
I was trying to flash a custom kernel (Phenomenal Extreme 4.0) from Clockworkmod on a rooted stock 4.1.2 rom and kernel. I placed the zips on my sd card, then flashed, but it was unsuccessful. Then, when I rebooted from CWM's main menu, the phone went dead. Nothing worked, no buttons, no nothing. Any combination I tried failed, from a simple reboot, to reboot into recovery, to a reboot into download mode. Took battery out, and placed it back in, still nothing.
I'd appreciate any help you can give me! If there's anything like a factory cable, that is still better than nothing. I think I bricked it, and no warranty (Samsung's 3 month is quite short). When I plug the phone in, the laptop responds with a sound but it's not the usual sound when you dock the device. A balloon says that device driver installation failed. Then nothing happens. In any case, I rooted it and there's a flash counter of 1 on it, even if I'm running stock everything. Again, I appreciate any help!
Click to expand...
Click to collapse
What forum did you find that kernel? Hopefully it was made for d2tmo.
+Bound for Valhalla!

I just checked, it wasn't. It's actually made for the international version -- my fault. Oh crap, I'm totally screwed, aren't I? *rolling eyes and a long sigh*
http://forum.xda-developers.com/showthread.php?t=1917234 My question is, it failed regardless, and why would it die AFTER I reboot the phone? It should've died right when I tried to install it through CWM.

seokhun said:
I just checked, it wasn't. It's actually made for the international version -- my fault. Oh crap, I'm totally screwed, aren't I? *rolling eyes and a long sigh*
http://forum.xda-developers.com/showthread.php?t=1917234 My question is, it failed regardless, and why would it die AFTER I reboot the phone? It should've died right when I tried to install it through CWM.
Click to expand...
Click to collapse
Google jtag repair.

That's an expensive paper weight.
|When Emotion Goes Up, Logic Goes Down|

I made a Nandroid before messing around.
Once I do the JTAG repair, can I restore using that Nandroid after re-rooting and flashing CWM? The guy who will be doing the JTAG said that it's dangerous because there's a risk of bricking involved.

I would just restore things individually, personally. I don't know what you had on there, but is there anything that you can't restore some other way ?

That happened to me when i flash wromg kernel. And I had a panic attack...but I somehow manage to go into recovery mod....if you can go into recovery mod...have no fear back up is there lol
Just wipe everything and restore your backup.
Sent from my SGH-T999 using xda premium

Send it back
Sent from my SGH-T999 using xda premium

seshaz said:
Send it back
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hopefully you can get odin to recognise it...

tdotdot said:
Hopefully you can get odin to recognise it...
Click to expand...
Click to collapse
I had the same problem when I first got my S3. I flashed a file that was for my S2 not realizing and the phone responded the same way or didnt respond at all. Im not saying this will work but you can try. Do the proper button combo to get into download. It wont show anything on your scrren but the phone could still be in download mode. Go ahead and try connecting it to your computer and see if odin will recognize it. Make sure you have your drivers installed and dont forget to push volume up to get all the way into download mode. It worked for me once before and I hope to never have to try it again. If you have already tried this then your out of luck and will have to jtag.

JTAG is no scam. It is a VERY reliable source! Go for it.
Sent from my Galaxy Nexus using xda premium

Never mind, warranty exchange. I don't want to send my phone to strangers, even if it's legitimate. Still $45-$60 on the credit card.
I have a question though, as long as the phone is under warranty, I can exchange for a replacement an unlimited number of times, right?

Warranty Exchange!
seokhun said:
Never mind, warranty exchange. I don't want to send my phone to strangers, even if it's legitimate. Still $45-$60 on the credit card.
I have a question though, as long as the phone is under warranty, I can exchange for a replacement an unlimited number of times, right?
Click to expand...
Click to collapse
Yes you can...I did it with my S2 until I got one that did'nt have any signs of being refurbished. It looked brand new! I have even told them that something was wrong with the phone (hardware issue) when there was nothing wrong just because the one year warranty was about to run out and it had a few cosmedic blemishes..I have given them a lot of money in the past 9 years so I do'nt feel too bad... I did it with my Vibrant as well.

[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:

[Q] Unroot Galaxy S3 mobile odin. Unique problem Charging port broken

I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.

machdown said:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
Click to expand...
Click to collapse
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.

BCSC said:
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
Click to expand...
Click to collapse
I entered download mode and dont see flash counter anywhere. I got the warning screen were you have the option to restart or download.
Ya I entered recovery and did a factory reset but nothing. Really cant do anything with charging port broken.
I sent it in anyways for repairs. Hopefully they just replace it

I'm having the same problem with my Gs3 with CM10 4.2.2 running. Thought this would help.
Sent from my SPH-L710 using xda app-developers app