I've got the Dev edition and when I try to flash a ROM I just get stuck at the boot slash screen.
e.g. I flashed the Carbon ROM and it just stuck on the Carbon logo (I left it for nearly 2 hours just to test) Same with the CM10.1 Alpha which stayed on the spinning CM logo.
I've made sure to wipe everything and I've re-downloaded multiple ROMs and tried.
Things like the Logo2Menu work and I'm actually running it. Restoring from TWRP backup works as well.
Hi
Greetings,
After you install the Rom
Extract the boot.img from the rom and put that file into your abd/fastboot folder and connect your phone to pc with your phone in bootloader and type the following code
"fastboot flash boot.img"
"fast boot erase cache"
Later reboot
Sent from my HTC Sensation Z710e using xda premium
Related
Unlocked bootloader with fastboot oem unlock
Rooted phone with fastboot by pushing a boot img to it(bexboot.v2.GRK39F_OTA)
Downloaded ics.zip(the partition scheme for ics based roms)
downloaded aokp passion ics rom
downlaoded gapps
Flashed all of them in cwm
But when i boot, it just stays at the aokp unicorn screen.
So far ive gotten back to point A again.
1.) put passimg.zip on sdcard, rebooted with power+down, it restored to stock 2.3.6
2.) Used bexboot boot.img to give me root - http://code.google.com/p/bexboot/
3.) installed rom manager, flashed cwm recovery
4.) Installed Blockrose, via blackrose.exe
5.) booted into cwm, installed ics.zip(which should partition the hboot/blackrose), installed the aokp zip, and the gapps, rebooted.
Stuck on unicorn logo screen again....
I think i need some help now...one thing i noticed, theres no more LOCK icon
1.did you wipe all partitions except sd before and after installing the hboot zip?
2.are you sure that your hnoot partition was changed after applying ics.zip?
Sent from my Nexus One using Tapatalk
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.
hello, I hope you manage to help me.
yesterday I was updating the rom of my m7, I had revolution hd 6 and I was updating to 6.1.
Now the phone goes into bootloop, if you try to enter the bootloader enters correctly, but then if I try to get into recovery after loading screen appears dark of recovery for a while (less than a second) and then restart the white screen htc that says "entering into recovery" and loops as well ..
the most logical solution that I've come up with is to reinstall the original ROM or via fastboot .. but I can not find file or driving ..
ps I'm new to htc, samsung android coming from \ sony \ motorola
thanks in advance!
Did you try to install recovery once again?
Now do this commands:
fastboot erase cache
fastboot flash recovery recovery name.img
fastboot erase cache
Go to recovery and install your Rom
Sent from my HTC One using xda premium
thsnks for reply.
yes, but the problem is again.. but not have test to delete cache.. i try now it
Damianoo said:
hello, I hope you manage to help me.
yesterday I was updating the rom of my m7, I had revolution hd 6 and I was updating to 6.1.
Now the phone goes into bootloop, if you try to enter the bootloader enters correctly, but then if I try to get into recovery after loading screen appears dark of recovery for a while (less than a second) and then restart the white screen htc that says "entering into recovery" and loops as well ..
the most logical solution that I've come up with is to reinstall the original ROM or via fastboot .. but I can not find file or driving ..
ps I'm new to htc, samsung android coming from \ sony \ motorola
thanks in advance!
Click to expand...
Click to collapse
Hey!
Please try this:
- Download and start the All-In-One Toolkit http://forum.xda-developers.com/showthread.php?t=2183942
- Plug in the USB cable
- On your device enter the bootloader
- Enter Fastboot
- In the toolkit choose "Erase Cache" below "Commands"
Now you should be able to enter the recovery again. There you can reinstall the ROM or restore a backup. At least this worked for me.
Regards
Damianoo said:
thsnks for reply.
yes, but the problem is again.. but not have test to delete cache.. i try now it
Click to expand...
Click to collapse
You must copy boot.img from Mike in adb than flash Boot.img.
fastboot flash boot boot.img
fastboot erase cache
Sent from my Maximus One Beast
best! now recovery work fine..! (erase cache in fastboot)
now try to reinstall rom
but.. for my info.. why this situation? into all off my previus devices it did not happen
thanks!
Idk but hey post your issues in q n a or use the search option
Sent from my Nexus 7 using xda premium
Since the device is S-ON, you have to flash boot.img manually via fastboot (except ROMs like TrickDroid, which has a script inside to flash boot.img from Recovery), otherwise it will stuck in bootloop.
For Recovery-Problems always fastboot erase cache is good, u should use it everytime after flashing recovery.img/boot.img.
LG, Helmut
now.. i've tryed to reinstall rom.. into install the setup stop at 30%, restart phone with sound down+power, now phone boot fine..
mmm this isn't good..
now with titanium do a backup and after go to full wipe...
hd2neuling said:
Since the device is S-ON, you have to flash boot.img manually via fastboot (except ROMs like TrickDroid, which has a script inside to flash boot.img from Recovery), otherwise it will stuck in bootloop.
For Recovery-Problems always fastboot erase cache is good, u should use it everytime after flashing recovery.img/boot.img.
LG, Helmut
Click to expand...
Click to collapse
but here i see not need with this rom boot.img into fastboot!
http://forum.xda-developers.com/showpost.php?p=40632524&postcount=4395
idk if ARHD got the flashscript for boot.img included and if mike changed boot.img/modules in 6.1
LG, Helmut
About an hour ago I went from the Cyan Fox rom to the new ViperRom and in Viper rom I had it install the newest version of TWRP. So I put my phone down for a couple minutes while I went to grab a snack, came back, and then it was on the htc quietly brilliant screen. So then I tried to boot into recovery and it just restarted. So somehow the viper installer wiped my rom and twrp from my phone. Fastboot and ADB work. Here's what I tried so far.
Tried to flash the latest version with TWRP from fastboot. It finishes but when i try to go into recovery it just reboots back to the HTC screen.
Tried to adb pull my internal storage with adb pull /sdcard/ but i get "remote object '/sdcard/' does not exist"
Does anyone know how to fix this? I remember doing this with my friend's nexus 4.
Thanks!
Sometimes I get this with Windows 8.1 even with my path environment updated with adb/fastboot..so I actually change directories all the way to platform- tools to fastboot flash recoveries and it works....just a suggestion for u.
Worse case is ruu
Sent from my HTCONE using Xparent Red Tapatalk 2
Solved
I figured it out, the Viper installer installed TWRP for the GSM One and it overroad my old TWRP. I finally got TWRP installed over fastboot but thanks.
My phone has CM11 snapshot M8
Earlier tonight Google services on my phone crashed and couldn't restart, the error message just kept coming up, so I decided to reboot.
When it tried to turn back on, it was stuck on the boot animation for about an hour, so I decided to go into recovery and wipe the dalvik cache.
But before I can press the wipe button, the teamwin logo just shows for a couple seconds and the screen turns black. Then the phone tries to reboot into system again. Which of course leads me back to getting stuck on the boot animation.
I tried it multiple times, but it just keeps going through the loop. My computer doesn't recognize my phone in fastboot either. Damnit.
What should I do now?
alex93310 said:
My phone has CM11 snapshot M8
Earlier tonight Google services on my phone crashed and couldn't restart, the error message just kept coming up, so I decided to reboot.
When it tried to turn back on, it was stuck on the boot animation for about an hour, so I decided to go into recovery and wipe the dalvik cache.
But before I can press the wipe button, the teamwin logo just shows for a couple seconds and the screen turns black. Then the phone tries to reboot into system again. Which of course leads me back to getting stuck on the boot animation.
I tried it multiple times, but it just keeps going through the loop. My computer doesn't recognize my phone in fastboot either. Damnit.
What should I do now?
Click to expand...
Click to collapse
Hold down the power button and the volume down together, the lights on the bottom will flash 10 to 15 times, the phone will go off, at this point, release the power button but continue to hold the volume down, this will take you to the bootloader, post a screen shot of your bootloader please.
Seanie280672 said:
Hold down the power button and the volume down together, the lights on the bottom will flash 10 to 15 times, the phone will go off, at this point, release the power button but continue to hold the volume down, this will take you to the bootloader, post a screen shot of your bootloader please.
Click to expand...
Click to collapse
Here it is. What do you see?
alex93310 said:
Here it is. What do you see?
Click to expand...
Click to collapse
flash twrp again, clear cache and boot in recovery:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
use twrp 2.7.1.1 with cm11
and your fastboot issue is probably caused by your computer OS. Windows 8.1 isnt compatible with hboot 1.44.
418
alray said:
flash twrp again, clear cache and boot in recovery:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
use twrp 2.7.1.1 with cm11
and your fastboot issue is probably caused by your computer OS. Windows 8.1 isnt compatible with hboot 1.44.
Click to expand...
Click to collapse
Luckily fastboot decided to work this time.
First I used the recovery I originally had in my computer but it said "error: cannot load 'twrp.zip'"
Then I tried downloading it from the official website again but it showed the same error message.
I'm running Windows 7 btw.
alex93310 said:
Luckily fastboot decided to work this time.
First I used the recovery I originally had in my computer but it said "error: cannot load 'twrp.zip'"
Then I tried downloading it from the official website again but it showed the same error message.
I'm running Windows 7 btw.
Click to expand...
Click to collapse
its an img file not a zip file.
Code:
fastboot flash recovery (recovery_name)[B].img[/B]
fastboot erase cache
fastboot reboot-bootloader
alex93310 said:
First I used the recovery I originally had in my computer
Click to expand...
Click to collapse
you must use twrp 2.7.1.1 with CM11
from cyanogen team:
Recovery Update
Beginning with nightly 20140501 (or milestone 7, if you prefer the stable channel), several HTC devices are being transitioned to a new fstab layout. This will not affect your data. This change requires kernel support in recovery for CyanogenMod packages to install.
Affected devices include:
evita - HTC One XL
fireball - HTC Droid Incredible 4G LTE
jewel - HTC EVO 4G LTE
m4 - HTC One Mini
m7 - HTC One [GSM]
m7spr - HTC One [Sprint]
m7vzw - HTC One [Verizon]
ville - HTC One S
jewel and ville users: This is not the /data/media transition. That change is still being ruled out because there is simply no migration path that preserves data. With that said, if you are running an unofficial build of CyanogenMod that also incorporates this fstab change, TWRP recoveries are available from mdmower.cmphys.com. Look for jewel-dm and ville-dm in the filenames.
All of these recoveries are backwards compatible.
ClockworkMod recoveries with version greater than or equal to 6.0.4.8 support this fstab change. HTC One AT&T (m7att), HTC One T-Mobile (m7tmo), and HTC One non-US GSM (m7ul) can safely use the recovery for the generic "HTC One" (m7). Note: version 6.0.4.8 for m4 may have been built before by-name support was added to the kernel.
More recent builds of ClockworkMod recovery can be found at unstableapps.com
TWRP recoveries with version greater than or equal to 2.7.0.8 support this fstab change.* If you have a favorite recovery maintainer, encourage them to incorporate "block: by-name" support into their recovery kernels!
(*) Official 2.7.1.0 for m4, m7, m7spr/m7wls, and m7vzw/m7wlv mistakenly did not include the necessary fstab support, so 2.7.1.1 was released for these devices, addressing the issue.
More recent unofficial builds of TWRP can be found at mdmower.cmphys.com. You'll find source code for all these devices linked there as well.
Click to expand...
Click to collapse
ref: http://wiki.cyanogenmod.org/w/HTC_fstab_updates
and like said above, you are not entering the right command, recovery is a .img file
so try to flash twrp again, erase cache, reboot bootloader, boot in recovery and wipe cache/dalvik. if it doesnt work, reflash the rom after a full wipe/format
Seanie280672 said:
its an img file not a zip file.
Code:
fastboot flash recovery (recovery_name)[B].img[/B]
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
alray said:
you must use twrp 2.7.1.1 with CM11
from cyanogen team:
ref: http://wiki.cyanogenmod.org/w/HTC_fstab_updates
and like said above, you are not entering the right command, recovery is a .img file
so try to flash twrp again, erase cache, reboot bootloader, boot in recovery and wipe cache/dalvik. if it doesnt work, reflash the rom after a full wipe/format
Click to expand...
Click to collapse
LOL wow what a noob mistake :silly:
Yeah I had 2.7.1.1 all the time, both the original one on my computer and the newly downloaded one.
The .img file flashed successfully and erased the cache from fastboot, but the issue has not changed at all.
I went through the process twice and still no hope
I noticed something different though. I have a custom boot animation. Now whenever I try to boot it straight into system, it shows splash screen>CM original boot animation>splash screen>custom boot animation. This does not happen when it reboots itself when I try to go into recovery. It's just the normal splash screen>custom boot animation.