Related
ok so i got a big problem my mogul is stuck at the supposed ''bootloader''.
i tried running a couple of diffrent things to try and fix it becuase i read somewhere that the phone is ''bricked'' but i dont know
my screen has red,blue,green and a white bar
in the red bar it says
TITA100
SPL-2.07.0000
CPLD-9
this has been f'd up for 4 days now,and neither htc or sprint knows whats wrong
and also my mogul wont connect via usb (but my razr will so cord and computer are both alright)
it happened while i was listening to audio manager,the sound cut out and wouldnt work so i tried to reset upon reseting i got here
i have tried to hard reset and the phone just goes back to the same spot
i have also tried renaming the ruu_signed.nbh (from the sprint official rom) to TITAIMG.nbh and it installs successfully but still goes to bootloader (even tried the ollie unlocker or whatever)
PLEASE HELP ME OUT GUYS!!!
have you tried just installing a new rom?
yes it installs successfully (when i load it from phone,not from my computer) but then it still goes straight to bootloader
wait, you were installing a rom from the storage card? and if so i would probably trying installing from an actual computer and see what happens
jbearamus said:
wait, you were installing a rom from the storage card? and if so i would probably trying installing from an actual computer and see what happens
Click to expand...
Click to collapse
did you not read my original post??
i said my mogul wont connect detect the usb for some reason,and it only did it after it went into the bootloader mode
Silly question, but have you tried pulling the battery? How about the exit bootloader program? I have never used the exitbl program, but there are instructions on how to do it around here somewhere...
TRY THIS
so i fixed the phone myself messing around with it
(no thanks to you so called ''pros'')
but still my charger/usb port wont work and my battery has 6% left lol
im gonna call htc right now and see what to do
So, care to explain what you did to "fix" it so when people search for this problem they might get an answer instead of posting a common question in a thread?
i pressed the camera camera by accident when i was pressing reset and it took me to the htc screen where its shows your radio version and rom version and everything.
it said ''no radio'',so i pulled the battery and put my memory card with the newest sprint rom (the file i used from the sprint rom was the RUU_signed.nbh,i named it to TITAMG.nbh)then i manually put the phone back into booloader by pressing power and camera key at the same time.
the rom loaded up and installed,then when it was finished i pulled the battery.
to turn the phone on i pressed the camera button,then the reset button both at the same time.then the phone loaded up and went through all the ''welcome to windows mobile'' garbage. there you go,thats exactly what i did.
but now my charger port wont work
punkrocker12201 said:
i pressed the camera camera by accident when i was pressing reset and it took me to the htc screen where its shows your radio version and rom version and everything.
it said ''no radio'',so i pulled the battery and put my memory card with the newest sprint rom (the file i used from the sprint rom was the RUU_signed.nbh,i named it to TITAMG.nbh)then i manually put the phone back into booloader by pressing power and camera key at the same time.
the rom loaded up and installed,then when it was finished i pulled the battery.
to turn the phone on i pressed the camera button,then the reset button both at the same time.then the phone loaded up and went through all the ''welcome to windows mobile'' garbage. there you go,thats exactly what i did.
but now my charger port wont work
Click to expand...
Click to collapse
I did see some threads on a different site I think about the USB port having some issues with the pins getting pushed back up into the back of the port and not making a connection any more. This kind of sounds like your problem as you said that your computer doesn't recognize the phone either. Some people were able to straighten the pins back down and use it again, some the pins broke so good luck if this is the case.
jambrose said:
I did see some threads on a different site I think about the USB port having some issues with the pins getting pushed back up into the back of the port and not making a connection any more. This kind of sounds like your problem as you said that your computer doesn't recognize the phone either. Some people were able to straighten the pins back down and use it again, some the pins broke so good luck if this is the case.
Click to expand...
Click to collapse
ya there was one pin pushed down and i actually thought at first when i looked in the charger then in the phones mini usb port. that the pin was broken off but it was just smashed down
so now i have my phone back (besides this cheap a$$ lg)
punkrocker12201 said:
ya there was one pin pushed down and i actually thought at first when i looked in the charger then in the phones mini usb port. that the pin was broken off but it was just smashed down
so now i have my phone back (besides this cheap a$$ lg)
Click to expand...
Click to collapse
So maybe you owe us "pros" an apology
punkrocker12201 said:
so i fixed the phone myself messing around with it
(no thanks to you so called ''pros'')
Click to expand...
Click to collapse
SORRY
lol
When I picked it up it would only boot to a screen with a triangle with an exclamation mark in it and it says Software Update Failed! Please try again. He said he was trying to load Android but didn't know what he was doing and every time he pulls the battery that's as far as it gets. I figured for $20 maybe I can get it into bootloader and do something with it. I got it home and did a battery pull, put it back in and held the power button and volume down and nothing. Now it won't even turn on at all. When I picked it up he did a battery pull and turned it on to the Software Failed screen but now nothing. I've left the battery out for an hour, had it plugged in to 2 different wall chargers and every USB port on my computer and nothing. I even stripped a USB cable and held the wires to the + - terminals on the battery for 15 minutes and nothing. I'm hoping the battery is just shot or not taking any charge and a new one might at least get me to the bootloader.
I suggest you make a Gold Card to flash it with. This is like the one almost assured flash of Windows Mobile to your HD2. a Gold Card will force a flash sometimes. If you do not know what a Gold Card is just Google Gold Card for HTC HD2.
If you can flash Windows Mobile back to the HD2 you can then try Android again on it if you want.
jmac1968 said:
When I picked it up it would only boot to a screen with a triangle with an exclamation mark in it and it says Software Update Failed! Please try again. He said he was trying to load Android but didn't know what he was doing and every time he pulls the battery that's as far as it gets. I figured for $20 maybe I can get it into bootloader and do something with it. I got it home and did a battery pull, put it back in and held the power button and volume down and nothing. Now it won't even turn on at all. When I picked it up he did a battery pull and turned it on to the Software Failed screen but now nothing. I've left the battery out for an hour, had it plugged in to 2 different wall chargers and every USB port on my computer and nothing. I even stripped a USB cable and held the wires to the + - terminals on the battery for 15 minutes and nothing. I'm hoping the battery is just shot or not taking any charge and a new one might at least get me to the bootloader.
Click to expand...
Click to collapse
20$ !!! HOW ?????
Ill Buy it from you as is for $50 Australian dollars plus postage. The Australian dollar is worth like 50 gadjillion US dollars at the moment so its a great deal for both of us.
hungry81 said:
Ill Buy it from you as is for $50 Australian dollars plus postage. The Australian dollar is worth like 50 gadjillion US dollars at the moment so its a great deal for both of us.
Click to expand...
Click to collapse
to your surprise 50AUD = 53.48USD
backlashsid said:
20$ !!! HOW ?????
Click to expand...
Click to collapse
Because at the moment it's a $20 paperweight. Black screen, no charging light, won't even go to the software failed screen. I don't know anyone else with another HD2 I can use to check the battery or to use to charge it if it is dead. If worse comes to worse I'll send it off to HTC.
T-Macgnolia said:
I suggest you make a Gold Card to flash it with. This is like the one almost assured flash of Windows Mobile to your HD2. a Gold Card will force a flash sometimes. If you do not know what a Gold Card is just Google Gold Card for HTC HD2.
If you can flash Windows Mobile back to the HD2 you can then try Android again on it if you want.
Click to expand...
Click to collapse
I read the tutorial a couple times and I'm guessing the phone would have to have power to do this. This puppy is dead at the moment. For all I know it was Raptured during the night.
check the battery pins carefully for bent pins, and also, just to check, when you did the bare usb cable charging, you put neg to neg, live to live, right?(black to - red to +, , + being the outer one)
Id probably try a phone shop, see if they'l let you put a battery in for a few seconds, just to confirm if its the battery that has died, and if theyre really nice maybe theyl let you try your battery in their hd2.
If it IS the battery and you get it working, its dead simple, no goldcard or anything like that needed,, , the exclamation screen you got is from flashing an incorrect (wrong carrier/region) stock rom via sd card whilst hspl was installed, (its been removed now, by the start of teh sd card flash, thats why it gave rom update fail) and simply entering bootloader and reflashing using a rom correct for your serial will fix that.
(or indeed entering bootloader, applying hspl then flashing your chosen cooked rom and radio, , , or radio and magldr, whatever you want to do. Its a scary screen the exclamation one, but its one of the easiest to get past)
Yeah a phone shop is probably a good idea. There's a T-Mobile pretty close. I had an HD2 I sold last year that I had put some different ROMs on and Android so I figured if this one was stuck at the software failed screen it would be a pretty easy fix. I used it in the Yucatan for the GSM signal plus it doubles as a pretty good camera and bought this one because I'm going back. But reading the threads about it just being dead and not booting to anything makes me think it might be trashed. If it is I'm only out $20. If it's to pricey for HTC to fix it there are a couple on craigslist cheap with broken LCD's. Might try piecing 2 together.
unfortunately looks like you've bricked the unit, you can actually resurect it by using JTAG software/hardware http://www.youtube.com/watch?v=XroEPU4qyuM
rudy173 said:
unfortunately looks like you've bricked the unit, you can actually resurect it by using JTAG software/hardware http://www.youtube.com/watch?v=XroEPU4qyuM
Click to expand...
Click to collapse
That's what I was thinking. But I didn't do it, all I did was pull the battery. If it is it's only $20
Its not the famous tmous radio brick, unless you didnt mention something you did in your first post.
the only way it gets that kind of brick is flashing a radio from a regular HD2, the fact that the flash failed (exclamation screen) and you say you didnt try to flash anything else would point to a different problem. If the radio HAD flashed, the phone wouldnt have booted even to the excl screen.
You see, when you flash a stock rom via sd card, if hspl is installed it will allow the flash to start, but step 1 is first changing the spl(removing hspl) then the phone restarts into the new spl, and flashing continues. But because hspl is no longer there, cid checks fail and the flashing stops, so no radio gets flashed, so no radio brick.
radio bricks happen when you flash a non tmous stock rom via Goldcard or via usb whilst hspl is installed, because over USB, hspl is NOT removed at step 1 so the flashing is allowed to continue, the radio gets flashed, the phone dies.
samsamuel said:
Its not the famous tmous radio brick, unless you didnt mention something you did in your first post.
the only way it gets that kind of brick is flashing a radio from a regular HD2, the fact that the flash failed (exclamation screen) and you say you didnt try to flash anything else would point to a different problem. If the radio HAD flashed, the phone wouldnt have booted even to the excl screen.
You see, when you flash a stock rom via sd card, if hspl is installed it will allow the flash to start, but step 1 is first changing the spl(removing hspl) then the phone restarts into the new spl, and flashing continues. But because hspl is no longer there, cid checks fail and the flashing stops, so no radio gets flashed, so no radio brick.
radio bricks happen when you flash a non tmous stock rom via Goldcard or via usb whilst hspl is installed, because over USB, hspl is NOT removed at step 1 so the flashing is allowed to continue, the radio gets flashed, the phone dies.
Click to expand...
Click to collapse
You see the problem is I don't know what this guy did to it. All he said was he tried to load Android. When I picked it up in would power on and stop at the Software Failed screen. After I pulled the battery it does absolutely nothing.
jmac1968 said:
You see the problem is I don't know what this guy did to it. All he said was he tried to load Android. When I picked it up in would power on and stop at the Software Failed screen. After I pulled the battery it does absolutely nothing.
Click to expand...
Click to collapse
exactly, which is why im suspecting battery/battery pins/power issue, because it DID come on for you, meaning it isnt a radio brick, and the pins are very easily bent when the battery is pulled, one slight twist to the angle of rotation and the casing on the battery around the flat connectors catches the pins on the way up and out.
If he was installing android, he most likely installed magldr, which prevents teh battery from charging when the phone is off, hence me wanting to double check you were doing the USB bare wire charger correctly, because a totally dead battery won't charge in the phone, if magldr is there. And so, back to testing if its teh battery, thats what you need to confirm before you can move on,,,,, is the battery alive but flat? ten seconds with a known good battery, or a HD2 running winmo (can charge when off with winmo installed) will answer it for you.
Yes I made sure it was hooked up correctly. I held the wires on the terminals for what I thought would be long enough. Maybe the battery is junk? Thanks for the pointers though. I do appreciate the help.
In my first post last night I took it you were having a issue with getting a ROM to flash. I see now your issue is not this so I do apologize.
Samsamuel has givin you some great advice. Have you tried connecting your wall charger to the HD2 and then power it on? This is how I would get my HD2 to boot back up so I could charge if I accidentally let the battery drain all the way down and I was using MAGLDR. (Not a problem anymore thanks to cLK)
Now seeing as you do not have a ROM to boot into this will not charge your battery but just maybe prove the HD2 is not dead. I agree with Samamuel about it not being bricked, I think you just have battery/power issues right now, namely the lack of power.
Go to this thread that just sprung up last Tuesday in the HD2 Windows Phone 7 Q&A and General forum. Read the first post as it gives a method of charging your battery when dead using MAGLDR. I have not personally tested this cause I no longer use MAGLDR. I can not promise you it works but it is worth a shot. Let us know if this worked for you and post in the thread I linked as well if it works. That thread needs a confirmation post.
I tried 2 different wall chargers and just tried to tip in the thread you suggested. Nothing. Even tried a PowerMat for 3 hours.
jmac1968 said:
I tried 2 different wall chargers and just tried to tip in the thread you suggested. Nothing. Even tried a PowerMat for 3 hours.
Click to expand...
Click to collapse
Does this conclude that the battery is dead ??? and you might need a new battery ?
backlashsid said:
Does this conclude that the battery is dead ??? and you might need a new battery ?
Click to expand...
Click to collapse
It might be.
jmac1968 said:
It might be.
Click to expand...
Click to collapse
Then go for it
Hi guys,
Tried searching for my problem, but though I found some similar stuff, noone had quite my problem.
I was checking my Nexus S after a trip and it was with the 'emergency only' message. This sometimes happens to me, not sure if it's due to the roaming activation or caused by a bug where the radio subsystem crashes after a long period without network.
Anyway, I proceeded to my common solution: Turn off and reboot.
Except that after the phone was off, it would not turn on.
It doesn't even vibrate. It doesn't show anything when connected to the wall socket or to the computer. It's just completely dead.
Now, I'm not even sure if this is a hardware or software problem. Any idea on how I can debug this?
Here's what I've tried:
1. Take the battery out: no changes (even tried leaving it out overnight).
2. Charge the phone overnight: no change.
Next step: I'll go to a store and try a different battery... meanwhile I'm without my primary phone which sucks... Can anyone help?
Thanks in advance!
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
If it is not the battery, i can see what else you can do, a "dont turn on" phone is a dead end...
Sent from my Nexus S using XDA App
Guess I'm screwed... I had some pics and other data there... anyway I can get it back? i.e. is there a way to remove the internal sd card?
saranyan said:
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
Click to expand...
Click to collapse
Was this tried? Cause if that works there's hope for you yet.
BlackHawkA4 said:
Was this tried? Cause if that works there's hope for you yet.
Click to expand...
Click to collapse
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
nunocordeiro said:
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
Click to expand...
Click to collapse
Sounds like something is wrong with the hardware then. Have you brought it the store? Might need to get a new one on warranty.
I have the same issue with my old Blackberry 9000. It worked fine up until I stopped using it. Left it in a drawer for a few months. Went to sell it to Sprint. Wouldn't turn on. No LED, no nothing. Worked fine months before when I was still using it. To this day I have no idea what's wrong with it and it doesn't turn on.
Why not get an external battery charger and charge the battery up and then test it?
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
If you can get to download mode nothing is lost. Just flash new image via Odin.
Sent from my GT-I9000 using Tapatalk
nunocordeiro said:
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
Click to expand...
Click to collapse
Never heard of that happening, but it's a possibility... Still, I would first attribute it to a bad battery and try that first
Sent from my Nexus S 4G
With a new battery (that works on another nexus S) still no luck. =(
I still can't find anyone with this problem. I feel like the unluckiest idiot on Earth.
I assume I can't get to download mode since I can't even get the phone to report it is charging (it used to do that even if off). Do you want me to try anything, though? I'm open to suggestions until Monday. Then I'm taking it to Samsung. Hope they can recover my pictures.
BTW, my receipt doesn't have the IMEI and a customer service rep told me I need it on the receipt or they won't give me free support. How can I get it with the phone off?
Regards and thanks to all who responded,
Nuno
nuno, if you cant power on even with a new charged battery, then it's a harware fault and nothing can me done... =o\
but thanks for the advice, i never thought about the data in sd card, i guess i should make some backups! =o)
nun
BTW said:
Look under your battery. IMEI should be printed on the sticker beneath. Good luck!
Click to expand...
Click to collapse
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
odd things can happen ... it sucks
igorgatis said:
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
Click to expand...
Click to collapse
Did you try flashing a different rom? Or radio/
I haven't experienced this myself but I'm very interested on what happened. Did you guys flash any custom ROMS? or Radios for that matter?
This looks very similar to what i have. I just got my nexus s GT-i9023, it doesn't boot into fast boot, recovery, download mode or normal. The most activity i have got so fare is when i take the battery out, put it back it, and try turn the phone on it will sometimes flash then do nothing. I have looked every ware. When i use "./platform-tools/adb get-state" it returns "unknown". Any help would be great.
What i think i did was this:
- Unlocked bootloader, this worked
- restart
- installed clockwork mod with fast boot, this worked
- wiped data
- wiped cache (correct me if i spelt that wrong, or anything else)
- flashed cyanogenmod, this got an error but i didn't notice it the first time and i can't remember what it was.
- flashed gapps, this didn't work, when i restarted the phone it said that the installer for gaps had quit.
- restarted
- flashed cyanogenmod again, this is when i noticed the error
- restarted, didn't change anything
- wiped data
- wiped cache
- flashed i9020t recovery, this http://forum.xda-developers.com/showthread.php?t=1061855 i think this is what stuffed it up because my phone is i9023
- wiped data after flashing, thats what it said to do, i thought it was strange but i went along with it.
- wiped cache
- reboot
- now doesnt work.
Take it to the store where you purchased and claim ignorance!
My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.
someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation
someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget
someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?
someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty
I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..
NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Just to rule out the obvious, have you tried different cable and computer?
gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
godraistlin said:
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
Click to expand...
Click to collapse
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
How did you brick your OP in the first place? Does it still charge?
Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.
gabriwinter said:
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.
godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Did you try holding power button for >40 seconds?
godraistlin said:
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
GAMIT PRUTHVI said:
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
gabriwinter said:
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
jhs39 said:
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.