Related
Dear Folks at XDA,
I would like to ask for you help with my HTC Touch Pro 2. I recently tried to update it to the new AthineOS CHome TF3D WM6.5 Manila ROM v 1.0 and unfortunately I failed.
The problem is that my phone now freezes at the black startup screen with the Touch Pro 2 logo and the red codes at the bottom.
I've flashed the ROM several times before and never got this issue.
Due to the fact that the phone doesn't finish the boot-up and I thus I can't get ActiveSync I'm afraid I messed up my phone for ever.
Please someone tell me I got a way out of this, I'd appreciate it very much.
Greetz,
SjonSjon
umm.... I don't think you can change the firmware just yet on the CDMA version of the phone... if you used a HardSPL that's available in the Rhodium forums then you probably used a GSM specific ROM on your CDMA phone... not sure what to tell you other than making sure you read the CDMA forum before trying something so risky. Best solution, unless someone knows how fix your phone in it's current state, is to toss it under your car and run it over and try to cash in on the insurance.
Problem solved!
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
I am glad you have recovered the beautiful device; and thanks for sharing a working solution.
sjonsjon said:
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
Click to expand...
Click to collapse
Good job!
big thanks for solution.
You just saved my life!!!
Don't get our hopes up! This is the wrong forum. CDMA TP2s can't be flashed at all yet.
This was a life saver post so a quick bump for anyone that needs it.
I unlocked my CDMA phone, installed a few roms -- decided to go back to my stock rom default (which was Telus) -- reinstalled and bam -- bricked.
Well, technically it's not a brick if you can get back into the bootloader to reflash. So no worries everyone. If everyone reads instructions well enough we should hopefully see zero "real" bricks. Or at most, just enough to only build bbq pit rather than a house.
I think my phone is truly bricked
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
my cdma is rebooting endlessley i reflashed stock rom and evorything. it seriously dosnt want to work. its most sadness... i am cashing in on the insurence. but they are going to send me a refurb..
spend 600$ on a phone got inurnce i hope the used one dosnt fail me.
Esazi said:
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
Click to expand...
Click to collapse
I did the same exact thing to mt TP2. Same outcome.
We have to learn somehow....
That stinks man. If you did, then your phone is truly bricked. You are going to have to get a replacement or switch to another phone because there is nothing you can do to get it going again. I tried everything possible and eventually just ordered a replacement. I have it now and it's working beautifully, but needless to say I am a little scared away from any more unlocking or flashing for a while.
If you read carefully you dont have to be scared of flashing
I was a noob some time ago but before doing anything I took care of reading and understanding before doing nothing.
lesson learned
By now I have flashed more than 60 times on 3 diferent HTC devices and all were a succes
Hope you get your TP2 working again!
I hope I can get there
Someday I hope to be a flashing expert, but until then I will take it slow and read carefully. Thanks for your encouragement. When I actually get money to pay for the unlock for my TP2, I will let you know how flashing goes.
How do you keep the phone in bootloader? Mine goes right to the press volume instuction screen. Other than that I'm stuck on the black name screen,also my usb will not register in device manager. This was my first try at flashing.
gadgetgirl28 said:
You just saved my life!!!
Click to expand...
Click to collapse
Holy hell, you're not lying. Thanks for coming back to post your solution!
This post saved me at least a few hours of frustration and ever worsening decision making.
So it's totally true???
this situation hasn't solution;
I was unlocking my phone (the HTC Touch Pro 2 <SPRINT>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, AND PLEASE somebody tell me , that it can be save it
;9
please help
i have the same problem. is there a way to save my phone?
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Well if your PC is not recognizing the phone, then there's not much you can try I guess (other then factory reset.) Maybe someone is gonna come up with something.
Aren't the gamesaves on your sd card?
There have been hardware issues associated with multiple downloads from the market and pulling the battery. This might or might not be the case. However you are covered with warranty in case it is.
Sent from my HTC Desire S using XDA App
esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
If she created a HTC Sense account and had set it up to sync then her texts would have been saved online.
If no other options download the corresponding to your region RUU (ROM Update Utility) from here. Then reboot to Bootloader (VOL DOWN + POWER Button). Make sure that you have HTC Sync installed. Go to fastboot screen (you should see FASTBOOT USB line). Start RUU.exe. It will handle everything automatically and hopefully you will have a brand new Stock system again.
If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!
olyloh6696 said:
If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!
Click to expand...
Click to collapse
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.
An boot loop isn't
an real indicator for fried emmc, most of the times you just somehow messed up part of the software or the partitions, this:
http://forum.xda-developers.com/showthread.php?t=1292730 it's an really fried emmc.
Let's try some solutions before destroying any hope!
Swyped from my Desire S
amidabuddha said:
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.
Click to expand...
Click to collapse
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium
esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
so, have you tried hard reset/factory reset. let us know what happen than. next time never pull out battery when your phone freeze. just press vol up + vol down + power button (all three hardware button) and the phone will restart. I personally had this problem few times and able to recover my device. start with hard reset your phone.
look at ben_pyett signature. you need the adb+fastboot and htc drivers for your windows pc to detect your device. I'm using linux and I don't need those drivers.
olyloh6696 said:
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.
Update: thanks for all the suggestions. I couldn't get any of it to work, including factory reset.
We are going to send the phone in for a warranty repair, most of her personal stuff is on her Google account or the SD card, so no major problems.
The HTC Sense website with SMS backup never worked for her, there is no option to log in from the phone.
As much as i love Android I am shocked that hitting "update all" in the market and/or pulling the battery can brick a 400 $ phone. Even buggy old Windows ME was fine if you pulled the pover cord.
My iPhone friends will laugh at me well into 2012 if I tell them this.
Do HTC have more faults than other brands? Both our Desires have had trouble. I am about to upgrade mine, maybe should look at another brand?
There is some hope!
amidabuddha said:
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.
Click to expand...
Click to collapse
+1
I'm afraid that I must agree.
In the early days of this problem, I too was probably guilty of announcing too early to users "that's you've fried your eMMC chip - that's a warranty return" where as over time we've now come to believe that this still a chance of hope, albeit not great or guaranteed, but none the less, fortunately several people have managed to recover from this situation, by a variety of means.
So even though the possible outcome might not be likely, I think that we should attempt to always suggest that there might be hope at least until we've tried all the possible solutions and now luckily the various users have compiled guides of the suggested options so this isn't that difficult.
The only time when I'd suggest that a user should probably instantly return a device, is if they are completely non technical or have a brand new device which is still S-ON. In which case they may as well return the device under warranty and get a replacement device or motherboard which will at least contain the non dubious/faulty chip, and will remove the possibility of future occurrence completely - so they'll actually be better off for the future!
esbenm said:
Update: thanks for all the suggestions.
Click to expand...
Click to collapse
Sorry to hear this. You were just unfortunate and what happened to you is rare, also it's not a fault of Android but, a HTC eMMC chip hardware issue caused by a particular dodgy version of the eMMC chip that comes on some of these phones.
I believe that HTC realised the fault and replaced the chip with another make after a fashion. So hopefully you'll get the different chip on your replacement device/motherboard.
I also think that they've changed the market application so that it downloads one application after rather than all the applications together, which was known to cause a device freeze, which often was followed by a battery user battery pull - which then led to this problem.
Next time... Never pull the battery! there are always other options.
Take care and good luck.
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
All right, 1st of all let me apologize if I'm creating a thread to which one or more already exist. Now, a brief breakdown of the situation I am, or rather, put my self in. A couple of months ago, I bought my HTC from someone. It was locked to Rogers ( Canadian HTC ONE ), and I decided to unlock it, because well, I wanted to. Everything was fine and dandy until I finally lost my $#!t when HTC failed to release the update it promised. So I decided to root my phone and install a custom rom into in. Also, I was not a big fan on Blinkfeed. I choose cynogenmod and was happy with it until a few months later, I realized that if I let the phone die completely, It would take 3 days ( YES.... 3 F%^$*NG DAYS ) for it to boot back up. I figure its a defect. Read about other with the same problem. Anywho, I thought if I updated to the latest firmware, It would fix the bugs and glitches the phone had before. Long behold, GAPS was not natively installed on the latest update and I went ape ****. The very retard me, freaked out and tried to downgrade to the old software and it made it worse. Long story short, I went into clockworkmod, factory reseted, erased cache and a whole bunch of other $#!t that basically sealed the lid for my HTC one. Now when I try and boot my phone up ,It goes through a never ending cycle of booting, then shutting down, rebooting into recovery, shutting down, rebooting, shutting down, rebooting into recovery etc etc etc... You get the jist of it im hoping. And if i plug it into the computer, It says " USB device is not recognized or has malfunction". What to do Ooooooo what to do guys???? Any help will be appreciated. Pls and thanks,
Last week it started and I was able to fix it but with a different stock rom. I also couldn't restart it or else it would go back into the loop. It is a Metro PCS G930T. I had to flash it with T-Mobile firmware as the only Metro firmware was for the G930T1. Now I downloaded that G930T1 firmware, but I'm not sure if I would be able to do it as it is a different model. I just don't like the UI of the T-Mobile one and want my old one back. This is only the second time it restarted by itself since the first boot loop but this time it's stuck again. I really don't want to have to wipe data every single week. Even though most of my stuff is synced I still have to go through settings every time and set it up again. I don't know how Samsung gets away with this either. They purposely engineer their products to stop working after 1-2 years. Straight up consumer fraud especially when they refuse to fix it while still under warranty.
Do you have solid proof of this allegations?
what are you talking about? I am just trying to get advice on what to do, not get into an ethical debate.
You said: consumer fraud.
That's asking for help?
Stick to the point.
yes. stick to the point. stick to answering the main question. don't mind the rant if you don't understand it.
Are you an Apple fan boy?
Edit what you said about Samsung, and I'll answer you.
And go drink your milk and go to sleep. You must be a ten-year-old.
You come here to seek help, not to rant.
Rant in your own home.
Are you using any sd card? I had a bootloop issue due to corrupted sd and when i ejected it and reboot phone worked like nothing had ever happened