Hello,
My phone ran out of battery a few hours ago. I charged it, but when it boots it gets stuck at the htc logo. The same thing happened to me a few months ago, but after restarting it 2 or 3 times it booted just fine. This time though, it won't get pasted it no matter how many times I reboot it. After trying all the tricks that I found on google, I resorted to do a factory reset. I should have never done that, it didn't fix anything but it did turn off usb debugging by disabling developer mode. So it essentially made sure that I can't fix it anymore. I can't do anything from my pc because my bootloader is locked and I need developer mode enabled to unlock it with fastboot. In recovery mode I get a red triangle with an exclamation mark but I can get to the options to update via sd card. For a second I thought that I found a way to reinstall the rom via the sd but of course they had to make sure that it doesn't work because the zip failed the signature authentication and the signature authentication can't be disabled with a locked bootloader.
So is there anything that I could try or has HTC made my phone so secure that I actually have to buy a new one instead of being able to fix it?
Any advise is more than welcome because right now my phone is really close to meet my friend the hammer.
Thank you
Related
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
So I have spent a lot of time running around trying to solve this. I think describing my problem will hopefully eliminate chasing dead ends.
The Problem:
My android OS is the one right before Lollipop. I have ALWAYS had the same PIN to get into my phone for years (7355608 The bomb code from Counter-Strike lol). Randomly (So it seemed) my Phone decided I didn't need a lock screen any more and it was gone. When i noticed this I went back into the options and set it back again. using the same PIN i always have. I try to get into my phone and the PIN does not work. I have found while digging around that I am not the only one with this issue. My phone is the Samsung Galaxy Note 3.
Added: The Update to Lollipop is waiting to be installed lol. Cant click on it since I cant get into my phone. But I dont think updating will help me at all anyways.
Additional Details:
I have a GMail account on my phone. I know the password. I had used USB Debugging Mode at one time and have the "developers options" opened. Doesn't seem to help because until you can unlock the PIN it wont connect to the PC to see or have any access to files or anything. I CAN NOT do a hard reset as there is valuable information to the point where i would pay to have this problem solved. My phone is NOT rooted or "unlocked" (unlocked as in stuck on one carrier)
What I Have Tried:
Android Device Manager - Doesn't nothing, when I use the LOCK phone it just tells me "You already have a PIN none was set"
AROMA - Starting on this but my phone is not rooted so I am not familiar with Android and every one that wrote a guide seems way to vague so I'm still researching this attempt on my on. AROMA is installed but apparently needs CWM (ClockworkMod) and installing that while locked out is where I currently am in this attempt.
Update: I don't understand what they mean by "Flashing" (I'm just going to throw it at a strobe light) and found out CWM is not needed if I can Flash it...
http://forum.xda-developers.com/showthread.php?t=2225695
XDA - XDA apparently has this method of using USB Debugging Mode and the Android Studio. But when I run the commands in the prompt it just tells it cant find the drive or something (I am thinking this is due to it not actually connecting the drive to the PC so it is being blocked from accessing what is needed to connect properly.
Repeated Failed attempts - This only works for Pattern Lock. Not PIN lock. FAILED.
I am willing to do anything to my phone to get my data back. Thanks.
Final Note: I just need all the data from the phone. If there is a way to get my data from the phone and then do a hard reset then I dont mind doing the reset. My goal is to get the irreplaceable information. Worst case I will buy a new phone and wait until this technology is old and easy to hack lol
http://forum.xda-developers.com/showthread.php?t=2244741&page=3
Good night everybody! my dad got this phone a while ago, after like 2 months he told me the phone was going crazy, I checked and was getting FC´s everywhere so get into recovery mode to wipe everything and there´s where problems started. I downloaded stock firmware and installed it but phone wouldn´t boot up, so my dad gave it to a guy that ``fixed it´´ but the problem came back after two weeks or so, the guy ´´fix it ´´ again but when I looked into the phone had no IMEI so didn´t recognized the sim card, the third time the guy got back the IMEI, that was long ago and today when I booted up the phone is having a weird behavior, sometimes gets stucked at the bootloader unlock warning, I restart it and after a couple of times starts the boot up animation but gets stucked at the M and like waving part.
I´ve tried getting into recovery mode but when I press any of those options boots to the warning bootloader. I got it to completley turn on when I pressed the recovery option; not expecting that to happened, but again some force close windows and decided to reboot it to see if would fix it but again to the same place stuck at the warning.
I´ve read many posts here im xda and outside but can´t find a solution. I tried to side load the firmware but looks like the pc doesnt recognize the phone´, when i got it boot up I connected it to the pc but didn´t recognized it, I installed the drivers and still the same.
Guess I need to get it recognized by the pc in order to try to side load a firmware. Sorry for the long post and any mistake, if someone can help to bring back to life this little fella.
Hello,
First of all, I just created an account to get help with a phone I have. I cannot seem to fix it, I contacted HTC support and the only option left is to return it to them for a fee to fix.
Details:
SIM unlocked AT&T HTC one m9
Issue:
After trying to update to marshmallow using the ruu 3.38.502.12 which is for AT&T phones, my phone is now bricked. There was an issue in the middle of updating, so my phone tried to revert back to the old recovery. During this step my phone glitched out and rebooted itself, now its stuck in a boot loop with no indication of a recovery or any OS.
I tried to redo the ruu update and I get an error saying my battery level is less than the % required, yet my phone screen is showing 100% battery.
I also tried placing the .zip file on a SD card and using "download" boot method to flash the rom "I get error saying no OS present"
I also tried fastboot but my phone isn't picked up by fastboot and sticks at waiting for device.
Any method that requires me to turn on debugging mode is useless because I cannot access the OS to turn this on.
Anyone have any other suggestions then what I've tried? Or is the only thing I can do is send it back to HTC and hope they can reflash the phone?
Thanks to all for the help,
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.