Database Info

JTAG pin out for ATT Skyrocket

I was curious if anyone has had any luck in locating the pin out for the jtag port on the ATT Samsung SGH-i727 "Skyrocket". I'm currently trying to locate and jtag my phone. Its not bricked. But I'd like to start digging and hopefully find an unbrick solution
Sent from my SAMSUNG-SGH-I727 using xda premium

Anybody...?
Sent from my SAMSUNG-SGH-I727 using xda premium

It does work. There are people who offer jtag services . But you will need to track them down and hope the share the pin out with you

Oh I know it works. The MSM8660 also supports UART over USB just like SP5C110 chips did. I've been seeing people with a lot of bricks. So I'd basically like to see if we can do an "unbrickable mod" with this chip set too.
Sent from my SAMSUNG-SGH-I727 using xda premium

Yup, ton of bricks around here! Mostly from user error (flashing roms for other devices), but some mysterious ones as well.
I'd love to see this happen.
Alternately, people have been looking into the possibility of using QPST (Qualcomm Product Support Tool) to re-flash the system image (hex file maybe?). QPST seems to see hard bricked phones when Odin does not.
But I hear QPST can be pretty tricky (and dangerous), so that may not get anywhere.

Yes QPST would fix the brick, I'm very sure of it. Problem is like you said very hard to use unless your experienced with it. And also what would we do about the hex? If there's a way to flash on in QPST maybe there's a way to dump one. However, would we need to "virginize" it as to allow install on phones without loss of device specific information?
Sent from my SAMSUNG-SGH-I727 using xda premium

Thx for alls answers... I gonna see what I do..thx!!

TiTy said:
Thx for alls answers... I gonna see what I do..thx!!
Click to expand...
Click to collapse
Did you find the pinout configuration for i727?
Is there any place that lists the pin out connections for different phone models or do they come with the Riff box?

heres a video with a jtag attached, see if u can see what wire is what, it might help
http://vegaslsx.com/vbulletin/youtube_browser.php?do=show&vidid=AkJQAbwZjRk

atrixboy said:
Yes QPST would fix the brick, I'm very sure of it. Problem is like you said very hard to use unless your experienced with it. And also what would we do about the hex? If there's a way to flash on in QPST maybe there's a way to dump one. However, would we need to "virginize" it as to allow install on phones without loss of device specific information?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I often buy broken phones from a friend and have access to two SGH-I727R phones one is hard bricked due to my not noticing that re-partition was checked on the second attempt to flash clockworkmod recovery with ODIN. The second one boots but has multiple issues like no wifi, no Bluetooth, no SIM connection, random data loss on internal SDCARD, USB doesn't show up on computer but charges, likely due to the couple of resistors that fell off the board with the USB connector. I seem to have lost them from the box I put them in. They were specs of dust, lol. Happened when I was cleaning off the white powdery corrosion from the boards.
The corrosion resembles battery acids and aluminum oxides from the housing degrading. And also other damage from water and the elements and likely all manner of unknown liquids, it was found at the local Garbage dump's battery disposal bin.Plus the phone states that the USB cable is connected when it isn't and I have to use the 300kOHM jig to get it to stop that silliness long enough to start USB debugging mode. And last but not least the battery will only charge when it is in download mode or recovery due to warnings that the battery is "too hot and too cold"???? therefore it won't resume charging until it has sufficiently cooled and warmed up (in reverse I am assuming hahahaha) from it's erm hot cold state. Which it isn't. Oh one more thing when booting to the stock rom it had before it was brutally raped and tortured then left to die in a bucket of decomposing and leaking batteries it shuts down app by app till it causes a reboot then it goes through the same loop. I can only get severely stripped roms to boot before the loop happens but after one successful boot it does stay booted. Normal sized Roms crash before it can successfully optimize it's apps. etc...
Anyway, I thought that I would try to use the bootable board to create a hex to flash to the nonBooting QHSUSB DLOAD bricked one, but alas I cannot seem to (haven't searched on it yet been wasting time playing around with QPST without any idea of how any of the tools work or what most of their capabilities are or what 70%+ of the terminology it uses means in relation to the rest of the limited knowledge and experience I have with erm normal erm flashing thingamy bobs. I could understand just enough of it to likely make things worse had I been able to connect to the booting device. And either way while in QHSUSB DLOAD I can see the phone but it does not seem to want to connect and Windows refuses to open the help files because it doesn't want to support those types of help files anymore. So once I find out how to
***So that's the background I apologize for the length. If anyone knows how I go about connecting the booting phone to QPST so I can create a flashable HEX file to then unbrick the other one please let me know. Or where I can get a hex file that is meant for the SGH-I727R phone. Thanks. Googling Hex file etc... returns useless results that have nothing to do with what I want. I will keep trying to find the information and if and when I do I will post it here for yourselves and anyone else that may need it. Plus I will upload the HEX file to my dropbox or similar cloud storage for anyone to use that needs it.

jtag is the only way, afaik no ones has done a diy jtag on the sr, Mobiletechvideos has been used by sr owners w/good results

[Q] I need help with my SL101 please

I admit I'm pretty new to all of this, but here's is the issue I'm having. I have an Asus Slider SL101 and I tried using the "One-Click Root" tool that is available on here and works for Transformers and Sliders. It rooted fine, then rebooted... I didn't even have a chance to install CWM or any other type of recovery, so all I have at my disposal is stock. After the reboot, it gets to the Asus loading screen with the progress circle spinning. Forever. I tried going to a cold boot, stops at the same screen. Tried wipe data, I get the blue progress bar and it looks like it works, same loading screen. Tried recovery, I get the red triangle. I've had it connected to my computer before but now when I try to connect it says that the MTP driver fails, I've also tried it on an XP laptop and it constantly says MTP Device found. I don't know if this is completely bricked, soft or hard. I'm completely lost and I would greatly appreciate any help. It's still under warranty and I did get an RMA number but I'm hoping someone can advise me into getting this done myself as I've read the horror stories of people sending theirs in only to hear that the warranty won't cover this. Thanks in advance.

Bump? Any help or suggestions at all?
Sent from my MB860 using Tapatalk 2

Unfortunately we Slider owners are pretty screwed in times like these since we can't use NvFlash. Might be best off going the RMA route if you're not able to use the stock recovery.

Damn... what are the chances they'll honor my warranty?
Sent from my MB860 using Tapatalk 2

tge101 said:
Damn... what are the chances they'll honor my warranty?
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
I had the same issue happen to me, you can always pretend you don't know anything. This may not be the most honest but I told them a system update messed mine up. They restored the system for me while under warranty.

From my standpoint, if they don't make recovery from an SD card a default option, I have no problem being a little dishonest. Especially when I'm reading people are being quoted $200 on a $300 device.
Sent from my MB860 using Tapatalk 2

tge101 said:
From my standpoint, if they don't make recovery from an SD card a default option, I have no problem being a little dishonest. Especially when I'm reading people are being quoted $200 on a $300 device.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
That's pretty brutal, but they can't necessarily see what you did to it. At least from my standpoint, the device was completely bricked when I sent it to them. And still within warranty, which is why I bothered at all, because the slider's support is pretty lacking from the dev community compared to the transformer. :\

Connected to phone via USB, must copy SD card, device always offline

I have been getting desperate on an issue which I mention in another thread.
I wrecked my phone and got a replacement, got it back to a state I wanted, so that's all good... However, I need to send the damaged phone back by tomorrow (Thursday) or else TMO is going to slap me with a $850 fee.
The problem is that I need to copy the contents of the SD card. This isn't an unreasonable endeavor because the phone, from all appearances, works fine, other than the fact that about 5 seconds after it gets to the desktop, it goes black...but it continues to sound notifications, etc., so I know it is still functioning, albeit with no screen.
When I plug into my laptop using adb, it acknowledges the device, but says its "offline". From looking around the web reading others experience with this error, it doesn't seem like a "real" error. Solutions suggested are changing USB ports, reinstalling drivers, rebooting phone, etc., and the problem seems to go away for those users. However I have tried these solutions, and yet my device still is considered to be "offline".
I use ADB often enough that I never turn off USB debugging so that isn't an issue. But while I know how to push and pull files , or fastboot flash a recovery, I don't know much else about ADB. Is there any experts or ADB gurus who can suggest some other ideas about how I can get this USB convection working? Or at least run some diagnostic too see if in fact the SD card is damaged?
It is very important I get these files of my SD..they are attorney work product and notes regarding a transaction (and also several pictures from the night the phone was damaged) . I make regular backups to dropbox, but apparently not regular enough as my backup wasn't current when I damaged it.
Please ... I am looking for any suggestions. And further, I can't believe that ifthe sd card was in fact damaged, I should still be able to recover some portion of the files. Can one access the sd card when the phone isn't on? It seems rather counterintuitive to me for HTC to create this obstacle consisting the microSD is non-removable on the first place.
Any thoughts are very much appreciated.
Sent from my HTC VLE_U using xda premium

Can't you just mount usb in recovery and pull the contents that way?
Sent from my HTC One S using xda app

lampel said:
Can't you just mount usb in recovery and pull the contents that way?
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
The screen didn't work.
Sent from my One S using Tapatalk 2

Because he said it worked for five seconds I assumed that to be rom related and thought there might be a possibility that recovery would work. After I posted I saw other posts and realized he's pretty knowledgeable... Not too used to that.
Sent from my HTC One S using xda app

[Q] Rooted phone won't turn on - still return to Verizon?

My rooted phone recently started crashing, then decided to stop turning on altogether, no download mode or anything. Probably a SDS residual memory issue.
1. Anyone have experience returning this to Verizon? Do they even care?
2. Will they even be able to know you rooted if it can't turn on?
Help much appreciated!

JaceB said:
My rooted phone recently started crashing, then decided to stop turning on altogether, no download mode or anything. Probably a SDS residual memory issue.
1. Anyone have experience returning this to Verizon? Do they even care?
2. Will they even be able to know you rooted if it can't turn on?
Help much appreciated!
Click to expand...
Click to collapse
If won't boot they have no way to check it. They have to reflash it (JTag) which wipes any trace. They send to Texas to refurbish and they don't even look.

Are you sure your battery is OK? It's really a rare thing for a phone to completely go through a sds issue like that.
Plug it in to your computer, and see if it mounts it as a qusb_dload drive to see if you're hard brick. Also, plug it in without a battery and see if the red light comes on.
I'm assuming Verizon would be able to tell you were rooted if your phone is bricked like that. Either way it's committing insurance fraud for turning that in and claiming it wasn't your fault. They would likely look for any reason to charge you $500 for a new device.
If it's the battery it's an easy fix, if you're hard bricked you still have options to fix it, if it's a hardware problem Samsung will fix it despite it being rooted. No need to go through Verizon.
Sent from my SCH-I535 using Tapatalk 2

JaceB said:
My rooted phone recently started crashing, then decided to stop turning on altogether, no download mode or anything. Probably a SDS residual memory issue.
1. Anyone have experience returning this to Verizon? Do they even care?
2. Will they even be able to know you rooted if it can't turn on?
Help much appreciated!
Click to expand...
Click to collapse
I had the same thing happened to me a few weeks ago. I used a sd card and img file to debrick the phone.

BadUsername said:
Are you sure your battery is OK? It's really a rare thing for a phone to completely go through a sds issue like that.
Plug it in to your computer, and see if it mounts it as a qusb_dload drive to see if you're hard brick. Also, plug it in without a battery and see if the red light comes on.
I'm assuming Verizon would be able to tell you were rooted if your phone is bricked like that. Either way it's committing insurance fraud for turning that in and claiming it wasn't your fault. They would likely look for any reason to charge you $500 for a new device.
If it's the battery it's an easy fix, if you're hard bricked you still have options to fix it, if it's a hardware problem Samsung will fix it despite it being rooted. No need to go through Verizon.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
When I plug it in without a battery the red light comes on for awhile then turns off. That means it's bricked right? Plugging it into a Mac yields no response.
My phone was working fine for a year+ after rooting, I never flashed a ROM or kernel. It just randomly started crashing a week ago for no discernible reason (reading the boards it sounds like what others experienced after the SDS fix). I don't think this is my fault correct?
jmxc23 said:
I had the same thing happened to me a few weeks ago. I used a sd card and img file to debrick the phone.
Click to expand...
Click to collapse
Is this relatively simple to do? Happy to try all other options, but it feels like a hardware/Dummy File Generator issue.

JaceB said:
When I plug it in without a battery the red light comes on for awhile then turns off. That means it's bricked right? Plugging it into a Mac yields no response.
My phone was working fine for a year+ after rooting, I never flashed a ROM or kernel. It just randomly started crashing a week ago for no discernible reason (reading the boards it sounds like what others experienced after the SDS fix). I don't think this is my fault correct?
Is this relatively simple to do? Happy to try all other options, but it feels like a hardware/Dummy File Generator issue.
Click to expand...
Click to collapse
Ya I'm pretty certain it's bricked, it's not a really hard process, but you need to follow the directions exactly and it takes persistence.
http://forum.xda-developers.com/showthread.php?t=2397145
That's the Verizon thread, the sprint thread gives specific directions, just use the debrick image used in this thread.
Other option is jtag or taking your chances and turning it back in, prdog knows what he's talking about more than I do, I'm just extra paranoid dealing with something potentially that expensive.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Ya I'm pretty certain it's bricked, it's not a really hard process, but you need to follow the directions exactly and it takes persistence.
http://forum.xda-developers.com/showthread.php?t=2397145
That's the Verizon thread, the sprint thread gives specific directions, just use the debrick image used in this thread.
Other option is jtag or taking your chances and turning it back in, prdog knows what he's talking about more than I do, I'm just extra paranoid dealing with something potentially that expensive.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! And thanks prdog for the peace of mind! If anyone else has an opinion/experience with this let me know, don't want to do anything stupid.:fingers-crossed:

x16 by powkiddy not turning off with hard shutdown nor is booting pass loading icon

Hi all,
So, my friend tried formatting the SD of this device and subsequently, the device turned itself off, now is not booting pass the loading icon, and will not turn off via hard shutdown (they just let the battery drain). I presume that the software has been corrupted. However, i am not familiar with this device or Pi etc. I have found the latest firmware and tool for the device amongst the comments. But the device isnt being picked up by Window.
I have gone ahead and started working towards forcing access to the device. I have started to install USBView to aid me. And will go from that. I suppose I'm more doing this out of interest.
But anywho, i just want some guidance on what i should be doing, or has anyone done this themself and or friend etc and could share what they did?
So, any help please would be great! And happy to answer any questions!
Thanks Kindly!

Leu Do said:
Hi all,
So, my friend tried formatting the SD of this device and subsequently, the device turned itself off, now is not booting pass the loading icon, and will not turn off via hard shutdown (they just let the battery drain). I presume that the software has been corrupted. However, i am not familiar with this device or Pi etc. I have found the latest firmware and tool for the device amongst the comments. But the device isnt being picked up by Window.
I have gone ahead and started working towards forcing access to the device. I have started to install USBView to aid me. And will go from that. I suppose I'm more doing this out of interest.
But anywho, i just want some guidance on what i should be doing, or has anyone done this themself and or friend etc and could share what they did?
So, any help please would be great! And happy to answer any questions!
Thanks Kindly!
Click to expand...
Click to collapse
You will have to solve the issue of getting Windows to recognize the device first. Then, you "might" have a chance, but, still no guarantees.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You will have to solve the issue of getting Windows to recognize the device first. Then, you "might" have a chance, but, still no guarantees.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Do you have any suggestions?

Leu Do said:
Do you have any suggestions?
Click to expand...
Click to collapse
When you connect the device to PC, does it make the connection sound? Does it show anything in Windows Device Manager? If either of these is no, you will not be able to fix this yourself. This will require expensive, specialized hardware/software tools or may even require replacing the motherboard.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
When you connect the device to PC, does it make the connection sound? Does it show anything in Windows Device Manager? If either of these is no, you will not be able to fix this yourself. This will require expensive, specialized hardware/software tools or may even require replacing the motherboard.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
It is no to those two. What software tools are you thinking I will need? I think the hardware would be fine, according to them nothing was broken. It was half formatted, so would make sense the hardware isn't speaking.

Leu Do said:
It is no to those two. What software tools are you thinking I will need? I think the hardware would be fine, according to them nothing was broken. It was half formatted, so would make sense the hardware isn't speaking.
Click to expand...
Click to collapse
The hardware/software tools are probably more expensive than replacing the device, then there is a matter of the significant technical skills required to use those tools, not an easy task, by any means. It's better to just replace the device as there are no guarantees that the process will even work, to begin with.
Or, replace the motherboard.
Edit: The hardware/software tools that I am referring to are things such as those required to run a JTAG service, RIFF box, Octopus box, etc. Pretty technical stuff, failure means replacing the motherboard or the device anyway, sooo....
Why waste the time and money?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The hardware/software tools are probably more expensive than replacing the device, then there is a matter of the significant technical skills required to use those tools, not an easy task, by any means. It's better to just replace the device as there are no guarantees that the process will even work, to begin with.
Or, replace the motherboard.
Edit: The hardware/software tools that I am referring to are things such as those required to run a JTAG service, RIFF box, Octopus box, etc. Pretty technical stuff, failure means replacing the motherboard or the device anyway, sooo....
Why waste the time and money?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I am doing it to learn, they are replacing the device. So, it isnt like a Pi? Ive never heard of these software tools either. Surely there is open source. I will dig around. I have experience to a degree.
Edit: as i said i am learning so i just want to ask why you have drawn that conclusion? Is that just general practice?

Droidriven said:
You will have to solve the issue of getting Windows to recognize the device first. Then, you "might" have a chance, but, still no guarantees.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
You have to reset with the Micro USB removed , otherwise it will not boot. that is the microsd card.