Database Develop

Galaxy bricked?

Hi all,
I have a friend who rooted his Galaxy Tab and has used odin to partition his device, an ext 4 partition i think, anyway, something failed and and gave an error and he turned it off because it became non responsive and now it wont turn on, the screen lights up but nothing comes on, power and up or down does nothing and power with up and down also does nothing, rooted with v4root.
Sorry if this is a little vague but is there anything anyone can say which might be able to help? I know adb can be used from the bootloader (or is it recovery) but if those key cominations are doing nothing then how could he get to it?
Thanks in advance and sorry if i sound vague.

Pm me with more details and ill help you out.
1. Can you get into recovery or dl mode?
2. Will it charge?
3. If connected to computer, will computer still recognize it?
Sent from my SGH-T959V using XDA Premium App

itsjusttim said:
Pm me with more details and ill help you out.
1. Can you get into recovery or dl mode?
2. Will it charge?
3. If connected to computer, will computer still recognize it?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Hi and thanks for replying,
Answers to his questions are below:
1. Can you get into recovery or dl mode?
NO – when pressing power and down (or up) it just makes the screen light up after about 10 secs then the light will turn off after you let go of the button
2. Will it charge?
Looks like it, although I do not get any icon to say it is charging or not. Have tried holding down the power and touching the screen (mentioned on another Forum) to see if the icon will appear but nothing. Have left it on charge from the mains all night (over 8 hours)
3. If connected to computer, will computer still recognize it?
No – Have installed the latest version of Kies and my machine does not pick it up as a connected device at all. Also, Odin no longer see’s it connected via USB (yellow tab with a COM number)
Like i said sorry for being a little vague, hope this helps.

Hi itsjusttim,
dladz is helping me out with this Tab issue. He said it best to try and post on xda and look for similar posts.
I've looked around and am very stuck at this moment in time.
If you want to PM me, please do

kyukashi said:
Hi itsjusttim,
dladz is helping me out with this Tab issue. He said it best to try and post on xda and look for similar posts.
I've looked around and am very stuck at this moment in time.
If you want to PM me, please do
Click to expand...
Click to collapse
Ello m8,
If you get a resolution post here so others can maybe get a hand from it.

Best thing I can think of is to let it charge overnight and try again to connect to odin.
If thats a nogo then I think I read somewhere that someone was making jigs to get into dl mode.
These things have helped others from recovering there tabs. I bricked my tab a month ago, tried the jig and still didnt work. I ended up calling samsung and "played stupid" and got it fixed. [$99.99 repair]
EDIT: just looked over my bill and the part they replaced is labeled as "PBA" and cost nothing to replace.
let me know if there are any other qs. Imo, looks as there is a way to avoid the $99 'standard repair' charge.
Sent from my SGH-T959V using XDA Premium App

looks like I've gota send it to Repair Center feel like such a n00b to do it but after lots of post reading and forum searching it seems like it's the only way!
Spoke to Samsung and they said coz "i've tried to do a software update and there is no software update yet officially available, that I may have voided warranty". I basically played dumb and they said to send it in.
It's looking like I'm getting it replaced or reflashed by them now, so hopefully will have it back soon and working

Really wish you good luck. Please keep us updated if/how much they charged you...
send from my SGT with Overcome...

Can't get into recovery/dload mode Phone boots to white At&t screen makes few sounds

Can't get into recovery/dload mode Phone boots to white At&t screen makes few sounds
I have recently messed up my Captivate when I was trying to flash a ROM. My phone goes up to the white At&t sign and then makes a few sounds and stops. It also goes to the charging screen when plugged in the cpu when off. I have tried countless ways to get it to go into dl mode or even recovery mode. Ive tried: ADB vol up and down plus power with usb plugged in/battery put in, vol down usb plugged in/battery put in, vol up usb plugged in/battery put in, just vol up and down usb plugged in/battery put in, and nothing seems to be working. WITHOUT someone tellin me to use a jig can ANYBODY please help me find a way to do this. I have even pressed menu and volume down while the phone was in off charging state with green bar loading and the cpu made a sound and cpu said unrecognized device...from there I have tried to root my phone hoping it goes into recovery mod(which ive done to fix my phone before) also from there i have tried odin but no recognizance and I also have tried adb reboot download and adb reboot recovery. NOTHING WORKS...someone please HELP ME!
thanks in advance

What rom were you trying to flash?

why SO resistant to someone telling you to make/buy a jig? its a very easy thing to make and it will solve your no download mode issue in seconds. if nothing else will get you in download mode a jig will for sure (unless your usb port is broken) you can try and exhaust all other solutions but after you've ripped all your hair out build a jig.
its like trying to dig a ditch with a garden spade when you have access to a back hoe

Good point
stud u really make a goop point about it being easier to buy a jig than to pull ur hair out. Which if this kid really was pulling his hair out he shouldn't have been doing this at all. But, I am also having this same problem. I was using a CM7 build and it worked great until i tried to install the gapps. then it went crazy. It rebooted itself and went through the Cyanogen Mod first screen then would get stuck on the CM7 blue android on skateboard bootscreen. If I touched the screen at the bottom right it would vibrate for some reason. Shortly after realizing I needed a jig for it I decide to buy a new one cause at the time I didnt know if I could properly make one. So I've kept my first captivate still trying to find a non-jig method. I recently taught myself begginers adb on Windows XP OS but I am very much a noob except for rooting and flashing. Any help of yours would be great anytime. Thanks,
Matt

gujuplaya111 said:
NOTHING WORKS...someone please HELP ME!
thanks in advance
Click to expand...
Click to collapse
Shows that youve been a member since Dec-2010 so Im assuming that you really did try everything because you have read and read and read (riiiiiiight!?) and without telling us whether you tried to flash a Froyo or Gingerbread ROM I'd sugguest that you buy a JIG. Its really the best solution and the less time consuming if you cant think of anything else to try. You can order one or make your own...literally took about 30 minutes for me to get my phone to a place where i can work with it....a trip to the radioshack and making the JIG and back home.
If you are making requests on specifically NOT to tell you to do it a certain way then you may have to accept that you might have to solve this problem on your own, especially if you said that you tried everything except the one thing that you cant do (which is what we might suggest) and probably will fix your situation.

So i re-read after making my first post to this. I've bought my 5th Cap. now and have quite a bit more knowledge than before. So my question is. If I've completely bricked my 3rd cap... No battery charge screen and all will a jig still work for me to get into download? I was tryin to come back from cm7 but something went wrong.... I really don't need the extra phone but it would be nice to have my back up
Sent from my SGS Captivate on Cog. 5 v2 using XDA Premium App

dm63755 said:
So i re-read after making my first post to this. I've bought my 5th Cap. now and have quite a bit more knowledge than before. So my question is. If I've completely bricked my 3rd cap... No battery charge screen and all will a jig still work for me to get into download? I was tryin to come back from cm7 but something went wrong.... I really don't need the extra phone but it would be nice to have my back up
Sent from my SGS Captivate on Cog. 5 v2 using XDA Premium App
Click to expand...
Click to collapse
If the screen doesnt turn on at all and there is no charge screen or recognition at all of usb than it is more likely then not hard bricked.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Thanks xijar then i will for sure purchase a jig. Worth a try anyway.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Galaxy Nexus COMPLETELY DEAD. Does not boot into ANY mode.

Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.

wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431

hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse

onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?

adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!

Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.

WTF are these guys for real? This thread should have been deleted the day it was started!!

This is posted in wrong section.
**Reported**

Thread Closed​
This forum is for the galaxy note, please post in the correct forum​

help! screen flickers on startup

ok, so my tab decided to be a pain in the arse today. when i try to power it on, run it in download mode or in recovery mode the samsung galaxy tab 8.9 screen shows up then the screen either shuts off or flickers and then shuts off before it can load up.
what options do i have to overcome this? i am rooted running JB.
tia.

skim234 said:
ok, so my tab decided to be a pain in the arse today. when i try to power it on, run it in download mode or in recovery mode the samsung galaxy tab 8.9 screen shows up then the screen either shuts off or flickers and then shuts off before it can load up.
what options do i have to overcome this? i am rooted running JB.
tia.
Click to expand...
Click to collapse
Yeah, same thing happened to me today I read that it is something to do with the bootloader, which can cause the tab to be bricked if not done right, so I'm going to try the ASOP JB instead see if that does the same thing.
---------- Post added at 09:17 AM ---------- Previous post was at 08:47 AM ----------
MikeMcGrathXmen said:
Yeah, same thing happened to me today I read that it is something to do with the bootloader, which can cause the tab to be bricked if not done right, so I'm going to try the ASOP JB instead see if that does the same thing.
Click to expand...
Click to collapse
Nope Dosen't work still the same when I install the AOSP (spelt it right this time), any pointers here would be great, I do want to try and fix this, I've been waiting for ages for the official ICS, but couldn't wait any longer so spent some time looking on how to do this and was amazed at the speed of JB, but the screen keeps flickering after standby. Anyone know step by step guide to fix this? Any help would be greatly appreciated. thanks Mike

HTC One Stuck at HTC Logo Screen, Unable to boot into the bootloader/recovery.

Hi guys, I'm writing to you in hopes that you can some how save me in this situation.
Like many others, I was stupid and deleted everything on my phone using TWRP. I have tried many suggestions, mostly those found in this thread :
http://forum.xda-developers.com/showthread.php?p=40907625
and in many others however I am unable to get out of the HTC Logo screen. While holding the power button the buttons on the bottom simply blink and nothing else. It doesn't reboot, no matter how long I hold it. The same thing happens when I try and boot into the boot loader.
My only option now is to just wait for the battery to die on its own I suppose but in the mean time I was wondering if anybody else had any suggestions for me. I really hope I didn't brick my phone v_v
Edit - Forgot to mention that when I did try the methods in that thread, the program won't recognize that the phone is connect however the HTC Sync application does pop up on my computer when I connect it via usb.

Did you try adb? You probably still have it from when you installed twrp. Connect your phone via USB, go to a command prompt in the directory with adb (e.g. in the fastboot directory) and type "adb reboot recovery". In windows you can get to a comand prompt (among other ways) by shift-richtclick of the relevant directory and choose "command prompt here"

Thanks for the response!
I tried that however the device isn't being recognized as being plugged in even though it clearly is. Just to repeat, I'm stuck at the HTC logo, not the bootloader or recovery. I know the recovery is still there however I'm unable to get into it from this screen. I'm completely at a loss at what to do next =/

Triplet11 said:
Thanks for the response!
I tried that however the device isn't being recognized as being plugged in even though it clearly is. Just to repeat, I'm stuck at the HTC logo, not the bootloader or recovery. I know the recovery is still there however I'm unable to get into it from this screen. I'm completely at a loss at what to do next =/
Click to expand...
Click to collapse
Yeah I only mentioned it because I, too, got myself stuck at the HTC Logo and, even though the phone wasn't recognized as a device by windows, adb still worked for me.

scottegos2 said:
Yeah I only mentioned it because I, too, got myself stuck at the HTC Logo and, even though the phone wasn't recognized as a device by windows, adb still worked for me.
Click to expand...
Click to collapse
I just posted a Tip on this in the General section on how to get around this without waiting on battery drain. In a nutshell hold your phone under a bright light and then hold the Power/volume button and it will take you to the bootloader. I know it sounds wierd, but the same thing happened to me flashing an international Rom and someone posted to do this, so I tried and damn if it didnt work. I realize its been a few days since you posted this, but if it happens to you again now you will know. :good:

smatherlee said:
I just posted a Tip on this in the General section on how to get around this without waiting on battery drain. In a nutshell hold your phone under a bright light and then hold the Power/volume button and it will take you to the bootloader. I know it sounds wierd, but the same thing happened to me flashing an international Rom and someone posted to do this, so I tried and damn if it didnt work. I realize its been a few days since you posted this, but if it happens to you again now you will know. :good:
Click to expand...
Click to collapse
weird, but interesting! thanks for sharing. :good:

I was about to ask how to get around this hanging. Super thanks for the strange tip. Worked like a charm and I'm back in the bootloader!

smatherlee said:
I just posted a Tip on this in the General section on how to get around this without waiting on battery drain. In a nutshell hold your phone under a bright light and then hold the Power/volume button and it will take you to the bootloader. I know it sounds wierd, but the same thing happened to me flashing an international Rom and someone posted to do this, so I tried and damn if it didnt work. I realize its been a few days since you posted this, but if it happens to you again now you will know. :good:
Click to expand...
Click to collapse
My international HOX recently got stuck at the boot screen after re-unlocking bootloader too. Volumn down + Power will only reboot it and get it stuck again. I first thought this was some kind of a joke, but I tried and saw IT DOES WORK!!!

smatherlee said:
I just posted a Tip on this in the General section on how to get around this without waiting on battery drain. In a nutshell hold your phone under a bright light and then hold the Power/volume button and it will take you to the bootloader. I know it sounds wierd, but the same thing happened to me flashing an international Rom and someone posted to do this, so I tried and damn if it didnt work. I realize its been a few days since you posted this, but if it happens to you again now you will know. :good:
Click to expand...
Click to collapse
THANKS! Was trying every possible way to reboot my phone and nothing would work. For some reason this bright light stunt got it booted. Odd, but worked.

Sorry, I know this thread is a few months old, but this is the only place I can find reference to this particular problem.
Has anyone found any real fix for this?
My HTC One is, as in the OP, stuck in the HTC screen following a borked ROM flash. I have tried the power button alone, power+vol-down, bright light, dim light, etc. So far nothing I have tried has resulted in anything besides the softkeys flashing; no shutdown, no reboot, no bootloader...nothing.
Anyone?
Or am I stuck just waiting until the battery dies...

You are holding the power abd vol down buttons for a very long time, right? Longer, as in way longer than normal.
If your recovery does not charge the phone you better not let it run down. I use philz, it charges ablnd has OTG , but moreover charges. It also comes up clean in TechNet ajust by plugging in imported
Sent from my HTCONE using xda app-developers app
---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------
Oops, not TechNet, recovery. Bad typo.

tdhite said:
You are holding the power abd vol down buttons for a very long time, right? Longer, as in way longer than normal.
Click to expand...
Click to collapse
Correct. No matter how long I held in the power buttons, it did nothing. I ended up letting it run down over the night and this morning ran a restore on the backup I had made before attempting the flash. After restore, phone is back to where it was before, so problem taken care of (sorta). Cyanogenmod 10.2 now installed and working.
tdhite said:
If your recovery does not charge the phone you better not let it run down. I use philz, it charges ablnd has OTG , but moreover charges. It also comes up clean in TechNet ajust by plugging in imported
Sent from my HTCONE using xda app-developers app
---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------
Oops, not TechNet, recovery. Bad typo.
Click to expand...
Click to collapse
??? Not really sure what you're trying to say here...?

Yea, crummy typing.
Just saying to be careful of battery if his recovery doesn't charge the battery. I've heard problems on recent TWRP releases for Sprint HTC One along that line, though I use PhilZ so can't be certain. If power down was possible, then usually plugging in alone gets me to recovery.
Looks like it all worked out anyway.
Sent from my HTCONE using xda app-developers app

x88x said:
Sorry, I know this thread is a few months old, but this is the only place I can find reference to this particular problem.
Has anyone found any real fix for this?
My HTC One is, as in the OP, stuck in the HTC screen following a borked ROM flash. I have tried the power button alone, power+vol-down, bright light, dim light, etc. So far nothing I have tried has resulted in anything besides the softkeys flashing; no shutdown, no reboot, no bootloader...nothing.
Anyone?
Or am I stuck just waiting until the battery dies...
Click to expand...
Click to collapse
Try holdin power and volume up, it will shut down, then power and volume down, will take you to recovery, that same thing happened to me and this fix it
Sent from my HTC One using xda app-developers app

Worked O.O
x88x said:
Sorry, I know this thread is a few months old, but this is the only place I can find reference to this particular problem.
Has anyone found any real fix for this?
My HTC One is, as in the OP, stuck in the HTC screen following a borked ROM flash. I have tried the power button alone, power+vol-down, bright light, dim light, etc. So far nothing I have tried has resulted in anything besides the softkeys flashing; no shutdown, no reboot, no bootloader...nothing.
Anyone?
Or am I stuck just waiting until the battery dies...
Click to expand...
Click to collapse
Oh ir's really weird and interesting but it worked like a charm!
I used my blackberry z10 as a torch to lit the proximity and pressed vol+/- and pwr....... and the One really shutted down....... lol
what's the problem, my god.......