Hey guys so this is the first time I try to throw a new Rom on my one ever since I got it last year and threw SuperUser on it (this is the thread I used, yes I am on a Mac http://forum.xda-developers.com/showthread.php?t=2245782) . Tonight I was able to start the install for ViperOne (http://forum.xda-developers.com/showthread.php?t=2345410) and everything was going good until the end, got a message saying there was a problem w/ installation 7 and to keep the log. Than I got a message saying that I may have lost root access and if I wanted Clockwork to fix it, I selected yes. And now I am on an ongoing loop. I get the green HTC logo saying "entering recovery" on top and than the recover flashes and goes back to HTC screen with the text "This build is for development purposes only..." and starts all over again. I am able to get into HBOOT and the top says ****Tampered**** ***Unlocked*** S-ON. I tried going thru the original thread and everything but I am stuck. Can't get into recover or anything.
Like I said earler, this is my second time doing this so I didn't clear anything prior to starting the ViperOne flash, I wasn't sure if I needed to. Anybody ever have this problem before? Or can someone help me out please?
I appreciate any help guys!
GCRamiro said:
Hey guys so this is the first time I try to throw a new Rom on my one ever since I got it last year and threw SuperUser on it (this is the thread I used, yes I am on a Mac http://forum.xda-developers.com/showthread.php?t=2245782) . Tonight I was able to start the install for ViperOne (http://forum.xda-developers.com/showthread.php?t=2345410) and everything was going good until the end, got a message saying there was a problem w/ installation 7 and to keep the log. Than I got a message saying that I may have lost root access and if I wanted Clockwork to fix it, I selected yes. And now I am on an ongoing loop. I get the green HTC logo saying "entering recovery" on top and than the recover flashes and goes back to HTC screen with the text "This build is for development purposes only..." and starts all over again. I am able to get into HBOOT and the top says ****Tampered**** ***Unlocked*** S-ON. I tried going thru the original thread and everything but I am stuck. Can't get into recover or anything.
Like I said earler, this is my second time doing this so I didn't clear anything prior to starting the ViperOne flash, I wasn't sure if I needed to. Anybody ever have this problem before? Or can someone help me out please?
I appreciate any help guys!
Click to expand...
Click to collapse
You need to update your custom recovery to TWRP 2.6.3.3 then flash your rom
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
clsA said:
You need to update your custom recovery to TWRP 2.6.3.3 then flash your rom
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks! I'll start right on it.
I was able to flash twrp but I don't have an option for erase cache. I selected reboot bootloader tried to go into the recovery but it flashes a bit than goes back into the loop.
So I was able to clear the cache and everything, I just now need to find a way to get the zip on the phone. For some reason I can't see it anymore. Could it be because I flashed it once already?
And I was able to install the Rom succesfully! Thanks for the help. I learned how to push the rom in tonight and got it going. Now I'm having a problem with the Viper One rom. Have any of you guys used the rom? I go thru everything, flash successfully but after I go thru all the steps for the setup, I get a mesage saying "Unfortunately Setup has stopped" and my only option is to hit Ok. Once I do that I go to a black screen and thats it. I tried to reboot the phone but it stays on the Viper One logo for 10 minutes now.
Related
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
So, did you unlock the bootloader before trying to flash the ROM?
Does it say "Unlocked" at the boot logo now?
Get back into fastboot and flash romracer's recovery and then try to mount the storage and get another rom on there.
SDRAKE101085 said:
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
Click to expand...
Click to collapse
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Well, you mentioned you can get into fastboot so that's a start. You can try to flash a proper recovery and try to boot into recovery and see if you can mount the storage, or if you have a card reader you can just put a ROM on your sd card and then flash. If you can't get into recovery but you can get into fastboot you can flash a rom that way. You'll have to search for the procedure but I'm almost certain it can be done. If all else fails, you can install the unlocked "Full" SBF through RSD Lite, but it is not really recommended but should work.
SDRAKE101085 said:
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Click to expand...
Click to collapse
Thanks so much. I got radracers on there and reflashed the neutrino rom again. Everything appears to be working. Now to just figure out the rest.
Thanks again.
Look tke the sd card and load the rom and google apps. Then go and fastboot wipe and re install the rom and try to boot honestly it just sounds like you got a corrupted rom
I have the Evo LTE S-on (HTC bootloader unlocked) and TWRP installed. The only problem I'm having is that I cannot seem to get .zip files to open from the install menu in TWRP (recovery). I factory reset and try to open the zip from the install menu but it just says "Failed". Specifically I am trying Kushdeck's new CM10 ROM. Any help would be greatly appreciated. Thanks.
PS. Not sure if this will help but on the install menu my files show up twice, the first time with the normal naming and the second with "/." in front of them.
Did u try and re download it again? Sounds like a bad DL if it keeps failing after a couple of attempts
Sent from my EVO using Tapatalk 2
Ok I'm trying that now. I'm also wondering if there's a problems with my /ext-sd because everytime I factory reset it says it couldn't access that. Do you think that has anything to do with it? Is reinstalling TWRP an option?
Ok thanks so much the re-download did it. But now I'm at a black/blank screen after start up. I factory reset, installed the CM10 ROM then Gapps and wiped the dalvik/cache. Then when I reboot it just goes to the HTC screen and after that nothing. Ideas?
This is going to sound strange but try factory restet, wipe cache/dalvik and then just reboot without trying to flash anything.. I've been having some similar issues as mine isn't recoglizing any MD5 when i try to flash a new rom.. I wiped my phone and have tried to flash a few roms and it fails every time and in wiping my phone it somehow took out my backup so without any other options (that I knew of) I just rebooted and luckily it loaded a completely bare vipor rom like what I started out with when I originally rooted.. BTW, did you create a backup before trying to flash? Should always make a backup....
Ya I had backed up. Turns out I needed to manually flash the boot.img which fixed the issue
elitelimfish said:
Ya I had backed up. Turns out I needed to manually flash the boot.img which fixed the issue
Click to expand...
Click to collapse
Thanks for this. I had the same problem, (S-ON, TWRP. black screen on boot). I was able to flash stock-based ROMs, but not CM10, so I suspected it had something to do with the things that HTCDev won't allow the recovery access to, but the logs from TWRP didn't throw any errors, so while I suspected boot, I didn't know what to do about it. And everyone knows that it's easy to be caviler with everything is working, but as soon as you start having problems, you get gun shy about trying things.
Your post was the solution for me. Extract the boot.img file found inside the zip or your chosen ROM, and flash it using fastboot:
"fastboot flash boot boot.img"
heywetried said:
Thanks for this. I had the same problem, (S-ON, TWRP. black screen on boot). I was able to flash stock-based ROMs, but not CM10, so I suspected it had something to do with the things that HTCDev won't allow the recovery access to, but the logs from TWRP didn't throw any errors, so while I suspected boot, I didn't know what to do about it. And everyone knows that it's easy to be caviler with everything is working, but as soon as you start having problems, you get gun shy about trying things.
Your post was the solution for me. Extract the boot.img file found inside the zip or your chosen ROM, and flash it using fastboot:
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Hey out of curiosity did you like any of the stock based ROMs? If so which ones? I kinda wanna try one out but haven't settle on one
I have a slight problem with my phone right now. I got the great idea to try and build a rom just for myself in kitchen based off the Telus 1.15.661.11 base. Everything appeared to work correctly, I got my rom flashed and working fine, haven't had any problems with it besides a FC issue with the HTC Sense input but i just uninstalled it as i use swiftkey anyways.
The problem is I can no longer access TWRP, I can get into the bootloader fine just when i select recovery it shows the TWRP logo then goes to a black screen and then proceeds to boot into the system. I have no idea how to fix it and but here's what I've tried so fair:
-Reflashing the recovery via fastboot
-Flashing a rom via fastboot (Can't be done gives me some remote denied error, i assumed because its still s-on?)
-Reflashing boot.img via fastboot (Figured it was worth a attempt?)
-Trying to reboot into recovery (Same thing happened, went from black screen to boot. Also i should note I could not get the phone to reboot via adb but could via the cwm rom manager (I just used it to reboot nothing else))
-Factory Reset from bootloader (didn't appear to do anything)
The one thing I have not tried is an RUU, however this was because first off i had difficultly locating one (I had the link somewhere but lost it) and second I don't think there is one for Telus (Although i would assume an ATT one would work?). Also ill try to locate the rom that i flashed, and maybe someone would be able to look at it and see what went wrong. Any help/ideas would be greatly appreciated to try and help restore my recovery.
EDIT: So i ran the ATT RUU and it failed towards the end of the process and I went through the recovery process. Then i re locked and unlocked my bootloader and after that i went to reboot into recovery and it works again. So im not sure what happened but if anyone has some insight it would be nice to know for the future.
Hi guys, got a htc dna, unlocked fine the bootloader, installed clockwork recovery.
Did a fastboot flash recovery and entered the recovery.
Tried to install viperrom, at first it was going just fine, when i entered the installation process(after all the choices), phone crashed unexpectedly, and reboot. Tried to enter again recovery, it crashes. No rom now, the phone shoes white htc screen.
Still having fastboot option, i tried flashing again recovery,flashes just right, but then again after i start it,it just crashes!!!
I had previously done the same process in htc one x, without problems. Now in droid dna, i can't understand what went wrong!!!
Any ideas, what to do???!!! THanks!
lock plz wrong section, sorry!!!!
Link to recovery used , try cwm from official website
the real signature is not visible in tapatalk
Ok so I searched the forums before this just to let you know.
I wasn't thinking and the wrong kernel got installed as the title says. So, I got into a bootloop (expected). It hits the fan after my next step :'(
I go to bootloader, then to recovery, start up TWRP, then screen goes blank and goes back to the htc bootscreen.
The odd thing is, it now has that disclaimer on the bottom for normal boot sequence.
I have attempted flashing other recoveries, erasing my cache, fastbooting roms, and fastbooting kernels. I assume my choices are limited with S-On since most of the fastboot commands return "remote:not allowed".
Do I have to wait for a RUU?
Thank you for your time in advance
UPDATE:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
IF YOU FOUND THIS BY SEARCHING
1. Fast boot flash recovery "recovery file" (I used clockwork non touch)
2. Fast boot erase cache MUST!!!
3. Boot recovery
4. Sideload Rom via adb
seamarshall said:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
Click to expand...
Click to collapse
Glad to hear you got it working again. Anytime you install a custom ROM though, you will see the disclaimer on the bootscreen. It isn't a big deal software wise though, it just looks ugly. I'd consider that a minor inconvenience for using a better ROM without the bloat.