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.
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
Hey i just PG41IMG-WIFI-light-B10 through the bootloader, at PG41IMG.zip and now its just bootlooping with the htc quietly brilliant logo.
i had s-off/revolutionary and rooted with stock gingerbread.
Im realy worryed guys have i just bricked my tablet? how can't turn it off :S nothig does anything
just got it into recovery through abd, does it recharge in recovery?
reading is fundemental.
You flashed the light version which requries and assumes you would be flashing a rom directly there after. So if you try to just boot after flashing it there is no system to boot into, thus boot loops.
Yes you should be able to charge in recovery and or power off through fastboot and charge
you just need to flash a rom and you will be good to go. Place the rom on your ext sd and enter recovery and let her rip
Just fixed it, have no idea what i did wrong, but just installed leedroids rom after getting into recovery, can someone delete this thread?
mcord11758 said:
reading is fundemental.
You flashed the light version which requries and assumes you would be flashing a rom directly there after. So if you try to just boot after flashing it there is no system to boot into, thus boot loops.
Yes you should be able to charge in recovery and or power off through fastboot and charge
you just need to flash a rom and you will be good to go. Place the rom on your ext sd and enter recovery and let her rip
Click to expand...
Click to collapse
Yeah i did read it all but it would just loop and i couldn't get it into recovery/fastboot wasn't detecting it.
it was stuck with no seeable way to
But adb was detecting it and managed to get it to reboot into recovery, i already had the rom ready on the sd card.
And god that noise it makes when looping could drive you nuts.
And yeah i did read it, read more than id like to admit lol
yes the part about not getting past the splash screen i do nto believe is in the instructions. for future notice if you are stuck in a boot loop you can just hold volume down and power. it will eventually boot into hboot
mcord11758 said:
yes the part about not getting past the splash screen i do nto believe is in the instructions. for future notice if you are stuck in a boot loop you can just hold volume down and power. it will eventually boot into hboot
Click to expand...
Click to collapse
yeah i tried that for ages, that was why i was so worried.
Not having a removeable battery there was no way i could see of getting out of it.
Its more luck than anything that i found the abd command to reload in recovery.
was worried it was that problem where it doesn't recharge. (yes paranoid i know)
But anyway, it all turned out fine
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.
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer
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.