I recently attempted to return my HTC One to stock ROM and all that fun stuff. I must have made a mistake somewhere along the line because now I'm stuck in fastboot. Phone won't even boot into ROM or Recovery.
Any attempts to use fastboot commands from the prompt just result in failure.
I'm not sure what to do from here. Any help would be greatly appreciated.
I've figured it out for the most part. Well on my way to getting my device back to normal.
Related
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
Hi everyone
Since I restarted my phone last night, my phone has been in a endless bootloop and I can't even enter recovery, without it rebooting again and going into the same endless bootloop again, around 2 seconds after showing the "Teamwin" logo.
I'm using ARHD, and if I remember correctly it's version 71.1. TWRP is "openrecovery-twrp-2.6.3.3-m7" and running ElementalX kernel.
I expect my partition is somehow corrupted, but I'm at a loss of ideas as to how I can recover my phone again. I would apreciate if I could somehow manage to make a backup of my data, but it that's totaly hopeless, I'm thinking of going for the ArtMOD ROM instead and starting fresh.
Is there a helpfull soul out there, that could maybe give me some insights as to what I can do from here? Thanks in advance!
I was hoping I could install a stock ROM and start from scratch again, but I somehow suspect having used a modified ROM has gotten me in trouble now and the ROM Upgrade utility sees this as a downgrade. I've not been able to find a newer ROM for the .401. series than "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". Although the updater believes I'm updating from 4.19.401.11 (the ARHD ROM).
I can get into FASTBOOT USB and the phone goes to the black HTC logo screen when trying to update, but quickly fails on the PC during the process at "Updating 1/5". When unplugging the USB cable the phone shows:"
RUU
Security fail!
Update Fail!
I've attached two screenshots, to better explain
Can some kind soul out there please help me getting a working phone again? What ROM I'll end up with doesn't really matter
Since you're using unlocked bootloader, why don't you try RUU to get back on Stock ROM.
Here is the collection of ROMS
Download your ROM.
from Windows Command prompt
adb reboot bootloader #
If it didn't work, Press and Hold Power button along with Volume down of your phone,
When you reach to bootloader, get into fastboot mode.
Now follow the following commands to restore the STOCK Rom. (make sure your downloaded ROM are in the same directory where you have fastboot.exe, abd, and abdwin.api etc)
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip RUU.zip (RUU.zip is of course your downloaded Stock ROM). If it says Failed, try again.
4) fastboot erase cache
5) fastboot reboot-bootloader
6) fastboot reboot
Good Luck
Hope that helps.
Thank you so much for helping out!
After several tries, tries and retries, I finally managed to get the phone back up and running with the stock ROM. I believe what finaly did the trick, was to use "fastboot oem lock" to get the stock ROM installed. From here, I'm now able to unlock it again and install a custom recovery (TWRP) and ROM (I went for ARTMOD). Thanks again!!!
So as my friend was sleeping last night apperently his phone was hardbricekd. When he woke up it wouldn't leave the screen: boot up failed. Failed to validate boot image: ret=-1. He texted me from his pc asking for help. I told him to boot into recovery and just reflash stop. When he tried it said: Fastboot demon: failed to initialize partition table. What can he do??? It was stock and hadn't been rooted in a very long time!
Same problem: Stuck in fastboot
I'm having the same issue. After having 6.0 for a few days, my Nexus 6 shutdown while I was using it. It will only boot into Fastboot mode, with the same errors. I finally got adb to recognize it when plugged into my computer, but don't really know how to proceed. The command "fastboot oem unlock" says I need to allow this option on my phone, but I can only get into fastboot so that's impossible. All the guides I see to flash anything require this step.
I've done some digging. http://forum.xda-developers.com/nexus-6/help/stuck-fastboot-flash-to-recovery-t3266921 ... This forum suggests it's not fixable by a home user, but if anyone else has more info please let me know. You guys on xda are infinitely more knowledgeable than I am on this.
Nevermind. A little more reading, and I understand more of the jargon. Locked bootloader, no TWRP = no bueno. RMA is my only option. Guess I'll order a Nexus 5X and take steps to make sure this won't happen again.
My phone is in a boot loop after a friend of mine tried to modify it and managed to install a wrong ROM. I can access bootloader, but not the usual HBOOT, my bootloader looks like this: (Because it's my first post I cannot put a link here, but maybe I can in the comments)
Recovery mode does nothing, it simply reboots the phone and the cycle begins. Fastboot mode is working, I can give commands through cmd, but not all commands work. For example i can flash boot boot.img, but when flash recovery recovery.img it says "partition 'recovery' not support flash", erase doesn't work at all, getvar all returns this....:
(Because it's my first post I cannot put a link here, but maybe I can in the comments)
ADB not working and when Fastboot devices it writes a random serial(0123456789AB). Something isn't good and that's why I suppose this isn't just a Soft-Brick.
Please help, I don't know what to do, can we make it work? :crying:
Thanks in advance!
Same exact thing happened to me yesterday and I'm still stuck with a bricked phone... Have you found any solution ? thx
HTC desire 626g+ soft brick
http://forum.xda-developers.com/desire-626/help/fix-htc-desire-626g-update-command-t3243510
This is the perfect solution.
if you cant install through cwm i could find a link which i used to lash the phone to official update
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?