[Q] Unable to unlock bootloader / CM10 stuck at boot logo - HTC Vivid, Raider, Velocity

Good morning all,
Got stuck in a bit of a situation today so I'm looking to see if I could get some help.
Got an S-Off Vivid and tried installing CM10 on it last night. Installed TWRP, installed the ROM, and got stuck at the Cyanogenmod boot logo. Tried rebooting, relocking the bootloader, reinstalling the ROM - no luck.
Figured I should RUU and start the process all over. Used this RUU: http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe (found here: http://forum.xda-developers.com/showthread.php?p=24042047). After returning to stock and starting the bootloader unlock process, I get a successful transfer of the unlock_code.bin, but the bootloader unlock confirmation screen doesn't load up when I'm in fastboot. The device reads "fastboot usb" and my OS detects it just fine, so I was a bit confused as to why the unlock procedure wouldn't continue as I've seen it do in the past.
Any help would be greatly appreciated!

Bumpage. Anyone?

Try another USB port USB cord or new computer. Something I listed will most likely be the fix. Or reinstall driverss
Sent from my Vivid 4G using Tapatalk 2

RUU'd, relocked bootloader, unlocked bootloader, installed TWRP and CM10.
Same problem. Guessing I'm just unlucky on this one?

Went through about 16 cycles of flashing the ROM and the boot.img (even though I'm S-Off) and now it works. Hep. /shrug

Homeslice talked about fastboot flashes not taking on the first try...
If you switch again... fastboot the boot image multiple times... it may help
Sent from my Vivid 4G using Tapatalk 2

I suffered this problem as well, but I did fix it. Try booting into recovery, clear all data/factory wipe, clear dalvik/cache, clear cache, mount /system, and THEN flash CM10. Use the newest nightly. THEN flash Gapps. You want: goo-inside.me/ gapps/ gapps-jb-20121011-signed.zip (I'm new so I can't post URLS.
The other gapps will have errors later on. This is the most stable.
Thanks if helped.

Related

Phone will not boot after trying to install custom Kernel

Alright so here is my predicament.
I have a T-Mobile HTC ONE.
I am S-OFF, have TWRP 2.5.0.0 installed on my device, my bootloader says ***LOCKED*** because I locked it using revone after performing S-OFF.
I tried to install ElementalX 1.1 and after installation, my phone would not boot.
I have tried pushing a different kernel to the device and flashing that in recovery as well but I got the same result - a nonbooting device.
I tried to fastboot flash a kernel, I tried to fastboot flash a different recovery to see if that would allow me to flash the kernel and get my phone booting. No dice. I get "REMOTE FAILED" or not allowed error.
I'm at a loss right now because I didn't back up my boot partition before trying to flash this kernel and I honestly don't know what to do short of doing the HTC Unlock process again and literally losing everything on my phone.. Photos and everything. I don't have a recent PC backup either so that absolutely has to be the last resort.
ANY and ALL help will be greatly appreciated. This is the first time I've ever been in this position and not known what to try next.
Thanks in advance,
Dan
Ok so I was able to use revone to unlock the bootloader again and was able to successfully flash CWM. I tried re-flashing the kernel using CWM and the phone still will not boot.
Does anyone else have any ideas?
dharvey4651 said:
Ok so I was able to use revone to unlock the bootloader again and was able to successfully flash CWM. I tried re-flashing the kernel using CWM and the phone still will not boot.
Does anyone else have any ideas?
Click to expand...
Click to collapse
Did you manage to get back your stuffs (photos and such) yet?
What rom were you running? Just dirty flash it
Sent from my Tricked out HTC One
ryryzz said:
Did you manage to get back your stuffs (photos and such) yet?
Click to expand...
Click to collapse
No I never was able to back up my stuff but I haven't given up yet. I'm refusing to re-flash an RUU until I have exhausted all other options.
Squirrel1620 said:
What rom were you running? Just dirty flash it
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
I was running Trickdroid. I'm still trying to get it back up and running.. Going to try and fastboot flash boot.img from stock 1.29 T-Mobile ROM next and see if that can get it to boot.
EDIT>> Trying a dirty re-flash now.
EDIT2>> Seems a dirty re-flash was just what I needed. Phone is booting now. I appreciate the tip.
Wonder why trying to flash a kernel while running TrickDroid would result in a non-booting device though. Makes no sense.
dharvey4651 said:
No I never was able to back up my stuff but I haven't given up yet. I'm refusing to re-flash an RUU until I have exhausted all other options.
I was running Trickdroid. I'm still trying to get it back up and running.. Going to try and fastboot flash boot.img from stock 1.29 T-Mobile ROM next and see if that can get it to boot.
Click to expand...
Click to collapse
I believe that you can boot into your recovery, right? Did you try adb pull to grab your stuffs?
TrickDorid has its own boot.img, if you try to flash stock T-Mobile boot.img over, then I think it'll cause a mess to you ROM. Try to avoid doing that.
I advice you to try adb pull to get your stuffs and then flash a RUU over
ryryzz said:
I believe that you can boot into your recovery, right? Did you try adb pull to grab your stuffs?
TrickDorid has its own boot.img, if you try to flash stock T-Mobile boot.img over, then I think it'll cause a mess to you ROM. Try to avoid doing that.
I advice you to try adb pull to get your stuffs and then flash a RUU over
Click to expand...
Click to collapse
Well I did a dirty flash and re-flashed TrickDroid. It got my phone booting and it seems there were minimal side effects.
Think I got lucky this time.
Still don't know why a kernel flash would have resulted in a non-booting phone if it said successful.
The strangest thing is that it would actually boot but non-responsive and with a black screen. I was still able to use adb and that's how I was able to re-unlock the bootloader and try fastboot flash the kernel.
Wish I had ENG or modded hboot though so that I had extended fastboot commands and I didn't have to mess with revone but it all worked out for now.

Need help with flashing back to stock rom

Background on phone: flashed TWRP recovery 2.4.4 and unlocked bootloader
Installed Paranoid Android custom rom
Do not like low call volume issues, low Bluetooth volume issues, and doesn't recognize my wired headset as containing a mic, people cannot hear me on it.
I am wanting to go back a stock rom. I dont care if its ICS or JB, preferably ICS. It seems the there were many options to going back stock. I tried running the .exe for the RUU, you must have a relocked boot loader. I relocked the bootloader, now i am stuck with a constant loop of booting bootloader, cannot access the recovery.
So i unlock bootloader again, reinstall recovery. Then now cannot load my rom. I keep getting errors in twrp stating it cannot mount the drive(internal sd) Get same error if i try to wipe caches. So i wipe system and rom off. Now I can clear caches and error about mounting internal drive goes away.
Now I am left without a rom. In order to run .exe RUU installer I must have locked bootloader, and have rom running in usb debug, As if right now that's impossible.
My last option is flashing the BORKED rom. My version of twrp is to new, i treid to install an older version and just messed up twrp.
Any help is appreciated, and returning to stock would be awesome. Thanks
OK...
You have a laundry list of issues...
First... You should get twrp 2.5.0.0
Then... Using fastboot...
Fastboot flash recovery (recovery name)
Then reboot to recovery...
Mount USB...
Plug phone into computer...
Hopefully windows will offer to format your internal sdcard...
After that...
If you want BORKED... find wcx recovery... Flash that with fastboot... Then install borked...
Good luck
Sent from my Vivid 4G using Tapatalk 4

[Q] Serious Help Needed

Hi, I have tried being clever and rooting my HTC ONE Mini, which all went perfectly well. Unlocked Bootloader and installed TWRP.
I found a radio update on a website and tried installing it, with S-ON. As you can imagine I am not stuck in Bootloop.
I somehow managed to wipe all the data off my phone and sdcard too.
So I am stuck with a phone in bootloop with recovery from TWRP.
Everytime i try and fastboot flash any file even an Android ROM.zip it doesnt like it. I am novice at this so you are probably reading this and think what is he doing.
Can someone help me or guide me to getting my phone back and running again. Please??
wrighty29 said:
Hi, I have tried being clever and rooting my HTC ONE Mini, which all went perfectly well. Unlocked Bootloader and installed TWRP.
I found a radio update on a website and tried installing it, with S-ON. As you can imagine I am not stuck in Bootloop.
I somehow managed to wipe all the data off my phone and sdcard too.
So I am stuck with a phone in bootloop with recovery from TWRP.
Everytime i try and fastboot flash any file even an Android ROM.zip it doesnt like it. I am novice at this so you are probably reading this and think what is he doing.
Can someone help me or guide me to getting my phone back and running again. Please??
Click to expand...
Click to collapse
You can't use fastboot to flash a rom.zip! It must be pushed to your phone (use either adb push or adb sideload from recovery) and installed from custom recovery.
Btw this is the wrong forum for your device. Htc one mini forum is here

[Q] Stuck sideloading

Hey guys,
Terribly sorry if this is a common question, but after two days of searching and being unable to use my phone, I decided to post instead.
I have previously succesfully installed Cyanogen on my HTC One, using CWM. After talking to some family and friends, I decided to try out ARHD instead, as it seemed more fitting to my needs.
I download the zip, flash it from CWM, but I constantly get the error "set_metadata_recursive: some changes failed" at end of installation. I am able to continue and install seems succesful, but I can never boot past the inital white screen HTC logo. I searched for info on this, and some reported it might be due to outdated recovery. However, I have tried with CWM 6.0.4.8 and I am currently running 6.0.4.6 Touch, but no luck with either version.
At one point, I also soft-bricked my phone. I were able to flash new recovery, but had to reset my SD card and I also lost all backups. Somehow the phone booted up in Cyanogen after this, and I were able to download a zip for ARHD 81. I tried flashing this, got "set_metadata_recursive: some changes failed" and I am now unable to boot my phone again.
I have tried pushing and sideloading, however neither seems to work. Since there's no progress bar for pushing, I had to be patient, but after two hours without result I have to assume it's not working. Sideloading always gets stuck at either 3% or 8%, I can't seem to find a cause for this.
I really hope you guys might be able to work out a fix for this issue with me, as I've reached a dead end.
Unlock
I have also unlocked the phone with HTCDev unlock tool, so that should be fine.
TalkingWaterfall said:
I have also unlocked the phone with HTCDev unlock tool, so that should be fine.
Click to expand...
Click to collapse
ARHD requires TWRP Recovery
download TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
then flash it
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now your rom will install without error
Alright. I have tried installing TWRP, but I always came up with errors booting into TWRP. I got it working once, but at that point in time I didn't have the ROM zip on my phone... I'll try it out asap and get back. Thanks.
That did it. Honestly I feel a little silly at this point, but I wish it were mentioned in the main ARHD thread that you needed TWRP, since in the "You Need" section, it simply requires a custom recovery.
I'd never seen the fastboot erase cache command before, so that helped out a lot getting TWRP working
Thank you so much!
TalkingWaterfall said:
That did it. Honestly I feel a little silly at this point, but I wish it were mentioned in the main ARHD thread that you needed TWRP, since in the "You Need" section, it simply requires a custom recovery.
I'd never seen the fastboot erase cache command before, so that helped out a lot getting TWRP working
Thank you so much!
Click to expand...
Click to collapse
Your welcome

I have failed at flashing

Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!

Categories

Resources