Develop Bugs

[Q] Did I brick my phone?

Hello,
I was trying to flash a new Rom onto my phone (Superfly) and installed the .zip file from clockwork, however, when I try to boot the phone, it sticks at the Mytouch slide screen.
I cant load into the card nor the phone.
Is there any way to reverse this?
Thanks in advance!

Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.

sandpaperback said:
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
Click to expand...
Click to collapse
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...

dion20 said:
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
Click to expand...
Click to collapse
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.

I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???

wipe everything on the phone, find the thread that walks you through that

cursexcore said:
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
Click to expand...
Click to collapse
As was noted previously, if you haven't flashed the ESPRIMG rom, you're basically looking at re-rooting your phone every time you want to install a different rom. This means going through the whole process again and again and again.

falken98 said:
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
Click to expand...
Click to collapse
thats weird, cause before I could get into clockwork after 2 tries max, not I tried repeatedly for 10 mins and it didnt work, so I should just keep tryin to get into clock work then?

Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.

sandpaperback said:
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
Click to expand...
Click to collapse
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Now I know theres something that makes it so I dont have to go thru the pain of rooting to get into clockwork I'm def gna use it..
what method should I use? Ive been doing the following and no luck so far
1 - cd to android sdk tools folder
2 - vol down + power for recovery
3 - highlight recovery
4 - run loop in cmd
5 - plug usb into phone
6 - plug usb into pc, and before it changes to HBOOT from USB i hit power to select recovery
7 - adb devices sees it as an offline device for a few cycles, then it disappears.
after step 7 I've tried running update.zip
unplugging and plugging back in
ctrl+c to stop the script when its offline
unplug when its noticed as an offline device
whats the best way to get into it now?
======
EDIT - finally got it into recovery, i loaded up htc's recover with it plugged it to the pc so it loaded up HBOOT from USB

normally your are not bricked if:
1. you can boot into recovery
2. you can not boot into recovery yet you can boot into bootloader [HOLD (power + volume down) to boot]
Don't worry I got a black/blank screen of death the other day for flashing the wrong boot.img fortunately I was able to boot into bootloader and start from scratch using the ESPRIMG.zip

dion20 said:
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Click to expand...
Click to collapse
I agree to an extent, but if you take the time to read through things thoroughly (as in every post in the How To Root or Engineering Build or even Rom Bible thread), you'll be okay. This is my first Android device as well. I put off rooting for a solid couple of weeks while I read through everything I could. I was completely paranoid about bricking my phone. Eventually, I went for it. Even then I had a couple hiccups along the way (including have to re-root two more times), but all the information is here.

So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!

cursexcore said:
[blah blah blah....] My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
My question: did u search here?
http://forum.xda-developers.com/forumdisplay.php?f=660
And found items about the champion build and this little file named ESPRIMG.zip?
U can also check out the ROM BIBLE stickie post.
u can try this:
http://forum.xda-developers.com/showthread.php?t=713507
or you can try this:
http://forum.xda-developers.com/showthread.php?t=713507
now if you really searched you would of found your own question:
http://forum.xda-developers.com/showthread.php?t=744709&highlight=unroot

cursexcore said:
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
I had the same problem you did, and fixed my phone, so its possible. refer to my post on the first page and then refer to this post and use the mirror that Wes himself posted.
http://forum.xda-developers.com/showpost.php?p=7001053&postcount=7

[Request]Acer A100 Recovery.img for ICS LOCKED

Hello Members
I need a Official recovery.img dump for this ICS version
ACER_AV041_A100_0.002.00_ww_GEN1 link >>http://vache-android.com/v1/download.php?fileID=116
my recovery does not install update.zip patches and power key does not select any opition
http://youtu.be/CWFlA1W08wE
this is my bootloader version
Bootloader v0.03.11-ICS: Starting Fastboot USB download protocol
help me please
You Can make a backup this IMG with "Acer recovery tool" downloaded from the google play store
thanks

Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.

I just noticed something, you are aware that image you linked to is a A101 image, right?

masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
thanks now works
u save my tab

rollidark said:
thanks now works
u save my tab
Click to expand...
Click to collapse
I'm glad it worked out for you, but if this fixed your device that you made a previous bricked thread about, could you please to back, and post an update to that thread discribing what you did, and how you did it, to get the device back up again? It'll definatly help anyone else with this same issue.

You're welcomed, we are here to help each other after all. You should follow pio's advice and describe what you did so others can benefit from your experience. We have to make such info as readily available as possible.

Having the same issue described
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.

citricube said:
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
Click to expand...
Click to collapse
He had a brick not a locked bootloader, you can't flash a bootloader directly if its locked with fast boot.
Tapatalked from my Galaxy S II.

Awesome
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:

citricube said:
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
Click to expand...
Click to collapse
Wow that's a pretty bad run, what's wrong with either one?
Yes I know holy threadjack Batman
Tapatalked from my Galaxy S II.

masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks

liltyke said:
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
Click to expand...
Click to collapse
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
adb reboot bootloader
Click to expand...
Click to collapse
once in fastboot
fastboot erase recovery
Click to expand...
Click to collapse
then
fastboot flash recovery "recovery.img file location"
Click to expand...
Click to collapse
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
fastboot reboot
Click to expand...
Click to collapse
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.

masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
Nicely done, masr1979!:good:

masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
thank you very much for the detailed explanation masr1979. I'll give it a shot when I get home from work.

Basically I got the rear camera replaced, it was working great. About a couple weeks later It's running sluggishly because I was running too many apps at once. So I decided to press the reset button while It was lagging out, next thing I know It's stuck at the silver android logo forever. I tried using some update.zip's but that just made the problem worse.

Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.

liltyke said:
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
Click to expand...
Click to collapse
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.

pio_masaki said:
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.

liltyke said:
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
Click to expand...
Click to collapse
So...you flashed the bootloader to get back to HC and now it won't use update.zip? What about booting into android, does that still work? Or fast boot? Or uhm...I seem to recall having to do a hard reset to get the downgrade to work, have you done this too? I never downgraded just seemed pointless when I was already on ics so I'm not experienced with it, just recall seeing the boot loader needing a hard reset to work.
Tapatalked from my Galaxy S II.

No, I never flashed the bootloader, not unless that happens while trying to run an update.zip. adb and fastboot seem to be working. Based on the earlier instructions 'adb reboot bootloader' does restart the A100 and gives me the bootloader message at the top left of the screen. When I run the ' fastboot erase recovery' command I get the FAILED message in the command prompt window and also get a message in red text on the A100 saying 'Fastboot: not support the command in lockmode, failed to process command erase: recovery error (0x2)'. When I run the 'fastboot reboot' command the A100 does restart. So all that leads to believe that the communication from my computer to the A100 is ok.
Booting into Android. The A100 starts and works fine if that is what you are referring too. As far as the hard reset, if that's the process of holding down the volume button while powering up and flipping the lock switch back and forth to reset the unit, then yes I have done that and it does work. My whole goal here is to get the unit to running ICS legitimately and get updates from ACER. I don't care what I have to do, it's just a couple of the other threads mentioned the need to go back to HC to get the official ICS update. So that's why I tried that. But the last time a update.zip worked was when I flashed the leaked ICS. I have got the dead android logo every time since.
Sorry if some of this info is redundant from my earlier post, I just wanted to get it all in the same place.
Thanks again for your help.

[Q] i9250 shows a phone connects to a computer icons and a yellow triangle

Hi, experts, help needed here.
My galaxy nexus (GSM version) was 4.0.4 perviously, then I OTA it to 4.1.1 and my phone's unlocked but never rooted. After OTA to 4.1.1, everything works fine for couples months. But about 1 week ago, when i tried to update an App then an odd thing happeded, right after i pressed the update bottle, screen fliker happened, then the phone stopped responds, after I pull the battey out then put it in, the phone just kept restarting over and over, only showed me an google logo with a un-locked icon...
I tried to get into the recovery mode and flash it with the Galaxy Nexus toolkit for whatever 4.0.4 or 4.1.1 version factory images, but everytime right after starts, then screen fliker occurs and then the toolkit just hung there. - and this even occured while i tried to wipe the phone.
I tried to use the odin tool as well, but still, everytime right after start flash, screen fliker occurs and odin hung there. And the worse thing is, after my last try with Odin, now my phone is showing a phone connects to a computer icons and a yellow triangle...
Is there still a hope? Thanks in advance.

My guess is Odin messed up your partitions. Can you still access the bootloader?

Petrovski80 said:
My guess is Odin messed up your partitions. Can you still access the bootloader?
Click to expand...
Click to collapse
no.. prevously i can access it, but now, only the yellow triangle and the phone and computer's icon shows up.
what can I do? :crying::crying:

not sure if it would be wise to suggest this, but you could try omapflash. I'm curious about it myself, I guess I'll start looking into that. if it has power like nvflash, not sure if that would help, since you have no backup of your "good" partition table. If you have the guts, of course. I would just return the device in to warranty. :victory:
edit: first google hit, title says "gt-i9250", the gsm version, don't know what you roll op.
edit2: read the whole thread. pretty useful insight right there.

bk201doesntexist said:
not sure if it would be wise to suggest this, but you could try omapflash. I'm curious about it myself, I guess I'll start looking into that. if it has power like nvflash, not sure if that would help, since you have no backup of your "good" partition table. If you have the guts, of course. I would just return the device in to warranty. :victory:
edit: first google hit, title says "gt-i9250", the gsm version, don't know what you roll op.
edit2: read the whole thread. pretty useful insight right there.
Click to expand...
Click to collapse
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.

efrant said:
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
Click to expand...
Click to collapse
hmm, i forgot that existed.
seriously, i think that a lot of the issues i see in that thread are probably caused by windows.
maybe OP's device's xloader/uboot went down the drain?
edit: found another good post on this. bookmarked.
edit2: and some more right here.
edit3: Naturally, I deviate away from toolkits or batch scripts, so I'm trying to look at this like nvflash. One thing that I read is that Omapflash commands are issued on the target instead of the host like fastboot, so that is making my mind spin.
edit4: here. "OMAP4460_TUNA_8G_HS_PRO 444007 01 HS" - 8G probably means hardware revision, the one we see in bootloader. HS could be High Speed device. Nope, High Security.
edit5: how many edits this going to have... "OMAP4 Jellybean Release Notes" - omappedia
edit6: totally different idea. OP, do you have an OTG cable? Because we got something called "SYSBOOT"
edit7: this is the most interesting thing yet. i'm salivating right now.

efrant said:
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
Click to expand...
Click to collapse
First of all, thanks for all the replys, that really fresh my mind..
For your addition information, yes, odin does recongnize my my while I connects to the PS, I guess the SCREEN FLIKER may be caused by the wrong odin tar packages... For my current situation, which version of the system should I flash? 4.0.4 or 4.1.1 or it doesn't matter? Besides, do you know where can I download a full packages of Odin flash packages which includes the partion table as well? Sorry to ask this stupid questions here cause I'm a newbee here and this is my first Android phone...

I've never used odin but I bookmarked this post just in case (I haven't seen any 4.1.1 ODIN repacks)

ge_johnny said:
First of all, thanks for all the replys, that really fresh my mind..
For your addition information, yes, odin does recongnize my my while I connects to the PS, I guess the SCREEN FLIKER may be caused by the wrong odin tar packages... For my current situation, which version of the system should I flash? 4.0.4 or 4.1.1 or it doesn't matter? Besides, do you know where can I download a full packages of Odin flash packages which includes the partion table as well? Sorry to ask this stupid questions here cause I'm a newbee here and this is my first Android phone...
Click to expand...
Click to collapse
You shouldn't need a partition table. It will work without one. And you can use either a 4.0.4 or a 4.1.1 tar. Both should be available in the dev section. Make sure you pay close attention to which boxes need checks in them - never put a check in box related to repartitioning.
For future reference, I would always recommend to use fastboot before resorting to odin. Less chances of you getting into the situation that you are currently in.
Sent from my Galaxy Nexus using Tapatalk 2

here is the update of the problem.
OMAPlash doesn't solve my problem at all, I run the defaullt omap4460_tuna_hs_pro.txt script, it looks like flash something to my phone but the problem still there.
I tried redownload some odin packages into my phone, but still screen fliker happened...
Any other suggestions?

from what i've read, you now have the ability to enter the target, omapflash commands are issued on the target, not on the host.
you can feed the device the x-loader and uboot, which will then give you fastboot, restoring then a factory image.
someone that has actually done the whole procedure or has more info on this, please share.
Sent from my i9250

Help!!
bk201doesntexist said:
from what i've read, you now have the ability to enter the target, omapflash commands are issued on the target, not on the host.
you can feed the device the x-loader and uboot, which will then give you fastboot, restoring then a factory image.
someone that has actually done the whole procedure or has more info on this, please share.
Sent from my i9250
Click to expand...
Click to collapse
Hey Could you please maybe explain how to go around this? I currently have a yellow triangle brick on my Gnex but it does get detected via USB on Odin so if there is a fix I would like to know!
Thanks in advance!

If I were you, I would just use a jig to get it into download mode, then just reflash. I dont think it will take a flash with that boot error.

Check this thread here.
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250

Don't think I explained myself very well
bk201doesntexist said:
Check this thread here.
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Hey guys thanks a lot for your replies! I don't think I got the severity of the problem across well enough. See, the phone was in bootloop but everything was going fuzzy all the time (including recovery) and the recovery mode was corrupt it wouldn't let me clear cache! and while it was running the clearing process, all I could see was yellow lines of errors saying cache cannot be mounted. After loads of failed attempts of trying to flash Stock ICS and Jellybean (Yakju, without wallet) the phone decided it wanted to brick and so didn't turn on at all! I found a forum online (http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/) which gave me the OMAPFlash method with which I unbricked the phone and got it started a couple of times. I tried to then flash stock again via fastboot, it didn't work it simply couldn't send files to my phone although the phone was connected because it was detected under fastboot devices. After this, I went into download mode and tried to flash using Odin, however, this crashed and the phone crashed too which required me to pull the battery out. From then, all I get is > phone!Pc < and now the phone is detected via USB and via OMAP but the OMAP doesn't bring me back to fastboot its stuck on that yellow triangle screen!
Again, Thanks a lot for all your help! If I don't get this sorted in a few days I'll be sending it to Samsung!

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

Pretty Sure I Hard Bricked - HELP!

Day before yesterday, I tried to go back to stock. Must not have had the right ROM or something. Long story short, phone doesn't turn on. Computer will make a noise letting me know that it has been plugged in though. Under device manager it comes up as...
Qualcomm HS-USB QDLoader 9008 (COM7)
So, hard bricked? Tried pulling the battery and everything else. So I guess, can anyone point me to a guide or explain here step by step what I need to do? I did some searching and found various guides, all of which seemed to differ. Looking for a good solid answer. I have a Jig on the way but not sure whether or not it will work.
THANKS ALL

nbarr7655 said:
Day before yesterday, I tried to go back to stock. Must not have had the right ROM or something. Long story short, phone doesn't turn on. Computer will make a noise letting me know that it has been plugged in though. Under device manager it comes up as...
Qualcomm HS-USB QDLoader 9008 (COM7)
So, hard bricked? Tried pulling the battery and everything else. So I guess, can anyone point me to a guide or explain here step by step what I need to do? I did some searching and found various guides, all of which seemed to differ. Looking for a good solid answer. I have a Jig on the way but not sure whether or not it will work.
THANKS ALL
Click to expand...
Click to collapse
What was your phone on prior to attempting to flash stock (bootloaders, ROM)?
Also, what did you try to flash?

nbarr7655 said:
Day before yesterday, I tried to go back to stock. Must not have had the right ROM or something. Long story short, phone doesn't turn on. Computer will make a noise letting me know that it has been plugged in though. Under device manager it comes up as...
Qualcomm HS-USB QDLoader 9008 (COM7)
So, hard bricked? Tried pulling the battery and everything else. So I guess, can anyone point me to a guide or explain here step by step what I need to do? I did some searching and found various guides, all of which seemed to differ. Looking for a good solid answer. I have a Jig on the way but not sure whether or not it will work.
THANKS ALL
Click to expand...
Click to collapse
Definitely doesn't look good. What did you try to flash? Do you have a link
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app

He posted more info about this here: http://forum.xda-developers.com/showthread.php?p=54466247
As I pointed out there, even though I've never seen it show Qualcomm HS-USB QDLoader, it does match what we do often see as QHSUSB_DLOAD.
@nbar7655, you also confirmed the red led in your last post, so yes it is bricked, and as suggested you're only option is to try the debrick method. If that doesn't work, the only other option is a jtag service. The jig, while good to have, will not help in this particular situation.

DocHoliday77 said:
He posted more info about this here: http://forum.xda-developers.com/showthread.php?p=54466247
As I pointed out there, even though I've never seen it show Qualcomm HS-USB QDLoader, it does match what we do often see as QHSUSB_DLOAD.
@nbar7655, you also confirmed the red led in your last post, so yes it is bricked, and as suggested you're only option is to try the debrick method. If that doesn't work, the only other option is a jtag service. The jig, while good to have, will not help in this particular situation.
Click to expand...
Click to collapse
Thank you. I did make this post just because I felt that it should have a post of it's own and I shouldn't sit on someone else' thread for too long haha.
So, my only option is through the debrick img, correct? Any ideas where I can grab one. I believe I know the steps to doing it. (Throwing it on an SD card) but I seem to find different debrick files all over the place. THANKS!

I agree about not hijacking that firmware thread for this, so no big deal.
This is the thread I was referring you to:
http://forum.xda-developers.com/showthread.php?p=47984104
It gets confusing because everyone creates a new thread for every brick just about. But since yours happened while on 4.3, try using the debrick.img provided in the OP.
If it doesn't work, don't give up. Many people have had to make several attempts before it would work. It may seem a lot, but id try at least 6 or 7 times before giving up on that image and looking for another.

OK and just to double check, all I have to do is write the image to the sdcard, pop the SD card into my phone and then (attempt) to power it on?
UPDATE: OH MY GOD! Got it into recovery!!! Where do I go from here? Lmao
UPDAT2: Ok, so I can boot into what looks like stock mode but I am sure that I am only booting from the SD card. So at this point, do I run odin and flash a stock ROM?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Im assuming you used the 4.3 debrick.img correct? And is it booting into stock or a custom recovery?
Either way, try to reboot download mode and Odin flash the MJB firmware. (Don't forget to take out the sd card first). Hopefully, after the flash completes it'll reboot right into the OS. You were on aosp before, right? You may need to factory reset to get it to boot all the way.

DocHoliday77 said:
Im assuming you used the 4.3 debrick.img correct? And is it booting into stock or a custom recovery?
Either way, try to reboot download mode and Odin flash the MJB firmware. (Don't forget to take out the sd card first). Hopefully, after the flash completes it'll reboot right into the OS. You were on aosp before, right? You may need to factory reset to get it to boot all the way.
Click to expand...
Click to collapse
Where can I find that firmware?
My bad, I am assuming from here: http://forum.xda-developers.com/showthread.php?t=2540998
If so, what exactly am I grabbing from that?
Also, any files that I grab from there...ODIN doesn't see them because they aren't the correct file types? Maybe I am not grabbing the correct ones?

Well, the firmware I had in mind is the same that is in the thread you first posted in. Try redownloading it and flashing again. Ill try to find an alternative if you prefer though.
I know there is a method where you first flash recovery with odin, then flash the firmware from recovery. Id have to locate the files needed though. (The thread you linked to may have exactly that though. I will look closer in just a bit)

Ok, if you want to try another way, go to this post:
http://forum.xda-developers.com/showthread.php?p=52341560
Download the one that says to flash with custom recovery.
Now, using Odin, flash TWRP or CWM recovery.
Now reboot to that recovery and flash the package you just downloaded.
Factory reset.
Reboot.
If it tries to boot, but hangs or goes straight to recovery, download the other package from that post and flash it in Odin. Then try to reboot again.
Basically, if you follow the instructions in thst post from start to finish, you should be able to boot up to stock 4.3. If you do not flash the last part in Odin (if you stop after the recovery flash), hopefully your device will be able to boot into whatever you last were running. It would probably be best to go back to full stock though.
Good Luck!

DocHoliday77 said:
Ok, if you want to try another way, go to this post:
http://forum.xda-developers.com/showthread.php?p=52341560
Download the one that says to flash with custom recovery.
Now, using Odin, flash TWRP or CWM recovery.
Now reboot to that recovery and flash the package you just downloaded.
Factory reset.
Reboot.
If it tries to boot, but hangs or goes straight to recovery, download the other package from that post and flash it in Odin. Then try to reboot again.
Basically, if you follow the instructions in thst post from start to finish, you should be able to boot up to stock 4.3. If you do not flash the last part in Odin (if you stop after the recovery flash), hopefully your device will be able to boot into whatever you last were running. It would probably be best to go back to full stock though.
Good Luck!
Click to expand...
Click to collapse
When trying to flash this in CWM: http://www.androidfilehost.com/?w=f...c22e9070f53359adf81131967fe536789e19937d7b610
I got an error (status 7)?
Update: Got it installed. Problem was that I had it stored on the SD card instead of the phone storage.
Update2: Currently sitting at the white screen with the AT&T logo. Will see if it gets past this in a few minutes. If not, I'll reboot into recovery and flash the stock ROM.
Update3: BOOTED IN!
Update4: Going to try to now boot without the SD card to make sure it isn't still booting from that!
Update5: SUCCESS! I can now boot from the system itself!!!!! ALL SEEMS GOOD!
You guys here are undoubtedly the best people around. Awesome responses and spectacular help! HOW DO I DONATE?!?!?!?

That's awesome news! Really glad to hear you got it working again! As for donations, many people will have a link under their name on each post, or on their profile. If you can't find this for someone you can always PM them and ask if they have a PayPal or other account they can accept donations with.

DocHoliday77 said:
That's awesome news! Really glad to hear you got it working again! As for donations, many people will have a link under their name on each post, or on their profile. If you can't find this for someone you can always PM them and ask if they have a PayPal or other account they can accept donations with.
Click to expand...
Click to collapse
Thank you very much. Consider a donation coming your way man. Thank you again for all the help.

Thank you! And regardless of that, I'm glad I could help!