Develop Bugs

[Q] Help - 5 vibrates and blinking green LED

Hi, I'm having problems with my DINC.
I was running SkyRaider Athena 1.2 with the stock Kernel, HBOOT 0.92, Radio 2.15.00.09.01 and S-OFF. It was getting a little slow and bogged down so I decided to start afresh and flash a new rom. I upgraded my Custom Recovery from 2.5 to 3.5 (it had been a while since I had flashed a rom) and flashed SkyRaider Sense 3.5.
Here is where the problems start. Whenever I turn off the phone and try to turn it back on I get the "HTC Incredible" screen, which then goes to black and I get 5 vibrations and a green flashing LED. I can get to the bootloader but when I try to get to the Custom Recovery, the same thing happens. One thing that I have noticed is that S-Off is now S-ON.
The only way that I can get the phone to turn on is to press the power button, and plug the phone into a usb for power. At that point it will start up normally, however the phone will not read the SDcard or internal phone storage at all, even in when I do the same thing to get to the custom recovery, which means that I can't flash roms, or use any apps that require some sort of memory.
I don't know if this is a problem with the rom so I posted this in the general discussion.
I've also found some posts on other websites where people have had similar issues but no solution:
http://www.incredibleforum.com/foru...f-vibrates-5-times-green-light-flashes-3.html
http://www.droidforums.net/forum/dr...9959-need-help-5-vibrates-blinking-green.html
Yes. I'm QuickSilver98 on those sites too
Any help would be greatly appreciated.

Sorry to say but I have yet to see a solution other then a insurance claim. I hope someone smater then I can help.

Just do a battery pull when that happens.
It has happened to me before a couple times, but after a battery pull everything works fine.

thanks for the suggestion, I've tried tons of battery pulls, but there's no change.

I've never heard of this problem but, then again, I've only been in the Android community since September and am far from an authority. I do have one thought though which I'm guessing is not a cure all for your problem but, could possibly be a part of the problem. Is it possible that maybe your SD card has crapped out on you? Have you tried putting it in a card reader to see if it is still readable? Just a thought, as I said. Good luck with your problem, in any case.
Sent from my ADR6300 using XDA App

I had this problem, I took the phone back to Verizon and they gave me a refurb. But this may help you
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/

c_live_lee said:
I've never heard of this problem but, then again, I've only been in the Android community since September and am far from an authority. I do have one thought though which I'm guessing is not a cure all for your problem but, could possibly be a part of the problem. Is it possible that maybe your SD card has crapped out on you? Have you tried putting it in a card reader to see if it is still readable? Just a thought, as I said. Good luck with your problem, in any case.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I thought of that, the memory card does work in other phones and other memory cards can't be read by the incredible. So it's definitely the phone.

Yeah, I figured it was something more. Just wanted to put it out there because of the possibility of more than one issue going on simultaneously. I know it's rare to have multiple problems at once but it does happen on occasion. Any luck zeroing in on your problem?
Sent from my ADR6300 using XDA App

Hey there, You linked to my post. I ended up having to get a refurb from verizon. my situation was the same and I was able to get the phone to "s-off" before I called them up and went through verizons troubleshooting routine.
they overnighted a refurb for free.
Best of luck with your phone.

Ixa said:
Hey there, You linked to my post. I ended up having to get a refurb from verizon. my situation was the same and I was able to get the phone to "s-off" before I called them up and went through verizons troubleshooting routine.
they overnighted a refurb for free.
Best of luck with your phone.
Click to expand...
Click to collapse
I'm thinking of going that route as well. I haven't been able to find any solutions anywhere and that seems like the best option.

My brand new Inc did this out of the box. I could get it to boot if it was plugged into USB, but even then things weren't quite right (Bluetooth didn't work, WiFi was wonky, internal storage was not recognised, etc). Apparently this is a Qualcomm hardware error code, and a warranty replacement is your only real option. Good luck!

fix
ok this happens all the time and all i have to do is pull out the battery and wait 20 seconds then i just either boot the phone up or boot it into hboot and then boot into recovery and reboot the phone.

Possibly Bricked T-Mobile T989

So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.

aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?

charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.

Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!

I still have the phone, I'm gonna try this now. Will update with results.

aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.

Well, I tried both suggestions to no avail. Anyone else have any ideas?

aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.

no cigar with the hold for ten seconds method on the power button.

aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.

Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.

What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk

@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).

Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App

aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk

Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.

Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.

aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.

Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.

more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse

HELP! VZW Galaxy Nexus completely DEAD!!

I've searched & searched thru XDA without any luck or finding someone with a similar situation.
My GNEX is unlocked, rooted & running AOKP 36.
I hung up the phone after a call...locked it...put it in my pocket...took it out a few minutes later and the phone would not turn on. My battery was over 50%, so i thought i pocket-powered the phone down.
The phone does not boot into any mode. I've tried them all. It is not recognized by my Mac or PC. Here are the things i've done so far: Battery pull. Charge overnight. Removed battery overnight. I bought a new battery & i'm still having the same problem.
Any ideas before i call Verizon and take the loss? I would really like to recover my pictures & videos.
Thanks in advance.

So you have tried to boot into recovery by holding down power and the volume buttons?
If not try this to get to recovery to do a restore.
http://www.youtube.com/watch?v=1SDd1DZUs-M
If you tried this, then you might need to send it in.

Thanks for the reply, but i've tried that already. I'm out of ideas...it's unresponsive.

falotm said:
Thanks for the reply, but i've tried that already. I'm out of ideas...it's unresponsive.
Click to expand...
Click to collapse
Do you have another battery or friend with a gnex? My girls died completely while plugged in over night. I got another battery and it fired up.
Needless to say a clean install was the next step.
Sent from my GT-I9300 using Tapatalk 2

Also hold down power button for awhile. And also try.with a different battery.
...

I bought a new battery from Verizon and tried it, but its still unresponsive. I charged both batteries overnight and nothing happens.
I've held all buttons for several minutes with both batteries, but nothing happens. It wont boot and it won't boot into recovery/bootloader/hard reset menu, etc (android with stomach open LOL)
On a few occasions, when i connect to my PC, it says new hardware detected OMAP 4440 (or something like that) & asks to install drivers. I have the Gnex toolkit, but the program does NOT detect my phone.
Thanks for the replies.

This happened to my fiance's vzw gnex. She was on stock though. Just surfing the web and it turned off. Dead as can be. She took it back and they gave her a new one.
Sent from my Xoom using xda premium

Oh.. Man you lost the bootloader.... If you have warranty go ask for a replacement, it's a pain trying to get the phone back up..
They won't know the phone its unlocked since it won't turn on
Nexus Cm9 + Franco

http://forum.gsmhosting.com/vbb/f63...b-prime-via-usb-cable-freeeeeeeeeeee-1465412/
Try this?
Can't hurt...

My Nexus is from Verizon & the tutorial you linked is for the GSM version. Do you think it matters?
I will still give it a shot. Thanks!

Did you check the pin area where the battery connects? Are the pins in good condition or any small foreign object around them?

If you're careful you can *maybe* odin it back to stock (you've already lost the pics tho).
Look in the dev area for any odin threads.....links to files and stuff are in there.

Jubakuba said:
Try this?
Can't hurt...
Click to expand...
Click to collapse
Thanks for the link. I installed the drivers, phone was detected, ran thru the program, but it failed at the very end. I think its because my phone is i515 & not GSM version.
I've given up hope. Time to get a replacement. I hope it never boots and they don't find out its unlocked & rooted.
I appreciate everyone's input.
Thanks!

a friend mine has a similar problem..
phone died without reason
where i can download the drives that you made mention?
i'll suggest him to try that .bat file

[Q] Possible Brick

I decided to ROOT my phone, which seemed to be sucessful, and then I attempted to install a Custom ROM (where the problem began). This ROM used the AROMA installer and all seemed to be going fine. I rebooted at the end. I wasn't watching my phone at this point because I'm used to reboots following ROM installs taking a while so I just ignored it a bit. When I looked back finally, the screen was off. I figured that it had just gone to sleep but I couldn't wake it up.
What's worse is that I cant get it to turn back on at all! I've tried pulling the batter, hard reset (Power + volume up and power + volume up + home key). Nothing. Is there any advice anyone can give me? What did I do wrong and is there a way to recover the device?

How much battery left you had before flashing?
Sent from my SGH-T999

lazarat said:
How much battery left you had before flashing?
Sent from my SGH-T999
Click to expand...
Click to collapse
I'm not 100% sure actually. was low when I started the root process but I did have the device plugged in the whole time though. Do you think that's the problem? I actually swapped my battery with my GF's battery (which was nearly fully charged) so I don't think its a "dead battery" issue. Any ideas on how I can get it back on? Doesn't even show the charging icon.

Plug it into Odin and see if anything comes up.
Sent from my SGH-T999 using xda premium

Yes your battery died in the process of flashing which sucks bwcause i do not know what are the consequences of it but seems bad since you cannot even get into download mode. Never flash with battery below 50%. Good thing is though that if the phone does not turn on at all then jist go to tmobilw store say left it overnight to charge when woke up was all black screen. Idk whats wrong with it. Get a replacement.
Sent from my SGH-T999

Pull the battery out for like 2-3 mins then let it charge for like 15 and try to get in download mode... If it does pop odin open and flash stock image. You can find it under the stickies in dev section.
Sent from my SGH-T999

I wasn't able to resolve the issue but I was able to take it back to the TMO store and just swap it for another one. The guy didn't ask too many questions. Crisis averted but it's made me hesitant to flash on this again so soon. I've rooted and flashed dozens of Android devices for myself and others over the years but this is the first time something like this has happened to me. Being careless I suppose. When I get my nerves back up, I'll be back.
Thanks for all the help you guys offered. I appreciate it.

[Q] Bricked T999

I have a GS3 that was rooted with a CM rom. I was using it the other day and the screen just suddenly went black. I tried rebooting it and popping out the battery, but to no avail. I can't boot it into download or recovery mode either.
When I put in the battery, the phone vibrates but nothing else. When I plug in the USB cable with no battery, it vibrates and the LED comes on for a few seconds before flickering off.
My first priority is data recovery, I've been a bad boy and haven't backed up my data for a while. My second priority is making it so they can't tell I have a flashed ROM when I send it out for warranty service, though AFAIK, this may be a nonissue.
I tried to make a 300k jig, and it didn't work (assuming I got the pins right).

Have you tried KAsp3rd's debrick method?
Stickies in development.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Have you tried KAsp3rd's debrick method?
Stickies in development.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I'm not stuck in QHSUSB-DLOAD as far as I can tell. Would it still be effective?

Could be. It basically allows you to boot download mode from the sdcard. From there you Odin flash the firmware and hopefully that would fix it. But if it's a hardware failure, which it could be per your description, I doubt anything will work.
Sent from my SGH-T999 using Tapatalk

New update. I figured out that the 300k ohm resistor trick DOES work, but only for like three seconds. Meaning that they'll be able to see the custom binary count, but (as far as I know) I can't reset it to 0.
The weird part is that it only works if I plug the usb jig into the phone before putting the battery in, if I put the battery in first, it doesn't work. It almost seems like it constantly thinks the power button is being pressed or something.
I guess I'm opening it up and looking for a short. The power button operates normally tactile-y speaking.
EDIT: new new update. I wasn't able to find anything physical when I looked at the pcb. But I verified my theory, somewhat. When I hold home and volume up/down (without touching the power button) when I put the battery in, it boots into download mode for a second before shutting down.
It's not behaving exactly like it would if it was only that though, because I tried holding the power button down on the t999l I got as a replacement, while inserting the battery, and the boot screen shows up for a few, where a boot screen never shows up on the bad phone.
DOUBLE EDIT: can I swap that pcb with the one from the t999l, or are they too dissimilar? Would I be able to swap it with one from another t999, or does the board that has the power switch also have the onboard storage?
TRIPLE EDIT: I answered my own question, the eMMC and the power switch are on the same board. But if the fault is caused by something else (e.g. a camera), would I be able to plug all the other hardware from the t999l into the t999, or can I just boot up the t999 without most of the hardware connected as a test?

I would not risk going through all that trouble. Not quite sure why you would honestly. You got a T999L right? Warranty replacement I assume? It's a superior device so why my not just use it as is?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
I would not risk going through all that trouble. Not quite sure why you would honestly. You got a T999L right? Warranty replacement I assume? It's a superior device so why my not just use it as is?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
1. I really want my data back.
2. I risk getting charged for out of warranty if they see it was rooted and flashed.
3. I'm going to sell it anyways, I got a note 3 because the S3 was on backorder and I couldn't do my job without a smartphone.

1. I'm sorry to say, but plan on this not being possible.
2. If it won't boot there is little chance you'd have to worry about it. They aren't going to go to extraordinary measures to check k the counter. Many people have claimed they sent a dead device back and never got charged, even though the counter had been tripped.
If you damage the good hardware you won't have much to sell.
I don't understand why you'd be willing to attempt to Frankenstein the two devices, but not at least attempt the debrick method I mentioned.
Also, you should be aware, even if it's something else, not a bad chip, it probably won't work. Much of the hardware is in fact different between the two. Different camera, different radios, different SoC....
I wish you luck if you decide to try this, but imo you are taking an awful big risk to try something that probably won't work anyway.
If your data is really that important maybe you should look into a data recovery service.
And in the future, back up back up back up!
Good luck whatever you decide. Let us know what happens.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
1. I'm sorry to say, but plan on this not being possible.
2. If it won't boot there is little chance you'd have to worry about it. They aren't going to go to extraordinary measures to check k the counter. Many people have claimed they sent a dead device back and never got charged, even though the counter had been tripped.
If you damage the good hardware you won't have much to sell.
I don't understand why you'd be willing to attempt to Frankenstein the two devices, but not at least attempt the debrick method I mentioned.
Also, you should be aware, even if it's something else, not a bad chip, it probably won't work. Much of the hardware is in fact different between the two. Different camera, different radios, different SoC....
I wish you luck if you decide to try this, but imo you are taking an awful big risk to try something that probably won't work anyway.
If your data is really that important maybe you should look into a data recovery service.
And in the future, back up back up back up!
Good luck whatever you decide. Let us know what happens.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Reading through the whole thread, I am going to agree with the Doc. Why would you go to all that trouble ? Nobody is going to be able to salvage that data, let alone snoop in it. You are best move on rather than Creating that Frankenstein Monster as Doc aptly put it.

The frankenphone would only have been for if the phone didn't work without the camera/speaker/etc connected. However when I disconnect everything from the main board except for the screen, I get the same behavior. So I guess the only thing I would want to test would be the touchscreen. I can't find any info on if the t999l touchscreen is compatible with the t999 board, but if anyone knows, that would be great.
I'm still going to try the microsd card debrick method, I was concentrating on the usb jig last night since that got me further than anything else so far.
As to why, I have pictures and whatnot on the phone that I want to save, as well as a bunch of work crap that will take me dozens of hours to recreate, plus a bunch of other personal stuff. If I can't get it, then I can't get it, but I want to exhaust my resources (within reason) before giving up.

dubloe7 said:
I'm still going to try the microsd card debrick method, I was concentrating on the usb jig last night since that got me further than anything else so far.
As to why, I have pictures and whatnot on the phone that I want to save, as well as a bunch of work crap that will take me dozens of hours to recreate, plus a bunch of other personal stuff. If I can't get it, then I can't get it, but I want to exhaust my resources (within reason) before giving up.
Click to expand...
Click to collapse
Try JTAG instead of this if sdcard doesn't work. Most of t999l hardware is supposed to be identical. Since partition are potentially different. So phone may not boot. But you might be able to do adb. Good luck.

Actually it's the other way around. Partition layout is the same (though firmware incompatible) and hardware is definitely different.
Sent from my SGH-T999 using Tapatalk

SD card didn't work, looking for jtag instructions.
EDIT: The more I look, the more it looks like a faulty power switch. Unfortunately, it doesn't look like I have a way to short the power switch or something in a way that doesn't void the warranty...
Any help on this is appreciated.

Well, I think I'm completely screwed now.
I found this, http://androidforums.com/samsung-ga...-help-black-screen-vibrating.html#post5262715 and somehow managed to lift the freaking solder pads.
What do you think the chances that they won't charge me a couple hundred dollars for "out of warranty service" are?
EDIT: good news: Confirmed that the cable that I lifted the solder pads on, which I assume is an antenna, probably isn't the problem (unplugged it on the t999l, and it works fine).
bad news: I also confirmed the power switch itself isn't the problem either. The left and right hand side aren't connected (according to my multimeter) when the button isn't pressed, but they are when it is.
Another edit: I unconfirmed the power switch part. It looks like the button only needs the slightest contact in order to short. I removed the power button from the case, surprisingly difficult since I saw people complaining about it falling out. Now the difficult part is making it think the switch is closed for long enough to not turn it on, but not long enough to turn it back off. I've gotten it to the boot logo, but I haven't gotten it to fully boot.
Yet another EDIT: the only way I can get it to turn on long enough to see the boot logo is by smacking it in my hand after it turns on, which seems to interrupt the constant button press signal. From the metering on the switch, it seems that even less contact is needed to turn on the phone than to signal the multimeter. Any suggestions as to somewhere to cut the power switch signal other than the power switch?