Hey guys, first post, but I'm in desperate help.
I have a HTC One from Vodaphone(UK) that had Android 4.3 on it.I rooted it, unlocked the bootloader and put Clockwork Mod Touch on it. All went smoothly and I had it for about a week.
I then installed Cyanogen Mod on it, but the installation failed and left me with all kinds of problems including the keyboard crashing completely and not working.
I formatted my phone again but now it's stuck loading Cyanogen Mod and doesn't move, the bootloader is still unlocked however I can't access the internal memory to put a recovery on it.
Is it bricked :c Please someone help
Its not bricked.
However, first an output of fastboot getvar all
Then a summary of whether you can get into recovery. And if you have any files there. Mean while lookup adb push and adb sideload commands to get familiar with them
Related
hey guys, i'm in a slight problem and in need of help...
i have a nexus one for few months now and a friend of mine asked me to root his new device and install a recovery img for him.
so i did, as i did for my nexus one and as any guide says. i installed the bootloader drivers. after checking fastboot-windows devices recognize the phone i unlocked the oem and installed boot.EPE54B.superboot.himem.img.
then, went to install the recovery img. again, checking fastboot-windows devices recognize the phone and after it did i fastboot-windows flash recovery recovery-RA-nexus-v1.7.0.img and the command prompt said the writing was ok.
then i rebooted the phone and it did reboot fine. tried to re boot it but then all went to hell. the phone booted but with no display! the phone is working, and touch screen is working (i'm hearing the startup notification and i sense the heptic feedback when i press things) but the display isnt working at all...
any idea what went wrong and how can i fix it?
anyone got any idea whats wrong with my phone?
is it something i did or is it a hardware malfunction?
What rom did you flash? have your tried flashing it again/another?
it would be very unlikely that you have caused physical damage to the phone, so it should be temporary, or coincidental.
omerwsb said:
hey guys, i'm in a slight problem and in need of help...
i have a nexus one for few months now and a friend of mine asked me to root his new device and install a recovery img for him.
so i did, as i did for my nexus one and as any guide says. i installed the bootloader drivers. after checking fastboot-windows devices recognize the phone i unlocked the oem and installed boot.EPE54B.superboot.himem.img.
then, went to install the recovery img. again, checking fastboot-windows devices recognize the phone and after it did i fastboot-windows flash recovery recovery-RA-nexus-v1.7.0.img and the command prompt said the writing was ok.
then i rebooted the phone and it did reboot fine. tried to re boot it but then all went to hell. the phone booted but with no display! the phone is working, and touch screen is working (i'm hearing the startup notification and i sense the heptic feedback when i press things) but the display isnt working at all...
any idea what went wrong and how can i fix it?
Click to expand...
Click to collapse
It seems like the phone was physically damaged or sth like that. Try to wipe all and flash a new custom ROM from recovery and see how it goes.
P/s: Lol, never try to help ur friends to do stuff like this, cuz there is a big chance that you might mess it up and have to give him yours, or buy a new one for him, which is worse
i didnt flash any ROM, it has stock ROM at the moment...
you think flashing a new rom will help? i'll need to flash it from adb, as i cant really get into the recovery (as i have no display )
Hello,
I just got the HTC One today, and installed CyanogenMod. There were problems with some key-features, so I decided to just stick with the stock rom. Unfortunetely, when I tried to re-install the stock rom, everything ****ed up, to say at least. So with the help of TWRP I wiped the SD-card, but I think something went wrong in the process, because the phone kept restarting only making it to the logo of TWRP. (Then, I tried to do an adb sideload, but I was told that no devices was found. Fastboot sees my HTC One, but ADB doesn't. Also, I am not able to transfer anything to the SD-card, as it is not showing up when I connect my phone to the computer. Now I am just stuck at the bootloader, with access to TWRP. The bootloader says TAMPERED and UNLOCKED.
I have been using the AIO-kit so do most of the unlocking.
How do I get my phone back to stock rom?
Or, how do I make ADB reconize my device?
Hi guys please help me...
Some how managed to soft brick my phone while updating to KitKat now all that happens is Google appears then goes to a blue screen with little lines all over it, no idea how to fix it.
It was a converted GPE version running 4.3. I have TWRP recovery installed and can access that but there is no back up file or recovery file or something similar.. how do i get a stock rom, get it onto the phone and install it?
I also have adb installed on my laptop but only know a few basic commands.. seriously need some help here..
Thanks
sferg.410 said:
Hi guys please help me...
Some how managed to soft brick my phone while updating to KitKat now all that happens is Google appears then goes to a blue screen with little lines all over it, no idea how to fix it.
It was a converted GPE version running 4.3. I have TWRP recovery installed and can access that but there is no back up file or recovery file or something similar.. how do i get a stock rom, get it onto the phone and install it?
I also have adb installed on my laptop but only know a few basic commands.. seriously need some help here..
Thanks
Click to expand...
Click to collapse
seriously mate, do some searching, don't wanna sound rude, but this has been asked & answered about a gazillion times.
anyway, one of three methods to get a ROM onto your phone:
1- OTG cable
2- adb push, as in "adb push <name of rom>.zip /data/media/"
3- adb sideload, as in "adb sideload <name of rom>.zip"
adb command work in custom recovery.
it is alive again.. i had seen your answer to another soft brick issue but the things i was doing was not working, however now it is, so thank you.
Basically I've been trying to root my 4 year old HTC one m7 and after finally discovering that the bootloader was locked I managed to unlock it with much hassel and managed to insert TWRP as a custom recovery screen (YAY)
Therefore thinking that I was being smart I tried to root the phone by Flashing SuperSU into it. However I flashed UPDATE-SuperSU-v2.76-20160630161323 which is the wrong version for my phone =((
Now my phone goes through the boot logo and into a lit black screen where it doesn't do anything. I assumed this was a soft brick but i am currently unable to get out of it. I can get into fastboot and access fastboot commands but am unable to use adb commands while the phone is in fastboot. Keep getting adb server version (31) does not match this client (36).
Stupidly i didn;t backup a Nandroid copy and am unable to restore it(yes yes its stupid of me, now I know)
Currently using a Windows 10 Computer.
Any Ideas on how to get my phone going again?
Hi guys, how's it going? I'm new to the forum, and also new to developing and modding android phones. So I kinda have a problem and was wondering if any of you had a solution in mind. Well, I recently bought a new HTC desire 555. I unlocked the bootloader and was attempting to root it when it got stuck in boot loop. There wasn't any twrp recovery files for my middle, so I got one that was the closest. After a few tries of it failing to boot into recovery mode with the twrps I downloaded, I thought maybe I needed to erase the cache with fastboot. That didn't work either. So then I erased recovery using
fastboot erase recovery
Click to expand...
Click to collapse
and that didn't seem to work either. At this point I was really tired and don't remember if I did anything else. Since I can't seem to find a stock rom (not that it would help much considering I couldn't root my phone) I thought I would pick some of your brains. Any ideas? It's nearly identical to he 626s, I have the stock Tom for that model but I can't get HTC sync manager to recognize my phone anymore (just need to bombard it with driver installations). Also, I tried to boot into recovery mode with different twrp image files which obviously didn't work). Anyways, any ideas?