Database Info

Can't get my G1 into recovery mode.

Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7

Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.

Dharkaron said:
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Click to expand...
Click to collapse
i tried and did not work

natienn said:
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Click to expand...
Click to collapse
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.

andonnguyen said:
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
Click to expand...
Click to collapse
how do you flash to the original theme? do you know of any links? thanks

Start holding the Home button before you press the Power button.

jashsu said:
Start holding the Home button before you press the Power button.
Click to expand...
Click to collapse
i tried that in different time lentghs from 10 seconds holdin both to 2 minutes, of course pressing the home key 1 sec before the power and holding both

Same problem
Need to bump this thread as I'm having the same issue. Have a HTC Dream with CyanogenMod-5.0.7-DS, trying to go to 5.0.8, but cannot get into Recovery Mode.
Yes, I am completely powering the phone off, holding Home just prior to pressing & holding Power. I keep both depressed for a few minutes and no joy, just sits at the G1 splash screen. I can remove the battery and press Power to bring the phone up normally. Have even dropped to the console, switched to root and issued "reboot recovery". The phone restarts and sits at the G1 splash screen as well.
Can anyone offer advice on how to restore my Recovery Mode? Many thanks...

You can try to reflash (or flash another) recovery with adb, fastboot or in terminal. Btw this thread is in wrong section. It should be in Q & A section.

You could even flash a recovery image from within your rom...you said you could boot the phone normally correct?
So drop into terminal and flash it if you don't want to mess with adb.
The Amon Ra 1.7 Recovery thread has the commands you need to flash through terminal...

These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.

yutsoku said:
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
Click to expand...
Click to collapse
Why would you need to reroot it, just flash a new recovery through fastboot.
fastboot flash recovery <name>.img

misread, yeah he could do that too but it would be easier to reroot if he knows how to do that... instead of learning a whole new method.
You're right though, that would be better.

Update
I am able to fastboot by holding the camera button in and powering on. It sounds like I just need to do the Amon Ra Recovery procedure in order to restore my recovery partition. I assume that I'll need to re-root, but I'm sure there are instructions there for that as well.
Thanks for all the quick replies!

So here's what I found....
I had the exact same problem, but first a little history then how I fixed it.
I purchased an 8GB MicroSD card so I could use Apps2SD and was quite pleased with the ability to do so. Until my battery life dropped to 5mins. It was already down from when I bought it last year.
The battery was severely screwed on my. If I used ANYTHING for more than 5 mins, it would die and would NOT boot up. Oh I could pres the power button and it would try to boot but then die somewhere in the boot process. That is until I plugged it into some charger (car or wall) and then it would boot, showing anywhere from 70 to 90% battery life.
After much research I found that it was the battery and so ordered a replacement off eBay from Hong Kong. $3.96 shipped to my door. Works great, and I am incredibly thankful for that.
So just prior to getting the battery I had done an upgrade to 5.0.8 with the vain hopes that it might help limp along but to no avail. The battery was gone.
Ok, so in comes the new battery. Great! I'll just reflash the ROM to make sure there are no lingering issues and we'll be good to go! Little did I realize that I did an 'upgrade' from CM Updater and when I booted into Recovery I flashed th zip file that was there....which was 5.0.7. DOH! No biggie, everything was working so I didn't worry too much.
Then I installed Clockwork's ROM Manager 1.8.x. A few days later there was an update, so I updated to 2.0.1.3. So I updated that. It went fine.
Few days later, and a few more apps re-installed, the system was running slow.
Apps2SD was greyed out. Huh?
Checked the card....Ubuntu was only mounting it Read Only. And the old swap partition, which I thought I had deleted, was still there. Dammt. But this s a side story I think.
So I wanted to reflash but there was no way I could do it because I could not get into Recovery mode. Ugh.
ROM manager had an update to 2.0.1.4. Ok, maybe that'll work. Nope. It said it updated fine but stuck at G1 logo like many others.
Doing some googling around I saw that it was a ROM Manager issue and that you should flash back down to 1.4.x. Well, since I knew it was working at 1.8.x I decided to reflash to 2.0.0.3. I could get into recovery mode now!
While this kinda solves one issue....I'll have to go into another thread to figure out the Read Only problem so I can re-partition my card again.

Thread closed. Please post questions in the Questions and Answers forums and not in the development forum.

[Q] CM 10.1 Permanent Soft Brick?

Running CM 10.1, 06/08 Nightly
I did search the threads and google, but could not find any posts about a phone that works normally except for download and recovery.
Problems:
1. Can't boot into recovery (via apps, power menu, or manually). It gets to the boot logo, and then blank screen and resets. It will keep resetting trying to go into recovery (a battery pull will put it back to normal).
2. Can't stay in download mode. When I put the phone in download mode, it turns off after a couple seconds. I can't ODIN it if it keeps turning off.
3. Power button doesn't work properly (sometimes it works, most of the times it doesn't). Example: I press the power button to close the screen. No response. A few minutes later I might press it, and the screen will close, but come back on and this time with power menu. I took out the button to verify that it wasn't stuck, and tried pressing the actual button inside the phone with the stick. I can feel it click, but it still has the same problems. Pretty sure it's not a stuck button.
What's working:
-Everything else. If I let the phone boot normally, it loads perfectly fine and into cyanogenmod. No issues with voice/data, any apps, or instability. No battery issue. No lag. No crashes. The only issue is with the power button, and my inability to boot into recovery or go into download mode.
History:
-I was experiencing a random reboot problem (and power button issue) from an earlier nightly, and I waited a couple months for a more stable version. The CWM recovery for some reason only worked sometimes. When I did get it to work, I flashed RC5 (format and wipe data, dalvik, cache, factory reset, etc.), which fixed my reboot problem, but not my power button.
-I came across this thread: at plus.google(.com)104277415207525128383/posts/iAVpVPYqMtM and updated the radio, even though the RC5 fixed my random reboot.
-I did try flashing CWM, TWRP, and Stock recoveries (the latest ones, and from CWM/EZ recovery apps), but have not tried CWM Touch. It doesn't seem to matter, it won't boot into recovery.
Perceived Solution:
-I have a plan with Best Buy - I am considering smashing the phone and getting it replaced with a refurb, but would like to avoid that if possible.
Anyone have any ideas? I am okay with the phone as is, but I would like to be able to update CM or to another ROM in the future
Thanks for helping me out!

Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium

DarkMenace said:
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.

phospholipid1 said:
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
Click to expand...
Click to collapse
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.

DarkMenace said:
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
Click to expand...
Click to collapse
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?

phospholipid1 said:
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
Click to expand...
Click to collapse
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.

It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2

Thanks for responding, guys
rellomar said:
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
Click to expand...
Click to collapse
Yes, I did. This brings me back into download mode, at which the phone just turns off.
BadUsername said:
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the commands; they ended up just shutting the phone off.
Yeah, I did ponder the idea that even though the power button "clicked," it might not necessarily be working. I google searched "galaxy s 3 broken power button" and there was a video with a description where the guy mentioned something about the circuit always being switched "on"
But his phone experienced different symptoms than mine (because the circuit was always switched on, the phone actually restarted itself while in normal operation. This hasn't happened to me).
Is there an app for me to definitely determine which buttons are being registered as they are pressed? Similar to programs that tell you what buttons you're pressing on your keyboard.
I would take it back to Best Buy, but I just don't want to give them any reason to say it was my own fault since I rooted and put a custom ROM on it.
Haha, I'll dunk it in salt water in favor of smashing it
Thanks again for your suggestions and ideas :cyclops:

[Q] soft brick vibration issue

So while trying to put on a new ROM (I've rommed and done custom recoveries and radios on this phone before) I had TWRP recovery on it and the ROM I was going to wanted CWM on it, so I flashed that and on battery it will show Samsung logo then go into a 2 second vibrate boot loop.
None of the button combos work. I ordered a jig on ebay and it flashes download mode for about a second before it flashes again and goes into the 2 second vibrate mode again. I tried to go from jig to Odin and it saw it for a split second, but disconnected/failed as soon as it started looping.
I read about the power button issue and the behavior matches, but I know I was the one that messed this thing up.
Is the JTag repair service my only option at this point?
I got an S4 so I'm just trying to get this revived to get rid of it so too expensive and I'll just sell it for parts.
thanks in advance for the help!
Jeffro

jeffro7172 said:
I read about the power button issue and the behavior matches
Click to expand...
Click to collapse
Focus on that.

theesotericone said:
Focus on that.
Click to expand...
Click to collapse
The reason I dismissed that was because I actually did it twice.the first time I was able to get into odin.
So of course the next time I did it, I told it to reboot into recovery and that was the last command I gave it. Since recovery is hosed I think that's why it's just looping.
I guess it could be the power button but I think because I hosed recovery, it's just not booting.

This phone has a separate recovery partition. So even if you hosed the recovery it would still boot. Theory here, like I said I've never seen anyone report a recovery bootloop. I think it's just a timing issue. Power button happened to get stuck when you where flashing something. The fact that it won't hold DL mode further leads to the simple solution.
You got a stuck power button.

Isn't the sop for this problem a battery pull? If you take the battery out and put it back in and the phone tries to turn on by itself(lights or vibration) then it's a faulty power button.

jondroid2 said:
Isn't the sop for this problem a battery pull? If you take the battery out and put it back in and the phone tries to turn on by itself(lights or vibration) then it's a faulty power button.
Click to expand...
Click to collapse
makes sense guys, that's what it does. Guess it just so happened to crap out right when I was messing with it. Thank you all, I'll head that route and see if I can get it revived.

It indeed revived with a take apart and some power button fiddling. Thank you all very much!

[Q] AT&T HTC One X Stuck at Viper XL Animation Screen

Hey guys,
I'll apologize in advance, since I'm sure I'm not the only one who's had this problem. I did try to use the search function, google, you name it. Didn't really come across any results that reflected my problem.
That all being said...
Tonight, my phone "died." I've been running Venom Viper XL for sometime now with no issues other than a pretty quick battery drain.
I was logging into 4square to check in tonight and I was getting a GPS error and a Wi-Fi disabled pop up. So I go into settings and check the Location stuff, turn the Google crap back on. Go back into 4square, same thing. I go back to the location settings, they were off again. Turned them back on. Saw that my wi-fi was enabled but "disconnected" so I disabled/enabled. Then my phone drops to the Viper XL splash screen. Tried to hold the power button to recycle it. HTC screen comes up, then to the Viper XL splash and stops. I tried a hard factory reset (volume down + power), same thing.
I can't get to anything. I plug it into my pc, can't get to anything.
I'm not sure what version of the Venom ROM I'm running. As far as I know, I haven't updated it in several months, even though something came out in September.
Am I stuck?

Firstly, volume down plus power isn't a factory reset, it's a hard reset. A factory reset is a very different thing. Have you tried flashing the ROM again or restoring a backup?
Sent from my Evita

timmaaa said:
Firstly, volume down plus power isn't a factory reset, it's a hard reset. A factory reset is a very different thing. Have you tried flashing the ROM again or restoring a backup?
Sent from my Evita
Click to expand...
Click to collapse
I just now was able to get into recovery. I'm running a back up and will go from there.
Thank you for responding though.

Ok, cool. In future you should probably exhaust possible options before creating a new thread though.
Sent from my Evita

timmaaa said:
Ok, cool. In future you should probably exhaust possible options before creating a new thread though.
Sent from my Evita
Click to expand...
Click to collapse
Like I said... I searched for a couple hours, so I thought I had. I can see how nearly every thread in here is pretty much started with "Search more." I didn't want to be one of those guys.
For anyone else reading that may have a similar issue:
As long as your phone turns on, you should be able to get to the bootloader. My problem was ignorance on this part, I didn't think I was able to.
1. Hold the power button + volume down until you get into the bootloader. I found that if I held these down, release when the screen went blank, then immediately pushed them down and held them, it got me into the bootloader.
2. Boot into recovery.
3. Take a back up of your stuff.
4. Re-install your ROM. If you don't have a copy of your ROM saved on your phone, plug your phone into your computer and mount your storage. This should make your phone storage available to your PC. Copy your ROM over to your phone, re-install.
5. Reboot. Though my phone was stuck in a restart loop after this. I initially did a reflash with the latest version of Viper XL without wiping. I went back into recovery and did a new install with a wipe. Problem solved.
6. Once you're sure your phone is back up and running, reboot into recovery and do a restore of your data from the back up you made earlier.
7. Enjoy having a phone again.

BigJanko said:
1. Hold the power button + volume down until you get into the bootloader. I found that if I held these down, release when the screen went blank, then immediately pushed them down and held them, it got me into the bootloader.
Click to expand...
Click to collapse
So many people are confused about how to get into bootloader. The main reason is that vol down needs to be held and not at any point released, until you get into bootloader. But the power button actually has to be released. The easiest way to accomplish this is:
- If the screen is on at all, hold both the power button and vol down until the capacitive buttons flash several times and the screen turns off. Once the screen is off, release the power button but keep holding vol down until you are in bootloader.
- If the screen is still black (or phone was powered off to begin with) simply keep holding vol down, and press the power button for a few seconds, then release it. But again, always holding vol down until the bootloader comes up.
If the phone boots normally, or goes to the boot splash, its almost always because you pressed vol down too late, or let go of it too early. As long as the screen comes on, failure to get into bootloader is almost always due to this user error.
People will often say "Press power and vol down" for bootloader. But this isn't really a complete and accurate description. And likely the reason why a lot of folks get confused.
Aside from this failure to get into bootloader, the remainder of your issue would have been easily solved if you had just originally had a nandroid on your phone. Recovering would have been as easy as:
1) Bootloader
2) Boot recovery
3) Restore nandroid
4) Keep on trucking
I'm surprised how so many people lately seem to be the practice of flashing ROMs or other mods without first making a nandroid backup. This to me is just a fundamental step in the process, and good basic practice. Failure to do so either signifies lack of knowledge, or doing mods in a careless fashion. Either way, its not good.
If you don't want the nandroid taking up all the space on the SD, I can understand that. In that case, have one on your PC that can be easily moved to your phone's SD in case of an emergency.

hi i was using my htc one x with viper xl but now i reset my system extsd cache everything .now when my device is on it shows me viper xl image alone so please kindly help me with this

kknaveenkk24 said:
hi i was using my htc one x with viper xl but now i reset my system extsd cache everything .now when my device is on it shows me viper xl image alone so please kindly help me with this
Click to expand...
Click to collapse
I think you have erased system and data partition too if u have done this you must have to flash viper Rom again

[Q] HTC one m8 hardbricked can't access any thing

I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.

Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know

DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go

piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.

M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset

piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.

Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please

rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.

It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.

rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?

Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..