My Nexus S went through the washer the other day and totally screwed my phone up. I was wondering if there were any way to retrieve the files and pictures saved to the internal memory. I didn't really think about the no sd slot issue until now It won't come on at all. I can take it apart if I need to. Any help would be greatly appreciated. Oh make sure you back up your files on a computer or secure cloud service. FML lol
I have never seen a way to get to the internal memory without being able to power up the device. Sorry
Yeah that's what I figured... I've looked all over the forums and googled it, everything. Im willing to try anything
zdiddy14 said:
Yeah that's what I figured... I've looked all over the forums and googled it, everything. Im willing to try anything
Click to expand...
Click to collapse
I think the chip is soldered on to the board so the only way to do it would be to unsolder it and solder it to a new nexus...
Eww dropping $300 on a new Nexus is a little out of the budget, I just bought a Droid Charge
Sorry, I really don't know any other way... Perhaps Samsung can help out?
Sent from my Nexus S 4G
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
Hi,
My A2 was hard bricked 2 months ago during downgrading from ICS to GB. Since then its nothing but a expensive paper weight for me. I have seen people recovering their HTC and samsung phones using Jtag method I was hoping someone has figured that for A2 as well. I live in India so I was not able to claim warranty. Any help will be highly appreciated.
Thank you.
john1989 said:
Hi,
My A2 was hard bricked 2 months ago during downgrading from ICS to GB. Since then its nothing but a expensive paper weight for me. I have seen people recovering their HTC and samsung phones using Jtag method I was hoping someone has figured that for A2 as well. I live in India so I was not able to claim warranty. Any help will be highly appreciated.
Thank you.
Click to expand...
Click to collapse
I am pretty sure people have looked into this man, but to no avail.
I'm not sure, but I wonder if the jtag method is rough for us due to our locked boot loader.
HTC and Samsung's are all unlocked for the most part.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
I am pretty sure people have looked into this man, but to no avail.
I'm not sure, but I wonder if the jtag method is rough for us due to our locked boot loader.
HTC and Samsung's are all unlocked for the most part.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
But, My friend had an old atrix for a while and even after having a locked bootloader using schematics and Riff box he flashed the firmware and was able to use his phone after a Hardbrick.
john1989 said:
But, My friend had an old atrix for a while and even after having a locked bootloader using schematics and Riff box he flashed the firmware and was able to use his phone after a Hardbrick.
Click to expand...
Click to collapse
I'm not sure if this would work on our phone, but I'm not saying it couldn't either. I think what it boils down to, and someone correct me if I'm wrong, but nobody has actually gotten the JTag or Riff boxes to even make an attempt at this. Therefore, we don't actually have a definitive answer to this...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Apex_Strider said:
I'm not sure if this would work on our phone, but I'm not saying it couldn't either. I think what it boils down to, and someone correct me if I'm wrong, but nobody has actually gotten the JTag or Riff boxes to even make an attempt at this. Therefore, we don't actually have a definitive answer to this...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
Yes, I agree to you, Its just that because of non popularity of Motorola phones very less hardware repairs are possible. If this be a samsung we might have thousand way to fix it. I know Jtag method little bit if someone provide me the Schematics and firmware then I will buy a riff box and flash it to my A2.
Well saw this video today : http://www.youtube.com/watch?v=4RL8pm_yRYs&feature=plcp
Is it relevant ? I mean i can see riff box and Jtag..can that be done for A2 also ?
john1989 said:
Yes, I agree to you, Its just that because of non popularity of Motorola phones very less hardware repairs are possible. If this be a samsung we might have thousand way to fix it. I know Jtag method little bit if someone provide me the Schematics and firmware then I will buy a riff box and flash it to my A2.
Click to expand...
Click to collapse
If you can come up with the JTAG and RIFF boxes, I'm hopeful you can enlist the help of your friend who's already done this type of thing. As for a schematic diagram for the Atrix 2, you may find something online, but not sure...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Guys the issue is what was done with the issue in the last leak. It hit an efuse, so unless someone knows how to reset that efuse with a jtag, then great, but when I was at at&t looking into it with the mobile design team we were unable to get the jtag and riff to see the a2.
so.... there are challenges that moto has thrown us with the last bricks that we will have to get past before we can resurrect the a2s that were bricked.
jimbridgman said:
Guys the issue is what was done with the issue in the last leak. It hit an efuse, so unless someone knows how to reset that efuse with a jtag, then great, but when I was at at&t looking into it with the mobile design team we were unable to get the jtag and riff to see the a2.
so.... there are challenges that moto has thrown us with the last bricks that we will have to get past before we can resurrect the a2s that were bricked.
Click to expand...
Click to collapse
What are efuse? What are the chances of resetting it?
Apex_Strider said:
If you can come up with the JTAG and RIFF boxes, I'm hopeful you can enlist the help of your friend who's already done this type of thing. As for a schematic diagram for the Atrix 2, you may find something online, but not sure...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
I asked my friend who used JTAG method on his old Atrix he said we need to find out the test points where the wires from riff box have to be soldered and then we will need a firmware that we have to flash from our computer. Test points can be obtained from Schematics diagram of a PCB board.
I'm no expert but Jtag basically connects (solders) to the board giving direct access to the NAND allowing you to, in a sense, force upload your firmware/bootloaders etc. I believe every phone should have this as Motorola has to have a port somewhere to debug and refurb the devices. I'm not saying it will work by default to a basic rift box, how ever it should be possible. I'm sure this process will equal to many many dead devices and a lot of patience from the dev trying to find it.
Edit: I've never owned or disassembled a Atrix 2 my statement is my logical thought line assuming Motorola has any sense in them. Also OMAP SoC are probably the most open source chipset out there.
So basically, someone needs to jump into this head first. Heck I got nothing else to do... research time!
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
So basically, someone needs to jump into this head first. Heck I got nothing else to do... research time!
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
The thing is you need to figure out how to reverse the efuse. I have no issues seeing our phone on the riff with jtag, if the the efuse is not blown. Once the ICS fxz fails happened I tested this at att corp, and we could no longer see the devices that I bricked with our old fxz method. we found the efuse that blew the circuit that brings power to the phone and the chipset, but we could not reverse it with jtag and riff.
Well shoot Jim, if you had no luck, this whole jtag thing is looking rather grim.
Thanks for looking into it though man.
Sent from my SAMSUNG-SGH-I727 using xda premium
My understanding of the matter is this: even if you manage to flash another firmware over the bootloader, you gain nothing, as there is a set of efuses required to be burned in to even allow the NS bootloader to run. Is this the case, or does it just prevent flashing the NS bootloader when the efuses are in their default state?
Hatrack said:
My understanding of the matter is this: even if you manage to flash another firmware over the bootloader, you gain nothing, as there is a set of efuses required to be burned in to even allow the NS bootloader to run. Is this the case, or does it just prevent flashing the NS bootloader when the efuses are in their default state?
Click to expand...
Click to collapse
I think I already answered this a few posts above. The efuses that are flipped basically render the phone completely useless and there is no power getting to the board or cpu anymore, only the white led is allowed power in this case. When this happens even jtag and riff box can not see the phone with the proper connections.
jimbridgman said:
I think I already answered this a few posts above. The efuses that are flipped basically render the phone completely useless and there is no power getting to the board or cpu anymore, only the white led is allowed power in this case. When this happens even jtag and riff box can not see the phone with the proper connections.
Click to expand...
Click to collapse
back in the day I used to "experiment" with DTV boxes. They were not ever meant to be flashed "manually." So, JTAG was the only way. There were two different ways depending on the box. One required power for the flash chip to come from the box, which had to be turned on in a "debug" mode. Others, you had to power the chip yourself and then flash it. So, I would think that even if efuse is blown you could still flash the chip with the proper schematic to locate the points. Problem is, you would have a properly flashed phone that still dont work because it can no longer power itself. The Jtag I used worked on xbox, dtv boxes, many things, JTAG is JTAG. If you had the right img JTAG would work, but with blown efuse it is a waste of time. anyone who is soft-bricked or stuck in FASTBOOT I think could benefit, but only them.
jimbridgman said:
I think I already answered this a few posts above. The efuses that are flipped basically render the phone completely useless and there is no power getting to the board or cpu anymore, only the white led is allowed power in this case. When this happens even jtag and riff box can not see the phone with the proper connections.
Click to expand...
Click to collapse
I didn't mean those efuses - you already told us that Moto's got some that render the phone useless. There are others that allow the NS bootloader to run though, no?
What are efuse ? can someone please explain me what it is?
I now understand that my A2 can never run again, but I only for my satisfaction I wanted to know that what is stopping from booting it up.
I hope you all can understand.
john1989 said:
What are efuse ? can someone please explain me what it is?
I now understand that my A2 can never run again, but I only for my satisfaction I wanted to know that what is stopping from booting it up.
I hope you all can understand.
Click to expand...
Click to collapse
I thought I knew, but motorola says Im wrong:
http://www.engadget.com/2010/07/16/motorola-responds-to-droid-x-bootloader-controversy-says-efuse/
Question is, are they lying, or would a jtag of a proper IMG result in reversing the efuse as they claim? Kinda makes me wonder if you send in a hardbricked phone, and then an hour later they're selling it as a refurbished.
my son has/had a nexus s 4g, and my wife has one too. hers still works. his is dead. no nothing dead. i don't want to fix it, just get the data off the card.
the board that contains the sd is detachable. what i wanted to know, is if i dissassemble her phone and put his card board in place of hers, can i then read his data? then after replacing the original board, her phone should be unaffected? these are my thoughts, just wanting to get some kind of feedback/confirmation before i proceed.
i did try searching, but i think my question is unique. I have seen noone taking things apart, except to do JTAG Service or screen replacement.
I have not tried this so a little more research may be necessary.
Are the phones all for the same network? If so, I think this is plausible. Replace SD, boot, then copy all the information.
NOT 100% SURE
Sent from my Nexus 7 using xda app-developers app
They are both sprint ns4g.
Sent from my ICS Epic 4G using xda app
here is the deal, the answer is yes, kind of.
if you switch the board it will read. if the board is good.
turns out that it is the part that is bad.
put the good one in the phone that did not work, and it booted. so there is the answer. the bad one did not boot...
put board back in original, and it works as it did before.
diptenkrom said:
my son has/had a nexus s 4g, and my wife has one too. hers still works. his is dead. no nothing dead. i don't want to fix it, just get the data off the card.
the board that contains the sd is detachable. what i wanted to know, is if i dissassemble her phone and put his card board in place of hers, can i then read his data? then after replacing the original board, her phone should be unaffected? these are my thoughts, just wanting to get some kind of feedback/confirmation before i proceed.
i did try searching, but i think my question is unique. I have seen noone taking things apart, except to do JTAG Service or screen replacement.
Click to expand...
Click to collapse
Why is it dead? How did it die?
Tell us more so perhaps there will be no taking the phone apart to get the data off SD card.
Vs Nexus S4G using tapatalk2
Hi all,
I have an S3 with a broken charging port and I ordered a new one through the replacement program Verizon has. A quote from a 3rd party repair shop was $70+shipping and I don't have soldering skills (and a new one was just $99 anyways). My question is, can I dissect the new S3 and old S3 and just swap the internal memory? I've taken apart my S3 before for repair work so taking both apart doesn't bother me. I thought about just doing a whole motherboard swap but wouldn't the internal memory go with it too? If anyone has any insight on where the internal memory is located on the mother board or how to swap them, it'd be appreciated.
You could use the new phone to charge the battery then put it in the old phone. Now you can copy your data to an sdcard.
If you really want you can Google i535SM and you should be able to download the service manual. You probably find what you need there, though I think swapping the internal memory like that is definitely going to require some serious soldering skills.
Sent from my Nexus 10 using xda app-developers app
jhoutz said:
You could use the new phone to charge the battery then put it in the old phone. Now you can copy your data to an sdcard.
If you really want you can Google i535SM and you should be able to download the service manual. You probably find what you need there, though I think swapping the internal memory like that is definitely going to require some serious soldering skills.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yeah that's what I figured. I'm just afraid my replacement phone is gonna have 4.3 stock and I won't be able to unlock the bootloader or rom it :crying: