Hi,I tried upgrading my M8 from 4.16 to 4.28 manually through windows but process hanged after 28%.When i unplugged and reboot my phone will only show android system recovery screen.i have sdk toolkit downloaded in my laptop and ruu 4.28 at&t file too.please help.
Related
I have the At&t HTC One and wanted to root,So i did steps as instructed in the all in one kit by hasoon,i unlocked bootloader,flash twrp
2.5 recovery, and then flash the same twrp kennel, the recovery appear on my phone, but then i cant push the SU into my phone, using perm
root,keep getting device not found although i have installed htc sync along with the driver, and i stuck at the recovery loop, cannot get out of it, so
then I enter bootloader again, and flash Superboot image, the phone appeared to be rooted as i can use titanium backup to delete apps but then
my wifi not working, and if i restart the phone i will stuck in the recovery loop no way to get out,please help
I was having major problems with my device not being recognized - issues with having BOTH the HTC Drivers AND HTC Sync Manager installed - kept saying the drivers needed to be reinstalled/updated, but if I did that, the device was never recognized - like the two installs compete.
I uninstalled both the drivers and the sync manager, rebooted my computer, installed sync manager, and ran it, IGNORING the request to update it.
The system FINALLY recognized my device when I plugged it in, and I was able to get superSU to load via TWRP.
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app
God help me.
While I was trying to sim unlock the phone, I accidentally changed permissions on the system folder to read-only (using root explorer). The phone will not go past the splash screen since. So I tried a factory reset with no avail. I decided to load a Stock ROM using the Sprint ROM but it wouldn't load; fails at verifying file. I tried different ROMs and none of them will take. I'm unable to get the PC or Mac to recognize the USB mode. The phone is on, but in Windows it says no emulation and Mac doesn't even pop up anything. I did install the ADB and fastboot drivers on both the PC and Mac but they still don't recognize it. I'm showing
T6-WHL XA Ship S-Off
CID- 11111111
Hboot 2.46.0000
on the boot screen.
Any help is greatly appreciated.
Update: Installed Cyanogen Mod 12 via SD Card. Went smooth.
So ive downloaded the lasted ruu from the htc website and run the exe file. and get nothing. I've run it as administrator ,compatibility mode and it just wont load.
Hello,
I have a problem with an HTC Flyer.
The device cannot be started in bootloader mode or recovery mode.
The only thing that still works is the download mode.
The device is displayed as Qualcomm Diagnostic under Linux and Windows 7.
Is there a way to re-flash the bootloader?
Then fastboot would be possible afterwards.
I downloaded the original rom from the internet.
I unzipped the Rom according to another manual, so I now have all parts of the Rom available.
I have already tried it with the QFIL program, but you need an xml file for this, but this is not available in the ROM for the flyer.