Develop Bugs

[Q] S-Off Recovery problem

Hello! Hi, I'm kinda new to all of this, and I downloaded all of this today. I've been reading a lot and watching a lot of videos, yet I nothing really seems to fix my devices problem.
I have a HTC One on the Verizon carrier and I have just recently S-Off'd it using Rumrunner (I used the Rom checker to make sure it was unlocked and it even says it is whenever i enter bootloader). Although I was successfully able to unlock my device, I seem to have trouble with entering into recovery mode. Whenever I try to go into Recovery mode, my device reads "Entering Recovery mode" in pink at the top for about 10-20 seconds. Then all of a sudden it just goes black and it reboots as if I had never even chosen to go into recovery mode. I don't know if this holds any significance, but I've noticed that my boot up logo only has "HTC ONE" on it, the writing "simply beautiful" is now removed.
I have tried using cmd and ADB to clear the cache, I've tried using ClockManager from Rom Manager, and I've tried multiple times on regular mode. None of them really seem to work and I don't really understand why. Can anyone please offer me some suggestions? Thank you.
Seriously I only want a transparent theme for my HTC One that's all LOL

@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?

Chilidog said:
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Click to expand...
Click to collapse
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S

Cinestra said:
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
Hmm... That is strange indeed...
Sent from my HTC6500LVW using xda app-developers app

I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
when I got my phone back from sonic, twrp wouldn't install for me so I had to use CWM.
OP should probably try both and make sure he's following the instructions here:
http://forum.xda-developers.com/showpost.php?p=45513789&postcount=2

I'm quite new to rooting as well. Seems we are having the same problem. I was able to get beaups' s-off exploit to work without any problems. When I load into HBoot it says the phone is unlocked and I've also used a Root Checker to determine the phone is rooted.
My next step was to try and install TWRP using fastboot. I ran a command prompt window using administrator rights during the whole process. Everything seemed to install just as it should. The problem is when I try to boot into recovery I'm having the same problem as Cinestra. I simply get the HTC logo screen with "Entering Recovery..." in pink letters at the top of the screen for around 15 seconds, then it reboots as if it would normally and restart the phone as usual. I have tried to reinstall the custom recovery step by step, using 'fastboot erase cache' before and after as well as using an older version of TWRP just in case that would help. Again, everything seems to install just fine but I still can not boot into recovery. I've also tried to see if the GooManager app would be of some help, but that is also not working for me.
I've since also tried flashing CWM but the same situation occurs. Install seems fine but no luck booting into recovery. ROM Manager was a no go as well.
I just can't figure this out. I've tried different cables, deleted and reinstalled HTC drivers/adb/fastboot, and multiple recovery images. I just gave beasleyj62's suggestion of holding down the power/volume down buttons after it goes to black when it starts to restart but that just put me into a bootloop sadly. Had to hold down the power button a few times to get it to boot correctly again. Any help on this would be greatly appreciated. Cheers.
I would also just like to add a little more info on my device in case this will help troubleshoot this. I'm using a Verizon HTC One with Software Number 1.10.605.10.

Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'

carassius-one said:
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
Click to expand...
Click to collapse
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Click to expand...
Click to collapse
Thanks. That answers that part of the question.

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.

Prizm432 said:
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Click to expand...
Click to collapse
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.

Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
carassius-one said:
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Click to expand...
Click to collapse

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. I think it was 3 or 4 pours. Seemed to work flawlessly.
2. Still trying to learn which includes learning what an ruu is. Maybe that is my problem. I ran rumrunner and then have been trying to flash a recovery ever since...with no other steps.

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.

No, no. The only RUU available is a decrypted one, which can only be flashed while S-OFF. So the ideas I put down were distinct, and not steps. My thought is that either (i) you return yourself to full stock and non-root as is explained in a thread in this subforum, or alternatively, (ii) flash the RUU to get a fully untouched setup (the RUU contains the factory "rom", bootloader and recovery and will return it to being fresh from the factory) on the device and then flash the recovery.
Prizm432 said:
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
Click to expand...
Click to collapse

Cinestra said:
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Go here: http://goo.im/devs/Flyhalf205/M7VZW/openrecovery-twrp-2.6.3.0-m7vzw.img

beasleyj62 said:
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
Click to expand...
Click to collapse
Thanks for your solution, unfortunately though, it doesn't seem to work.
jpradley said:
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Click to expand...
Click to collapse
Hmm alright so you suggest flash this other version of TWRP instead? That would make sense because the link looks like it's specialized for Verizon. I will try that out today!
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. It took me about 3 pours. That is an interesting thought and I think it may very well be valid, but I would prefer not to reset or relock my device though.
2. I have not decrypted RUU yet because I was unfamiliar with the term. I may try this if the new TWRP code does not work

@Prizm432 it looks like you are flashing the wrong Twrp zip. It has to end in m7vzw.zip
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Help! Have I screwed up my bootloader?

So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?

ab2 said:
So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?
Click to expand...
Click to collapse
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.

NotATreoFan said:
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.
Click to expand...
Click to collapse
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.

I don't use ROM Manager, but I just installed it on my phone. The prompts all refer to recovery, and make no mention of bootloader. See below.
Sent from my HTC6500LVW using Tapatalk

ab2 said:
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.
Click to expand...
Click to collapse
Its most likely referring to the recovery, not the bootloader; Assuming you're root, Rom Manager is there to flash custom ROMS and custom recoveries. I don't think you'll have bricked your phone if you installed a bad recovery, but I think your best bet would be install a compatible one manually.
SO pick a thread and follow the directions under installation:
http://forum.xda-developers.com/showthread.php?t=2416273 CWM
http://forum.xda-developers.com/showthread.php?t=2416431 TWRP
i'd pick twrp

Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?

Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.

ab2 said:
Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?
Click to expand...
Click to collapse
The S-Off exploit removes stock recovery, so it will go nowhere until you flash CWM or TWRP. Fastboot will work regardless.
Sent from my HTC6500LVW using Tapatalk

ab2 said:
Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?

I've never used that command personally. I have Quick Boot (Reboot) from the market and use it for getting into recovery and fastboot from Android.
Sent from my HTC6500LVW using Tapatalk

ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
Do you have fastboot unchecked under power settings? Phone doesn't totally reboot with that checked.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
adb reboot recovery = takes you to recovery
adb reboot bootloader = takes you to fastboot/booloader
I don't believe adb reboot fastboot is a command, so it just does adb reboot

Can't flash a recovery ROM to HTC One Verizon

I might be doing something wrong but I can't flash any recovery ROMs to my HTC One. I used rumrunner S-off today and gained root access with my stock ROM. I tried using command prompt to flash a TWRP recovery ROM, and it only worked once but now whenever I try to do it it says either "cannot load image" or gives me a partition error.
I tried going into recovery with the one I flashed and when it says entering recovery mode it either goes into a continuous reboot cycle or proceeds to the lockscreen. I tried using flashify today too and it says my device isn't compatible with any of the recovery ROMs.
Please help, I'm so frustrated and all I want to do is flash Android Revolution to my HTC! Also, was I supposed to factory reset my phone before all this? Because I still have all my apps, photos, data, etc.
P.S. I'm a noob at this stuff so I might be doing something wrong.

Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One

jbh00jh said:
Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One
Click to expand...
Click to collapse
No luck. Flashify won't install anything

ak074 said:
we will need more information about what all you've been trying and the results.
s-off was successful?
bootloader locked/unlocked?
what are you typing into the cmd prompt?
result from that cmd?
where did you get the recovery from? are you sure it's for the vzw htc one?
etc...
Click to expand...
Click to collapse
S-off was successful.
Bootloader is unlocked (And somehow the phone became rooted in the process)
cmd prompt: fastboot flash recovery recovery.img
cmd prompt kept saying something about unable to load the image
Got the recovery from ClockWork Mod - It is Verizon HTC One version
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!

shadowskaya said:
No luck. Flashify won't install anything
Click to expand...
Click to collapse
OK first off make sure the recovery you are trying to flash ends in m7vzw.img second, Flashify doesn't work for everyone so you might have to do it from adb on your computer. And finally, there is no android revolution rom for the Verizon htc one.

The developer of Flashify has a thread in Android developing and hacking/ apps and games / Flashify. Sometimes these threads have updates posted before the play store does. Start at the back of the thread and read toward the beginning,find the latest info faster (about a 25 page thread).
Sent from my Galaxy Tab 10.1

shadowskaya said:
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!
Click to expand...
Click to collapse
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!

karn101 said:
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!
Click to expand...
Click to collapse
Thank you for the tip, I will remember that the next time I flash a recovery to something. It was the correct recovery, but for some reason the fastboot and adb wouldn't flash it. Maybe I just needed a reboot of pc or something...

Had the same issue after s-off with twrp. Ended up flashing cwm touch instead and it works just as well. Although I do miss twrp.
Sent from my One using XDA Premium 4 mobile app

[Q] HTC One M8 GPE won't boot to custom recovery

Hi all-
I just received my HTC One M8 Google Play Edition today. I successfully unlocked the bootloader (I see the open padlock every time it boots), but I'm running into trouble with TWRP. I downloaded TWRP 2.7.0.3 from this thread. Since I'd like to get OTA updates in the future, I am attempting to boot (not flash!) TWRP using
Code:
$ ./adb reboot bootloader
$ ./fastboot boot ~/Downloads/openrecovery-twrp-2.7.0.3-m8_ul_ca.img
downloading 'boot.img'...
OKAY [ 1.251s]
booting...
OKAY [ 0.001s]
finished. total time: 1.252s
$
but after the second command, the phone just reboots to the normal system. I have attempted renaming TWRP to recovery.img, but that didn't change the behavior. I have tried a factory reset, and that didn't change the behavior. If I attempt to manually enter recovery from HBoot, I get the dead android logo.
I really just want to flash SuperSU.
Any and all help is greatly appreciated. Thanks!
Stephen

TWRP doesn't work on GPe for some reason. Use Philz CWM.
Sent from my HTC One_M8 using Tapatalk

Tikerz said:
TWRP doesn't work on GPe for some reason. Use Philz CWM.
Click to expand...
Click to collapse
I wondered about that, but for some reason I didn't find the Philz m8 thread until you mentioned it. So I downloaded CWM from this thread and had the exact same experience...
Other thoughts?
Thanks!
Stephen

A little concerned that I wasn't able to boot either TWRP or CWM, and (while I don't think I'd flashed anything) just going into HBoot and selecting recovery also didn't work (dead Android icon), I grabbed the 4.4.2 firmware from here and flashed the stock recovery.
After flashing the stock recovery I had the *TAMPERED* label in HBoot (which surprised me a little because I assumed stock would 100% match what was already there). Now if I selected Recovery from HBoot I would get a temporary flash of "This image is for development use only (etc.)..." and then end up back in HBoot. I tried once or twice more to just boot CWM and still no luck. So finally I flashed CWM, installed SuperSU, and then flashed back to stock. I guess I'll find out when the first OTA rolls around if the system is still "stock" enough.
Thanks,
Stephen

scbash said:
Hi all-
I just received my HTC One M8 Google Play Edition today. I successfully unlocked the bootloader (I see the open padlock every time it boots), but I'm running into trouble with TWRP. I downloaded TWRP 2.7.0.3 from this thread. Since I'd like to get OTA updates in the future, I am attempting to boot (not flash!) TWRP using
Code:
$ ./adb reboot bootloader
$ ./fastboot boot ~/Downloads/openrecovery-twrp-2.7.0.3-m8_ul_ca.img
downloading 'boot.img'...
OKAY [ 1.251s]
booting...
OKAY [ 0.001s]
finished. total time: 1.252s
$
but after the second command, the phone just reboots to the normal system. I have attempted renaming TWRP to recovery.img, but that didn't change the behavior. I have tried a factory reset, and that didn't change the behavior. If I attempt to manually enter recovery from HBoot, I get the dead android logo.
I really just want to flash SuperSU.
Any and all help is greatly appreciated. Thanks!
Stephen
Click to expand...
Click to collapse
I might be wrong, but isn't the command "fastboot boot recovery recovery.img" whereas "recovery.img" would be the path to the recovery you want to boot to without flashing? If I'm not mistaken, "fastboot boot" would boot the phone up to the system.

suprtrukr425 said:
I might be wrong, but isn't the command "fastboot boot recovery recovery.img" whereas "recovery.img" would be the path to the recovery you want to boot to without flashing? If I'm not mistaken, "fastboot boot" would boot the phone up to the system.
Click to expand...
Click to collapse
When I did it with my wife's Nexus 5, it was "fastboot boot <image>" (and there it worked without a hitch). In the middle of other things last night I did try that and got "no such file: recovery". So I'm still open to user error, but at least that particular change didn't fix my problem...
Thanks,
Stephen

scbash said:
When I did it with my wife's Nexus 5, it was "fastboot boot <image>" (and there it worked without a hitch). In the middle of other things last night I did try that and got "no such file: recovery". So I'm still open to user error, but at least that particular change didn't fix my problem...
Thanks,
Stephen
Click to expand...
Click to collapse
download the stock revovery listed here (in development).install cwm, root, and redo your stock recovery via fastboot

rbouza1 said:
download the stock revovery listed here (in development).install cwm, root, and redo your stock recovery via fastboot
Click to expand...
Click to collapse
Yup, that's what I ended up doing earlier this afternoon. Thanks though.
Stephen

Thus may be a dumb question but how do we root the gpe edition. I tried with weak sauce but it failed. Thanks
Sent from my HTC One_M8 using Tapatalk

aaronc_98 said:
Thus may be a dumb question but how do we root the gpe edition. I tried with weak sauce but it failed. Thanks
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I figured it out- http://howtorootmobile.com/root-htc-one-google-play-edition-unlock-bootloader-install-twrp/
thanks,

Fastboot boot stopped working on One m7 since 3.x. I'm assuming they continued the trend..
sent from my mobile device

Unfortunately non of the recoveries available will "boot" into recovery. Philz works if you flash the recovery. I would say flash philz recovery and then flash back the stock GPE recovery I posted in Dev

scbash said:
When I did it with my wife's Nexus 5, it was "fastboot boot <image>" (and there it worked without a hitch). In the middle of other things last night I did try that and got "no such file: recovery". So I'm still open to user error, but at least that particular change didn't fix my problem...
Thanks,
Stephen
Click to expand...
Click to collapse
Yep, found out I was wrong when I went to do it myself. After some research, it seems the code used to include the extra "recovery", but no longer does.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

SaHiLzZ said:
Fastboot boot stopped working on One m7 since 3.x.
Click to expand...
Click to collapse
graffixnyc said:
Unfortunately non of the recoveries available will "boot" into recovery.
Click to expand...
Click to collapse
Thanks for the confirmation SaHiLzZ and graffixnyc. I was worried I might have a bum phone there for a bit.
Stephen

SaHiLzZ said:
Fastboot boot stopped working on One m7 since 3.x. I'm assuming they continued the trend..
sent from my mobile device
Click to expand...
Click to collapse
fastboot boot didn't work on the m7. It works on the m8 I have tested it and I used an unreleased recovery to boot the recovery to pull the stock recovery from the GPE. You can boot the recoveries on sense based roms but for the GPE edition one the ones for Sense aren't booting. the dt.img's are different between the two devices.

graffixnyc said:
fastboot boot didn't work on the m7. It works on the m8 I have tested it and I used an unreleased recovery to boot the recovery to pull the stock recovery from the GPE. You can boot the recoveries on sense based roms but for the GPE edition one the ones for Sense aren't booting. the dt.img's are different between the two devices.
Click to expand...
Click to collapse
Since booting rather than flashing is my preferred workflow, do you know if the "unreleased recovery" you used is planned to be released? I've already flashed Philz and flashed back, but for future use it would be convenient.
Thanks,
Stephen

Just had the same problem like yours but the latest CWM 6.0.4.8 works for me.
I got touch CWM from here
The superuser.zip file from here
Both are made by clockworkmod
Commands
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-touch-6.0.4.8-m8.img
Once I got in the temporary CWM recovery, I backed up the entire system to sdcard. I pulled out the stock recovery image file (24MB in size) in case I need it for OTA in the future.
Then flash the superuser.zip and reboot back to the vanilla android. Stock recovery and everything else was untouched and we got rooted.

erythrophilia said:
Just had the same problem like yours but the latest CWM 6.0.4.8 works for me.
Click to expand...
Click to collapse
After the 4.4.4 OTA update, I was also able to boot (not flash) Philz recovery to reroot my phone.
Long version in case it's helpful to someone else in the future: I think either my phone shipped with corrupt firmware or I somehow corrupted it while unlocking the bootloader originally, and then I made matters worse by flashing back to a "stock" firmware that didn't exactly match the shipped M8 GPE recovery. Turned out that with that bad "stock" firmware the 4.4.3 OTA failed to apply, so to make the 4.4.3 OTA work I had to flash the 1.16.1700.16 firmware from this thread. After the 4.4.3 update ./fastboot boot <custom-recovery> still didn't work, so I did the flash custom/root/flash stock cycle. Then a week later the 4.4.4 update rolled through without incident, and suddenly ./fastboot boot <custom-recovery> worked fine.
Thanks,
Stephen

Recovery Boots to Black Screen

So I clean flashed the newest community edition of Oxygen. Directly after I flashed it I flashed SuperSU. Everything goes well, no big error messages (I edited the updater-script for Oxygen). So I boot into Oxygen, and I can't find root. Everything is working beautifully but there's just no SuperSU. So I reboot to recovery, about to flash the zip again, but I get a black screen. Doesn't go away until I hold the power button for 15 seconds. Rebooted to fastboot, flashed TWRP recovery image. Same result, black screen when booting into recovery. Is there something I'm doing wrong? It's usable but I'd really like root....

Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560

daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
Thanks so much!

camcorder123 said:
Thanks so much!
Click to expand...
Click to collapse
No problem.

I've got this same problem. Thanks for the TWRP fix!
Did you manage to get SuperSU / Root to work?

daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
Thanks. It worked.

daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
you are awesome, thanks so much this fixed my issue

recovery black screen and fastboot not working on computer
HI .
I am stuck with this black screen on recovery problem. And fastboot is not working on my system. Please help.

vijaysivakula said:
HI .
I am stuck with this black screen on recovery problem. And fastboot is not working on my system. Please help.
Click to expand...
Click to collapse
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.

Fastboot not working
HermitDash said:
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Click to expand...
Click to collapse
Fastboot not working on my office laptop. Funnily, it used to work earlier. Could someone help me with that? Or I will flash it over the weekend when i am home and revert to complete stock. The Community Build did not seem very attractive or useful in the few days I tried.

vijaysivakula said:
Fastboot not working on my office laptop. Funnily, it used to work earlier. Could someone help me with that? Or I will flash it over the weekend when i am home and revert to complete stock. The Community Build did not seem very attractive or useful in the few days I tried.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2317790
Minimal ADB and Fastboot.
Then just install drivers for your phone or do a search and you'll find it for the OnePlus 3

Worked For me too!
camcorder123 said:
So I clean flashed the newest community edition of Oxygen. Directly after I flashed it I flashed SuperSU. Everything goes well, no big error messages (I edited the updater-script for Oxygen). So I boot into Oxygen, and I can't find root. Everything is working beautifully but there's just no SuperSU. So I reboot to recovery, about to flash the zip again, but I get a black screen. Doesn't go away until I hold the power button for 15 seconds. Rebooted to fastboot, flashed TWRP recovery image. Same result, black screen when booting into recovery. Is there something I'm doing wrong? It's usable but I'd really like root....
Click to expand...
Click to collapse
Helped me too, thanks big time

LunaticWinchester said:
Helped me too, thanks big time
Click to expand...
Click to collapse
Got same issue. Notify me if there is any solutions...thx.

Thanks work like a charm!

Sorry for reviving this thread, but I managed to solve my problem with this solution. however after a while, because of some problems I booted into recovery, and after seeing the TWRP logo the phone goes black and I can't do anything. I believe I might have killed my phone, but does anyone have some idea?

coyotejodido said:
Sorry for reviving this thread, but I managed to solve my problem with this solution. however after a while, because of some problems I booted into recovery, and after seeing the TWRP logo the phone goes black and I can't do anything. I believe I might have killed my phone, but does anyone have some idea?
Click to expand...
Click to collapse
Plz check some of my older posts. I posted a stock recovery Link. Use that and you'll be able to boot just fine.
Sent from my ONEPLUS A3003 using Tapatalk

HermitDash said:
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Click to expand...
Click to collapse
I have unlocked my bootloader. when i flashed twrp it showed a blank screen it is not tuning on after holding the power button for 20 min. please help