I found the UART port on the Fire HD6. It's on the JDEBUG pins. Will post more info later. For now here is a demo:
UART connection layout image
Normal Boot Log
Fastboot Boot Log
My infinite adb reboot script
Edit: RX and TX ports found on the fire HD7 5th gen: http://forum.xda-developers.com/ama...bootloader-unlock-ideas-t3289721/post66265656
great find !
there should be some interesting stuff being output via UART
I realize that I'm necro'ing a 15 month old thread and for that I apologize. However, I've found NOTHING else on the web regarding this topic, hence the necro'ing.
At any rate, I recently bricked my Fire HD 7 (4th Gen) after flashing the 5.2.0 stock recovery zip. It's bricked to the point of having zero signs of life. So, my questions are:
1. Did you ever locate both Tx and Rx pins on the board?
2. If I can successfully communicate with this board via my TTL serial adapter, is there any chance of a successful recovery?
I realize that the effort required to do this is not justified by the current value of the device. However, that is not my concern. I'm simply in it for the challenge.
Thanks!
notorious.dds said:
I realize that I'm necro'ing a 15 month old thread and for that I apologize. However, I've found NOTHING else on the web regarding this topic, hence the necro'ing.
At any rate, I recently bricked my Fire HD 7 (4th Gen) after flashing the 5.2.0 stock recovery zip. It's bricked to the point of having zero signs of life. So, my questions are:
1. Did you ever locate both Tx and Rx pins on the board?
2. If I can successfully communicate with this board via my TTL serial adapter, is there any chance of a successful recovery?
I realize that the effort required to do this is not justified by the current value of the device. However, that is not my concern. I'm simply in it for the challenge.
Thanks!
Click to expand...
Click to collapse
If you are still around, please head over here :
http://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747
The first question is, can you establish any communication with the Fire HD 2014 preloader when it's bricked ??? If you can, that'd be quite exciting !
notorious.dds said:
I realize that I'm necro'ing a 15 month old thread and for that I apologize. However, I've found NOTHING else on the web regarding this topic, hence the necro'ing.
At any rate, I recently bricked my Fire HD 7 (4th Gen) after flashing the 5.2.0 stock recovery zip. It's bricked to the point of having zero signs of life. So, my questions are:
1. Did you ever locate both Tx and Rx pins on the board?
2. If I can successfully communicate with this board via my TTL serial adapter, is there any chance of a successful recovery?
I realize that the effort required to do this is not justified by the current value of the device. However, that is not my concern. I'm simply in it for the challenge.
Thanks!
Click to expand...
Click to collapse
Man I have been trying for hours now. I'm a bit disappointed. I created a whole breakout board setup for what I thought was the uart port. I still have only found the TX. Going to head over to that other thread as well and see if he knows anything about it. It could still be where I am looking but am just missing it...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know this is a really old post, so I might not get a response, but did you ever figure out the pin for RX? Have a HD6 that all I get is the amazon logo at boot. the how to that I have used to unbrick before does not work because this happened after the update to 5.6.0.1. Wondering how to go about communicating through the JDEBUG port. I used gtkterm like I do when configuring cisco equipment. Are there certain setting for the port to communicate properly. Really trying to bypass the read and write block through the usb that seem to happen with the update.
Update- Found half my answer serial and UART are not really the same thing. Looks like I need a USB to UART cable.
Personally, I'd recommend you go with this if you're simply trying to unbrick:
https://forum.xda-developers.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999
I'm pretty sure that it will require that you fully brick it first though (i.e. No Amazon logo, or any real signs of life)
However, if you're getting to an Amazon logo, you should be able to boot to recovery, no? If so, you shouldn't even need to use that aforementioned unbrick process.
toasterboy1 said:
I know this is a really old post, so I might not get a response, but did you ever figure out the pin for RX? Have a HD6 that all I get is the amazon logo at boot. the how to that I have used to unbrick before does not work because this happened after the update to 5.6.0.1. Wondering how to go about communicating through the JDEBUG port. I used gtkterm like I do when configuring cisco equipment. Are there certain setting for the port to communicate properly. Really trying to bypass the read and write block through the usb that seem to happen with the update.
Update- Found half my answer serial and UART are not really the same thing. Looks like I need a USB to UART cable.
Click to expand...
Click to collapse
notorious.dds said:
Personally, I'd recommend you go with this if you're simply trying to unbrick:
https://forum.xda-developers.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999
I'm pretty sure that it will require that you fully brick it first though (i.e. No Amazon logo, or any real signs of life)
However, if you're getting to an Amazon logo, you should be able to boot to recovery, no? If so, you shouldn't even need to use that aforementioned unbrick process.
Click to expand...
Click to collapse
That is the previous unbricking method I mentioned. Worked really well in the past but does not work with 5.6.0.1 it blocked the reading and writing so trying to get around that. It started with trying to flash from cm11 to FireOS and the recovery got lost, so no recovery. It has spiraled down from there. Now I cannot even get to the boot loader because I cannot get into adb. I figure it is a lost cause and already have a replacement, so I figure what better time to learn. It is already beyond broken.
toasterboy1 said:
That is the previous unbricking method I mentioned. Worked really well in the past but does not work with 5.6.0.1 it blocked the reading and writing so trying to get around that. It started with trying to flash from cm11 to FireOS and the recovery got lost, so no recovery. It has spiraled down from there. Now I cannot even get to the boot loader because I cannot get into adb. I figure it is a lost cause and already have a replacement, so I figure what better time to learn. It is already beyond broken.
Click to expand...
Click to collapse
Just curious... what if you tried a fastboot cable? I know the fastboot cable is not supposed to work with this device, but I wonder if it makes any difference when there's no recovery installed.
Also, my experience with UART hasn't been super positive. It works, but there's a nice learning curve associated. Subsequently, I found it rather easy to destroy a couple of bootloaders.
Hopefully, you learn quicker than I.
notorious.dds said:
Just curious... what if you tried a fastboot cable? I know the fastboot cable is not supposed to work with this device, but I wonder if it makes any difference when there's no recovery installed.
Also, my experience with UART hasn't been super positive. It works, but there's a nice learning curve associated. Subsequently, I found it rather easy to destroy a couple of bootloaders.
Hopefully, you learn quicker than I.
Click to expand...
Click to collapse
Thought about the fastboot cable. I know it is possible to DIY so I might try that or might just buy one when I get around to getting a 1.8v UART USB board, I think that is what is needed. Not in a hurry now as I just bought a lot of 2 HD6s off ebay that where listed for parts and they are both working fine. Already rooted, TWRP, and CM11 on one as that how the one I destroyed was setup. Hopefully I can get the other one on FireOS 5 and build a device tree and try building CM12, unless I am told that would be impossible. This whole thing started because I wanted to get the headphones working in CM11.
Would appreciate any information you could share on UART. I was just going to try the unbrick ISO through the UART port.
toasterboy1 said:
Would appreciate any information you could share on UART. I was just going to try the unbrick ISO through the UART port.
Click to expand...
Click to collapse
Most of my experience with the UART port comes from trying to unbrick wireless routers. UART is simply the serial interface that lets you communicate directly with the board. Once you know which pins are which on your board, getting it connected is relatively straight forward.
However, after you get it connected, this is in my experience where things get messy. There are many different environments in which you could find yourself once connected. Depending on the environment, you may or may not be able to get decent help from Google as to how to procede.
In general, what you're doing with UART is writing directly to the board's memory. This allows you to possibly overwrite the bootloader, recovery, etc.
What I can say is that the ISO will likely do you no good via UART. It's possible that you might be able to extract some info from the ISO that you could use in contructing your UART commands.
If done correctly, you could get your device back. If done incorrectly, you might have a true brick.
Need help same situation here
toasterboy1 said:
That is the previous unbricking method I mentioned. Worked really well in the past but does not work with 5.6.0.1 it blocked the reading and writing so trying to get around that. It started with trying to flash from cm11 to FireOS and the recovery got lost, so no recovery. It has spiraled down from there. Now I cannot even get to the boot loader because I cannot get into adb. I figure it is a lost cause and already have a replacement, so I figure what better time to learn. It is already beyond broken.
Click to expand...
Click to collapse
Ive got 2 hd6 device stuck on fire logo no recovery no fast boot even that linux unbrick method not working with new update which not allow you to read and write
~
Related
Bricked my xoom with wrong imagefile when rooting it.
I would like to know which part, if possible, to replace to get some life in my xoom. I'm stuck at the Motorola logo screen with "Starting RSD 3 mode" or nothing. Can't connect to it with RSD-Lite, ADB or fastboot. I cant connect to it from any of my computers. I have a Linux 32-bit and a win7 64-bit.
So,this is my question.
Can I replace something in the tab to get access to it? Something that comes "preloaded" with the software that I need to communicate with the device using ADB or fastboot? I think, if it's possible to do that, I can flash new imagefiles found in this forum to it.
To tear it down I found this guide:
http://www.ifixit.com/Teardown/Motorola-Xoom-Teardown/4989/1
What do you think? Is it possible? And, if so, where can I find that piece of hardware? Motorola company spareparts? Thats the hardest I think.
I have the exact error as you do! How do we unbrick this error???
I think it's impossible without sending it in for replacement or repair. It would be nice if someone who repairs it tell me what they did when they repaired it. If it's a hardware replacement or some kind of "forced" flash of new software. I hope they have some software tools that we in the community doesn't have. If so, it shouldn't be so expensive.
My problem is that I bought it from a person who bought it from Best Buy in New York. I don't have any warranty because I'm not the one who bought it and here in Sweden they won't repair it because they don't have a service-agreement with Motorola yet. So I have to do it myself or throw it away.
Contact your nearest Motorola office directly, they didn't ask for any paperwork to replace mine.
http://forum.xda-developers.com/showthread.php?t=1035202&highlight=omnia1994
read this thread slowly.. start from pg 2. good luck dude
poisike said:
Contact your nearest Motorola office directly, they didn't ask for any paperwork to replace mine.
Click to expand...
Click to collapse
you are lucky
rachelleroy said:
you are lucky
Click to expand...
Click to collapse
Really lucky, I managed to get a Xoom with a problem that no one has seen or heard about
I had same problem. Try power, vol- and vol+ all at same time. When it comes back on do power and vol -. that should put you back to fast boot. It worked for me anyway.
omnia1994 said:
http://forum.xda-developers.com/showthread.php?t=1035202&highlight=omnia1994
read this thread slowly.. start from pg 2. good luck dude
Click to expand...
Click to collapse
Yes I did a fast "read-thru" of this thread. My problem is different. I can not reboot into fastboot mode. Only RSD 3 mode, and RSD-Lite can't see it. I tried to flash the 3g sbf file just to see if I could restore the fastboot mode and check if RSD-Lite could do anything at all. Nothing happened. That's why I want to learn a little about hardware and replacement of hardware "things". I think that's the only way for me to fix it.
I'm thankful that you are trying to help but all threads are about fixing things with fastboot and fastboot is DEAD on my xoom.
I am searching for a way to restore fastboot.
I feel STRESSED OUT after bricking my Xoom. I bought my Xoom with a $200 off rebate, which is $400 total from costco. PLEASE, someone help us with the RSD mode 3 error!!!!!!
Same problem
Hi jai134,
Just wondering if you had any joy with hardware replacement or some other solution? I think my problem is exactly the same as yours. It's RSD mode 3 or nothing! Windows and Linux can't see the device, and no combination of button presses seems to do anything.
The guys at #xoom on freenode very kindly spent a couple of hours trying to help me out last night but to no avail... it turns out I flashed a zip instead of a boot.img using fastboot.
Dockheas23 said:
Hi jai134,
Just wondering if you had any joy with hardware replacement or some other solution? I think my problem is exactly the same as yours. It's RSD mode 3 or nothing! Windows and Linux can't see the device, and no combination of button presses seems to do anything.
The guys at #xoom on freenode very kindly spent a couple of hours trying to help me out last night but to no avail... it turns out I flashed a zip instead of a boot.img using fastboot.
Click to expand...
Click to collapse
Read through this thread. You might be able to solve your problem with a "factory " cable > http://forum.xda-developers.com/showthread.php?t=1121650
Sent from my Xoom using XDA Premium App
Thanks. That sounds like what I'm looking for... I refuse to believe this one can't be salvaged!
I'll give it a try, and will let you know how it goes.
Hooray!
It worked! My Xoom is unbricked. I made a scary looking factory cable which allowed me to flash with fastboot. My experience was exactly the same as post 41 in the following thread:
http://forum.xda-developers.com/showthread.php?t=1121650&page=5
Here's one end of the cable. The other end is just a regular type A USB plug.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I soldered some staples to the cable and attached them to a micro-usb male breakout board I got on Amazon (see post 43 of the thread linked above). I'd advise covering the connections and staples with electrical tape. I didn't have any handy and consciously decided to take the risk, but any contact between the staples could have fried the USB ports on the Xoom and/or the computer. I'll be taping this up and keeping it on standby in case it's needed again!
Thanks very much for your help cam30era, and also the guys on IRC at freenode, especially Kas and Solarnz.
I just walked someone through this error yesterday, after about 2 hours we recovered his xoom. Don't forget to stop by the xoom irc channel on freenode, you would be surprised the stuff we recovery from in there.
bwcorvus said:
I just walked someone through this error yesterday, after about 2 hours we recovered his xoom. Don't forget to stop by the xoom irc channel on freenode, you would be surprised the stuff we recovery from in there.
Click to expand...
Click to collapse
Why not write up the procedures and put up a download for a pdf?
This modification will go like this: http://forum.xda-developers.com/showthread.php?t=1206216
After that, unbricking your Epic will be like this...
See here for full instructions: http://forum.xda-developers.com/showthread.php?t=1242466
Of course I don't OWN an Epic so I will work with someone who does.
introduction
I'm not kidding when I say UnBrickable. Modifying the OM pins means you can boot from USB, UART or MMC. This makes the phone quite UNBRICKABLE. There is nothing you can do software wise to prevent the device from booting into this mode. We are communicating with the unrewritable, efused IROM on the processor. It's the thing that makes the system on a chip into a "system on a chip".I am here now to tell you how to turn your Samsung Droid Charge into a KIT-S5PC110 development board. The KIT-S5PC110 development board is the platform used to develop our phones. There are some differences between this mod and the official development platform. The S5PC110 has a removable internal SDCard and no touchscreen.
Why would you want to do this? When you plug in the battery and connect it to the computer in "off" mode, it will become an S5PC110 board awaiting download of a program to run. This occurs long before anything like software or firmware enters the processor. This is the IROM of the device awaiting commands or a power on signal.
Because it is accepting a memory flash, anything may be put onto the device to perform a boot sequence..... Apple iOS (iPhone4 has the same processor) WP7 (mango supports this processor).
This will be a replacement for JTAG once we are able to make some firmware. How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, your phone will connect to the computer via USB and await commands. Otherwise it will pretty much act like an Epic. See the Special Instructions section.
Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing. You can also speak to myself(my username @gmail.com) or Connexion2005(aka MobileTechVideos.com)
2. soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. flux
4. solder
5. tweezers
6. A relay (possibly- for the wire within to use as a bridge)
performing the modification:
1. tear apart your phone... Make sure to take out your SIM and external SDCard before you do this.
1A. Remove the screws.
1B. Separate the top case from the bottom case
1C. disconnect the display connector and free the camera and button assemblies from the case.
1D. Remove the mainboard
****VIDEO OR PICTURES NEEDED*****
2. Perform the mod as follows: Replace the xOM5 resistor from the right position to the left position.
*OR: remove the xOM5 resistor and jumper the center pads of xOM5 to the center pads of xOM0.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to pre2epic4g for donating the board for teardown!
3. reassemble the phone.
Special Instructions
This replaces the battery charging sequence. The normal battery charging sequence can be activated by holding power for 4 seconds.
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
3 button Download mode works as usual, however you must not have the S5PC110 drivers installed on the computer. You can use your custom rom menu option, adb reboot download, or use a terminal to "reboot download". 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 mode.
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software. See here for setting up the UART output http://forum.xda-developers.com/showthread.php?t=1235219
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line Download Tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
firmware
One-Click Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=705515&d=1314762609
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
-___-' If only I knew someone who was good with Soldering that I could trust. I unfortunately will have to pass. :/ I've been waiting for this too. Thanks so much Adam.
Thank you so much can we do this if the device gets bricked? And I have someone I can trust so I'm lucky
Sent from my SPH-D700 using Tapatalk
rulyskull said:
Thank you so much can we do this if the device gets bricked? And I have someone I can trust so I'm lucky
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yes, it works on a bricked device. These methods communicate directly with the processor so there is nothing like firmware or bootloaders in the way.
AdamOutler said:
Yes, it works on an already bricked device.
Click to expand...
Click to collapse
Alright cool thanks I have something to fall back on now, thanks for all your work Adam
Sent from my SPH-D700 using Tapatalk
Thanks a lot Adam! Although I won't jump right into trying this with my current Epic, I won't make ur efforts go to waste. I just jumped on ebay to see if I coulf locate a bricked Epic for cheap and maybe have something to do while I await official GB. Who knows, maybe I'll get lucky n be able to unbrick a sucker or two
Sent from my SPH-D700 using xda premium
Its here I may try...not that good at soldering though :\
The board is coated in glue. Its not nearly as risky as it looks. It takes some time, but you're not going to screw anything up if you're decent with a soldering iron.
Nice work on the port to the Epic!
So glad to see this made it's way to the Epic.
Thanks a ton James for donating the board!!
=]
SWEET!!! this is a nice surprise I cant wait to get my lab set up so I can do this. Has Rebellos had any time to cook up some software? Is the captivate running nexus s roms yet? Im so excited
theduce102 said:
SWEET!!! this is a nice surprise I cant wait to get my lab set up so I can do this. Has Rebellos had any time to cook up some software? Is the captivate running nexus s roms yet? Im so excited
Click to expand...
Click to collapse
If you do this, can you make a video of you doing the unbrickable mod, like the soldering stuff.
So there's no way to do a software equivalenT of this, right?
masaidjet said:
If you do this, can you make a video of you doing the unbrickable mod, like the soldering stuff.
Click to expand...
Click to collapse
Yeah ill see what I can do, it wont be anytime soon though =/ ill probably wait until I actually brick before doing it. Or until we get a custom bootloader
xboxfanj said:
So there's no way to do a software equivalenT of this, right?
Click to expand...
Click to collapse
Nope. Which is why it's "unbrickable"
aw ****! im buyin all the bricked epics i can find.
sohardivetried said:
aw ****! im buyin all the bricked epics i can find.
Click to expand...
Click to collapse
theres none on craigslist or ebay! lol.
ugothakd said:
theres none on craigslist or ebay! lol.
Click to expand...
Click to collapse
Lol stupid people not selling their bricked epics
Sent from my SPH-D700
Could I unbrick it if I were to screw up on the soldering job?
stir fry a lot said:
Could I unbrick it if I were to screw up on the soldering job?
Click to expand...
Click to collapse
Yes. Just don't apply power until its right.
For the last three months, since I softbricked and brought my Infuse back to life with GTG's Ultimate Unbrick I've been fighting the poor performance and sluggishness on my Infuse and cursing the day I rooted it! Today I started uninstalling apps right and left and BAM! We Have Performance! Sometimes, it's the simple things stupid! You've loaded too much crap on your phone!
No no you have it all wrong! You didn't have too many apps you simply need a bigger phone.
Sent from my SAMSUNG-SGH-I747 using xda premium
vmatt said:
No no you have it all wrong! You didn't have too many apps you simply need a bigger phone.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
My Toshiba Thrive 10.1 32G Tablet with Google Voice is already a much bigger phone! :laugh:
That being said, I'm still having issues with my infuse which no longer talks to my PC in Download mode and is back to being so sluggish at times I can't even answer a phone call. I'm kinda wishing I hadn't rooted the phone again....:crying:
Just install a new rom.
Sent from my SGH-I997 using xda premium
SteveCampsOut said:
My Toshiba Thrive 10.1 32G Tablet with Google Voice is already a much bigger phone! :laugh:
That being said, I'm still having issues with my infuse which no longer talks to my PC in Download mode and is back to being so sluggish at times I can't even answer a phone call. I'm kinda wishing I hadn't rooted the phone again....:crying:
Click to expand...
Click to collapse
You can always put it back to stock unrooted ya know.
http://forum.xda-developers.com/showthread.php?t=1629079
Not for nothin' but I'm pretty sure root isn't whats slowing down your phone
dginsd said:
You can always put it back to stock unrooted ya know.
http://forum.xda-developers.com/showthread.php?t=1629079
Not for nothin' but I'm pretty sure root isn't whats slowing down your phone
Click to expand...
Click to collapse
Not if it's no longer talking to my PC via USB in Download mode that I'm aware of.
Have you tried different USB ports, and or a different USB cable? I have three stock Samsung cables and only one will transfer data.
All three will charge just fine though
Sent from my SGH-I997 using xda app-developers app
<sigh> It's hard bricked now. No Download mode.
Helpful tips
SteveCampsOut said:
<sigh> It's hard bricked now. No Download mode.
Click to expand...
Click to collapse
I had thought I lost it for good. Nope. Google a few key words- INFUSE BOOT LOOP- FIX POWER BUTTON ON INFUSE- NO DOWNLOAD MODE INFUSE-
******************************** Fixed the unbrickable infuse *******************************:good:
1. NEW USB CABLE.
2. CLEANED POWER on off Button.( stuck on) LOOP there it is!!! LOOP there it is!!!
SteveCampsOut said:
<sigh> It's hard bricked now. No Download mode.
Click to expand...
Click to collapse
So just to be clear your getting nothing at all, no Samsung logo, or boot animation? How 'bout a battery charging logo?
If you getting none of that definitely give Rickrocks013 sugestions a try. Take the phone apart and clean the power button contact points and make sure its functioning properly, and get a good USB cable (the ones that come with the phone are about as cheap as they come) If you currently have a USB cable in the condition that two of mine are in (no data connection) download mode would be impossible to achieve.
My understanding of the Infuse is it's near impossible to brick, sometimes a bit of extra effort may be required, but with developeres like scott working to keep software updated for our device, the effort is well worth keeping your device running, IMO.
http://forum.xda-developers.com/showthread.php?t=1336359
dginsd said:
So just to be clear your getting nothing at all, no Samsung logo, or boot animation? How 'bout a battery charging logo?
If you getting none of that definitely give Rickrocks013 sugestions a try. Take the phone apart and clean the power button contact points and make sure its functioning properly, and get a good USB cable (the ones that come with the phone are about as cheap as they come) If you currently have a USB cable in the condition that two of mine are in (no data connection) download mode would be impossible to achieve.
My understanding of the Infuse is it's near impossible to brick, sometimes a bit of extra effort may be required, but with developeres like scott working to keep software updated for our device, the effort is well worth keeping your device running, IMO.
http://forum.xda-developers.com/showthread.php?t=1336359
Click to expand...
Click to collapse
No I'm getting a screen with a phone and a computer with an Exclamation mark inside a triangle between them and it won't connect to the PC anymore and it won't boot it just comes back to that screen no matter what I do. Geek Squad couldn't get it into download mode either.
SteveCampsOut said:
No I'm getting a screen with a phone and a computer with an Exclamation mark inside a triangle between them and it won't connect to the PC anymore and it won't boot it just comes back to that screen no matter what I do. Geek Squad couldn't get it into download mode either.
Click to expand...
Click to collapse
Have you tried a new USB cable and tried different USB ports on the computer?
What type of computer are you using and what operating system is it running? If your running a windows variant try re-installing the samsung kies drivers. You could also install Linux on a small partiion, ultimately having a Linux based OS (as a second if your not comfortable leaving windows) is a great thing to have, if your going to be doing a lot of tinkering with android based phones, it's nice to have as a rescue system once windows goes down as well.
I just don't think I have the brain power anymore...
dginsd said:
So just to be clear your getting nothing at all, no Samsung logo, or boot animation? How 'bout a battery charging logo?
If you getting none of that definitely give Rickrocks013 sugestions a try. Take the phone apart and clean the power button contact points and make sure its functioning properly, and get a good USB cable (the ones that come with the phone are about as cheap as they come) If you currently have a USB cable in the condition that two of mine are in (no data connection) download mode would be impossible to achieve.
My understanding of the Infuse is it's near impossible to brick, sometimes a bit of extra effort may be required, but with developeres like scott working to keep software updated for our device, the effort is well worth keeping your device running, IMO.
http://forum.xda-developers.com/showthread.php?t=1336359
Click to expand...
Click to collapse
I will gladly mail it to someone who thinks they can fix it. I've already switched to Straight Talks Samsung Galaxy Centura with ICS. Sadly, the new phone has no GPS. I don't plan on rooting again. I've been having health issues lately that include lightheadedness, dizzy spells and just plain old fuzzy thinking so frankly I think it's currently beyond my ability to fix what I've broken.
dginsd said:
Have you tried a new USB cable and tried different USB ports on the computer?
What type of computer are you using and what operating system is it running? If your running a windows variant try re-installing the samsung kies drivers. You could also install Linux on a small partiion, ultimately having a Linux based OS (as a second if your not comfortable leaving windows) is a great thing to have, if your going to be doing a lot of tinkering with android based phones, it's nice to have as a rescue system once windows goes down as well.
Click to expand...
Click to collapse
Using the correct USB cable is what allowed me to screw up the phone in download mode. I was using Ultimate Unbrick with Odin but it appeared to be stuck on establishing communications. I rebooted the phone and that's when it went to the no longer talking to your PC screen. the new Samsung Galaxy Centura sees the PC just fine with the existing USB drivers. I'm running Windows Vista Pro 64 Bit.
In case anyone doesn't understand what I'm talking about, here's what my phone now looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that I at least have a working phone again I guess I don't mind tinkering with this if anyone thinks it's not truly hard bricked but so far I'm finding no love trying to get back into download mode or getting my PC to see the phone with the above image on the screen.
Where did you get that cable? My guess is that it's still a bad one.
That screen is another form of download mode. That screen always comes up after a bad flash via Odin or heimdall. Try buying a new cable, then keep trying different usb ports. I've had the issue of Odin getting stuck a bunch of times and gotten that screen. Finding the right usb port and cable has gotten me out of that mess every time.
There is a chance your current cable might work after enough tries, but you will want to blow your brains out trying. It's easier to just get a new cable. A good flash of Odin should take like 3 minutes. Just start over if it takes longer.
Good luck.
MattSoRaven said:
Where did you get that cable? My guess is that it's still a bad one.
That screen is another form of download mode. That screen always comes up after a bad flash via Odin or heimdall. Try buying a new cable, then keep trying different usb ports. I've had the issue of Odin getting stuck a bunch of times and gotten that screen. Finding the right usb port and cable has gotten me out of that mess every time.
There is a chance your current cable might work after enough tries, but you will want to blow your brains out trying. It's easier to just get a new cable. A good flash of Odin should take like 3 minutes. Just start over if it takes longer.
Good luck.
Click to expand...
Click to collapse
I had never seen that screen but figured thats what it was from his description, glad you could confirm. BTW I agree with the assessment of a bad cable or port as your primary issue.
Just a thought, you mentioned using oden, have you tried using the heimdall back to stocks? You need to have Java installed but they work really well.
Sent from my SGH-I997 using xda app-developers app
If help is still needed shoot me a PM and I'll do what I can.
Sent from my SGH-I997 using xda premium
FauxAffliction said:
If help is still needed shoot me a PM and I'll do what I can.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for the offer but I shipped it UPS to the Samsung repair center on Monday. They got it today so hopefully I'll have it back within a week.
Samsung ROCKS!!
Not only did they pay for shipping, they didn't charge me a dime to fix the mess I made of my phone! And I was totally honest and upfront about breaking my warranty by rooting my phone from the get go! Talk about Customer Service above and beyond my expectations!!!! :victory:
If anybody can add me on skype or steam or any other IM platform, that would be fantastic, just PM me if you could, with your user for anything.
I have all the possible QPST tools needed to interface with my device, and it still has some life left in it, for example it is still able to interface via usb through qualcomm's 9008 qdloader drivers.
I have tried endlessly to unbrick this device using various tools and methods, but they all come up with that same error relating to Sahara, firehose, or programmer. I can't seem to get MiFlash to do anything, since I know basically nothing about how it works, just that I followed some guys tutorial on flashing to the Opo, but it doesn't seem to work. All the QPST tools say it can't communicate with the
flash programmer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Am I screwed except for JTAG? I really, desperately need help, and this seems to be the only place to get actual help from devs who actually understand what is happening in terms of partitions, etc. (Xda won't help me since I'm a new user and I've tried posting multiple times and got basically no response.)
Help!
Wax that no one can help us?
Have you tried this guide?
It works for me, unbricked my OPO twice.
soralz said:
Have you tried this guide?
It works for me, unbricked my OPO twice.
Click to expand...
Click to collapse
If friend as you can see, all these tools have already been used.!
soralz said:
Have you tried this guide?
It works for me, unbricked my OPO twice.
Click to expand...
Click to collapse
What works for you and the majority of other people sadly doesn't work for me, or people with my issue.
No tool this specific case exists yet to fix this.
It's as simple as that. I need a developer, I need a programmer. That is all I need. And I've been on the hunt for months.
PikuChan said:
What works for you and the majority of other people sadly doesn't work for me, or people with my issue.
No tool this specific case exists yet to fix this.
It's as simple as that. I need a developer, I need a programmer. That is all I need. And I've been on the hunt for months.
Click to expand...
Click to collapse
Hmm, probably incorrect driver? What OS environment are you in to flash the OPO anyway?
soralz said:
Hmm, probably incorrect driver? What OS environment are you in to flash the OPO anyway?
Click to expand...
Click to collapse
Linux, Windows 7, Windows XP, Windows 8 and 8.1 separately, (seriously), you name it. I've tried everything. I mean that to its fullest If the tools in my post weren't enough, I've also tried a billion others, whether they relate to the OPO or not.
Again, people with this issue need a developer, the device doesn't go into 9006 Loader mode when tools like ToolStudio try to flash things to it, aka locked bootloader (I think). This has nothing to do with drivers. I'm not looking for a one click solution, one doesn't exist. I'll do almost anything to fix this.
If you got sahara error unplug your phone and try again with holding VolUp and plug it back in. This is to force it into 9008 mode again.
tropenfrucht said:
If you got sahara error unplug your phone and try again with holding VolUp and plug it back in. This is to force it into 9008 mode again.
Click to expand...
Click to collapse
All this has been done, and nothing appears to be a more serious problem than that.
krizzhellsing said:
All this has been done, and nothing appears to be a more serious problem than that.
Click to expand...
Click to collapse
Indeed. I just need custom linux code to mess with the partitions. I had a friend try wiping EVERYTHING in Twrp terminal, all the partition data, nothing remained. And the ColorOs tool (Msm8974 Downloader) still managed to rebuild the partitions, etc. If there's any way I can nuke the OPO's current partition data through something like a linux perl script, I'd probably be set to restore it through the regular tools.
Here's what happens when I try to flash anything with qdloader's perl script in Linux.
Good Luck.!
I see it very difficult to repair, better choose to buy the motherboard on eBay for $ 100, I wish you luck hopefully you can fix.
Same issue here. Tried everything and every suggestion out there. Still stuck on 'Sahara' issue. I also tried with the QFIL software but met with the same dead end. The idea of wiping the entire partition tables in Linux may work, if only we can get the 'how'. I'm just stumped why this one is having this issue; the first one I unbricked went smoothly, no issues and worked perfect afterwards. I wish I can get my head around this quickly; it's giving me sleepless nights.
stuck at same step
me too tried all possibilities and stuck at same step; spent sleepless nights to fix it and still hunting for solution
How did you bricked your oneplus one?downgrade to kitkat?
Sent from my A0001 using XDA Free mobile app
OPO dead unexpectedly
assassin0408 said:
How did you bricked your oneplus one?downgrade to kitkat?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
My Phone dead unexpectedly , @ night after charged to 80% unplugged and slept; @ morning no display, no reaction on any action. but experienced hot at front camera
Sounds like hardware failure for it to just stop. You could've had an unexpected surge charging, and the some part of the motherboard failed. I agree with earlier post, it might be time to replace it. Sucks, but it happens and I've seen it happen from time to time when I worked 3 years in wireless (VZW and ATT) in college. None of our tools would bring them back and we had software to do exactly what you're asking/looking for. It would wipe the phone to the point of literally being a brick, then reload everything back onto it. It would take hours sometimes and most failed. They eventually started hiring people just to do that all day, and we'd ship them off to a local store that had people doing it all day in the back offices.
Sent from my A0001 using XDA Free mobile app
nikeman513 said:
Sounds like hardware failure for it to just stop. You could've had an unexpected surge charging, and the some part of the motherboard failed. I agree with earlier post, it might be time to replace it. Sucks, but it happens and I've seen it happen from time to time when I worked 3 years in wireless (VZW and ATT) in college. None of our tools would bring them back and we had software to do exactly what you're asking/looking for. It would wipe the phone to the point of literally being a brick, then reload everything back onto it. It would take hours sometimes and most failed. They eventually started hiring people just to do that all day, and we'd ship them off to a local store that had people doing it all day in the back offices.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Ok thanks seems like its time to buy new phone
Same problem
Hi I have the same problem, I tried with windows 7, 8, 10, XP, but does not solve the hard brick, is nothing msiimage.mbn because someone knows this problem?:crying:
OnePlus One gone X came in
laxlucky said:
Ok thanks seems like its time to buy new phone
Click to expand...
Click to collapse
Bought new phone OnePlus X.
Hey everybody! As the title says, I replaced the motherboard on my SM-G920V with one from my wife's old S6 (also 920v). She thought it'd be fun to throw it at me when she was angry, and shattered both front and back glass. BUT ANYWAY... After I finished installing everything how it's supposed to be, I started it up and was so happy to have my S6 back to OE2! My only issue now is that it won't charge, yet will recognize a charger. I haven't been able to connect it to a computer, because mine was blessed with a lovely RootKit/netbot that took over every aspect of my machine. So if any of my hardware people could help me out, that'd be great! What could I have done wrong?!
Maybe just replace the charging port and everything will be right. good job on switching the motherboard, it is really hard to do anything with this phone, I just sent it to samsung when my touch wasn't working, eventually paid 40$ but screen is like 300$ , they said my touch connection to the motherboard was bad. Anyway, I recommend you to send your phone to there or switch alone your charging port, good luck
What was your reason for changing the motherboard on your phone?
Sometimes you have to match the right Rev.# Hardware for the charging port. So basically change out the USB pcb board with the one in your wife's phone and check does that work.
To fix your rootkit portable superanti spyware software or kaspersky. Easy fix...
bahmonkeys said:
What was your reason for changing the motherboard on your phone?
Sometimes you have to match the right Rev.# Hardware for the charging port. So basically change out the USB pcb board with the one in your wife's phone and check does that work.
To fix your rootkit portable superanti spyware software or kaspersky. Easy fix...
Click to expand...
Click to collapse
My reasoning was simple, and purely justifiable: ROOT! Mine did the upgrade with the patches, so I lost root. I figured "Why not?!" I'm pretty good with computer hardware, so I figured I'd try my luck with phones. I will definitely try that when I get home from work, thank you!
And as far as the RootKit, I tried a couple things, but I think it took over my flash drives too. I'm definitely gonna get the machines (yes, all 3 of my machines got it) repaired, but I have more important things right now. Like my phones and my new-ish baby and food. Can't forget food.
Sent from my LG-H810 using xda Forums PRO
snap-your-toes said:
I'm pretty good with computer hardware, so I figured I'd try my luck with phones.
Click to expand...
Click to collapse
Apparently not good enough.
Lol
krelvinaz said:
Apparently not good enough.
Lol
Click to expand...
Click to collapse
Apparently...but she turned on and everything else is in proper order. So...better than most!
Sent from my LG-H810 using xda Forums PRO
snap-your-toes said:
Apparently...but she turned on and everything else is in proper order. So...better than most!
Sent from my LG-H810 using xda Forums PRO
Click to expand...
Click to collapse
Let me know if you were able to fix this, my galaxy S6 edge is not charging anymore, only slow charging (usb charging speed) which takes more than 6 hours for a full charge, i even tried some replacement usb boards and they didn't fix the issue, so i don't know what to do anymore, and i don't want to send it to samsung.
juanyunis said:
Let me know if you were able to fix this, my galaxy S6 edge is not charging anymore, only slow charging (usb charging speed) which takes more than 6 hours for a full charge, i even tried some replacement usb boards and they didn't fix the issue, so i don't know what to do anymore, and i don't want to send it to samsung.
Click to expand...
Click to collapse
Did you try chnaging the USB cables, chargers etc. Also sometimes dust on the USB port can cause a loss of connection. This is a old trick you could try and still works very well. Get an old toothbrush (make sure its clean and dry) and brush any dirt off the USB port connection
---------- Post added at 01:11 AM ---------- Previous post was at 01:04 AM ----------
snap-your-toes said:
My reasoning was simple, and purely justifiable: ROOT! Mine did the upgrade with the patches, so I lost root. I figured "Why not?!" I'm pretty good with computer hardware, so I figured I'd try my luck with phones. I will definitely try that when I get home from work, thank you!
And as far as the RootKit, I tried a couple things, but I think it took over my flash drives too. I'm definitely gonna get the machines (yes, all 3 of my machines got it) repaired, but I have more important things right now. Like my phones and my new-ish baby and food. Can't forget food.
Sent from my LG-H810 using xda Forums PRO
Click to expand...
Click to collapse
I still don't understand why you changed the motherboard. Could you explain!? You trying to say that your (original) phone upgraded to 5.1.1 and you lost root? So you decided to change the motherboard.*
Did you open both phones and see if the USB motherboard is a different version on either phone.
As I said with the rootkit download superanti spyware portable or kaspersky will fix everything. Easy!!
If you need a hand with that rootkit I will help you
BOOM!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bahmonkeys said:
I still don't understand why you changed the motherboard. Could you explain!? You trying to say that your (original) phone upgraded to 5.1.1 and you lost root? So you decided to change the motherboard.*
Click to expand...
Click to collapse
It did the upgrade to the patched 5.0.2 and snatched root away from me. I had my wife's broken one laying in a drawer, so I figured I'd try swapping.
bahmonkeys said:
Did you open both phones and see if the USB motherboard is a different version on either phone.
Click to expand...
Click to collapse
Yes, I did. And they are completely different. But in looking at my original, I snapped the ribbon connecter. Whoops. So them I thought about all the stuff that on the back panel (see image). So, what i ended up doing, was a swapping out everything that connected to the motherboard from the back panel. Power button, Volume buttons, and the speaker/mic hardware. And I'm proud to say, IT WORKED!!!!!
So, thank you for pointing that out to me. I really do appreciate it.
bahmonkeys said:
If you need a hand with that rootkit I will help you
Click to expand...
Click to collapse
I appreciate this as well. If I need some help with it, I know who to contact.
You upgraded your original phone? As in you got a custom ROM which was pre-rooted? Is that what you mean? This still doesn't explain why you would change your original motherboard with your wife's one. I still don't understand why you would change motherboards.
Why didn't you just Flash TWRP and respected BL and modem for your phone. Then Flash a 5.1.1 Rom for your phone. Android version 5.1.1 seems to have solved all the problems that 5.0.2 has. You wouldn't have needed to change any motherboard then.
So everything is working now that's good.
bahmonkeys said:
You upgraded your original phone? As in you got a custom ROM which was pre-rooted? Is that what you mean? This still doesn't explain why you would change your original motherboard with your wife's one. I still don't understand why you would change motherboards.
Why didn't you just Flash TWRP and respected BL and modem for your phone. Then Flash a 5.1.1 Rom for your phone. Android version 5.1.1 seems to have solved all the problems that 5.0.2 has. You wouldn't have needed to change any motherboard then.
So everything is working now that's good.
Click to expand...
Click to collapse
The Verizon bootloader is locked, first off. And second, the patched 5.0.2 that they released OTA made it to where you can't downgrade. The original 5.0.2 was rootable. Not the patched version. Anyways, problem was solved. I'm working on my laptop's issues now.
Sent from my LG-H810 using xda Forums PRO