Database Develop

What's wrong with my phone!!!

Okay, so i've been on and off these forums and never decided to create an account until now. (I know you guys see these types of threads a lot)
I have an HTC Vivid and can't get it to boot. Whenever I try turning it on, it goes into fastboot (I have bootloader unlocked) or HBOOT.
I have tried getting CWM on it, but whenever it reboots, it gets stuck at the HTC logo like when you usually boot.
I can re-lock the bootloader, but it wont change a thing.
Also, when I type [adb devices] my device doesn't show up, but the phone says FASTBOOT USE.
When I try a factory reset, all it does is reboot the phone. Also I do not have a SD card with me.
This is my second HTC Vivid (the first one was rooted successfully with the Illiminati ROM but had a malfunction so I got a new one under warranty)
I have been using this guide: http://forum.xda-developers.com/showthread.php?t=1450396
and this program: http://forum.xda-developers.com/showthread.php?t=1498003 (which may be the cause to all of this idk)

I would invest in a cheap micro sd. I used the zip from the guide thread to restore mine back to stock (although I believe you have to relock bootloader first) and then try to unlock and root etc after that. I know that may not help if you have no way to get an sd. But they are always handy!
Sent from my HTC PH39100 using XDA App

We need more details as to how this happened. What did you do/trying to do when it started messing up?

oem relock and flash original ruu to go back to stock then go back through steps...

Wild Child said:
oem relock and flash original ruu to go back to stock then go back through steps...
Click to expand...
Click to collapse
this would be correct

i agree with above post. +1
a god is coming so you know

Wild Child said:
oem relock and flash original ruu to go back to stock then go back through steps...
Click to expand...
Click to collapse
I try doing this but cmd gives me:
... INFO[ERR] Command error !!!
i have the HTC drivers

DjSpunz said:
I try doing this but cmd gives me:
... INFO[ERR] Command error !!!
i have the HTC drivers
Click to expand...
Click to collapse
You shouldn't be flashing the RUU thru cwm, it's a program that is ran on the computer

doktor buknasty said:
You shouldn't be flashing the RUU thru cwm, it's a program that is ran on the computer
Click to expand...
Click to collapse
What program?
Im a noob at this and this is my first android phone...
I'm good at listening to instructions so can someone please tell me what to do step by step???
I can't unlock bootloader, as it gets stuck at the boot screen

DjSpunz said:
What program?
Im a noob at this and this is my first android phone...
I'm good at listening to instructions so can someone please tell me what to do step by step???
I can't unlock bootloader, as it gets stuck at the boot screen
Click to expand...
Click to collapse
fastboot oem lock is the command.
From there, get ruu.exe, connect phone to computer, run the ruu by doubleclicking on the computer, follow the directions of the ruu program.
From there you can unlock the bootloader using the guides posted and flash recovery, then flash custom rom.

DjSpunz said:
What program?
Im a noob at this and this is my first android phone...
I'm good at listening to instructions so can someone please tell me what to do step by step???
I can't unlock bootloader, as it gets stuck at the boot screen
Click to expand...
Click to collapse
If you've never done fastboot or adb before, my guess is that you are probably running stock. If that's the case, got to htc's website and download the drivers for the Vivid, then plug your phone in and proceed to run the RUU.exe. If the drivers are properly installed, the RUU should detect your phone and update it to ICS (make sure to back up your files as phone storage will be erased as well).

[Q] developer screen??

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

[Q] HTC One Bricked (bootloop)

Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.

megahafo said:
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
Click to expand...
Click to collapse
What is happening when you enter recovery?

MacHackz said:
What is happening when you enter recovery?
Click to expand...
Click to collapse
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.

megahafo said:
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
Click to expand...
Click to collapse
try reflashing it and wiping cache etc

MacHackz said:
try reflashing it and wiping cache etc
Click to expand...
Click to collapse
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.

Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?

tokenwoken said:
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
Click to expand...
Click to collapse
The cue there if wiping the cache partition.

Riyal said:
The cue there if wiping the cache partition.
Click to expand...
Click to collapse
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?

Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash

tokenwoken said:
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Click to expand...
Click to collapse
I had the same problem, going to try to sideload this stock de-odexed rom (didn't work the first few times) and CHILL THE PHUCK out until AOKP.
scared me lol first HTC device, brand new, and I thought I broke it.
P.S I realized that REVOHD uses AROMA, that's why it wouldn't sideload.... Am I Rite?

Similar issue
tokenwoken said:
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
Click to expand...
Click to collapse
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!

Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

thanks but....
shrex said:
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.

suhazgummadi said:
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
Click to expand...
Click to collapse
You have the zip file of ARHD in your pc extract the boot.img using winrar thats it and you have to put that file in abd/fastboot folder in pc
and everything what i said its to be done in pc
excpet putting phone in fastboot mode

suhazgummadi said:
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Click to expand...
Click to collapse
The Sprint version is never going to work on any carrier other than Sprint. It's a CDMA device. The sim slot if for connecting to Sprint's LTE network, but requires a CDMA connection first and foremost to work at all.
Sent from my HTC One using xda premium

Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
megahafo said:
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Click to expand...
Click to collapse

Quickest and easiest way to fix this issue is...
'fastboot erase cache'
'fastboot reboot recovery'

hnt20 said:
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
Click to expand...
Click to collapse
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?

HumorousMaximus said:
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
Click to expand...
Click to collapse
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:

mky4b11 said:
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
Click to expand...
Click to collapse
Thanks for the tip, I was able to get back into AROMA but the original issue that got me to this point came up again. Aroma installer runs and during the install it kicks itself out and sends me back to recovery, so the installer doesn't complete. It gets to about 30% and craps out just after it writes system data and starts to install the .apk's. Screen goes black and it reboots itself and sends me to recovery.
thoughts?

[Q] HTC ONE M7 - Can't unlock bootloader after it is relocked

i have searched high and low for help on this one and can't find anything similar.... Though I found one thread that suggests I attempt the HTVDEV unlock code 5 times in a row.. Which did not work.
I returned my phone to stock several weeks ago. Locked the boot loader (see pic#1) Then I had something weird happen , where The phone rebooted to a "enter password to decrypt"??? I never encrypted my phone. So I read the only way around this was to do a factory reset. So, I rebooted the phone into bootloader and attempted a factory reset. The phone then rebooted and is frozen on the HTC splash screen. See pic#3
I have attempted to unlock the bootloader so I can flash a good recovery (which I cannot access, then will just reboot)
So basically I only have access to fastboot. When I plug in the phone into windows, I cannot access through ADB. (Same thing in Linux)
Any help would be appreciated.
Thanks

Have you attempted an RUU?

sauprankul said:
Have you attempted an RUU?
Click to expand...
Click to collapse
I could not get an ADB connection. I attempted to flash a new recovery, but of course with no root, s-on and bootloader locked... no dice.

charlesairman said:
I could not get an ADB connection. I attempted to flash a new recovery, but of course with no root, s-on and bootloader locked... no dice.
Click to expand...
Click to collapse
Can you get into fastboot?

sauprankul said:
Can you get into fastboot?
Click to expand...
Click to collapse
fasboot yes for me. i can get to the point to unlock the bootloader, but it freezes when i tap "yes"
Gentleman, any luck on this?

preslav88 said:
fasboot yes for me. i can get to the point to unlock the bootloader, but it freezes when i tap "yes"
Gentleman, any luck on this?
Click to expand...
Click to collapse
Yeah and all you can do from fastboot with those restrictions is, erase cache. Erase it like 3 times in a row and see if it works, who knows. I flashed cwm recovery which sometimes gets me into recovery, like 1 out of 10 recovery flashes. then you are allowed to finally use adb commands

[Q] Need to unlock bootloader, but borked device

Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?

Few threads about this today. Seems a regular user error. Can't think of a fix right now..

rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.

boot to bootloader, fastboot oem unlock from fastboot command console on computer.

TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.

Have the same problem and try to solve it with Motorola. No luck at the moment.

lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot

simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22

rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.

TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.

rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...

Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.

I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).

You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.

beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???

simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).

I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?

efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...

You're all using the newest fastboot?

flash the factory img
edit.. nevermind, i see ive already said that