[Q] How to repair a bricked Xoom - Xoom Q&A, Help & Troubleshooting

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?

Related

Anyone got a busted phone?

I'd like to do some research on an Infuse 4g. If anyone has a busted phone, I'd like to do some reverse engineering on it. The work I do will benefeit the community and it will help out greatly with porting other OSs and working with alternate bootloaders. In order to get the information about the OM pins, I must remove the processor. I do not have the ability to replace the processor afterwards. The board will give it's life to help others.
It does not matter about condition.... won't turn on, water damaged, screen cracked, case broken.. I'd like to destructively examine the mainboard for component identification and location.
AdamOutler said:
I'd like to do some research on an Infuse 4g. If anyone has a busted phone, I'd like to do some reverse engineering on it. The work I do will benefeit the community and it will help out greatly with porting other OSs and working with alternate bootloaders. In order to get the information about the OM pins, I must remove the processor. I do not have the ability to replace the processor afterwards. The board will give it's life to help others.
It does not matter about condition.... won't turn on, water damaged, screen cracked, case broken.. I'd like to destructively examine the mainboard for component identification and location.
Click to expand...
Click to collapse
If I had an extra $125 lying around to pay the insurance deductible (soon to be $199...), I would gladly 'lose' my phone for the cause.
Otherwise, I've seen a couple on craigslist, but the cheapest was $75 due to "toilet damage".
I purchased my phone outright for $600. It has no insurance and a few months of warranty. I would not recommend anyone participate if their phone is under warranty or warrantable.
If you have an extra device around, I'd like to document it and make something for everyone to use as a reference for hacking their devices.
AdamOutler said:
I purchased my phone outright for $600. It has no insurance and a few months of warranty. I would not recommend anyone participate if their phone is under warranty or warrantable.
If you have an extra device around, I'd like to document it and make something for everyone to use as a reference for hacking their devices.
Click to expand...
Click to collapse
That would be awesome! I will keep an eye on eBay and craigslist for any dirt-cheap non-functional Infuses. I'd probably be willing to pay up to $25 for a cadaver.
Bump, we've got a bootloader hello world running on the Captivate. I'd like to get this up and running on an infuse. It won't be long until we have a download mode for our processor.
Once we get download mode, we will be able to run a tethered boot of just about any ARM compatible operating system.
Bump. This means unlocking the actual bootloaders.
AdamOutler said:
Bump, we've got a bootloader hello world running on the Captivate. I'd like to get this up and running on an infuse. It won't be long until we have a download mode for our processor.
Once we get download mode, we will be able to run a tethered boot of just about any ARM compatible operating system.
Click to expand...
Click to collapse
This mod work.and works well. Bump for my wife's infuse.
Sent from my unBrickablE captivate.
This is a reality, we just need a broken board to find out the mod.
it's one of the resistors near point B which needs to be removed and jumpered to another resistor.
{
"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 do have an infuse that has been in a pool but it works well enough to use
Just curious as to what other OS's would actually be ported to the infuse and what the actual bootloader unlock could do
Edit: WP7 and MeeGo would be really cool!
halfnelson117 said:
I do have an infuse that has been in a pool but it works well enough to use
Just curious as to what other OS's would actually be ported to the infuse and what the actual bootloader unlock could do
Edit: WP7 and MeeGo would be really cool!
Click to expand...
Click to collapse
For now I'm playing it safe and trying something about my level.. check this out. http://forum.xda-developers.com/showthread.php?t=1247962
We could get Nexus running on our devices too. For those who don't know, Nexus is the official Google Dev platform which they release the latest, greatest android versions.
Good luck adam that be great
Sent from my SAMSUNG-SGH-I997 using xda premium
I currently don't have debit card or Id totally get this.
http://www.ebay.com/itm/Samsung-Inf...0569291862?pt=Cell_Phones&hash=item1e66894856 its only $29 right now with less than a day remaining,
Ill keep looking for cheap ones when I get my new debit card ill get one if I can get it for under $50 bucks.
maybe we should start a donation thread to get a broken one for Adam?
Bump! Still need an Infuse4G mainboard. Anyone got one with water damage, a broken screen, or anything? I need it to pull the processor off for analysis.
AdamOutler said:
Bump! Still need an Infuse4G mainboard. Anyone got one with water damage, a broken screen, or anything? I need it to pull the processor off for analysis.
Click to expand...
Click to collapse
I'm going to look for another broken infuse to buy to give to you, and if the worst comes, ill try to get some money and report mine as lost, and get another one.
Just a question, if you get this mod working, what exactly does it do?
Sent from my phone. :3
Longcat14 said:
I'm going to look for another broken infuse to buy to give to you, and if the worst comes, ill try to get some money and report mine as lost, and get another one.
Just a question, if you get this mod working, what exactly does it do?
Sent from my phone. :3
Click to expand...
Click to collapse
It works like this, you do the hardware modification once, and you can unbrick your phone under ANY circumstances like this:
It enables uploading of the Hummingbird Interceptor Bootloader (HIBL). The HIBL enables uploading of unsecured code. You can upload bootloaders or kernels, or just about anything with the HIBL.
AdamOutler said:
It works like this, you do the hardware modification once, and you can unbrick your phone under ANY circumstances like this:
It enables uploading of the Hummingbird Interceptor Bootloader (HIBL). The HIBL enables uploading of unsecured code. You can upload bootloaders or kernels, or just about anything with the HIBL.
Click to expand...
Click to collapse
So.. your telling me (watched that video), that you HARD bricked your phone, did a little hardware, and brought it back from the dead thanks to the HIBL? You sir, are a god amongst tech folk.
Sent from my phone. :3
Longcat14 said:
So.. your telling me (watched that video), that you HARD bricked your phone, did a little hardware, and brought it back from the dead thanks to the HIBL?
Click to expand...
Click to collapse
Yes. I DELETED the Primitive and Secondary bootloaders totally from that device, used Ultimate UnBrick Resurrector to upload Download Mode to the device, then used Heimdall One-Click to reload firmware.
I have an infuse with a busted sim card reader and it wont turn on pm me if its good for you
Sent from my SGH-I997 using XDA App
pumasmedina7 said:
I have an infuse with a busted sim card reader and it wont turn on pm me if its good for you
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Dude, that would be SO helpful.
If you can, do it, the Infuse will be useless after that though (Processor removed, from what he's said), but I think you can just warranty replace it for another after that.
So this is what we need to get other OS'es on the Infuse?
By other OS'es, you mean like the HD2 that has WP7, Android and everything?
OR does this mean better ROM's?

[Q] Stuck on [RUU]WP

I am currently using HackAce to root my Inspire 4g.
At first it didn't work, so I tried again after fixing my USB cord problem. I wasn't using mine, I accidently grabbed my friends. Now I am stuck on [RUU]WP,radio,95 and I've been stuck on this for a while now. My phone currently shows the black HTC screen with the green loading bar that is currently stuck about 3/4ths of the way. I've read the manual I think a thousand times and can't seem to find the answer to this.. or am I over looking it out of frustration.
Can anyone tell me how to fix this problem or should I just leave it?
http://forum.xda-developers.com/showthread.php?p=26918811
You can go there, which is a few post below yours, and if you continue scrolling down you may find a few similar to yours.
But before heading to the irc channel, see if you can find your issue.
Sorry I couldn't be more of help, not too familiar with those kinda problems.
One last thing, if you can't find your issue here in the inspire, you can check the desire hd forum, there are a bunch of Q&A where people have gotten stuck in the past couple of weeks.
Sent from a dream.
yeah well no one in the channel is being any help... so idk.
Have you checked the thread here on xda for the hack kit?
What I do know is that your phone is repairable, no worries there. Give me a few, I'll see if I can find something.....
http://forum.xda-developers.com/showthread.php?p=26793050
Been here yet?
http://forum.xda-developers.com/showthread.php?p=25934577
Is this one similar to your issue?
Edit: where are you currently with your issue? Have you done anything?
A more detailed explanation of everything that you have done and where you are right now would help.
Sent from a dream.
not quite.
When my friend decided to root my phone, it was my fault the phone messed up the first time... he tried to fix the problem by factory resetting it, which I'm sure messed up my USB debugging and charge only options. I switched the cables, switched out the SD card because the second time I tried it, the SD wouldn't take. So the third time I tried this, it went a lot farther then last time but its now like stated above in the first text. I'm entirely new to this, I have always been an iphone user, so thats why I let him do it, since he did his the same way we are doing now... but for some reason, mine won't get past the RUU(radio95) part. It's been on that for about 3 hours now and I'm too afraid to unplug it.
http://forum.xda-developers.com/showthread.php?p=26632920
http://forum.xda-developers.com/showthread.php?p=26357698
The second link has another link at the bottom.
Now, I'm just posting these for you to find which one is similar to your issue.
Read them, don't try anything you are not 80-90% sure off.
What else? Three hours stuck in the same spot? Well, there's only one thing to do.
After that press and hold the down volume button plus the power button to see what happens.
Edit: I edited the previous post above your last one in case you didn't read it.
2nd edit: scratch everything I said. You are still running the hack kit with your phone plugged in. Read the hack kit forum. I believe everything else I suggested is pretty much useless. Maybe I ought to go get some sleep
3rd edit: http://forum.xda-developers.com/showthread.php?t=1421904
Check this, I believe this is your issue.
Sent from a dream.
now I have white triangles with !!! in them around the HTC logo...
you posted a thread about it but it didn't help me any.
First, stop trying things.
Take a break, nothing will happen if you don't do anything.
Re-read our conversation, skip the links. Find out where the miscomunication happened.
Google "white triangles around htc logo" it should be the one from 22 of april, it's about the third link, title [Q] htc logo with 4 triangles with exclamation marks.
Once again, don't try anything yet. First find out what you have.
Sent from a dream.
{
"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"
}
this is how I feel right now. lol
From what I was able to understand, there are a couple links I posted that were issues you had
The last one, the google search may be were you are right now.
Read, be patient, you'll get there.
Sent from a dream.
I cant even get it to do anything, not even a restart while using the down volume and the power button at the same time.
First. Explain in detail everything you have done. The more the better.
Include what you did with the volume and power button. Was the cellphone on when you tried that? Off? Connected? Everything.
Sent from a dream.
OKAY. NOW!
This is what my phone is saying...
***** AAHK *****
ACE PVT ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.06.06.30_M
eMMC-boot
Apr 12 2011,00:55:45
RUU
Do you have the options fastboot, recovery, and so on?
By the way, you are rooted.
Sent from a dream.
I currently have no options. thats the only things it says on my screen along with two triangles in the bottom corners.
Now Im stuck as what to do. It's going to be one of several things. BEFORE TRYING ANY ONE OUT MAKE SURE IT IS FOR YOUR CASE / SCENARIO. YOU CAN MESS SOMETHING UP IF YOU DO NOT KNOW WHAT YOU ARE DOING. I do know that at this point you can still fix your cellphone.
It is either going to be
-run the hack kit again.
-Can't remember what it's called but it has to do with flashing or pushing a file through....
Read the threads I posted, it might be there. If not, search both the inspire Q&A and the desire hd Q&A, i've read it in one of those.
Do a search for your symptoms, might be quicker.
DO NOT DO ANYTHING IF YOU ARE NOT SURE.
also, hit the hack kit channel, they might be able to help you, just be patient and above else, try to explain everything in detail. What you did and the same info you just posted.
Sent from a dream.
keiyako said:
I currently have no options. thats the only things it says on my screen along with two triangles in the bottom corners.
Click to expand...
Click to collapse
Keiyako, You are stuck because you didnĀ“t follow the manual. If you get stuck, you have to fix connectivity issues and then re run the Kit. In fact, if the radio failed, you could have flashed it over again. You are already S-OFF so, could have solved that by just flashing CWM and then a Custom Rom.
Just flash a ruu for your phone and start over. Stop trying things that eventually will mess the device.....and why do you say that nobody helps in the Hack Kit IRC channel? we there everyday and most of the hours of the day....but we also sleep, eat and have families....
I'm not that tech savvy. I didn't do the rooting, my cousin did, messed a lot of it up because he said he knew what he was doing... This is how he left my phone, all I was trying to do was to get some advice before I even touched it. Needless to say, I have it fixed now thanks to a friend I went to high school with who runs a repair/mod business here in town.
Sorry.
keiyako said:
I'm not that tech savvy. I didn't do the rooting, my cousin did, messed a lot of it up because he said he knew what he was doing... This is how he left my phone, all I was trying to do was to get some advice before I even touched it. Needless to say, I have it fixed now thanks to a friend I went to high school with who runs a repair/mod business here in town.
Sorry.
Click to expand...
Click to collapse
hi I have the same problem! how did you fix it?

UART port found on Fire HD6

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
~

Oneplus One. EMMC Possibly Corrupted but not sure, need help unbricking.

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.

[Q] Replaced motherboard, now it's not charging!

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

Categories

Resources