Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
cuongcn said:
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
Click to expand...
Click to collapse
did u update hboot with an unlocked bootloader...thats no good
are u still can access Hboot?
sometimes, u should flash a kernel with ROM to work on it. if you still running Stock ROM, don;t flash MOD kernel like Holiraider. it will couse boot loop.
if u still able to access HBOTT, no need to worry.
@meatwad0222: I unlocked bootloader and updated hboot. It succeeded in rooting the phone. I got problem when I tried to flash a kernel.
@prahasta: I can't do anything. The phone never turned on again, even if I plugged the charger, the LED was not on. Pressing power button with volume down did not work at all. In general, I can't access to hboot.
Hm... It will be difficult.. hope it wasn't couse by hardware.
Sent from my HTC Raider X710e using xda premium
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
austin4913 said:
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
if Bootloop, at least u still can access HBoot, but he can't do that.
try to connect it to PC with Full Battery. then check if your PC still detect it. if PC can detect it, try to flash Official RUU.
My laptop does not recognized it. It said that it can't find a driver for that. I searched in xda-forum and I found the driver. Right now, in the device manager of my laptop, it says Qualcomm HS-USB QDLoader 9008. I tried to flash an office RUU but it stopped at <waiting for device>
Thank for your replies.
good to hear your laptop still detect the phone.
u need to pick right RUU for your device.
used Hanson tools, choose to unlock your bootloader again (hope this work). after unlock bootloader, and u can acces HBOOT, choose fastboot mode then instal CMW/WCXs recovery. once done, try to access CWM. if u can acces CWM recovery, there is no worries anymore, u just need to instal correct ROM and Kernel.
My laptop only detects the phone as a Qualcomm chip, not as a phone. When running Hasooon tool, it stops at <waiting for device>.
Sounds like it's in dload mode.
If your phone is in dload mode then I think that is a soft brick...it is fixable, from what I read on another thread, but is more difficult...but not impossible..I had to download HTC drivers for my laptop...the following 2 sites contain the files.
http://forum.xda-developers.com/showthread.php?t=1450105
http://www.theandroidsource.com/viv...65-latest-htc-vivid-sync-driver-download.html
Sent from my HTC PH39100 using xda premium
I talked to HTC customer service for repairing. After everything was set up, I thought that I lost my warranty since I rooted my phone (in HBoot, it said RE-LOCK"). I will give a try with the "wire trick" in the thread "Juopunutbear S-OFF". Hopefully after wire those holes, I can access to the debug mode and "wake up" my phone. Otherwise, I have to spend $5 more to buy those warranty stickers on eBay and have the phone fixed.
I thought that it would be a jtag, but it was not. I did not succeed. I have to send it to HTC for repair.
I think I know the reason caused my problem. I tried to recover why I was on S-ON. Thus, the firmware will "fight" each other and the hardware will not know what it should do. The result is a software-bricked phone.
I managed to get myself stuck in a locked bootloader with no way to get back into android or flash a rom from recovery. Would I be able to flashboot a .img file from being bootloader locked or will I have to run the RUU.
I am only saying this because I can't get windows 8 to find my phone even with the drivers installed. I am guessing it has something to do with being USB 3.0 and on a MBP. The only way I can seem to get fastboot to work is in OS X, Wine hasn't been able to run past the initial loading screen so that idea was shot. Any ideas would be greatly appreciated.
Unlock the bootloader..if memory serves me correctly you only need to be in fastboot for that. Once you're done with that, flash your corresponding RUU (since you don't have s-off and supercid).
Or you could flash recovery by putting it in the same folder as adb and typing "fastboot flash recovery recovery.img" and go from there.
And lastly just factory reset from bootloader..that could also work
Sent from my HTC One using xda app-developers app
My m8 is stuck in a boot loop and i am unable to access the recovery to factory reset the phone. Its been like this for 2 days now, and i have not found any solid help on the matter. I can get into hboot, however fastboot does not work and i cannot get into the recovery (the options are there, but when i press them they just disappear and nothing happens). If i connect the phone to my pc, the fastboot usb option shows up.
What im looking for are some step by step instructions on how to fix the matter. Ive posted on the /r/techsupport subreddit, and ive been told to either use an RUU or try and reflash a recovery, but without the instructions on how to do so.
oats123 said:
My m8 is stuck in a boot loop and i am unable to access the recovery to factory reset the phone. Its been like this for 2 days now, and i have not found any solid help on the matter. I can get into hboot, however fastboot does not work and i cannot get into the recovery (the options are there, but when i press them they just disappear and nothing happens). If i connect the phone to my pc, the fastboot usb option shows up.
What im looking for are some step by step instructions on how to fix the matter. Ive posted on the /r/techsupport subreddit, and ive been told to either use an RUU or try and reflash a recovery, but without the instructions on how to do so.
Click to expand...
Click to collapse
You have some options
Non-s-off
fastboot flash a recovery with this command
Code:
fast boot flash recovery recovery.img
if your s-off
use caption_throwback's bootloader flashable twrp with your external SD card
use the Harman Kardon ruu
Sent From my Evo 3D with the dark Lords kernel
So I seem to have made the mistake of formatting data - don't ask me why, I wasn't thinking. Now I cannot get past the bootloader or the Google splash screen. On Windows BTW.
Things I've attempted:
ADB and Fastboot - When I ran the command to unlock, it said I already was. :good:
CF's root - Rooted
Wug's toolkit - Tried returning back to stock img, but says ADB device was not found. Step 1 was to enable USB debugging, but I cannot boot into the ROM so that is a no-go. I am using the original OEM cord. I've tried using another USB port as well... nothing.
If I am missing something, please let me know. The drivers should be good to go since I upgraded them 2 days ago.
Update: Dowloaded TWRP and installed via Fastboot. Restarted bootloader, booted into recovery, and the TWRP splash screen popped up. Shortly after that, the Google screen came up and is hung.
I found this thread http://forum.xda-developers.com/nexus-6/help/help-nexus-6-stuck-bootloader-t2949817. When I type fastboot devices, it shows my device's serial number.
Are you sure you didn't delete data? Formatting should not cause that issue. You can flash the stock userdata.img back and stock boot.img
Sent from my Nexus 6 using XDA Free mobile app
or, while in twrp, adb push/sideload a rom(and gapps) to your phone and flash it in twrp recovery.
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Revolution_09 said:
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Click to expand...
Click to collapse
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
alray said:
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
Click to expand...
Click to collapse
Thank you! Everything else went smoothly and I've flashed 5.1 now.