First off let me state that I have looked through a majority if not all of the Amaze bricked threads and cannot seem to locate/understand fully the unbrick process. I have found what appears to be two different ways of unbricking the phone one was here http://forum.xda-developers.com/showthread.php?t=1668340 and the other here http://forum.xda-developers.com/showthread.php?t=1627882 .
I will state my problem with the phone. The phone is about 2 months old and had the stock rom installed on the phone. I sold the phone on ebay and the guy that bought the phone contacted me a day later and stated "I sold him a dead phone" which is clearly not true. This clown attempted to root the phone and ended up bricking the phone. He states that he never did such a thing and the phone would not charge or turn on. I had the guy send the phone back to me and sure enough the phone would not charge or turn on. However when I plug into my computer it attempts to search for drivers. I had the drivers installed on my computer due to it being my phone so I thought it was odd that it was searching for new ones. The problem lies that the driver it is searching for is ( qhsusb_dload ) which from me searching around appears to be caused from bricking the phone. Long end of the short ebay sided with the buyer and I am out the money and have a bricked phone even though the picture on the listing shows the phone working and having 3/4 battery life left.
What I have tried so far is what @tiki66 explained that helped him. I downloaded the amaze file (PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14.550L.17DC_30.78.550L.15_release_257469_signed.zip) from file factory and renamed it to the ( PH85IMG ). I also reformatted an 8gb sd card to the fat32 and put the file onto the sd card and put it in the phone. The phone still would not turn on or charge.
I also have tried @dexter93 way of unbricking. I have installed the version of linux that was required. My hang up is the second and third requirements being ( the appropriate package for the device and the latest RUU for your device ) I believe the RUU is the ruby file that I have downloaded. I have watched the youtube video about 5 times and attempted to link to the phone through the terminal however it stated that the program I was searching for was not there. It seems as soon as I get clarification on steps 2 or 3 would get me through to the phone.
Any and all help would be greatly appreciated. I apologize for the run on or rambling.
Thank you!
Peter
Does adb detect the phone? And does the phone boot into fastboot? If adb does detect it then try to push a recovery to it and see if it takes.
Double0EK said:
Does adb detect the phone? And does the phone boot into fastboot? If adb does detect it then try to push a recovery to it and see if it takes.
Click to expand...
Click to collapse
I cannot get the phone to do anything. I it may be possible that the battery is completely dead however I have left it on the wall charger for about 5 hours. I have seen a few time when I would hit the power button the screen flashes a very dull white for a split second.
I have tried the down volume button and power button about 100 times in the past 2 days.
That could be it. Some recoveries don't allow charging while off so if the guy did root it and put CWM recovery then it doesn't allow charging while off. Try to charge the battery externally or use a different battery.
Yes, it sounds like the guy probably flashed a recovery that can't charge while off.. the only way to get the phone to turn on until you can fix that issue is to charge it with an external charger of some sort.
Definitely not bricked, but as useful as a brick until you can charge it somehow..
Related
I posted a thread asking about resting my binary count to 0, i got a reply saying flash the zip via cwm then flash the stock rom and i wouldnt loose root so in which i did the first part and flashed the counter reset zip in cwm
the flash went through phone shut off and wont reboot??????
Ive tried a battery pull ive tried to get it into odin even plugged in charger no activity now at all, and the device was perfectly fine before this crap!!
If it won't power on at all you may he hard bricked. You can try a Jig but that may be hit or miss if you can't get it to work. You can do warrenty on it just say the phone shut off and won't power back on. I did this with my galaxy s2 I-777 when I hard bricked.
Edit: Just seen that you have insurance on it. I would just do a claim and get a new one.
Sent from my ICS powered Note
Ya i know thats an option but still wtf , its like when someone develops the hack to do such a task as resetting a binary count they should also have a explanation on why or what happens if it doesnt work.. If everyone does it the same way there shouldnt be an error, it just doesnt match up.
I had a perfectly fine working phone and did the flash as said to,, i shoulnbt have to go through a rediculous claim.
I had 90% battery charge ive donbe batt pull done the download mode method tried to plug it into pc and wall outlet
the odd thing is my pc recognizes the device like its in some state of recovery but the phones screen stays black
The pc says qhsusb dload when i plug in the phone to my laptop of course with the screen still black is that a good thing?
Does that qhsusb dload mean something
lojak29 said:
Ya i know thats an option but still wtf , its like when someone develops the hack to do such a task as resetting a binary count they should also have a explanation on why or what happens if it doesnt work.. If everyone does it the same way there shouldnt be an error, it just doesnt match up.
I had a perfectly fine working phone and did the flash as said to,, i shoulnbt have to go through a rediculous claim.
I had 90% battery charge ive donbe batt pull done the download mode method tried to plug it into pc and wall outlet
the odd thing is my pc recognizes the device like its in some state of recovery but the phones screen stays black
Click to expand...
Click to collapse
That is the risk of customizing your device. But if your computer still reads it you may still be OK. Buy a Jig or search YouTube on how to make one and see if that works. Also you can keep trying to put it into download mode and get Odin to see it. Worse case seniero you will have to do a claim on it. Sucks I know when I HB my s2 I was freaking out cussing and looked like a crazy person flipping off my phone lol
Grab a beer take a few and then try again
Sent from my ICS powered Note
That's one of the reasons I have not tried the counter reset hack yet. AFAIK it's only cosmetic and shows up when you enter download mode. From what I understand it doesn't affect the phone functionality anyway. Mine is up to 48 now. I guess i will see if I can make it to 100... it might reset after 99, hehe.
Thread closed
There is no need to open up two threads, keep all of your discussions in this thread.
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
dadrumajor said:
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
Click to expand...
Click to collapse
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
FinZ28 said:
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks! What exactly would a JTAG do? I did some research but couldn't find a good answer. Is there an advantage to that over just bringing it to Sprint to replace it, or do you think they might not take it?
EDIT: I went through my research again; I guess I just didn't understand it the first time. So, a JTAG can access and write to any memory on the phone, especially the memory that is now unavailable due to messing up the low-level boot software?
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
iconoclastnet said:
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
Click to expand...
Click to collapse
Just an update - I went to Sprint, and they agreed to replace the phone...waiting on it at the time of writing, but I will be starting from scratch. I plan to unlock the bootloader and root but not try for S-OFF as TWRP does have a way around it...and I WILL be staying away from ParanoidAndroid, although I love their ROM. Too bad...I just don't want another paperweight on my hands!
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
dadrumajor said:
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
Click to expand...
Click to collapse
Sorry for the delayed response, I was out of town for a couple of weeks and didn't notice your reply until now. Anyway, just for the record...
The notification led was indicating that the battery was about to run out (yes, I set a custom notification color for very low battery). It appeared to finally give up and shut off just moments before I reached the charger. So, I plugged it in and let it charge over night like usual, except the next morning it wouldn't turn on or respond to anything. At first I thought that the battery might not have charged for some reason, so I switched to a wireless charger because it has a charging/full indicator led on the charger itself, and confirmed a fully charged battery. Plugging it into the computer revealed the QHSUB_DLOAD / QDL mode status. I still haven't been able to get it out of that mode. At this point I'm really more interested in recovering the data from it than whether or not the hardware works normally anymore.
As for Paranoid Android, I've been using it successfully on a couple of other devices (both before and since the brick incident) and haven't had any problems with it, so it may be a complete coincidence. I'm at a loss for a good explanation though.
The issue was with TRIM not being removed from some early 4.3 ROM builds, which caused the bricks. It was discussed in some of the ROM threads. Had nothing to do with whether a phone was S-on or S-off.
Sent from my HTC EVO 4G LTE
Hey guys, im a regular over on the htc forums but not very used to samsungs and was wondering if i could get some clarification
Got this tablet from a friend to repair if i could. the tablet was in possession of my friends mother who is 60+ and careful with her tech. never drops it, always charges it on time. then device was never flashed or rooted in any way. It was handed to me already in apx mode and the back story was simply it wouldnt turn on any more. i asked if it was powered off while updating, or fully discharged or anything but was told no. it was just placed onto the charge when she went to bed and was non functional in the morning. as stated the device is in apx mode, i looked into it and the bootloader is locked so NVFlash is non functional. i have been trying the battery drain method but ive had the power button taped down for 3-4 days now with an otg cable plugged in and other stuff like pen drives etc connected to it to try drain the power to no avail. i got impatient and i tried the disconnect and reconnect the battery method (as the op stated that the battery drain and the battery pull method should have the same effect), but to no avail.
Im beginning to think that its seen its last days as the battery pull method has consistently failed, and i cannot seem to find a j-tag method anywhere.
so, am i correct in thinking that its just spare parts now? device has been OOW for quite a while now and given that the battery was fully charged prior to me obtaining it, it could take weeks to discharge.
If anyone with experience on this issue could chip in that would be great! cheers!
H.M.M
Simular issue, any fix yet
heavy_metal_man said:
Hey guys, im a regular over on the htc forums but not very used to samsungs and was wondering if i could get some clarification
Got this tablet from a friend to repair if i could. the tablet was in possession of my friends mother who is 60+ and careful with her tech. never drops it, always charges it on time. then device was never flashed or rooted in any way. It was handed to me already in apx mode and the back story was simply it wouldnt turn on any more. i asked if it was powered off while updating, or fully discharged or anything but was told no. it was just placed onto the charge when she went to bed and was non functional in the morning. as stated the device is in apx mode, i looked into it and the bootloader is locked so NVFlash is non functional. i have been trying the battery drain method but ive had the power button taped down for 3-4 days now with an otg cable plugged in and other stuff like pen drives etc connected to it to try drain the power to no avail. i got impatient and i tried the disconnect and reconnect the battery method (as the op stated that the battery drain and the battery pull method should have the same effect), but to no avail.
Im beginning to think that its seen its last days as the battery pull method has consistently failed, and i cannot seem to find a j-tag method anywhere.
so, am i correct in thinking that its just spare parts now? device has been OOW for quite a while now and given that the battery was fully charged prior to me obtaining it, it could take weeks to discharge.
If anyone with experience on this issue could chip in that would be great! cheers!
H.M.M
Click to expand...
Click to collapse
My P7510 is acting like it is bricked. It will not start. I tried the power button and volume combination and nothing works. I connect to my Windows 8 PC only see it in Device manager as "Other Device" as a APX without the drivers loaded. I have charged the device for hours on two different chargers.
It had 50% charge when my nephew was playing Angry Bird and he returned it in what I thought was just sleep mode. I tried turning it on 4 hours after I got it back and it would not come on. I figured the battery was dead so I charged it but to no avail.
It is not rooted and has the stock 4.0.4 Android version.
I cannot ask my nephew what he did because he is autistic and would be scared to deaf it he though he broke my tablet.
Any help is appreciated.
datastar said:
My P7510 is acting like it is bricked. It will not start. I tried the power button and volume combination and nothing works. I connect to my Windows 8 PC only see it in Device manager as "Other Device" as a APX without the drivers loaded. I have charged the device for hours on two different chargers.
It had 50% charge when my nephew was playing Angry Bird and he returned it in what I thought was just sleep mode. I tried turning it on 4 hours after I got it back and it would not come on. I figured the battery was dead so I charged it but to no avail.
It is not rooted and has the stock 4.0.4 Android version.
I cannot ask my nephew what he did because he is autistic and would be scared to deaf it he though he broke my tablet.
Any help is appreciated.
Click to expand...
Click to collapse
ive not had any luck, no one else has replied and nothing i have tried has helped.
heavy_metal_man said:
ive not had any luck, no one else has replied and nothing i have tried has helped.
Click to expand...
Click to collapse
I found another thread about removing back cover and disconnecting the battery for ten minutes. It worked for me http://forum.xda-developers.com/showthread.php?p=47342233#post47342233
thanks but ive tried that already no joy.
heavy_metal_man said:
Hey guys, im a regular over on the htc forums but not very used to samsungs and was wondering if i could get some clarification
Got this tablet from a friend to repair if i could. the tablet was in possession of my friends mother who is 60+ and careful with her tech. never drops it, always charges it on time. then device was never flashed or rooted in any way. It was handed to me already in apx mode and the back story was simply it wouldnt turn on any more. i asked if it was powered off while updating, or fully discharged or anything but was told no. it was just placed onto the charge when she went to bed and was non functional in the morning. as stated the device is in apx mode, i looked into it and the bootloader is locked so NVFlash is non functional. i have been trying the battery drain method but ive had the power button taped down for 3-4 days now with an otg cable plugged in and other stuff like pen drives etc connected to it to try drain the power to no avail. i got impatient and i tried the disconnect and reconnect the battery method (as the op stated that the battery drain and the battery pull method should have the same effect), but to no avail.
Im beginning to think that its seen its last days as the battery pull method has consistently failed, and i cannot seem to find a j-tag method anywhere.
so, am i correct in thinking that its just spare parts now? device has been OOW for quite a while now and given that the battery was fully charged prior to me obtaining it, it could take weeks to discharge.
If anyone with experience on this issue could chip in that would be great! cheers!
H.M.M
Click to expand...
Click to collapse
I think the reason nobody has replied because it looks like you did your homework and tried everything that would have been suggested. Unfortunately the battery disconnect is the last resort if it's not hardware. If it was software issues the battery disconnect should have worked AFAIK.
I had to send mine (GT-P7510) in for repair when it went into apx mode. Fortunately for me it was under warranty.
Just a thought, but have you left the battery disconnected for a day or more? Wondering if the tab is holding a charge some way with the battery not connected. Maybe connect something with the battery disconnected to drain all possible remaining charge from the tab. For a day or more even. I've seen stranger things happen even a few who where they said it just started working out of the blue. Not likely to help but might be worth a try.
EDIT-Just had another thought I remember one tab I fixed that was stuck in apx mode and removing the battery didn't help. I diconnected the battery and plugged into the charger held the power button and it booted. I let it do a full start before connecting the battery.
Can't remember for sure, but I may have held power+volume down. Could be worth a shot.
Sent from my GT-P5210 using XDA Premium HD app
Hello Everyone,
I may have done the stupidest thing ever. I was attempting to partition my sd card using an app I found in the play store (don't remember which at the moment), Well i believe that i may have messed up and accidentally deleted the HBOOT partition. the phone continued to run fine but then when i restarted the phone never came back on. the phone does absolutely nothing, no lights no vibrations no charging indicator nothing. I have been at this for 3 days now and i think i am about to give up. Any one out there have any advice. I have found the unbricking thread but they all specify its for S-ON only and i am S-OFF when i plug it into the computer is is recognized as QHSUSB_DLOAD although the drivers dont load. I found some drivers online but that did nothing.
I too might have this problem. I'm not sure because it has been well over a year since the incident and I have moved on. My evo, when connected to a charger, flashes a red light for about a minute and then does nothing. It will not pull up a charging logo and will not boot. The battery is completely dead. I know I used to be able to access recovery on the device but the original sd card is gone. Would this mean if I got the battery charged somehow that the phone would still be bricked? When I plug it into a computer is says htc_shooter. The phone is s-off and i dont remember the hboot it had or firmware version. If anyone has advice for me that would be wonderful, however if my phone is forever a brick then no big deal.
Mr_JacobClutch said:
I too might have this problem. I'm not sure because it has been well over a year since the incident and I have moved on. My evo, when connected to a charger, flashes a red light for about a minute and then does nothing. It will not pull up a charging logo and will not boot. The battery is completely dead. I know I used to be able to access recovery on the device but the original sd card is gone. Would this mean if I got the battery charged somehow that the phone would still be bricked? When I plug it into a computer is says htc_shooter. The phone is s-off and i dont remember the hboot it had or firmware version. If anyone has advice for me that would be wonderful, however if my phone is forever a brick then no big deal.
Click to expand...
Click to collapse
When I had this problem it was due to my battery having run down so much and not being able to draw a charge. If you have a spare battery try swapping that in and see if it makes a difference.
If you don't have a spare you can try what I did which is to take out your battery and put it in airtight bag and place it in the freezer overnight. Put the battery back in and try to power it back on in the morning.
When I first read this I thought it was crazy but I thought what the hell and incredibly it worked. Something to do with the low temp allowing the battery to draw enough to charge. Of course you could have an altogether different issue and I would only try it if you have nothing to lose.
Hey all, I got my phone into a serious problem this time... And myself too
I don't know what happened but I just plugged my phone in, started charging... , no I didn't leave it all day, when it was charged but I found out that it didn't charge further than 75%
I waited 10 minutes, still nothing.
I unplugged, showed that it was charging, I thought it may be lag and rebooted the phone.
Nothing, still same, I plugged my OTG cable in and weirdly it fixed itself but after pulling it out it got back to "charging"...
After a few tries it did the same on the OTG cable, I tried cleaning the USB input thingy on the phone but nothing...
Now I'm forced to stay at the wall plug because the phone lasts seconds thinking it's charging since we know that it runs full-speed.
I tried getting into recovery but... Well, I powered off the phone, managed to get to fast boot and it showed "hboot searching sad card for updates" or something like that! it takes long so I powered it off again and it started itself up without touching, I assume that's because it thinks it's charging.
Can I do something to get that phone back to life or is it time for a new one?
Anyone getting this problem too? Or did anyone have it and fixed it? Please tell me how
Sad to hear this. Have you tried any other chargers?
/\/\ said:
Sad to hear this. Have you tried any other chargers?
Click to expand...
Click to collapse
I tried 3 different chargers each with 3 different cables, an apple charger, some belkin charger and another charger with 700mA
my dad fixed it somehow until it went empty and had to replug the charger, it fixes itself below 10 and above 20 prcent it goes back weird
Well, things going totally insane now, I wanted to format the internal SD and flash a rom with sideload.
Went recovery, wiped everything, started sideload... Computer gave an error, I think it was something with timeout or something idk anymore...
Tried it 20+ times! all same
So I went to install stock recovery, installed it too, everything passed, then locked boot loader with fastboot oem lock, succeeded too, but it showed security warning, but I just went on and installed the European RUU, which failed due to code 158 image error...
Redownloaded that RUU, same thing...
Downloaded others, ran each for 1.5+ hour! but it seemed to take hours instead 20 minutes so i lost hope, I still am able to unlock boot loader,install recovery and stuff but unable to get a rom on it, can anyone at least tell me how to maybe flash ROM through USB OTG? I know that works, right before my phone died I used a PC mouse on it...
I need to fix this phone and sell it quickly, support is dropped also so that's the best idea, I cannot afford to give this phone for maybe 10 euro so I really have to get this fixed.
I got patience until mid-October because the OPO comin out probably, anyway I'm waiting for ANY suggestions to get a rom on it, may be stock, custom idc, I just need it working because I found out that the USB charging problem is hardware, not software, my phone still won't turn off
Thanks in advance -ozi
So guys, today I got a bit upset and disappointed because of the loss I almost made, yeah, almost.
Because I sorted out how to get the phone back to life when this issue happens.
Well, it all started with a full memory, yeah I had 5/64GB free space left.
And my phone got the bug/hardware fail then too, I still don't know what it is, but that isn't fixed yet.
I thought like "what can go wrong if I just try to put my phone to all ZERO".
So without even stopping for a second and thinking what can make a problem, I formatted the whole phone.
I knew I was going to use ADB Sideload but not that it was going to take 3 days.
So I went to Sideload (PhilZ recovery) and while side loading the stuff, it got stuck, approximately 30 percent where it stopped working.
The error was something with protocol if I remember correctly since I'm not having this issue anymore.
This happened maybe 20 times, yes, I was freaking out at the command prompt trying to figure out why it didn't work.
Anyway then after hours of searching my brain reminded me of the ADB Push command I once read somewhere... And immediately researched for it, how to use it and such...
Then I rebooted recovery, did ADB push rom.zip /sdcard ... FAILED
Why did it fail, well, I didn't know...
Got very disappointed this time and went to what I was doing: searching on Google, xda...
Took over a day, to be honest, really, I must say I posted this WAY too early, because I could've searched first.
You know, school, laziness, sleepiness and such.
But back to the point. I've finally found some old files sitting there, taking their space in my HDD, they were These files.
(Download them if you want to fix your phone too.)
I opened it, TOTALLY forgot about it, not even remembering it was there...
I saw flash TWRP recovery and flashed it, since I had no adb connection, the first one failed but then fastboot opened, and my device was at fastboot at that moment, knowing that you need fastboot to flash a recovery.
SUCCEEDED, even if I knew that it was going to succeed, I was happy because it was one of the first things which succeeded .
So I opened recovery, and went to advanced - ADB Sideload
I tried everything again, and this time uninstalled htc sync manager (not the drivers).
It took long, just about 30minutes to transfer a 980MB file, MagioROM...
But at least it WORKED, now I got a working ROM.
Now about the USB issue, I'm going to look further into that, I'll change the title to "ROM and USB Charging issue".
Tho I really think it's just the hardware. And I'll update this when I get some further.
And to the fast-panicing people amongst us (including me), do research and don't give up. This way you will less likely have an expensive brick
So today I went on and opened up my phone, I got nothing better to do anyway, it was still thinking that it's charging, but I made sure it weren't the pogo pins by cleaning them and checking the cables...
It was an USB connector problem, when I touched it a bit with a screwdriver, it went back normal and when I plugged it in it got messed up again.
So the people who got this problem: go warranty before it's too late or do it yourself by buying parts and replacing them, I must say, one x+ was one of the worst jobs to open up a phone tho lol