Related
So I plugged my Vibrant into Odin to revert to stock. Apparently everything went wrong, and now my phone is stuck at the Phone---!---computer screen. It seems that my phone won't respond to hardware methods of entering download mode, so am I screwed?
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
I've tried that, and many other methods, multiple times already. It seems that none of the volume/power methods do anything for my phone. I'm certain that if hardware-locks do exist for certain vibrants, mine just so happens to be one of them (Date on box is August 13). I just want to know if anyone with a similarly dated phone has ever been able to access download mode without adb.
If anyone knows of more methods, please post them. If all else fails, I'll go complain in my local T-Mobile store that my phone died. I have no idea if that'll get me anywhere, but it's worth a shot.
Does anyone who has had a problem similar to mine know of any fix? By that I mean, has someone who has had a presumably hardware-locked phone ever been able to boot it into download mode without adb? I'd really like to know if I can salvage this thing, or if I have to try my luck with T-Mobile.
Try holding volume down and holding power button and plug in USB while this is happening.
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Generic112 said:
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Click to expand...
Click to collapse
When you see the " !---> (pc)" symbol, plug your USB in. Hold down volume +, volume -, and power. As soon as the screen turns black release the power button only. Continue holding Vol + and Vol -. You'll enter Download mode.
I've tried that multiple times, but I will continue to try it. It seems as though my phone won't register that buttons are being pressed. All that happens is the phone reboots to the Phone--!--Computer screen every time the power is held and released (As it should). No combination of buttons seems to have any affect on this. Oh well, I'll continue trying and hopefully someone will post a working method.
I have the same problem and the hardware button method isn't working and I am stuck at the Phone ! Computer screen, and I read around the forums and they say that some Vibrant's have the hardware method locked, so you can't boot into Download mode from using the buttons. Since adb cannot find the phone when its stuck at this screen it seems we are both screwed. I have found no other solution other than returning it Tmo, not sure if they will exchange since it might be a violation of warranty.
I'm just going to play dumb when I go to T-Mobile. I'll say it just booted into that screen, and I can't get out of it. The hardware lock appears to be a defect, since it's not present on most Vibrants, so that should be able to warrant the replacement phone. I've been with T-Mobile awhile, and they're usually pretty good with replacements. Besides, the phone would be easily fixed if it wasn't broken in the first place.
But before I go to T-Mobile, I'm going to try and talk to Customer Service. If it's a common problem, then I'm sure it can be covered under warranty (Even though MOST ways of getting it require voiding warranty). Again, on the basis that this wouldn't be a big deal if my phone worked like a normal Vibrant. Besides, I'm sure T-Mobile can flash it without requiring the hardware method, so even if they only charge me some sort of service fee, I won't really mind.
As final moral reassurance for myself, I only tried to flash it because apps started FC on me and the phone constantly acted weird. The only thing I've done is root it, so it's not like I really set it up to fail.
Let me know how it goes with Customer Service. I would to get this problem resolved as well with the least amount of trouble. I don't want to have a brick and have to pay like $500 for a new phone. And I think the hardware buttons thing might actually be a defect. I tried doing the hardware buttons thing to get to recovery mode once before and it worked. I did this to install an update.zip to root the phone. It only worked that one time and now the buttons don't boot into recovery mode or download mode. It if works once then not again, there has to be something wrong.
I'll be trying them tomorrow (It's 10PM where I am). If all goes well, I'll try and contact you. I'm pretty sure I'll be safe so long as I don't mention rooting it. The firmware flash they'll have to do should help me on that front, so unless they catch on, I should be safe. Anyway, hopefully tomorrow I'll be good news, otherwise expect some post from me on Monday or Tuesday, depending on whether I have the time to deal with them or not.
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
I am also struck with the same problem
Hi,
I am also struck with the same problem. Please let me know if you guys got any method to resolve the problem or T-Mobile was able to help.
the3dman said:
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
This method actually worked for me. I was beginning to think I'd have to build the USB jig, but tried this as a last ditch. Thanks!
The above method has worked for me numerous times with the same problem, my old bricked one, and my new one. Try holding down power button as well once or twice, never know. You have to keep the volume buttons pressed the whole time for it to work.
Sent from my SGH-T959 using XDA App
ViralCipher said:
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
Click to expand...
Click to collapse
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
ech419 said:
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
Click to expand...
Click to collapse
He should be able to get the phone woking again, what happened is not a big deal. If he sends it in the way it's sitting right now, t'Mo's techs won't have a problem getting it working again. (IMO) Especially if they find out the phone's rooted, I wouldn't be surprised if he gets charged.
I bricked my phone so bad, it was beyond recovery. I erased the bootloader, therefore it was completelly dead. No life. I got a replacement under warranty for free, never got charged for it.
My advice would be to try and get to work again before sending it in.
-----------------
---This first post is outdated. My current question is one post below. I've left the content of this post for other noobs to see.
-----------------
Hey folks, sorry to bother you all but all input would be greatly appreciated. I'm rather unfamiliar with android flashing and kernels, and have spent the last 8 hours trying to figure this out to no avail.
Following this (http://forum.xda-developers.com/showthread.php?t=1238070) (section 5) guide on how to get back to stock gingerbread on my phone (after a few partially failed attempts flashing other roms), I was using Odin, had the .pit 2.2 as well as CI500_VZW_EH03_GB_CM.tar.md5 loaded into the program and left it running. About 20 mins in, the phone stopped progressing and I started to get concerned. After two hours, I powered down the phone and proceeded to reattempt the flash. This is when things got weird. My phone was unable to enter the Download Mode and instead showed Android system recovery when plugged in, or a black screen with a phone and a computer, with arrows between when not plugged in. The weirdest part is that the phone no longer recognized vol+ or the power button when in Android Recovery, and could only vol- to go down the menu, then was stuck at the bottom of the list.
I've searched everywhere on this site, and google to try and come up with a solution.
When pluggin into the computer, I hear a connection sound, but the device is not recognized by Odin. Pressing the running a blind vol+ and vol-, then a vol- to hope Odin recognizes the device, as pointed out in this (http://forum.xda-developers.com/showthread.php?t=1764022) thread, resulted in nothing. Holding vol- while pluggin in the usb cable, doesn't show the download mode. All of the steps in this (http://forum.xda-developers.com/showthread.php?t=1026746) thread proved futile, as most of them required download mode anyways.
I'm going to keep searching and keep you posted as things come. Your help as always will be greatly appreciated!
Edit: Things just got weirder... After a few more attempts at making this work, I'm now getting an "Unable to charge non-supported battery. See user manual." With this error, I'm not able to get into Android Recovery anymore. More searching...
Edit 2: AFAIK I'm gonna need a jig. Anyone confirm?
Edit 3: Got a jig, Download Mode working, all is well. Please remove this thread, or leave it for other noob flashers to see.
Hey Folks, its been a while since I last posted in this forum, but I ran into a pretty serious issue earlier this evening. I was attempting to flash CM9 to my T959D and was running into tonnes of trouble. Throughout my attempts I was restoring back to stock rom, kernel and bootloader. During one of these restores, Odin froze in Win 7. Since then I've been unable to detect any form of life from the phone. It simply sits in a black screen. Holding the vol down while booting, blind vol up and down cable inserting, using my Jig and inserting the cable/battery in various orders results in nothing. The most I hear is a device failure to connect sound in Windows with no sign of life in Odin.
What can I do?
Someone posted stating leaving the battery out for multiple days would reset something on the motherboard, allowing me to get into download mode. Though I was hoping to have this resolved tonight. I realize that there aren't many people left with these phones, but I hope someone has a solution to this.
I'm going to be installing ubuntu tonight on an older desktop in a effort to resolve this. Though my experience with it is very limited, and success is unknown.
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
TheMegosh said:
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
Click to expand...
Click to collapse
Make sure you use the stock Samsung cable see if you can reinstall the drivers hook it into the computer and hold volume down if you can get any type of signal from the phone your good.
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
MultipleMonomials said:
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Hey no offence but stop telling everyone on the street they need too soljeir there phone with unbrickable mod before they can fix I'm tired of having too calm the person down after you said they have too open up the phone its utter bull****. 1 out of 10 soft bricks you may need it I've been without download mode and fixed mine just fine.
Sent from my SCH-I500 using Tapatalk 2
An update:
Took my phone in to get the jtag service... He said some of my partitions were corrupted, one of which was the boot layer. He put a new bootloader on, and showed it could be placed back into recovery and download mode, but when I got home the device was even more dead than when I left; no device failed to connect sound in windows, just nothing. I'm taking it back to him in a week after exams to get this resolved. Maybe the battery has reached the end of its life...? I checked it with a volt meter, and it had 3v+ so I really don't know.
Sent using Science!
As bbrad pointed out, there may be other solutions, and my answer could be totally wrong, but if even your bootloader is cooked, Unbrickable Mod may be your only hope. Since UM affects startup code literally hardwired into the chip, it should work as long as the JTAG doesn't interfere.
Posted from my Fascinate using XDA Premium
Another update. So apparently I flashed a bootloader from another phone, which royally screwed up the partition, kernel and mounted drives. The technician managed to get the original bootloader, kernel and rom on the phone and everything is working from stock again.
Why on earth is the 959d Telus version such a pain in the ass to customize?
Is there anyone on here that uses a 959d that can direct me to a proper method to leaving stock? Before this entire situation I had vodoo kernel on, with cwm, but every time I flashed a kernel it would hang on reboot and either sit on a black or white screen. In a lot of cases I would flash in cwm, reboot, then I would be brought back to cwm as if there was no rom on the phone at all, no matter what I formatted and wiped.
When I'm not on my phone I can link all of the guides I've tried that leave me back where I started. So I re flash back to stock using Odin.
At the end of the day, I have to ask, is it really worth it in the end? I've rooted and flashed many roms on other phones but have never run into as many problems as with this fascinate t959d
Sent using Science!
I've been trying to get my S2 right for awhile and finally traced some of my problems to a bad microusb connector...Anyways.. was in the process of flashing back to stock from cm7 with Odin and the phone hangs on the downloading screen, waited an hour and nothing changed. I know it says to not power off device but there was no way around it. Now the phone is bricked pretty darn good I believe. I can't get it to come on at all. I've tried the 3 button recovery mode, the download mode, and the good ole fashioned power button. One interesting thing is that the phone gets warm to the touch when the battery is installed, like it's trying to process something. Any Ideas what I can do?
Pull the battery and leave it out. Next try to put the phone into download mode by holding either one or both volume buttons while plugging in the USB cable. The PC will provide the power. If this boots to download mode, you can try flashing again from there.
firstly, thanks creepyncrawly for the advice! I've read some of your post and tuts and they've been a big help to me!
I just tried what you said and it's still a no-go. You got any other tricks left in the bag??
Am I the only one who read the title as "blackberry"? God I feel stupid...
killman2659 said:
Am I the only one who read the title as "blackberry"? God I feel stupid...
Click to expand...
Click to collapse
That's what I thought too lol
Sent from Team Pirate
extremeways said:
firstly, thanks creepyncrawly for the advice! I've read some of your post and tuts and they've been a big help to me!
I just tried what you said and it's still a no-go. You got any other tricks left in the bag??
Click to expand...
Click to collapse
Only guess work as to what happened. If there are no signs of life no matter what you do (aside from the phone getting warm) then one guess is that the usb port failed/disconnected during the flash of critical files. However, the stock package does not contain bootloaders, unless you used one from the download repository. So like I said, just guessing.
Anyway, I don't know any thing else to do except jtag repair, and with a bad usb port, that would not be cost effective. If it's under warranty, then go for warranty replacement. As far as I can see, you didn't cause the problem by what you did. It looks to me like it was due to hardware failure.
Already ahead of you I called att for warranty yesterday. I'm thinking the same as you as far as a bad USB port messing my flash up. The phone had been giving me all kinds of fits lately with that and I had that camera buzzing issue as well. Through my searches on this site it seems like the USB ports on our phones are a weak point. lots of people having trouble with them. It looks like the same port other devices use so do any of you know if ours is a cheaper one or is it just the nature of the beast with phones because of all the plugging and unplugging that a phone naturally goes through in it's lifetime?? And what about the camera buzzing? Anyone figure out what exactly causes that? If I had to guess it would be using the LED as a flash light, that's when I noticed it happening.
I'm just thinking ahead to when I get my replacement now and want to change any of my habits with the phone if that will extend the life of it.
On a side note, they offered me a skyrocket, to which I pitched a fit to no avail. I ended up accepting that but with the stipulation that I get a i777 when they are back in stock. I may escalate it to customer relations to see if I can get an s3 out of the deal. Though to be honest I would take an S2 over an S3. I love my S2
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
I just got a galaxy note for my galaxy nexus last night (traded) and I took it home and install goomanager and downloaded a rom that was "compatible" it saved to the directory that goomanager puts it in so I rebooted into CWMR and cleared cache / data etc then proceeded to install zip from SD Card. it started by saying flashing kernel 4% or whatever and then came back with an error. me being as bright as I am recently...I fixed permissions and rebooted thinking that it would at least let me back into recovery.
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot. Is there a way I can at least get it into Download mode? Hell stick a magnet on it to erase everything even?
I don't need another paper weight..I have an iPhone for that.
Can you boot into download? If so, use Odin to flash the correct kernel.
Can you boot into recovery? If so, flash the correct kernel.
If you can't do either one, your phone is bricked and you will need to send it for a repair. $50 and one week later you will have your phone back with stock 4.0.4 ICS rom. Its called a JTAG service, from www.mobiletechvideos.com. Many note user have gone there, from just this thing.
The jig that works with other phones 99% of the time won't work with the note.
Don't trust CWR. Get your roms from our developers.
Jig 99% Of the time won't work... you made that statistic up. If button combos aren't working it's definitely worth a shot, resistors are super cheap, especially compared to jtag which doesn't sound needed here yet.
And what do you mean. "Don't trust cwr get your roms from the devs here"?
That is a recovery... he didn't download anything with it, he used goomanager.
And even if he downloaded it from here...he would've flashed it in cwm... xda isn't a custom recovery...
So you tried holding the down volume button+ power to get it into download? Flashing a kernel will not remove your recovery/download mode unless you flashed a Rom not made for your device that installed something on said partition(s).
As for the jig...don't know statistics, but I am a one percenter. Worth a shot imo.
https://www.youtube.com/watch?v=6K-lvaAop2w&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I717 using Xparent Gray Tapatalk 2
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade. Josh from mobile tech gave me one of his he sells on the site.
As nun said, the combos should work, they are in the bootloaders, flashing a kernel won't effect those unless says kernel is for a different device, then you wouldn't get a single thing outta the device at all, no charging screen, no bootloop. Nothing. Whatsoever.
studacris said:
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade.
Click to expand...
Click to collapse
Right amigo 99% + 1% = 100%. You and Nunhugger are the only ones who said a jig worked for them. So actually its way higher than 99%. . . But you guys are ninjas. Your phone would probably reboot if you just told it to. I just wanted to kill the eventual jig question early.
And my response about CWR was because it sounded like he used the old app Rom Manager to see what was available. Clearly it was wrong so I told him not to trust it, and put in a plug for our developers.
When an update is released the forum gets slammed with complaints about bad flashes of incorrect kernels, and I have seen several members heal their phone by flashing the correct kernel. I just figured he was not accustomed to the button combos of the note and would get to that eventually. But if it was for the wrong device I wanted him to get his mind around the $50 and week wait.
Sheesh. . . decaf.
Well seeing that I can't Get into either mode and no button combos will work, I am assuming I need the JTAG. I figured an app like GooManager would have at least gave me the right roms for my device. it did say i717 but that could just be my memory playing tricks on me.
Man, I'm real sorry. But the JTAG service has been used by many, and with lots of positive comments. Good luck.
hahah thats okay, I mean its a great phone, definately not worth keeping in a draw collecting dust so I will go with the JTAG service. Thanks Guys!
You still have signs of life, it shows the charging animation, therefore your phone isn't bricked.
Do some searching on making a jig, I personally think it's well worth a try.
You could very well fix your phone for under $10 and have the satisfaction of accomplishing this yourself And have the know how to do it again...
It doesn't have the charging animation. just a dead black screen.
Then why did you say this?:
leveliv said:
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot.
Click to expand...
Click to collapse
That's more than a little misleading...
Will not boot...could mean many things.
From a easily fixed bootloop down to a brick.
Saying it was infinitely charging made it sound less severe.
if it weren't for that line, I wouldn't have bothered to tell you to use a jig.
JTAG it is
cris, why do you need to experiment with finding the proper resistance? Why should there be any variability in that circuit? Perhaps that is why some users have used up as many as six usb port replacement parts.
By the way, my 99% statistic is, like my entire post, just my opinion, and strictly a figure of speech. If it were a fact I was quoting I would have included a footnote. Remember those painful things? Do we have to include disclaimers for any figure we use? Sorry to mislead anyone!
I said "dead" because its not necessarily dead because a JTAG thing can fix it..and I said "charging" because to the normal person who didn't know anything was wrong with said device it would look like it was charging. But anyhow. I'm sending the phone out this week. I just don't understand why all the phones can't be as open as the devices straight from google.
You're phone is dead.
JTAG is akin to zombie, the phone needs disassembled and a special rig is needed to hook to the motherboard and flash EVERYTHING back to the nand at the prebootloader level.
The I717 is pretty much just as open as a nexus as far as easily modified and rooted...
No locked bootloader even which nexus have though it's a single line in a terminal to unlock, that step isn't needed on this device.
Only thing that isn't as open is the hardware drivers.
You may have flashed an incompatible kernel for a DIFFERENT device... and that on any phone will brick you.
And ranger not sure if it's the circuits within the phones that vary from device to device, ands seem to require a more specific voltage across those pins to trigger download mode
Or, if It's the resistors that are the variable. They are only rated within a certain +/- tolerance the cheaper ones having a larger margin of error.
And lol yes I am a ninja, but I didn't do anything special to my jig at all, I got mine from mobiletechvideos, funny enough it's worked on 4 captivates, a vibrant, 2 note 1s, and an s3, but didn't work on an s2 I was fixing.
the one I got from Goomanager was probably for the i700 which shouldn't even be able to happen.
They have video proof of them fixing phones with dead black screens from exactly what happened to mine using the JTAG Method. As far as I am concerned this thread can be closed cause I got the answer to my question.
the JTAG rewrites basically everything anyways so it is being sent out later this week. Till then I'll use a blackberry or something...Take care guys hopefully next time you see me post it will be to help someone and not asking for help
You'll be up and running by next weekend. By then, lots of exciting development will be happening on the released rom.
I doubt it, I live in Canada and have to send it to the states. It probably be closer to the weekend. Unless I expedite everything.