Couple issues after replacing camera, mic and display! - Sprint HTC One (M7)

Hey,
I had to replace the display, battery, mic and camera for my phone and now when i turn it on it shows the htc logo then it gets black and doesnt boot up, im able to boot into bootloader but if i choose recovery it does the same thing, gets black and doesnt boot.

Terramoto said:
Hey,
I had to replace the display, battery, mic and camera for my phone and now when i turn it on it shows the htc logo then it gets black and doesnt boot up, im able to boot into bootloader but if i choose recovery it does the same thing, gets black and doesnt boot.
Click to expand...
Click to collapse
If I were you, I'd use the RUU to reset everything back to stock. If it still doesn't work, then you've at least narrowed your issues down somewhat. I wrote a guide to RUU that might help, although you may have to adjust it to your particular situation: http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110

Related

[Q] Help!!! Grainy green screen With lines during boot up

It started about 30mins ago, was on a call which the screen locks off when u on a call like stand by, but when ending the call the screen would turn on back no matter what. anyways i took out the battery thinking maybe the roms just buggy or the battery dead since it was on low. puttin back the battery the phone wouldnt turn on, took it out and tried again same result.
so i put it on charged nothing, gave it about 2mins charge it came on, but the boot screen with the X just had some green pixel dots all over and horizontal lines for about 3 secs then back to normal, but the phone wont boot pass that.
took out the batteries again, back in then try boot into fastboot or bootloader but nothing, just the boot screen, then the rom booted after waiting, took longer than normal. so i turned it off and try the bootloader or fastboot but it wont load just the rom, so i restarted to recovery mode from the rom it worked, turn off and try bootloader or fastloader mode they worked, now it seems all working fine, also my touchscreen is responding perfectly and the rom loading ok.
but anytime i boot the phone the bootscreen has the green pixels and lines just the same. im abit worried as i dont want things getting worse, is there anyway to fix this, is it some virus? could i just flush everything and start over???
any help would be greatful, thanks.
ppl with simular problem:
http://forum.xda-developers.com/showthread.php?t=642761
http://www.google.com/support/forum/p/android/thread?tid=77fefa8bdd57d7a3&hl=en
You guys think updating my radio from 4.06 to probably 5.08?
Almost similar with few different colors but I dropped my n1. It took me almost a day to see that the LCD was broken. Turn off the phone or screen and look in sunlight. They really were hard to notice and I showed to 4 different peoples whom all failed to notice until I showed them. Hope yours is just a minor software problem.
well i just check its not broken and it didnt fall from me so im guessing its software but im wondering if it can fix but i dont wanna flash my phone and things get worse or even brick my phone, so im asking before i try anything more.

[Q] Captivate Black Screen With Buttons Highlighted. Help!

Hi Folks,
I have been using an unlocked Captivate for 3 months. I recently flashed MIUI ROM - 1.7.8 (from Cognition) and it was working fine for a day. Suddenly, when I had put the phone on charge (power not USB), the screen turned black and the phone is not working after that.
I flashed to stock (ODIN: as mentioned here: http://forum.xda-developers.com/showthread.php?t=776255) but after that the AT&T logo comes up (with the screen display very dull) and I hear the Samsung startup sound (no screen). That is all. It goes to black screen with the buttons highlighted.
If I connect it to my PC, I can browse the SD card but the screen doesn't turn on at all. I tried re-flashing to stock multiple times with no luck. Please help!
indophile said:
Hi Folks,
I have been using an unlocked Captivate for 3 months. I recently flashed MIUI ROM - 1.7.8 (from Cognition) and it was working fine for a day. Suddenly, when I had put the phone on charge (power not USB), the screen turned black and the phone is not working after that.
I flashed to stock (ODIN: as mentioned here: http://forum.xda-developers.com/showthread.php?t=776255) but after that the AT&T logo comes up (with the screen display very dull) and I hear the Samsung startup sound (no screen). That is all. It goes to black screen with the buttons highlighted.
If I connect it to my PC, I can browse the SD card but the screen doesn't turn on at all. I tried re-flashing to stock multiple times with no luck. Please help!
Click to expand...
Click to collapse
So your saying your phone actually fully boots, you just can't see it? (I would test this by calling myself) This is a problem I've never heard of.... Can you boot into recovery with a working screen? Could be a hardware problem, considering how it happened.
Hi,
I was able to call my number earlier (before flashing back to stock) but not anymore (get a busy line after the first ring). However, I get the AT&T screen (only time I see something on my screen) and the Samsung startup tone and the buttons are all highlighted. The screen is black.
Even when I did Odin, I was doing it from a black screen (the Download icon on the screen didn't show up). I never get to see anything on the screen other than the at&t logo (so not able to boot into recovery actually!).
I just hope it is not a h/w pbm. I would rather try fixing it myself (if it s/w pbm) than taking it to the store
indophile said:
Hi,
I was able to call my number earlier (before flashing back to stock) but not anymore (get a busy line after the first ring). However, I get the AT&T screen (only time I see something on my screen) and the Samsung startup tone and the buttons are all highlighted. The screen is black.
Even when I did Odin, I was doing it from a black screen (the Download icon on the screen didn't show up). I never get to see anything on the screen other than the at&t logo (so not able to boot into recovery actually!).
I just hope it is not a h/w pbm. I would rather try fixing it myself (if it s/w pbm) than taking it to the store
Click to expand...
Click to collapse
What kind of charger were you using? Honestly, it sounds like you fried some of those beautiful innards I'm no expert, though.
Twicebak3d said:
What kind of charger were you using? Honestly, it sounds like you fried some of those beautiful innards I'm no expert, though.
Click to expand...
Click to collapse
It could possibly be because of the power issue (my charger model is ETA0U60JBE which supports 100-240v and I have 240v at my place so it should not ideally be a pbm). I'm just trying to see if there is some s/w fix for this situation before giving it for a h/w check.
Would this be a problem with my LED screen (though I see the at&t logo come up)? If it is, would it be some connection issue to the LED screen or a completely dead LED?

[Q] Is this phone Gpu malfunctioning?

Hello.
I have a friend who asked me to replace its screen and digitizer that were broken.
I bought one altogether and installed.
But the problem is that the picture appeared with horizontal streaks as shown in this photo I have taken:
made a hard reset but stayed the same, then I made the OTA upgrade to ICS.
after that nothing more is shown in screen, It vibrates and I can get in fastboot, blinded of course because scren is black all the time.
then I tried to install custom roms, installed cwm recovery and when I go to recovery sometimes the screen lights up and shows this:
when i press up and down I see a litle change in the screen but not readable.
I tried to install roms but I think it does not start because the buttons does not light up.
what do you think I should do?
Napalm_PT said:
Hello.
I have a friend who asked me to replace its screen and digitizer that were broken.
I bought one altogether and installed.
But the problem is that the picture appeared with horizontal streaks as shown in this photo I have taken:
made a hard reset but stayed the same, then I made the OTA upgrade to ICS.
after that nothing more is shown in screen, It vibrates and I can get in fastboot, blinded of course because scren is black all the time.
then I tried to install custom roms, installed cwm recovery and when I go to recovery sometimes the screen lights up and shows this:
when i press up and down I see a litle change in the screen but not readable.
I tried to install roms but I think it does not start because the buttons does not light up.
what do you think I should do?
Click to expand...
Click to collapse
Looks like something hardware is broken. You can't flash any ROMs right? You might want to try a RUU if you think it may be software
But I'd say hardware
Was it anything like that before the new digitalizer install? Perhaps it is not installed correctly?
poondog said:
Looks like something hardware is broken. You can't flash any ROMs right? You might want to try a RUU if you think it may be software
But I'd say hardware
Was it anything like that before the new digitalizer install? Perhaps it is not installed correctly?
Click to expand...
Click to collapse
I think I can flash a rom, but I don't know if it gives an error on the screen. is there a way to make a log file of the install or boot process?
To flash a rom I put the rom file on sdcard and boot into recovery, then volume down 4 times, power, power, volume up 2 times, power, and 5 times up, power.
to install a ruu is this same process? Or can I install from fastboot? that way I get an output of the command on the pc...
the old digitizer and screen was all black, it was completely broken.
Napalm_PT said:
I think I can flash a rom, but I don't know if it gives an error on the screen. is there a way to make a log file of the install or boot process?
To flash a rom I put the rom file on sdcard and boot into recovery, then volume down 4 times, power, power, volume up 2 times, power, and 5 times up, power.
to install a ruu is this same process? Or can I install from fastboot? that way I get an output of the command on the pc...
the old digitizer and screen was all black, it was completely broken.
Click to expand...
Click to collapse
I reckon 99% of the time there are no errors in ROM installs. You could try get a adb logcat of the booting?
installing a RUU is completely different. It is done from a PC where you go through the tutorial on the computer while the phone is attached. So, it will tell you on the computer if there are any errors
Okay so this is an improvement
I changed the Display of 2 IncS and both worked afterwards. Your Screenshot looks like the connector isn't connected properly.
Maybe the screen connector isn't connected correctly?
Try reconnecting the display-connector. Make sure that it sits correctly.
MrToastbrot said:
I changed the Display of 2 IncS and both worked afterwards. Your Screenshot looks like the connector isn't connected properly.
Maybe the screen connector isn't connected correctly?
Try reconnecting the display-connector. Make sure that it sits correctly.
Click to expand...
Click to collapse
Yes it is the connector, but I try and try many times and only once it was ok, but when assembled the parts it stoped working...
I don't see anything wrong in the connector or flex, I don't know why it does not work properly...
Napalm_PT said:
Yes it is the connector, but I try and try many times and only once it was ok, but when assembled the parts it stoped working...
I don't see anything wrong in the connector or flex, I don't know why it does not work properly...
Click to expand...
Click to collapse
+1 for connector or especially the flex. It would be good to replace with another screen(or flex, I don't know).
This doesn't seem to be a software problem. It looks like just a problem for transferring data to screen.

[Q] Could anyone please confirm if it's totally bricked?...

Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
KomuroXV said:
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Click to expand...
Click to collapse
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Seanie280672 said:
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
Click to expand...
Click to collapse
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Fain11 said:
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Click to expand...
Click to collapse
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
Click to expand...
Click to collapse
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Seanie280672 said:
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Click to expand...
Click to collapse
KomuroXV said:
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
If only I could find a way to the bootloader mode, I would be so happy.
q.q
KomuroXV said:
If only I could find a way to the bootloader mode, I would be so happy.
q.q
Click to expand...
Click to collapse
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Fain11 said:
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
Click to expand...
Click to collapse
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
nkk71 said:
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Click to expand...
Click to collapse
Oh... yes, I've heard about the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
KomuroXV said:
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
Oh... yes, I've heard abot the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
Click to expand...
Click to collapse
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Seanie280672 said:
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Click to expand...
Click to collapse
Did just that, right at those two little spots,but now the trick's not working, even though it had before, only I'm not sure if it was flashing to the two-little-spots.
Phone was charged and off. I turned it on holding Power+ Volume Down, with the phone's two spots facing straight to the flashlight.
It went straight into the bootloop still.
Are you sure it is there, and not right in the front or back camera?
Is it bricked?
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
hugof99 said:
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
Click to expand...
Click to collapse
Well, unlike your case, my phone was actually 99.9% clean since I fixed it with the RUU. I don't think there's a ROM related issue with these reboots my phone has now.
Problem: Turned phone off while it was doing something inside stock's Recovery. Now got caught in an infinite reboot because of that,
It is actually something like this.
http://www.youtube.com/watch?v=85HtJYcVAos
http://www.youtube.com/watch?v=rai4nCciKBg
http://www.youtube.com/watch?v=W5PCJYKaCrE
Just that mine is HTC One, and, well, besides from that screen it's also rebooting on his own every 8-10 seconds.
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
iElvis said:
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
Click to expand...
Click to collapse
Just as it sounds. I pressed down the power button to turn it off while Recovery was starting, and soon after that, the infinite bootloop started.
The RUU was 100% good, and I tested everything I could before trying to flash a ROM again.
But, just in case, it was this one:
http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/
Anyway, as I said, after I checked everything around the phone, I went to bootloader, clicked recovery by accident, and on reflex turned it off pressing down the power button.
Since then, there's been an infinite bootloop, rebooting every 8 to 10 seconds.
Sadly, and I guess it's because it was freshly flashed from a RUU, I can't access through ADB either.
q-q
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
iElvis said:
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I've been trying to do this for days on my own (couldn't get help) but I finally managed to install a Unbuntu and run the sudo ./revive.sh
[email protected]:~$
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ chmod +x revive.sh
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
The phone is actually connected to an USB 2.0 port, rebooting on his own still, but connected.
It's not detecting it though.
:/

Major problem. Phone Stuck at start up logo

This morning during a call my phone shuts off for no reason. It is not rooted no physical or water damage. I tried to power it on it will vibrate than attempt to start get stuck at boot screen than eventually turn black. I tried booting into recovery to hard reset I will get to the menu do all the prompts and get the lg logo and back to black screen. I don't know what is going on. Is this a common issue? Admins if this is in the wrong section feel free to move it.
Kingaries79 said:
This morning during a call my phone shuts off for no reason. It is not rooted no physical or water damage. I tried to power it on it will vibrate than attempt to start get stuck at boot screen than eventually turn black. I tried booting into recovery to hard reset I will get to the menu do all the prompts and get the lg logo and back to black screen. I don't know what is going on. Is this a common issue? Admins if this is in the wrong section feel free to move it.
Click to expand...
Click to collapse
Not sure what caused the issue but if wiping from recovery doesn't work I would look into restoring phone with kdz file. Sucks to do that seeing as all data will be gone but hopefully you have a backup. If restore doesn't work you need to call T-Mobile for replacement
Sent from my Porn Infested G4
The replacement has been processed. Unfortunately trying to factory ? reset doesn't work because the phone ? wouldn't stay on long enough for that to happen. Love to know what actually caused this issue. Kinda kicking myself for not doing a weekly backup.
I actually got the same problem on mine but mine is rooted and was working fine but then randomly my phone is doing bootloop. I don't have terp installed and I'm I only able to boot up to software upgrade mode. Ive tried the step for format everything with holding the volume up n on button but after I did the reset stuff still does boot loops. Also another problem is that whenever I plug in phone to computer it doesn't show up, so I have no option to add roms or anything like tht to internal or sd card. Is there anyways too flash anything of the software mode, if so can you plz let me know thank you.

Categories

Resources