Related
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.
so i need some serious advice. i had my phone rooted, and i screwed up and while attempting to fix the tiny storage size bug (it was 2 AM), i formatted EVERYTHING because i somehow managed to forget what the word 'format' means. so now; it is softbricked, the sdcard has no rom files on it to be flashed, i cant mount it anyway, i get an error saying 'missing UMS lunfile' when i try to mount the usb, adb wont detect my phone, fastboot just sits there, the RUU says it cant find any devices, i cant lock my phone's bootloader either. . my hboot is 1.28, i was using a custom version of ICS, and it was bought in australia a few days before the update. i rooted while running ICS.
PlasticTurd said:
so i need some serious advice. i had my phone rooted, and i screwed up and while attempting to fix the tiny storage size bug (it was 2 AM), i formatted EVERYTHING because i somehow managed to forget what the word 'format' means. so now; it is softbricked, the sdcard has no rom files on it to be flashed, i cant mount it anyway, i get an error saying 'missing UMS lunfile' when i try to mount the usb, adb wont detect my phone, fastboot just sits there, the RUU says it cant find any devices, i cant lock my phone's bootloader either. . my hboot is 1.28, i was using a custom version of ICS, and it was bought in australia a few days before the update. i rooted while running ICS.
Click to expand...
Click to collapse
Have u tried lex's multi tool . http://forum.xda-developers.com/showthread.php?t=1865265 that's the only thing I can think of regarding to help ur situation.
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
PlasticTurd said:
so i need some serious advice. i had my phone rooted, and i screwed up and while attempting to fix the tiny storage size bug (it was 2 AM), i formatted EVERYTHING because i somehow managed to forget what the word 'format' means. so now; it is softbricked, the sdcard has no rom files on it to be flashed, i cant mount it anyway, i get an error saying 'missing UMS lunfile' when i try to mount the usb, adb wont detect my phone, fastboot just sits there, the RUU says it cant find any devices, i cant lock my phone's bootloader either. . my hboot is 1.28, i was using a custom version of ICS, and it was bought in australia a few days before the update. i rooted while running ICS.
Click to expand...
Click to collapse
U can flash the rom.zip(extracted from the ruu) using fastboot command fastboot flash zip rom.zip
Sent from my HTC One XL using xda premium
fshami said:
U can flash the rom.zip(extracted from the ruu) using fastboot command fastboot flash zip rom.zip
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
okay, update :L
i still cannot use adb. i have howerver managed to get fastbot working, so i tried to flash a rom; no luck. so i locked my phone and ran the RUU. no stupid error message this time, because this time it was retarded: WRONG RUU VERSION, PLEASE USE THE CORRECT UTILITY.
see, im in australia, and there are only 2 ruu for the land down under. this is the second one ive tried, after th first one GAVE ME THE SAME ERROR
soi have some questions:
1) is it possible i have a european or otherwise overseas model?
2) this one is badly worded and confusing, so bear with me:
i dont have clockworkmod on account of locking again, but i think the inabilty to flash the phone may come from the inability to contact the sdcard. is there a command in fastboot that would set the partitions back up from scratch? if i can do that, i could then flash the adb drivers back on my phone, then use adb push to force the damn rom.zip onto my strorage then use clockworkmod to flash the rom? (all my grammar are belong to hulk)
i need a speedy reply as ive got my boss breathing down my neck about this (if i dont fix it they cant contact me if im not in the office or home)
PlasticTurd said:
okay, update :L
i still cannot use adb. i have howerver managed to get fastbot working, so i tried to flash a rom; no luck. so i locked my phone and ran the RUU. no stupid error message this time, because this time it was retarded: WRONG RUU VERSION, PLEASE USE THE CORRECT UTILITY.
see, im in australia, and there are only 2 ruu for the land down under. this is the second one ive tried, after th first one GAVE ME THE SAME ERROR
soi have some questions:
1) is it possible i have a european or otherwise overseas model?
2) this one is badly worded and confusing, so bear with me:
i dont have clockworkmod on account of locking again, but i think the inabilty to flash the phone may come from the inability to contact the sdcard. is there a command in fastboot that would set the partitions back up from scratch? if i can do that, i could then flash the adb drivers back on my phone, then use adb push to force the damn rom.zip onto my strorage then use clockworkmod to flash the rom? (all my grammar are belong to hulk)
i need a speedy reply as ive got my boss breathing down my neck about this (if i dont fix it they cant contact me if im not in the office or home)
Click to expand...
Click to collapse
Well, i don't really understand a thing, why people don't use recovery + S-OFF.
The best way to ensure your device works as it should and avoid future problems, is to have a custom recovery, and S-OFF, this avoids soft-bricking, and i never really understanded soft-brick term as long as you have fastboot...
You can always unlock your bootloader, and flash a recovery again, use XL Multi Tool.
Flash a recovery, flash a ROM, flash S-OFF, flash a new RUU, and as far as i know you don't need ro lock bootloader in order to flash a new RUU if you are S-OFF, so try it like this
Hope this helps
ok, so I used the all-in-one tool kit (from the development area) to root my phone. The CWM went fine. I tried to flash the explosion rom (developers area again) and when it rebooted it went into the "development purposes only" screen. I can boot into bootloader and access the hboot and fastboot options. I tried going into recovery and factory reset, but it just reboots into the developer screen again. Any advice on how to remedy this is greatly appreciated!!!
Thank you
Missing customize/mns and cid folder, flash other rom to fix.
desirech4cker said:
Missing customize/mns and cid folder, flash other rom to fix.
Click to expand...
Click to collapse
I hate to say it, but can you dumb that down a bit... I am a bit of a noob
.
Dumb version: the dev that made the rom removed folder mns and cid folder to remove htc sense stuff which is needed for htc framework, or has some missing values in the xml, if you still don't understand ask it in the explosion rom thread about the bug.
desirech4cker said:
.
Dumb version: the dev that made the rom removed folder mns and cid folder to remove htc sense stuff which is needed for htc framework, or has some missing values in the xml, if you still don't understand ask it in the explosion rom thread about the bug.
Click to expand...
Click to collapse
ok, thanks., I clicked the button for ya. So, I got the why it happened, still not sure what to do now. I did the CWM before, but now when I try to boot to recovery, it kicks me back to the "developer screen." I've tried redoing the CWM, but still can't get into it, so I don't know how to wipe everything and/or flash a new rom.
Connect phone to usb turned on even it's on developer screen or on homescreen type "adb reboot recovery" in windows cmd, be sure your on adb folder when you used to unlock your bootloader.
Then it will shut off and be in recovery, if still can't go to recovery reflash recovery.img typing "fastboot flash recovery recovery.img" in bootloader mode, then go back to fastboot and choose recovery.
desirech4cker said:
Connect phone to usb turned on even it's on developer screen or on homescreen type "adb reboot recovery" in windows cmd, be sure your on adb folder when you used to unlock your bootloader.
Then it will shut off and be in recovery, if still can't go to recovery reflash recovery.img typing "fastboot flash recovery recovery.img" in bootloader mode, then go back to fastboot and choose recovery.
Click to expand...
Click to collapse
rebooted to recovery, kicked back to "dev screen", flashed recovery.img (cwm), successful. Returned to bootlloader, clicked recovery, kicked back to "dev screen." Any other ideas? I don't know if I can click that button multiple time, but I'm going to try and I really appreciate your patience.
Ok, So I played pissed off retail customer and got them to replace my phone... Love it...
Anyways, I just had one question before I risk tanking another phone. I know a lot of people run GSM, but mine is CDMA, can I root, and run the unknown rom as laid out in the noob guide in the general discussion area? or was that part of my problem in the first place?
gsxrrocker said:
Ok, So I played pissed off retail customer and got them to replace my phone... Love it...
Anyways, I just had one question before I risk tanking another phone. I know a lot of people run GSM, but mine is CDMA, can I root, and run the unknown rom as laid out in the noob guide in the general discussion area? or was that part of my problem in the first place?
Click to expand...
Click to collapse
You could do it but I think you might lose access to your network because of the different radios but I'm not 100% sure.
If you are gonna try tho you should probably make sure you have a ruu for your network (if you can find one) so you can flash it back if anything goes wrong.
Sent from my HTC Desire C using xda app-developers app
You can't flash roms bcoz it's all for GSM that's why you got problems.
gsxrrocker said:
ok, so I used the all-in-one tool kit (from the development area) to root my phone. The CWM went fine. I tried to flash the explosion rom (developers area again) and when it rebooted it went into the "development purposes only" screen. I can boot into bootloader and access the hboot and fastboot options. I tried going into recovery and factory reset, but it just reboots into the developer screen again. Any advice on how to remedy this is greatly appreciated!!!
Thank you
Click to expand...
Click to collapse
Wait...how did you gain root and what recovery were you trying to flash that ROM with. My CDMA Desire C will not root or boot into recovery. The superuser script requires you to be able to boot a custom recovery to flash it...and all I get is the developer screen error like you. AI have posted for how to find info on building a recovery for the CDMA version, but noone has responded. And there are no sources for our CDMA version listed, which I complained to HTC about. But they misunderstood my complaint as a complaint that we were not upgraded to JB yet...dummköpfe
Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?
If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.
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