Hi everyone, so I have a 1GB/8GB Omate Truesmart that has been awesome. After having the Imperium Operative ROM on it and realizing the sensors were not working, I decided to try and revert back to the stock firmware. However, that's where the trouble started. My cradle wasn't working properly during the process and stopped in the middle of it, and now I can't even boot my watch on (unless there's some alternative way). On top of that, anytime I try to connect it to any of my USB ports, it keeps saying on my Windows 7 laptop that the USB device is not recognized, and I tried uninstalling and reinstalling the drivers again.
So, if anyone can please help me and guide me in "unbricking" the watch and just being able to have my laptop recognize it so I can actually do the stock firmware process, I'd be really grateful. Thanks a lot!
You used Sp flash tool correct? I'd suggest reading the unbricking guide first but answer these first:
What color was the progress bar when it stopped?
Have you tried a different port?
Have you pulled the battery yet?
Sent from my GT-P5110 using Tapatalk 2
Actually fixed it!
kuronosan said:
You used Sp flash tool correct? I'd suggest reading the unbricking guide first but answer these first:
What color was the progress bar when it stopped?
Have you tried a different port?
Have you pulled the battery yet?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
Hey kurunosan, so I did follow the unbricking guide exactly, but because my cradle is a little bit finicky (the microUSB has to be plugged into it in an exact position for it to be read by the laptop), it had messed up during the unbricking process and therefore, caused it to be "bricked". To answer your questions though, the color of the progress bar was yellow, I tried all the different ports around my laptop, as well as my work laptop. And I wasn't able to pull the battery because I haven't been able to unscrew the back yet (I blame those crazy small screws lol).
BUT, I was finally able to fix the drivers issue and my watch was recognized by my laptop finally. If I have time later in the next day or two, I'll try and make a guide about it if something like that happens to anyone. Or if anyone is curious or has had it happen to them, you can feel free to PM me.
I'm just glad that my TrueSmart is finally functional again!
shadowninja23 said:
Hey kurunosan, so I did follow the unbricking guide exactly, but because my cradle is a little bit finicky (the microUSB has to be plugged into it in an exact position for it to be read by the laptop), it had messed up during the unbricking process and therefore, caused it to be "bricked". To answer your questions though, the color of the progress bar was yellow, I tried all the different ports around my laptop, as well as my work laptop. And I wasn't able to pull the battery because I haven't been able to unscrew the back yet (I blame those crazy small screws lol).
BUT, I was finally able to fix the drivers issue and my watch was recognized by my laptop finally. If I have time later in the next day or two, I'll try and make a guide about it if something like that happens to anyone. Or if anyone is curious or has had it happen to them, you can feel free to PM me.
I'm just glad that my TrueSmart is finally functional again!
Click to expand...
Click to collapse
The good news for you is that because it was only yellow, your watch was just stuck in preloader mode and you hadn't fully bricked it.
If you disconnected it while the progress bar was purple, you'd be in some serious trouble.
I'm very familiar with preloader and it's such a pain in the ass when the drivers do gymnastics and switch ports or flat out don't work.
Preloader
kuronosan said:
The good news for you is that because it was only yellow, your watch was just stuck in preloader mode and you hadn't fully bricked it.
If you disconnected it while the progress bar was purple, you'd be in some serious trouble.
I'm very familiar with preloader and it's such a pain in the ass when the drivers do gymnastics and switch ports or flat out don't work.
Click to expand...
Click to collapse
Oh gotcha, did not know that about the preloader. Well, good thing that was the only case then!
I have had a similar experience with my Truesmart. I originally tried to apply Lokifish's Root + Enhanced Security patch. This unfortunately failed for some reason and resulted in me not having root or any USB functionaility.
So I went through the process of putting the watch back to stock. I followed the process to the letter, but something went wrong during the process and it ended up with SPTools giving up (looking at the logs it looks like it lost USB connectivity - attached). Now the watch seems to be bricked. I have attempted the process again but SPTools is not detecting anything.
Any help or advice would be very much appreciated....I am a very sad bunny at the moment :crying:
I would prefer to not have to remove the battery (for obvious reasons), but will do if there is no other way round it.
Beta_Tester666 said:
I have had a similar experience with my Truesmart. I originally tried to apply Lokifish's Root + Enhanced Security patch. This unfortunately failed for some reason and resulted in me not having root or any USB functionaility.
So I went through the process of putting the watch back to stock. I followed the process to the letter, but something went wrong during the process and it ended up with SPTools giving up (looking at the logs it looks like it lost USB connectivity - attached). Now the watch seems to be bricked. I have attempted the process again but SPTools is not detecting anything.
Any help or advice would be very much appreciated....I am a very sad bunny at the moment :crying:
I would prefer to not have to remove the battery (for obvious reasons), but will do if there is no other way round it.
Click to expand...
Click to collapse
The patch will tell you if there's an error. It will show the command with the word "failed".
Regarding SPTools attempt to return to stock. In looking at the log it was continuously connecting and disconnecting which usually demotes either a driver,dock or USB issue. It is most likely in a bootloader mode but locked up. I suggest you leave the TS alone for a few hours or possibly overnight and attempt to flash it again.
Unfortunately you have given my very little to go on so other than general fixes there's not much I can tell you. In the future if you run into any issues flashing anything or running scripts it is best to post in that projects support thread and wait for help.
The log clearly shows multiple disconnects, probably because of a bad query. I suggest the same thing Loki did.
Sent from my Galaxy Nexus using Tapatalk 2
Related
-----------------
---This first post is outdated. My current question is one post below. I've left the content of this post for other noobs to see.
-----------------
Hey folks, sorry to bother you all but all input would be greatly appreciated. I'm rather unfamiliar with android flashing and kernels, and have spent the last 8 hours trying to figure this out to no avail.
Following this (http://forum.xda-developers.com/showthread.php?t=1238070) (section 5) guide on how to get back to stock gingerbread on my phone (after a few partially failed attempts flashing other roms), I was using Odin, had the .pit 2.2 as well as CI500_VZW_EH03_GB_CM.tar.md5 loaded into the program and left it running. About 20 mins in, the phone stopped progressing and I started to get concerned. After two hours, I powered down the phone and proceeded to reattempt the flash. This is when things got weird. My phone was unable to enter the Download Mode and instead showed Android system recovery when plugged in, or a black screen with a phone and a computer, with arrows between when not plugged in. The weirdest part is that the phone no longer recognized vol+ or the power button when in Android Recovery, and could only vol- to go down the menu, then was stuck at the bottom of the list.
I've searched everywhere on this site, and google to try and come up with a solution.
When pluggin into the computer, I hear a connection sound, but the device is not recognized by Odin. Pressing the running a blind vol+ and vol-, then a vol- to hope Odin recognizes the device, as pointed out in this (http://forum.xda-developers.com/showthread.php?t=1764022) thread, resulted in nothing. Holding vol- while pluggin in the usb cable, doesn't show the download mode. All of the steps in this (http://forum.xda-developers.com/showthread.php?t=1026746) thread proved futile, as most of them required download mode anyways.
I'm going to keep searching and keep you posted as things come. Your help as always will be greatly appreciated!
Edit: Things just got weirder... After a few more attempts at making this work, I'm now getting an "Unable to charge non-supported battery. See user manual." With this error, I'm not able to get into Android Recovery anymore. More searching...
Edit 2: AFAIK I'm gonna need a jig. Anyone confirm?
Edit 3: Got a jig, Download Mode working, all is well. Please remove this thread, or leave it for other noob flashers to see.
Hey Folks, its been a while since I last posted in this forum, but I ran into a pretty serious issue earlier this evening. I was attempting to flash CM9 to my T959D and was running into tonnes of trouble. Throughout my attempts I was restoring back to stock rom, kernel and bootloader. During one of these restores, Odin froze in Win 7. Since then I've been unable to detect any form of life from the phone. It simply sits in a black screen. Holding the vol down while booting, blind vol up and down cable inserting, using my Jig and inserting the cable/battery in various orders results in nothing. The most I hear is a device failure to connect sound in Windows with no sign of life in Odin.
What can I do?
Someone posted stating leaving the battery out for multiple days would reset something on the motherboard, allowing me to get into download mode. Though I was hoping to have this resolved tonight. I realize that there aren't many people left with these phones, but I hope someone has a solution to this.
I'm going to be installing ubuntu tonight on an older desktop in a effort to resolve this. Though my experience with it is very limited, and success is unknown.
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
TheMegosh said:
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
Click to expand...
Click to collapse
Make sure you use the stock Samsung cable see if you can reinstall the drivers hook it into the computer and hold volume down if you can get any type of signal from the phone your good.
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
MultipleMonomials said:
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Hey no offence but stop telling everyone on the street they need too soljeir there phone with unbrickable mod before they can fix I'm tired of having too calm the person down after you said they have too open up the phone its utter bull****. 1 out of 10 soft bricks you may need it I've been without download mode and fixed mine just fine.
Sent from my SCH-I500 using Tapatalk 2
An update:
Took my phone in to get the jtag service... He said some of my partitions were corrupted, one of which was the boot layer. He put a new bootloader on, and showed it could be placed back into recovery and download mode, but when I got home the device was even more dead than when I left; no device failed to connect sound in windows, just nothing. I'm taking it back to him in a week after exams to get this resolved. Maybe the battery has reached the end of its life...? I checked it with a volt meter, and it had 3v+ so I really don't know.
Sent using Science!
As bbrad pointed out, there may be other solutions, and my answer could be totally wrong, but if even your bootloader is cooked, Unbrickable Mod may be your only hope. Since UM affects startup code literally hardwired into the chip, it should work as long as the JTAG doesn't interfere.
Posted from my Fascinate using XDA Premium
Another update. So apparently I flashed a bootloader from another phone, which royally screwed up the partition, kernel and mounted drives. The technician managed to get the original bootloader, kernel and rom on the phone and everything is working from stock again.
Why on earth is the 959d Telus version such a pain in the ass to customize?
Is there anyone on here that uses a 959d that can direct me to a proper method to leaving stock? Before this entire situation I had vodoo kernel on, with cwm, but every time I flashed a kernel it would hang on reboot and either sit on a black or white screen. In a lot of cases I would flash in cwm, reboot, then I would be brought back to cwm as if there was no rom on the phone at all, no matter what I formatted and wiped.
When I'm not on my phone I can link all of the guides I've tried that leave me back where I started. So I re flash back to stock using Odin.
At the end of the day, I have to ask, is it really worth it in the end? I've rooted and flashed many roms on other phones but have never run into as many problems as with this fascinate t959d
Sent using Science!
I am trying to flash my vibrant to stock, but my laptop says usb unrecognized.This causes Odin not to detect my vibrant in download mode. I have downloaded all drivers including nexus drivers, but still same error usb unrecognized. I have then start on switching data cables including the stock data cables but the errors remain the same. I have tried on different computers and different windows, nothing working its the same errors on all computers. I have messed up by formatting everything in the Vibrant, now it boot loops to Vibrant logo. I can get into download mode normal but I cant get into CWM or any recovery mode, its probably because I have formatted the whole phone. When the phone is off, I plugged in the micro USB to the phone from the laptop, all it shows is the white lines that are in circler motions and then freezes. Weird my laptop still detects it as a USB unrecognized. As the phone is plugged in to the laptop I try taking the battery out and my phone is still on with the frozen screen of those white lines in circler Motions. Can anyone help me, or at least explain to me what the problem may be? My thoughts is that it may be a hardware problem. If so can anyone provide me some schematics on the USB portion? I hope we can bring some light on this problem. Giving it to T-Mobile is not an option. I have dealt with many problems and solved it, but this is one problem that keeps me stomp in my own tracks.
You can give a man a fish and he will eat for a day, but if you teach a man to fish, he will be able to eat for a lifetime!
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Woodrube said:
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Click to expand...
Click to collapse
I agree with you, it may be a HW issue. I have tried connecting other phones to my laptop and it reads it just fine, but for my vibrant no success. Im gonna go ahead and actally open it up and check on some componets, i have a feeling that it may have burnt one of the componets due to over charge. Ill get back with you on my findings. Keep me updated on your progress.
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Woodrube said:
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Click to expand...
Click to collapse
yes i've tried. I used a Q-tip and some alcohol, still same problems.
Update: Nothing!! How about you?
I have tried un/reinstalling the drivers, Odin v1.8, 1.3 and 1.0, about 4-5 cables and all 3 ports. I have cleaned the USB with alcohol and at this point am at a slight loss. The phone boots into DLmode and charges fine, so I don't think it is a faulty USB port. I cannot get into any recovery or ROM boot. All I have is DLmode and the GB bl screen. No kernel or ROM splash.
Gasp! I'm in a similar boat guys. My phone charges fine, and all my drivers are working and up to date...I can get into DL mode and all that jazz...phone even boots up and works! (fortunately)...but no dice on it being recognized by my or any computer. Glancing into the port, it looks like there may be some corrosion on the left hand side of the port, or some sort of damage...can't really tell without a proper magnifying glass. but it does look damaged or at least irregular. I've been reading around, and cleaning sounds like a potential solution...I've no idea how you guys are cleaning with giant q-tips lol but hopefully I can figure that one out also and give it a whirl xD But in the mean time, I sure hope somebody can come to the rescue
I don't know if this can help you guys, but this is how i hard bricked my vibrant few months ago. I get into download mode trying to get back to stock from ICS and my computer didn't recognize my phone....after a couple of hours my phone was completely dead and after a few days of research i brought it back to life using the unbrickable mod. What i'm thinking now is to use the Unbrickable Resurrector but you will need Linux...it always worked for me but i'm not sure if you need the unbrickable mod already applied. However i think if you have Linux installed you can have a try. Here is the link for the unbrickable resurrector http://forum.xda-developers.com/showthread.php?p=17135277#post17135277
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying:
Before I explain my problem, let me first say that I am a novice when it comes to modifying phones. Shortly after buying my Razr, I knew that I wanted to root my phone, but I didn't know how. I found a program (that I can't recall now) rooted it, and had no problems. My problem came when I wanted to accept the OTA upgrade. I tried using Voodoo to keep my root while I accepted the OTA update, but that's where things when wrong. I don't know everything that went wrong because it seemed like nothing that I was doing was having any effect. It was having an effect, but not the effect that I wanted. After some uneducated decisions on my part, I found my Razr stuck in a bootloop. After trying to "fix" things, I gave up on it, but I decided to hold onto the phone. I replaced it with an HTC Rezound and moved on. I chose the Rezound only because it wouldn't take long to get it and it was affordable.
Last week, I decided that using the Rezound (it's definitely not all bad) has made me want to revive the Razr. I ordered BlackHat's adapter and used MattLGroff's utility (http://forum.xda-developers.com/showthread.php?t=2192467) to wipe my phone and flash JB.
This worked, with two exceptions. First, the phone still wouldn't charge. I came across a forum post that talked about successfully charging a phone in the car when it wouldn't charge inside with a computer or wall outlet. I was skeptical, but it worked. After charging the phone in the car, I can now charge it inside with a computer or wall outlet.
The second problem remains, and I am wondering if something that I did to soft-brick the phone caused a hardware problem. That seems unlikely, but I am new to this, so anything's possible as far as I'm concerned. In the attached picture, you can see that the bottom third of the screen shows up almost like static on a TV, but it's broken down into a grid. Also, the right half of the screen shifts up almost the height of the screen. Both of these problems come and go, but the "static" at the bottom of the screen comes much more often. I have to navigate through folders and menus before the shifting problem happens. Regardless, if I am at the home screen, for example, and I shift right or left (or navigate anywhere for that matter), the screen will be clean with no errors for a moment. After a second or so, the glitches usually show up.
I almost forgot about the last issue. When I wake the screen, it's quick and responsive; however, when I turn off the screen (by tapping on the power button), there is a lot of lag in the animation. Normally it would be a quick and smooth transition to the thin, horizontal line, and then it would quickly disappear. Now I can watch as it slowly blurs and stretches. It works, but it lags. This happens every time I turn off the screen.
Does anyone know what could cause this? Am I beyond repair? After typing this out, I doubt that it's a hardware problem, mainly because the static and shifting are not constant. But again, I'm totally new to this.
If anyone has any suggestions that involve utilities, then it would be ideal if I can use Linux. I have access to a Windows computer, but not at home.
Thanks in advance to anyone who can offer some insight.
Does anyone have any insight into this? Two months later and I'm still stumped. It doesn't matter how I use MattLGroff's utility...the same issues are still present. Could I maybe use a utility that will revert me to an older system? That way, I might be able to receive an OTA upgrade to JB.
I'm grateful for ANY input...
Thanks!
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
AztekSoul said:
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
neffje said:
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
Click to expand...
Click to collapse
hi,i had the same bug with rds lite didn't show me the spec of the phone,but only --------.
try anyway and remember to have the motorola driver in the pc (i don't know if works with wine,i had try only i my other windows pc)
This device is EOL I realize but I would like to root it. Problem is I can't get any pc's to even acknowledge it is plugged in. Can I get this thing rooted again without ADB???
My bootloader is unlocked from when I first got the device.
EDIT: So it was the USB port that was bad. Ordered a daughter board from E-Bay and now I have working ADB. I'm going to leave this thread open in case someone does figure out a way to get root without adb...
andyroidking said:
This device is EOL I realize but I would like to root it. Problem is I can't get any pc's to even acknowledge it is plugged in. Can I get this thing rooted again without ADB???
My bootloader is unlocked from when I first got the device.
Click to expand...
Click to collapse
If you can't get the drivers set up, try Wug's NRT toolkit. He has a walk-through on setting up/removing/reinstalling drivers. You don't need ADB to root, but you do need to boot into a custom recovery to install a root program (I use SuperSu). You can boot a recovery via CMD from fastboot as long as the recovery is in your adb/fastboot data folder.
FWIW, NRT can do all.
Sent from my Nexus 9 using Tapatalk
ritchea said:
If you can't get the drivers set up, try Wug's NRT toolkit. He has a walk-through on setting up/removing/reinstalling drivers. You don't need ADB to root, but you do need to boot into a custom recovery to install a root program (I use SuperSu). You can boot a recovery via CMD from fastboot as long as the recovery is in your adb/fastboot data folder.
FWIW, NRT can do all.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I'm really thinking it is my connector. Sometimes it doesn't even charge. I guess I could try to boot one of my pc's into a live Linux distro. I never had issues when I ran Arch. Actually I could try it on my server. It is an Odroid XU4 though but it runs Arch... Thanks.
Cables are most often the cause.
ritchea said:
Cables are most often the cause.
Click to expand...
Click to collapse
Linux doesn't recognize it either. I assume it is the port/cable. The original cable is long gone but I have many brand new Anker and other brands but none work for connecting... Guess I'm screwed. Really wanted root because I'm having issues with battery drain again and the screen not coming on. I wanted to get a custom kernel running... Oh well.
I use off-brand cable exclusively. Have you tried uninstalling all Android USB connections then allowing an auto re-install? I've had to do that with my N9 at times. A few times, the driver showed up in device hardware but nothing further (connection). I right-clicked and updated driver-just went through the process with no new driver just basically re-install. Once, it was the cable but all others worked.
ritchea said:
I use off-brand cable exclusively. Have you tried uninstalling all Android USB connections then allowing an auto re-install? I've had to do that with my N9 at times. A few times, the driver showed up in device hardware but nothing further (connection). I right-clicked and updated driver-just went through the process with no new driver just basically re-install. Once, it was the cable but all others worked.
Click to expand...
Click to collapse
I tried removing everything. It never even acknowledges it is even plugged in. I also tried on 1 brand new Windows system. Same deal. I did a live boot of Linux and nothing. I tried on my Odroid and nothing. I'm not new to this and have many PC's and other devices but none work.
Only thing I noticed is under developer options it comes up as ptp or mtp but if I try changing it I will always say charging no matter what I pick.... So I never even get a USB permission dialog...
As this isn't new territory, you know some cables don't have pin config for data transfer.
Are you able to get recognition of your device with ADB devices command?--recognized but unauthorized?
[C:\Program Files (x86)\Android\sdk\platform-tools>adb devices
List of devices attached
007667324ccb229b unauthorized]
ritchea said:
As this isn't new territory, you know some cables don't have pin config for data transfer. Have you done a factory reset? That may be the only way to get proper permissions for PC again.
Click to expand...
Click to collapse
Yup... And I'm doing it again now. This time both in Android then from the bootloader (pwr+dn).
Also apparently when I flash stock back on this a year ago for my son to use I never flashed the recovery image, or not correctly because there is no recovery at all. Just hboot... When I select recovery I get the dead Android..
I altered my previous response. Andy lying on his back is the stock recovery portal. You have to hold power button then push/release vol+. It can be tricky, but pretty sure that's the sequence. I'll flash stock recovery to double check if needed.
ritchea said:
I altered my previous response. Andy lying on his back is the stock recovery portal. You have to hold power button then push/release vol+. It can be tricky, but pretty sure that's the sequence. I'll flash stock recovery to double check if needed.
Click to expand...
Click to collapse
I have to go do some other stuff right now... I think he had the triangle exclamation in his chest though... I'll try some more later. Thanks!
When you have time https://youtu.be/DuuSTnbQSlM
ritchea said:
When you have time https://youtu.be/DuuSTnbQSlM
Click to expand...
Click to collapse
Doh! I'm so spoiled with rooted devices and twrp I forget you have to jump through hoops to get into some recoveries... So, I did the Android reset, Hboot reset and stock recovery hard reset. And no changes. Still only charges. Oh, well. Thanks again.
Quick update... Ordered a usb daughter board from e-bay. Last $10 I'll spend on this device...
andyroidking said:
Quick update... Ordered a usb daughter board from e-bay. Last $10 I'll spend on this device...
Click to expand...
Click to collapse
My USB started acting up on mine too. Watching a movie with a USB otg and it just stopped. I then discovered the only way for it to work was to jiggle it then hold it in a certain angle. I'm guessing something is loose. I haven't opened her up yet. I'd like to grab a new USB port for mine. Is it soldered to the daughterboard? Seems like changing the daughterboard will be easier.
madbat99 said:
My USB started acting up on mine too. Watching a movie with a USB otg and it just stopped. I then discovered the only way for it to work was to jiggle it then hold it in a certain angle. I'm guessing something is loose. I haven't opened her up yet. I'd like to grab a new USB port for mine. Is it soldered to the daughterboard? Seems like changing the daughterboard will be easier.
Click to expand...
Click to collapse
A few screws... I had to fix my camera because I pulled the back off wrong trying to disconnect the battery a while ago. Just gotta be careful. When the part comes in I'll update.
Video:
https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
eBay store:
http://www.ebay.com/itm/For-Google-...e=STRK:MEBIDX:IT&_trksid=p2057872.m2749.l2649
andyroidking said:
A few screws... I had to fix my camera because I pulled the back off wrong trying to disconnect the battery a while ago. Just gotta be careful. When the part comes in I'll update.
Video:
https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
eBay store:
http://www.ebay.com/itm/For-Google-...e=STRK:MEBIDX:IT&_trksid=p2057872.m2749.l2649
Click to expand...
Click to collapse
I looked it up and saw it. I noticed the rear camera was attached. Thanks for the info. I changed the screen on my n7 2013, but never thought to change the port on this one. D'oh.
@madbat99 @ritchea
Got the daughter board from China. About 25 minutes to install (I'm getting real good at taking this device apart now...lol). Powered up and connected to my Windows machine. And... It is recognized now! Can't believe I fought so long thinking it was a driver/windows issue.
After taking it out I can see why it would wear out/break. Cheap plastic and it has such a large opening on the outside my son probably tried all the time to plug it in wrong...
@ritchea thanks for your help!
@andyroidking,
I did nothing but super glad you were able to fix it!...and share it with the community.
andyroidking said:
@[email protected]
Got the daughter board from China. About 25 minutes to install (I'm getting real good at taking this device apart now...lol). Powered up and connected to my Windows machine. And... It is recognized now! Can't believe I fought so long thinking it was a driver/windows issue.
After taking it out I can see why it would wear out/break. Cheap plastic and it has such a large opening on the outside my son probably tried all the time to plug it in wrong...
@ritchea thanks for your help!
Click to expand...
Click to collapse
I ordered one from the link you provided. Coming from China so I hope it doesn't take too long. Can't wait. The port is waaaay to big, too much room to jiggle around. Hope this fixed my problem too.