Hey all,
So like about a year ago I installed twrp and rooted my one m8s and couldn't care less to update anything but everything was working fine.
Recently I bought a new phone so today I thought lets wipe the device and factory reset it. Well thats where it went wrong.
After the reset it tried to boot but was just stuck on the white screen with the HTC logo.
I then held the power + vol up, which triggered something and showed an other logo for a second then just going dark, but the device is still on and backlit.
I cant get out of this for some reason neither will the device turn off. When i connect it to my pc it gets recognized but I cant get into storage.
Also adb and fastboot won't see the device and the htc_fastboot.exe I got from here throws an adbwinapi.dll missing error.
I am really stuck on what to do and i was hoping maybe someone could help me out here?
Thanks in advance.
Regards,
Bart
EDIT: got the phone to turn off when the battery died and was able to boot into fastboot from there, lets see where this gets me.
EDIT #2: Welp I fixed it I suppose. If someone please could remove this thread since I can't
Related
Hi,
I have a really tough problem with my Verizon Galaxy Nexus. After I boot it up it shows the Google logo and then the screen goes black. It is still on because I have left it there hoping it would pass this screen but the battery died eventually. If I put the phone into a computer I get the charging screen and it will charge. I can get into fastboot mode. I have tried unlocking the device so I could flash a new ROM but as soon as I use the Gnex toolkit to unlock it, the fastboot mode reboots and it is locked again. When the device is plugged into the computer in fastboot mode Windows is constantly giving the noise that something is plugged in than unplugged then plugged in, on and on and on. I have put it in Odin mode and flashing the 4.04 image ROM looked like it worked but still after the phone reboots it just shows the Google Logo and then goes black. I have gotten into the stock recovery and wiped data and cache and that did not help either. Any help would be appreciated!
Nick
PS
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
I followed that and afterwards my screen still comes up black after the Google logo.
I just tried to install TWRP recovery to see if that would help. I went through all of the fastboot commands and they said they completed successfully. When the phone rebooted the stock android recovery was still on the device... so for some reason this phone is taking the commands and they are getting returned as successful but they are not successful... super strange.
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
My Gnexi said:
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
Click to expand...
Click to collapse
Correct, seems highly likely his eMMC deep fried. If unlocking bootloader doesn't even work, I would try nothing else and get its mainboard replaced.
Thanks. Now that I know, I can stop wasting my time trying to fix this.
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
Hello,
In the last few months i have had some minor issues with my phone. In May or in June I have tried to root my phone. It was my first device I wanted to root, so I decided to use Kingo Android root. It didn't work. I installed HTC universal toolkit ( or how was it called ) from XDA forums to my computer. With its help I unlocked the bootloader, installed the TWRP and rooted the phone with Kingo. Everything worked OK, the only problem was that TWRP didn't respond to touch input. I didn't solve it at the time because it wasn't urgent. A month ago I installed few root apps from Google Play, but I didnt experience any issues. Today I was browsing the internet and suddenly I saw a HTC logo and the screen came grey. I waited for a minute and then force turned the phone off. It didn't want to start again. I booted into bootloader. It showed few errors, but was successful to boot. I wanted to open recovery, but it opened the bootloader menu again. Factory reset option didn't work too. I turned the phone off and then turned it on again, but it was stuck in infinite startup loop. Also the HTC logo was broken, there were strange colourful squares around it.
How can I repair my phone? I know that it isn't totally bricked, but this looks really bad. At least I would like to save my data and I will buy a new phone.
Thank You very much for Your help.
Dominik
P. S.: Sorry if I made any mistakes, but I am not a native speaker.
So today it doesn't even turn on!!!! I have tried everything, I was holding power and volume down button for almost two minutes, did the same with my mobile connected to the charger and to the computer, but nothing :crying: .
CAN ANYBODY HELP ME?????
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem
So i tried rooting my samsung. with this option
and now its stuck on the twrp logo and it doesnt even turn off it just loads the logo again and again please i need help quick.
Can't enter anything. And the phone doesn't show up in odin. I can only restart the phone
Managed to open it in recovery? somehow its showing up on abd
Seeing how you really are rather new an all, Plus the fact no body else has mentioned anything, I have to ask....
So, Have you fixed your phone yet? (Now a week later ...???)