After trying to root the phone it's stuck on the Bootloader unlocked screen and keeps restarting. I installed TWRP earlier this year but I deleted the backup recently.
I've been trying to install reinstall a new image but since it's bricked I can't get into the folders via my PC. Trying the ADB route didnt make a difference cause I can't seem to get my phone to show under List of devices attached for the ADB.
And now I'm frustrated with it...
And now I'm getting ADB server is out of date. Killing... Then it still doesnt show the device...
Update: Got past the Bootloader unlocked screen...but Im now stuck at the blue Motorola loading screen...
Related
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?
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
I tried to use this guide to update to 5.1.1.
http://forum.xda-developers.com/g-watch-r/general/install-android-wear-5-1-1-to-lg-g-t3114528
Now, I'm stuck on the LG Screen at boot up. I can enter recovery mode/bootloader.
I'm fine with sideloading back stock boot recovery and sys images.
The only problem is that my device won't show up in ADB.
Allow me to clarify that 30 minutes ago, my device WAS showing up in adb while I was using the guide that I mentioned earlier.
Does it not advance past the LG screen at all? I know when I did an upgrade it look a long while for it to boot back up.
Have you checked to see if you have any missing drivers in Device Manager? When you reach the bootloader you'll need to reinstall the generic ADB drivers.
After trying to install CM on my kindle after rerooting it (it lost its root after amazon pushed an update a couple months back), I'm getting stuck with a boot loop which gets me to the static yellow kindle fire logo and then resets over and over back to the same static logo.
It's not being picked up by ADB after installing the SDK and USB drivers, and obviously not being picked up in device manager.
Just trying to figure out what my next steps are. I'm already guessing it'll be getting a fastboot cable/making one, but any other ideas you guys have I can work on in the mean time?
Any help is much appreciated, thanks!
[SOLVED] Just updating now I have my fastboot cable; accessed, and used Restore2Stock (google) to install TWRP onto my device via fastboot. After that, I adb push'd the stock o/s back onto the system and use TWRP to reinstall.
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?