Maybe this question belongs in the general android dev section, if so then sorry. What makes a phone "brick". I know what it means, but why can't we in brick them. If everything is wiped, what keeps us from accessing the wiped partition with a pc and doing what we want to with it. We do it with computers all the time. I know its not exactly the same, but its very similar isn't it? Is it like the BIOS going bad on a pc that causes them to brick?
Sent from my ADR6425LVW using xda app-developers app
From what I have heard, at least on the Rezound, bricks are generally caused by bad hboots. People do often compare hboots to BIOSs, but when they do, they always qualify their statements, adding that the two actually have little in common, but it's the best comparison between Android and PC. I'm sure someone else can explain that a lot better than I can. I believe a brick can also, theoretically, be caused by a bad kernel/boot partition, since it is what tells the phone where to get the information needed to boot (or something like that).
People also sometimes call it bricking when they just mess up the hardware in some way, like while replacing the digitizer.
Their are methods to unbrick from an hboot related brick, but they do not always work.
What Max said.
Just wanted to say you did indeed post this in the correct section. Even if it's a development related question, questions belong in the questions section
Sent from my ADR6425LVW using XDA Premium.
I always thought the same thing why can't you just wipe everything and reinstall if the brick is caused by a software issue then what's the stop you from removing that software and putting working stuff on.
The only thing I can think of to answer my own question would be, for example, you know how you can adjust the voltages to the CPU, well lets say you install some bad or damaged software which controls the Hardware say you send too much voltage to a component such as the CPU and you fry the component by sending too much voltage or maybe its even possible by sending not enough voltage.
Just a thought anyways . I could be way off I have no idea really.
Sent from my HTC One S using xda premium
Bad hboot brick is the most common common and it is irreversible because you need a functional hboot to flash anything. So a corrupted hboot leaves you with a catch 22. Your hboot is bad, you want to flash a working hboot but your bad hboot can't flash anything so your stuck.
A kernel or bootlooping brick is a soft brick because you can still boot to hboot or recovery and flash a working kernel
Sent from my ADR6425LVW using xda app-developers app
Can't a bad radio brick it too? I know on a pc you can start with nothing, no boot partition or mbr, and the kernel is flashed with the os (windows, linux), and you boot from a cd or floppy. The only thong you start with is BIOS. Is being incapable of booting from another source like USB or sd card the main reason we can't unbrick most phones? I guess I'm just looking for deeper detailed nerd answers for a better understanding. I'm a nerd as most of you would probably claim to be too lol and I just want to get a better understanding of how it all works.
Sent from my ADR6425LVW using xda app-developers app
There are three main parts to phone firmware. You have the boot loader, which handles very low level stuff and generally doesn't touch partitions, but provides a boot environment for other software such as recovery and system...which is why, in Broad com routers, it is called the CFE or Common Firmware Environment. Think of it as the BIOS of the phone. If the boot loader is corrupt or damaged, chances are there will be no way to recover the phone via normal methods; JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Recovery is in a way like DOS. It has the ability to create, mount, change, and delete partitions, but can't touch low level stuff like the radio or bootloader. It can modify and remove files on partitions and change specific things such as the kernel. A damaged recovery can usually be fixed without any special tools as the phone will boot but won't go into recovery mode. In the case of the Rezound, a PH98IMG flash would fix it.
The operating system of the phone is as Windows or Linux GUI is to a computer. It provides the user with an easy to use environment as well as tools and software to help the user do what he wants to do. A damaged OS may boot, and problems may be limited to a few specific apps, or the problem may be system wide to the point of unusability...or if there is something wrong with the kernel, the OS will not start at all, and will be stuck in a boot loop. Easily fixable via recovery.
socal87 said:
JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Click to expand...
Click to collapse
What's JTAG?
feralicious said:
What's JTAG?
Click to expand...
Click to collapse
A lot of devices have JTAG ports that allow us to use another piece of hardware to access the deeper levels of the hardware and software.
This makes it possible to unbrick by fixing those deep files that are required for the device to work.
Also, Wikipedia is your friend.
Here's the nerdiest answer you're going to get. Your phone is ultimately just a large hunk of copper and silicon. It contains all sorts of microchips and connections and are necessary for literally every function of the phone. Literally... From the LEDs to the audio components. Everything. If youve heard of a schematic that's what I, talking about. Each one of these microchips must be programmed form its specific function. Were literally talking hardware level here. No Android OS no hboot etc.
Point of explaining all of that being that there are all sorts of programmable parts of the phone that you will never modify, access, or even think about. If you manage to access and screw up the wrong thing.. You can quickly go from functioning phone to just a hunk of copper and silicon. Hboot is the lowest layer software that devs will modify. If you screw up the hboot.... You are left with a brick. Is it ultimately possible to unbrick in any situation? Yeah of course. How else would HTC have made the phone in the first place. But if you screw up the hboot... You're gonna need an engineering degree to fix that thing. And at the cost/effort that that would take.. You'd be better off buying a new phone. Thus your phone is totaled and its best use just because a paperweight.
Sent from my Nexus 7 using Tapatalk 2
I think it's important to note that most of the phones people post about being "bricked" aren't actually bricked. A lot of times people panic and if they can't fix their phone, they call it a brick. It's kind of a common, often used slang term. Now there's terms like hardware brick, hard brick, software brick, and soft brick and probably some more.
But if it's fixable in my opinion using a computer and commands, or if you can see it's getting power, it's usually not really bricked.
For example, when the s off process came out the forums were over run by people who "bricked" their phones while trying to attain s off. What actually happened in a big number of these cases was that the windows script replaced the boot.img that was on their phone with a custom boot.img for the service mode. When there was a windows error with the software which was newly developed and released, and the windows app hung up or the computer went weird mid process, they had a black screen with a funny image, like a disk and arrow maybe, and when they turned the phone on it only went to that screen. In fact it happened to me which is why I figured out how to fix it and what caused the problem.
Now all they would have had to do is run a fastboot command from their computer, "fastboot flash boot boot.img" to flash the boot.img that matched whatever rom was installed on their phone, and they would be back up and running. But for a large number of users, when they phone was unresponsive and turning it on took them straight to the black screen, they considered it "bricked."
When in fact the phone was doing exactly what it had been commanded to do, and it was the person who was expecting something unreasonable, when you think of it in 1's and 0's, or black and white. Of course this isn't always the case, there are some real bricks, just not as many as one would first believe if they scanned through forum topics for the word bricked in the title.
Related
Has anyone successfully done this??
Link: http://forum.xda-developers.com/showthread.php?t=1220181
I finally hard-bricked my Vibrant, and I'm wondering if this has been accomplished, instead of sending it to a specialist to JTAG it the traditional way!!
Im trying to see if I can resurrect it myself instead of losing it for a week!
And yes I'm aware of the One guy here in the states that does JTAGing, but Id be seriously outa work for a week as my phone is my work/life line, cuz I'm an Independent contractor, so its not about the money Id spend but the time down without a way to work/communicate, I haven't contacted TMO yet and told them it was hosed using the Kies method to upgrade it to Froyo. Wish I never had done that!! Should've known better, didn't see/read any post about the horrors of using Samsungs KIES program until it was too late!!!
I was trying to purge a SH 5.0 install that went bad, I flashed back to stock Eclair. Then went to Froyo, But thats when I developed a problem with boot looping after doing Froyo, so I tried the KIES program to go to "FROYO" and that's when It bricked!!!
Anyways its bricked hard, and I'm wondering if this has actually been done successfully!
And any tips that I might need to get the Heimdall Program to actually detect it thru the USB method, would be awesome! Even though it wont turn on!!
Link to the thread: http://forum.xda-developers.com/showthread.php?t=1220181
JTAG isn't a method that can be done through usb. If you had googled jtag, you would have found out that it is a physical port built into the motherboard of our phones. In fact most electronics have a jtag port.
*Joint Test Action Group**(*JTAG*) is the common name for what was later standardized as the*IEEE
1149.1**Standard Test Access Port and Boundary-Scan Architecture*. It was initially devised for testing*printed circuit boards*using*boundary scan and is still widely used for this application.
Today JTAG is also widely used for*IC*debug ports. In the embedded processor market, essentially all modern processors support JTAG when they have enough pins.*Embedded systems*development relies on*debuggers*talking to chips with JTAG to perform operations like*single stepping*and*breakpointing. Digital electronics products such as*cell phones
*or awireless access point
*generally have no other debug or test interfaces.
In order to flash your phone, it will have to be dismantled, and hooked up to the jtag box.
Beware of angry gingerbread man
Adamcooks, I read the entire squabble about this between you and RaverXX
I downloaded your one click as well!!
So can you give me some advice on how to get my phone to even simply turn on, WO the soldering involved using traditional method of JTAGing??? Mine wont power up or show any LED activity, nothing when plugged in or do anything using traditional methods known to work with "SOFTBRICKING"
I mean, it seems my Boot loader is corrupted, or the other file you suggested, when Raver and u were arguing!! If I could even get a faint indication of life from the phone, It could be brought back to DL, but a DL Jig, as well as all the other extensive methods to get it even to power on, let alone go into DL mode isnt working at all, after many, many try's!
Can your one-click program, with the proper BL's for my T959 Vibrant be acknowledged by either yours or Heimdall's Program, so as to even be able to flash this WO, Jtaging it, even if it wont even power up in any way to handshake with my lappy???
BTW, I'm not trying to start another **** storm, after what happened with RaverXX, but it seems some of the people who had the same scenario as I do, were successful, so I'm wondering between the 2 of you, how to approach and try this, I respect both ya'll's work and contributions, but for me the bottom line is to get my phone working once again, short of either#1 JTAGing it, or trying to go thru the painful experience of trying to get TMO to replace it with a new same model, because KIES fubar'd it!!
Anyway I wish you 2 guys could lay out the proper set of instructions as you suggested, along with the proper files or links, for us to try either his method or yours. I think its possible to resurrect these phones, this way short of physical damage, and as such!! IDT you 2 fellas would've put so much effort into this theory, if there wasn't some merit to it!
So I'm all ears and eyes to your suggestion of how to get my phone to even breath again, so I can go back to DL mode, and get her working again!!
But when nothing what so ever happens, no power up, no lights, no nothing occurs, it seems to me its bricked, even though you say a truly bricked phone , has physical hardware damage, which tech is prolly correct, however in this case, mine is software bricked very hard!!!! And for purposes of communication and clarity, Ill stick with bricked, If I knew the MB was fried and or damaged, Id simply order another one, and replace it, and power up the phone, and be done with this ordeal, but my corruption occurred during using the Samsung KIES program, regrettably!!
And I'm fairly certain that either the Boot loader file is corrupted or the file you say creates a black screen usually displaying the Pc-phone logo is done for, so again, should I try the command prompt instructions to fix that, or do I use your one-click, or go to ravers method ?? I asking legitimately, because I know your knowledge in these matters has merit!! Thanks for your reply!!
Unless he changed his account, that was a different Adam in that other thread. I still say try it, cant make things any worse.
Sent from my ZenDroid, meditating on the XDA App
I may give a sharp response sometimes, but an internet squabbler I am not. connextion(sp) has a motherboard cradle that contacts the correct pins to jtag flash, without causing any damage to your phone.
Have you tried the resistance jig? I think that skorpn is the one who makes them ( 301k ohm resistor plug into the usb port can force d/l mode if the bootloaders aren't borked)
these are the last two resorts in ng phone resurrection.
Beware of angry gingerbread man
Ya My mistake Sorry
Ya I got you mixed up with another developer who has a very similar handle, so many apologies, however I wasn't flaming you anyway, shape or form, just apologizing for the mistaken ID
BTW Is the skorp resistance Jig a completely different animal from the DL Jig Tech Mobile sells doing the same result, in other words is it able to bring a phone like mine in the condition it is, into DL mode??? I saw the Skorp design, it just seems to me, its the same thing I already have from Tech Mobiles design. Accomplishing the same thing, but for phones that actually power on in some way shape or form, light off etc!!
Anyway thanks for your input, and effort, I'm still sorting all the info on everybody's suggestions and methods, short of JTaging it!!! Gonna make a move on a procedure here soon, this evening!!
is there any way at all to come up with a method of restoring an actually bricked phone...shouldnt there be a way to get the phone running again by forcing a file to flash to a certain component...i mean they have to program these phone somehow to begin with...only wondering cuz the purpose of s-on is to protect the phone from faulty or slightly defective code which could seriously damage the devices ability to boot up, but with s-off im assuming theres a way to circumvent any possible issues with the phone, of course there would have to be someway of interfacing with the phone while its inoperable...and im only assuming there are only two possible bricking situations, extremely damaged code or hardware failure...thinking back to my days with the droid x i always wondered why we never just opened the phone up and tried replacing the encrypted efuse chip/bootloader with a hacked one...just thinking outside the box, removing the fear of bricking a device would help development since we could theoretically get away with anything especially creating completely custom kernels and whatnot
There is a "l download" mode that you do something similar to the s-off wire trick to get into and that allows you to push something to the phone through bootloader. I have not seen anyone successfully unbrick their phone through because to get into this download mode, the phone has to have some sort of life which the phone usually does not in the cases I have seen.
Sent from my ADR6425LVW using Tapatalk 2
Chad was looking into trying to see if the phone could be used with JTAG to see if it could be unbricked, but don't think he's really found much yet.
what if we could sort of create a software buffer that wouldnt allow code in the hboot to be corrupted? im thinking something like a pc where you have the bios and then actually boot from a second application...the hboot would remain completely free and open to run and allow modifications but you are not modifying it directly, only the applications directly under it...im assuming boot manager could be adapted for this use...in theory it would work like knoppix does with linux where linux is actually installed under knoppix and knoppix is a really basic specialized operating system built for dual booting...i believe this is the way most roms for the droid x were created by utilizing the 2nd init to bypass the official rom (rom of course being the actual iteration of the term not the custom roms we flash)...by equating the hboot of the rezound to that of a bios in a pc, im proposing a method of circumventing the code needed to actually make the phone function, to either ensure there is no possibility of bricking...of course im not too sure how the innards of the phone actually operate, im just drawing inspiration from other tech...
...also what are the chances we could just replace what ever chip the hboot is installed on in the event its ever corrupted?!?!
Or could we somehow build a virtual machine running android including the lower level hboot. And run it on a pc that way it won't fry the phone it will just freeze the emulator
Sent from my ADR6425LVW using xda app-developers app
only if we could get android and its subsequent builds (phone and android version) emulated in the most accurate way possible...since emulating a different cpu architecture and its software is always full of bugs...im not against the idea, ive considered it and its possible but we would still need something running on the phone to ensure the phone its self is not bricked if/when the virtually conceptualized rom is ever tested on the actual handset...it would be awesome if it could be adapted for use on different platforms...
rezin said:
what if we could sort of create a software buffer that wouldnt allow code in the hboot to be corrupted? im thinking something like a pc where you have the bios and then actually boot from a second application...the hboot would remain completely free and open to run and allow modifications but you are not modifying it directly, only the applications directly under it...im assuming boot manager could be adapted for this use...in theory it would work like knoppix does with linux where linux is actually installed under knoppix and knoppix is a really basic specialized operating system built for dual booting...i believe this is the way most roms for the droid x were created by utilizing the 2nd init to bypass the official rom (rom of course being the actual iteration of the term not the custom roms we flash)...by equating the hboot of the rezound to that of a bios in a pc, im proposing a method of circumventing the code needed to actually make the phone function, to either ensure there is no possibility of bricking...of course im not too sure how the innards of the phone actually operate, im just drawing inspiration from other tech...
...also what are the chances we could just replace what ever chip the hboot is installed on in the event its ever corrupted?!?!
Click to expand...
Click to collapse
Only in a perfect world....
Sent from my ADR6425LVW using Tapatalk 2
Evocm7 said:
Only in a perfect world....
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
It's already poosible...it just hasn't been done for android to my knowledge, much less the rezound
rezin said:
It's already poosible...it just hasn't been done for android to my knowledge, much less the rezound
Click to expand...
Click to collapse
Yeah I remember I used to develop home brew software for the xbox (original) and someone created a complete emulator for windows where we could test anything before flashing it to the xbox. That's why I said that for our phones it could work but I suppose it would have to be different for every phone
Sent from my ADR6425LVW using xda app-developers app
So considering what ive heard about the Unbrickable mod if i buy another device off ebay with a broken screen i should be able to just replace the main processor board correct?Or is it the harddrive as well perhaps? what exactly happens when it becomes unbrickable?How much of the device is actually affected?
Brasstire said:
So considering what ive heard about the Unbrickable mod if i buy another device off ebay with a broken screen i should be able to just replace the main processor board correct?Or is it the harddrive as well perhaps? what exactly happens when it becomes unbrickable?How much of the device is actually affected?
Click to expand...
Click to collapse
I...I... don't understand this question?
Basically my device is bricked almost beyond repair, theirs something called Unbrickable mod that you can do but you actually have to take the whole thing apart and short some resistors together or something.I don't understand the mod well enough to do it myself so im really just asking instead of modding it if i can just replace the whole board, but i dont know exactly what part of the device is making it bricked.
Brasstire said:
Basically my device is bricked almost beyond repair, theirs something called Unbrickable mod that you can do but you actually have to take the whole thing apart and short some resistors together or something.I don't understand the mod well enough to do it myself so im really just asking instead of modding it if i can just replace the whole board, but i dont know exactly what part of the device is making it bricked.
Click to expand...
Click to collapse
The only thing I've ever heard of with "unbrickable" in it, is the "Unbrickable Resurector" here: http://forum.xda-developers.com/showthread.php?t=1386669. The Galaxy Player 5.0 is considered "unbrickable" because there is nothing you can do "software wise" to brick the device without being able to bring it back. The only way, I know of, to brick the Player 5.0, is for there to physically damage the hardware of for the hardware to fail.
I haven't heard of any mod where you can "short some resistors" unless your talking about JTAG....
Why do you believe that your device is bricked beyond repair?
Meticulus said:
The only thing I've ever heard of with "unbrickable" in it, is the "Unbrickable Resurector" here: http://forum.xda-developers.com/showthread.php?t=1386669. The Galaxy Player 5.0 is considered "unbrickable" because there is nothing you can do "software wise" to brick the device without being able to bring it back. The only way, I know of, to brick the Player 5.0, is for there to physically damage the hardware of for the hardware to fail.
I haven't heard of any mod where you can "short some resistors" unless your talking about JTAG....
Why do you believe that your device is bricked beyond repair?
Click to expand...
Click to collapse
Oh sure you can totally brick it in software. I've done it twice. You have to corrupt the SBL without corrupting the PBL. That way it still tries to boot from eMMC, but fails, instead of trying to boot over USB.
He's talking about http://forum.xda-developers.com/showthread.php?t=1206216. Apparently AdamOutler's friend's device was PBL corrupted, so he only needed the Resurrector to fix it, and hence has never looked for the OMx pins (see http://forum.xda-developers.com/showthread.php?t=1236273 - nobody's tested it).
@Brasstire, the broken part is the bootloader on the flash memory chip, which is between the CPU and the mainboard, so you'd need to replace the mainboard. Or you can get it JTAG'd for $40 from mobiletechvideos (http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-player-5-0-jtag-brick-repair-service/).
Mevordel said:
Oh sure you can totally brick it in software. I've done it twice. You have to corrupt the SBL without corrupting the PBL. That way it still tries to boot from eMMC, but fails, instead of trying to boot over USB.
He's talking about http://forum.xda-developers.com/showthread.php?t=1206216. Apparently AdamOutler's friend's device was PBL corrupted, so he only needed the Resurrector to fix it, and hence has never looked for the OMx pins (see http://forum.xda-developers.com/showthread.php?t=1236273 - nobody's tested it).
@Brasstire, the broken part is the bootloader on the flash memory chip, which is between the CPU and the mainboard, so you'd need to replace the mainboard. Or you can get it JTAG'd for $40 from mobiletechvideos (http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-player-5-0-jtag-brick-repair-service/).
Click to expand...
Click to collapse
Thanks for the conformation, i assumed it was the main board but wasn't sure that was the only thing affected.I think ill just end up replacing the main board, JTAGing and fixing it myself will be about the same price but i think ill do it myself so i have some extra replacements parts when im done.
Made the mistake of bricking my Att HTC ONE M7. Ive tried everything to revive this damn thing, did loads of research to see if anyone came up with a solution with no luck.
I was restoring my backup phone (Galaxy S2) to convert my mom to an android and get her away from that pile of **** iPhone. I downloaded a philz recovery from the xda app on my ONE for the S2 (which is something I've always had a rule against for this reason).
To make a Long story longer I, for some reason, thought it was for my ONE. Flashed it in recovery (TWRP) "Failed" then I realized what i did. But it failed, I then flashed a bootanimation. "Success"..
Restarted my device but it never came back on. No lights, screen, or response from any combination of buttons.
I guess the recovery flash ,even though it failed, was the nail in the coffin. I just can't believe it died that easy even though it let me flash a bootanimation. Not paying attention just cost me a lot of money and loads of pride.
It shows up qhsusb_dload in device manager. I e-mailed HTC and I'm gonna try a warranty claim. Also talked to someone about Jtag.
If anyone wants to attempt a solution Im game.. I will keep this post up to date with what run around HTC gives if I go that route. If anyone cares...
"IF IT AIN'T BROKE, FIX IT UNTIL IT IS...
HTC ONE Rooted, Unlocked,
Tampered Just a Tad,
Maximus HD 4.4 KitKat
Died an Honorable Death.. due to
Lapse in judgement, temporary
Mental Retardation..
Sent using my HTC One XL backup, fill in,
The ONE I can always count on...
Are you able toqccess fastboot or TWRP?
Sent from my HTC One using xda app-developers app
No, cant access anything.. black screen. No response.
Sent from my HTC One X using xda app-developers app
Update:: HTC told me to do this combination of buttons that I haven't read anywhere else. It didn't work for me but it might be a solution for others experiencing the dead black screen issue.
•Charge the device for at least 10 minutes
•With the device truly OFF while still being plugged into the wall outlet, push in and hold volume up and volume down AND power button, for 2 minutes.
•Let go. Device will boot up, and battery/charging logic are re-calibrated.
Sent from my HTC One X
https://www.youtube.com/watch?v=db5f3If-2Jw&feature=youtube_gdata_player
Idk if this I'll worth... Wish you the best. Reading more in dept about your problem, you are in a touth position
Sent from my HTC One using xda app-developers app
Sending my phone in for Jtag via Mobile Tech Videos. I've only heard good things (on average) gonna send it off Monday and we shall see...
Sent from my old faithful HTC One X
I am also stuck
i am also stucked QHSUSB DLOAD really worried please help if any body is having solution
Does your charge led come on when it's plugged into the wall? Do any lights at all work?
Sent from my HTC One_M7
rasoolakhter said:
i am also stucked QHSUSB DLOAD really worried please help if any body is having solution
Click to expand...
Click to collapse
Their is a fix now .. I did mine today
QHSUSB_DLOAD Fix
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
http://forum.xda-developers.com/showthread.php?t=2770684
Prerequisites
the appropriate package for the device
a supported bricked device
a usb cable
fastboot
distro utils: md5sum, strings, tail, grep, unzip ( all included in most linux distros)
some basic linux experience
root access on a linux machine
patience
DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.
Instructions
Boot the linux box and download the appropriate package for the device.
Remove the sim card from the phone. Do not connect yet
Extract the package in your working directory
Open up a terminal and cd to that directory
Run revive.sh as root and connect the device
Code:
sudo ./revive.sh
The procedure is automated. At the end of the unbrick process, you will need to charge the device fully and then flash one of the full firmwares bundled, as pointed from the script. This is crucial to ensure device stability.
Click to expand...
Click to collapse
The problem with mine is that after I bricked it I sent it to be jtaged. When I got it back it wouldn't unlock to any network. No matter what it asks me for an unlock code.
Maybe I can run this on my phone and restore the emmc that cross checks the modem.???
What harm could it do
Sent from my HTC One
cannonofcourse said:
The problem with mine is that after I bricked it I sent it to be jtaged. When I got it back it wouldn't unlock to any network. No matter what it asks me for an unlock code.
Maybe I can run this on my phone and restore the emmc that cross checks the modem.???
What harm could it do
Sent from my HTC One
Click to expand...
Click to collapse
where did u send?
How much was it ?
I sent it to mobile tech videos... I heard good stuff about them but don't send it to them if you want your phone to work again. I don't remember what it cost me but I wish I would have waited for this unbrick method. The jtag process fried my modem or part of my motherboard. Try the unbrick method. People have had a lot of luck with that.
HTC ONE M-7
cannonofcourse said:
I sent it to mobile tech videos... I heard good stuff about them but don't send it to them if you want your phone to work again. I don't remember what it cost me but I wish I would have waited for this unbrick method. The jtag process fried my modem or part of my motherboard. Try the unbrick method. People have had a lot of luck with that.
HTC ONE M-7
Click to expand...
Click to collapse
i tried that method but after the command i get a message error that my device isn't found
My Amaze was connected via USB to my Ubuntu laptop and I was testing a game I was working on. Suddenly, my computer could not recognize my device and, my device and charging light was off (the battery was at ~94%). I have 3 batteries, and none of them work when trying to power on the device. My device was S-OFF, SuperCID, rooted, and running Android Revolution ROM HD. I was using a Samsung cable if that makes a difference. I tried booting with Power+Vol. Down but that did not work. I figure it is a hardware problem, but it seems odd that it would do this all of a sudden. Can anybody confirm what is wrong with it, and maybe a possible fix? Thanks!
Edit: I get the QHUSB_DLOAD driver message.
Anyone? Please help!
Sorry, your phone is almost bricked. Flash chip bug makes large chunks of the entire flash unreadable. It's more likely to happen if you issue a trim command or format a partition in the wrong way. (Well, it's the right way for flash, but our chip can get borked.) Mine just happened when I was copying a bunch of data over.
You corrupted something fairly early in the boot process but not the earliest thing. Search for fixes for the qhusb and you'll find a couple things. They didn't work for me, but might for you. Even if you fix it, it might re-brick itself after a bit of usage.
ezdi said:
Sorry, your phone is almost bricked. Flash chip bug makes large chunks of the entire flash unreadable. It's more likely to happen if you issue a trim command or format a partition in the wrong way. (Well, it's the right way for flash, but our chip can get borked.) Mine just happened when I was copying a bunch of data over.
You corrupted something fairly early in the boot process but not the earliest thing. Search for fixes for the qhusb and you'll find a couple things. They didn't work for me, but might for you. Even if you fix it, it might re-brick itself after a bit of usage.
Click to expand...
Click to collapse
Thank you for your response! You logic seems to be correct as I wasn't messing with any critical files. Please update your post if you find a solution!
Did you find the post(s) I was talking about? They may work for you. It basically involves trying to rewrite the bootloader.
I ended up punting and trying to desolder the MMC chip so I could try to get my data off it. Unfortunately, it's epoxied on so it got very damaged even though I was using a pretty good hot-air reflow station, so I haven't tried soldering it to a SD-card reader.
ezdi said:
Did you find the post(s) I was talking about? They may work for you. It basically involves trying to rewrite the bootloader.
I ended up punting and trying to desolder the MMC chip so I could try to get my data off it. Unfortunately, it's epoxied on so it got very damaged even though I was using a pretty good hot-air reflow station, so I haven't tried soldering it to a SD-card reader.
Click to expand...
Click to collapse
I have tried that numerous times to rewrite the bootloader, but to no avail. Can you post a picture, and do you think a JTAG would work?
cowboy1995 said:
I have tried that numerous times to rewrite the bootloader, but to no avail. Can you post a picture, and do you think a JTAG would work?
Click to expand...
Click to collapse
Picture of the board? I think I have it around somewhere. If I can find it, sure.
In theory it should work, but I don't think anyone has publicly mapped out the pins for it and I didn't feel like trying to figure out the software side of things to connect it to the generic JTAG adapters I have access to. It's possible that one of the phone-centric JTAG makers has an adapter board, but I'm not willing to spend $bank on a phone worth barely anything.