Related
Hello,
I recently purchased a replacement HTC Desire HD and would like to install jellytime on it, like I had on my old phone.
I get an error when trying to install the flashboot image:
# ../fastboot boot boot.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
The phone says S-ON and it is HBOOT version 0.85.0024
../fastboot devices
HT139T202307 fastboot
I do not have access to windows system and think I should have all of the tool necessary since I can use adblinux and fastboot and see the device ok
Thanks guys. I really want to get off of this ATT image!
iamatt said:
Hello,
I recently purchased a replacement HTC Desire HD and would like to install jellytime on it, like I had on my old phone.
I get an error when trying to install the flashboot image:
# ../fastboot boot boot.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
The phone says S-ON and it is HBOOT version 0.85.0024
../fastboot devices
HT139T202307 fastboot
I do not have access to windows system and think I should have all of the tool necessary since I can use adblinux and fastboot and see the device ok
Thanks guys. I really want to get off of this ATT image!
Click to expand...
Click to collapse
Is your bootloader unlocked?? Because you are S-ON and that is why you won't be able to flash a partition image. Or you are S-OFF or you have an unlocked bootloader. That has nothing to do with not using windows.
glevitan said:
Is your bootloader unlocked?? Because you are S-ON and that is why you won't be able to flash a partition image. Or you are S-OFF or you have an unlocked bootloader. That has nothing to do with not using windows.
Click to expand...
Click to collapse
Hello! and thanks for reply. Ok I did go do unlock boot loader routine from htc developer site and now the boot loader says 'unlocked' now. I guess I'm almost there? What would be the next step to root the phoe so I can get back to following the JellyTime roms?
iamatt said:
Hello! and thanks for reply. Ok I did go do unlock boot loader routine from htc developer site and now the boot loader says 'unlocked' now. I guess I'm almost there? What would be the next step to root the phoe so I can get back to following the JellyTime roms?
Click to expand...
Click to collapse
you have to flash the image file from fastboot USB not HBOOT, and in the cmd session you have to be in the same path as the file is located.
glevitan said:
you have to flash the image file from fastboot USB not HBOOT, and in the cmd session you have to be in the same path as the file is located.
Click to expand...
Click to collapse
Hi. I flashed clockwork mod and now when my phone reboots it gets stuck on htc boot screen. I tried re-flashing a backup rom I had from SD card and still no go. HBOOT says unlocked and there is some errors in the screen when the hboot loads but it goes by real fast. I can communicate with the device still with fastboot. Any suggestions to at least get this phone so it will boot? argh and I am going out of town this weekend so a usable phone would REALLY be good.
iamatt said:
Hi. I flashed clockwork mod and now when my phone reboots it gets stuck on htc boot screen. I tried re-flashing a backup rom I had from SD card and still no go. HBOOT says unlocked and there is some errors in the screen when the hboot loads but it goes by real fast. I can communicate with the device still with fastboot. Any suggestions to at least get this phone so it will boot? argh and I am going out of town this weekend so a usable phone would REALLY be good.
Click to expand...
Click to collapse
Have you flashed the boot.img before flashing the custom rom??
Boot in fastboot usb, plug the phone, then: From the custom rom zip file, just extract the boot.img file and flash it in fastboot this way:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Then choose recovery and flash the rom as usual...
glevitan said:
Have you flashed the boot.img before flashing the custom rom??
Boot in fastboot usb, plug the phone, then: From the custom rom zip file, just extract the boot.img file and flash it in fastboot this way:
Then choose recovery and flash the rom as usual...
Click to expand...
Click to collapse
Hey man! you really saved my butt!!! I got it working again phew.. It looks as though (as you suggested) that my boot image was not aligned with the rom I was trying to use. Seriously thanks again.
iamatt said:
Hey man! you really saved my butt!!! I got it working again phew.. It looks as though (as you suggested) that my boot image was not aligned with the rom I was trying to use. Seriously thanks again.
Click to expand...
Click to collapse
No problem...just take into consideration that everytime that you flash a rom, you need to flash the boot.img.
Take care and enjoy!!
iamatt said:
Hello,
I recently purchased a replacement HTC Desire HD and would like to install jellytime on it, like I had on my old phone.
I get an error when trying to install the flashboot image:
# ../fastboot boot boot.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
The phone says S-ON and it is HBOOT version 0.85.0024
../fastboot devices
HT139T202307 fastboot
I do not have access to windows system and think I should have all of the tool necessary since I can use adblinux and fastboot and see the device ok
Thanks guys. I really want to get off of this ATT image!
Click to expand...
Click to collapse
It looks like your problem was a wrong command. The command is 'fastboot flash boot boot.img'. You wrote 'fastboot boot boot.img'. :silly:
Hey Guys,
Hope that someone can help me, I have rooted, installed recovery and custom firmware on a few HTC's.
But this has frickin stumped me !!
The desire I have gotten my hands on does not show locked or unlocked in the boot menu, but It has got S-off I didn't think it was possible??
Tried to unlock the bootloader through HTC dev and that failed, so i thought it was already unlocked
Tried flashing recovery through fast boot, but that failed!!
I'm a bit lost, anyone got any ideas as to where I'm going wrong??
Step one: Stop trying to unlock it...there is no need
Since the phone is already s-off you dont need to worry about unlocking the bootloader.
S-off is the highest level of "openness" you can have on the desire. You have the ability to write to all of the partition that you can with an unlocked bootloader, plus more.
The fact that flashing a recovery failed is indeed a problem though. What was the exact error?
Chromium_ said:
Step one: Stop trying to unlock it...there is no need
Since the phone is already s-off you dont need to worry about unlocking the bootloader.
S-off is the highest level of "openness" you can have on the desire. You have the ability to write to all of the partition that you can with an unlocked bootloader, plus more.
The fact that flashing a recovery failed is indeed a problem though. What was the exact error?
Click to expand...
Click to collapse
Dude,
Thanks for that, I'm now clearer on the bootloader issue.
This is what was returned from the fastboot command.
C:\>fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.829s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.830s
C:\>
Now the phone is just bootlooping at the HTC splash screen, any ideas whats gone wrong??
sudd1976 said:
Dude,
Thanks for that, I'm now clearer on the bootloader issue.
This is what was returned from the fastboot command.
C:\>fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.829s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.830s
C:\>
Now the phone is just bootlooping at the HTC splash screen, any ideas whats gone wrong??
Click to expand...
Click to collapse
in my sig (click to show content) theres 4ext recovery as PB99IMG, click the link and follow instructions to flash recovery.
Or
Use the twrp recovery img that u have and flash it using fastboot command
fastboot flash recovery TWRP.img
Then u should be able to boot into recovery
It's ALIVE !!!!
jmcclue said:
in my sig (click to show content) theres 4ext recovery as PB99IMG, click the link and follow instructions to flash recovery.
Or
Use the twrp recovery img that u have and flash it using fastboot command
fastboot flash recovery TWRP.img
Then u should be able to boot into recovery
Click to expand...
Click to collapse
Guys,
Ok, so i realised that I was being a major dumbass and using the wrong fastboot command to try and flash my recovery.
Even when I used the command - fastboot flash recovery TWRP.img, the result was the same, no recovery for me and a bootloop
But the 4ext recovery as PB99IMG zip file on the root of my S/d card has worked, I now have a working recovery and no more bootloop.
Thanks for all your help guys
sudd1976 said:
Guys,
Ok, so i realised that I was being a major dumbass and using the wrong fastboot command to try and flash my recovery.
Even when I used the command - fastboot flash recovery TWRP.img, the result was the same, no recovery for me and a bootloop
But the 4ext recovery as PB99IMG zip file on the root of my S/d card has worked, I now have a working recovery and no more bootloop.
Thanks for all your help guys
Click to expand...
Click to collapse
Glad it worked :cyclops: ps: 4ext recovery is by far the best recovery so keep using it
Out of interest, what version of twrp were u trying to flash??
This is the official device listing TWRP Recovery
But i found this version for desire
By island3r
Im guessing u tried to flash wrong version, hense the fail.
jmcclue said:
Glad it worked :cyclops:
Out of interest, what version of twrp were u trying to flash??
Click to expand...
Click to collapse
I tried flashing both of these recoveries
CWM - Touch 5.8.2.0 - Bravo
TWRP - 2.6.0.0 - 2013.07.16
Had the same result on both neither would flash in fastboot.
Taking a look through the files on the phone i can see leftover data from both CWM and also Titanium backup, so its totally been flashed and rooted before I got my hands on it.
Verizon HTC One Unlocked and S-Off via RumRunner's method, except installed clockworkmod. Installed Android Revolution. Flash seemed to go well, but when phone tried to reboot it got stuck in a loop at the htc this build is for development purposes.... then it shuts of, and boots back to the screen. If I try to boot to recovery it goes back to the same loop.
Thanks for any help Kurt
krerath said:
Verizon HTC One Unlocked and S-Off via RumRunner's method, except installed clockworkmod. Installed Android Revolution. Flash seemed to go well, but when phone tried to reboot it got stuck in a loop at the htc this build is for development purposes.... then it shuts of, and boots back to the screen. If I try to boot to recovery it goes back to the same loop.
Thanks for any help Kurt
Click to expand...
Click to collapse
What is "Android Revolution"?
krerath said:
Verizon HTC One Unlocked and S-Off via RumRunner's method, except installed clockworkmod. Installed Android Revolution. Flash seemed to go well, but when phone tried to reboot it got stuck in a loop at the htc this build is for development purposes.... then it shuts of, and boots back to the screen. If I try to boot to recovery it goes back to the same loop.
Thanks for any help Kurt
Click to expand...
Click to collapse
Are you sure ARHD is even compatible with Verizon? Last I heard they weren't going to support our device.
Next time you reboot (hold power) press the down volume button to go into fastboot and then get into recovery that way. Restore previous nandroid, assuming you backed up first.
Sent from my HTC's darkside.
jpradley said:
What is "Android Revolution"?
Click to expand...
Click to collapse
Custom ROM
res0prw2 said:
Are you sure ARHD is even compatible with Verizon? Last I heard they weren't going to support our device.
Next time you reboot (hold power) press the down volume button to go into fastboot and then get into recovery that way. Restore previous nandroid, assuming you backed up first.
Sent from my HTC's darkside.
Click to expand...
Click to collapse
Thanks, but that is the way I've been trying to go into Recovery.
krerath said:
Thanks, but that is the way I've been trying to go into Recovery.
Click to expand...
Click to collapse
Sorry I can't help anymore. Can you ADB into your phone? Maybe sideload a Verizon custom rom?
This is why you should only flash roms from the Verizon forums, or at least double check with the rom dev.
Sent from my HTC's darkside.
krerath said:
Custom ROM
Click to expand...
Click to collapse
That's really informative -- not!
Is it a ROM made for the Verizon HTC One?
jpradley said:
That's really informative -- not!
Is it a ROM made for the Verizon HTC One?
Click to expand...
Click to collapse
Yes, look at this link http://forum.xda-developers.com/showthread.php?t=2183023
jpradley said:
That's really informative -- not!
Is it a ROM made for the Verizon HTC One?
Click to expand...
Click to collapse
Sorry, didn't mean to be short. I'm downloading a VZW Stock ROM now. I'll try to fastboot flash boot that from Fastboot on the phone. I think that's the correct procedure.
krerath said:
Sorry, didn't mean to be short. I'm downloading a VZW Stock ROM now. I'll try to fastboot flash boot that from Fastboot on the phone. I think that's the correct procedure.
Click to expand...
Click to collapse
You're still being short. I take it you admit that you were playing with an inappropriate ROM?
Why do you want a Stock ROM now anyhow? Grab Slim , or NOS, or NuSense.
And you don't "fastboot flash" a ROM.
You flash either Clockwork or TWRP recovery, then download the ROM to your phone, boot into recovery, then install the ROM zip file.
jpradley said:
That's really informative -- not!
Is it a ROM made for the Verizon HTC One?
Click to expand...
Click to collapse
Here's what happened when I tried to flash a stock ROM
c:\Android>fastboot flash boot VZW_Stock_Rooted_deodex.zip
sending 'boot' (1147284 KB)...
OKAY [ 45.054s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 45.089s
jpradley said:
And you don't "fastboot flash" a ROM.
You flash either Clockwork or TWRP recovery, then download the ROM to your phone, boot into recovery, then install the ROM zip file.
Click to expand...
Click to collapse
krerath said:
Here's what happened when I tried to flash a stock ROM
c:\Android>fastboot flash boot VZW_Stock_Rooted_deodex.zip
sending 'boot' (1147284 KB)...
OKAY [ 45.054s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 45.089s
Click to expand...
Click to collapse
Follow the instructions in the first quote, you cannot flash a rom with fastboot you have to be in the recovery.
Also, where did you read that Android Revolution HD was supported on the Verizon HTC One? The link you provided in a previous post did not mention anything about supporting the Verizon HTC One.
Edit: I was just thinking this through and you will most likely have to use the sideload feature to get the rom onto your phone so you can flash it. In TWRP you can find the sideload function under the "Advanced" section.
ONLY use roms found from these sections - Verizon HTC One Android Development - and - Verizon HTC One Original Android Development. Other roms found in the other HTC One sections WILL NOT WORK.
Agreed. Android revolution is not supported on Verizon One yet. I use to get my Roms out of the general HTC One forum when I was with AT&T (many more were listed there than the AT&T Specific forum) but I knew they would work with that phone. You cannot do that anymore so better to stick with the actual Verizon HTC One forums.
SO I have been messing with this HTC inspire 4g and I was having some software issues on the factory ROM. So I decided to flash a custom rom to it, but I forgot that I relocked the boot loader. Now I can't seem to flash the boot.img since the bootloader is locked, and I forgot to backup the factory rom before messing with this, so now it will only boot into hboot, fastboot, and recovery. How do I proceed?
Thank you.
DeadlyFoez said:
SO I have been messing with this HTC inspire 4g and I was having some software issues on the factory ROM. So I decided to flash a custom rom to it, but I forgot that I relocked the boot loader. Now I can't seem to flash the boot.img since the bootloader is locked, and I forgot to backup the factory rom before messing with this, so now it will only boot into hboot, fastboot, and recovery. How do I proceed?
Thank you.
Click to expand...
Click to collapse
Unlock the bootloader again with the same token. Then flash the custom rom and the boot.img.
glevitan said:
Unlock the bootloader again with the same token.
Click to expand...
Click to collapse
Sorry. I am rather newb to this. How do I proceed to unlock the bootloader with the token. Since the ace hack kit is so automated, I didn't learn a darn thing from it.
DeadlyFoez said:
Sorry. I am rather newb to this. How do I proceed to unlock the bootloader with the token. Since the ace hack kit is so automated, I didn't learn a darn thing from it.
Click to expand...
Click to collapse
If you used the Hack Kit then you should be S-OFF. If you are S-OFF, then flash a custom recovery from fastboot and then a custom rom.
glevitan said:
Unlock the bootloader again with the same token. Then flash the custom rom and the boot.img.
Click to expand...
Click to collapse
I am currently "S-ON". How do I proceed?
BTW, What does S-OFF and S-ON even mean? I've never come across it in all of my previous android hacks?
ok. I figured it out. Thank you.
how did you solve your problem?
I got the same problem. After unlocked the hboot, installed recovery, then installed a custom rom, now my phone is softbrick.
I can boot to hboot, fastboot, and recovery only. I cannot install any custom rom, reboot after install custom rom from recovery, the phone stuck at the white HTC screen.
The phone is S-ON.
I also have another problem with ADB devices, when I am in the fastboot, the fastboot devices shows the device, but when I am in either hboot or fastboot, the ADB does not show any devices.
Help!!!
DeadlyFoez said:
ok. I figured it out. Thank you.
Click to expand...
Click to collapse
tongben said:
I got the same problem. After unlocked the hboot, installed recovery, then installed a custom rom, now my phone is softbrick.
I can boot to hboot, fastboot, and recovery only. I cannot install any custom rom, reboot after install custom rom from recovery, the phone stuck at the white HTC screen.
The phone is S-ON.
I also have another problem with ADB devices, when I am in the fastboot, the fastboot devices shows the device, but when I am in either hboot or fastboot, the ADB does not show any devices.
Help!!!
Click to expand...
Click to collapse
1 take the boot.img from the inside of your custom rom.zip
2 put it in the same folder/ drive or herever you have adb
3 go into fastboot with your phone
4 open cmd and type fastboot flash boot boot.img[/B
go out of fastboot and start your phone up
because you still s-on the boot image can't be installed trough recovery.
no warranties here but i had the same problem and it worked fine
good luck
Lexuz,
Thanks for your help. I tried the fastboot flash boot boot.img
I got the following error:
sending 'boot' (2932 KB)... OKAY [ 0.496s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
Help!!!
Edited:
The error "Signature verify fail" only appear when there is "*** RELOCKED ***" shown. I put the hboot back to "*** UNLOCKED***" then when I tried the "fastboot flash boot boot.img", it succeed. However, when I reboot, instead of stucked at the white htc screen, it shows different boot screen (instead of the white HTC screen), but the phone did not go further after an hour.
I also tried "fastboot flash boot ..." in combination of recovery flashing but none works.
tongben said:
Lexuz,
Thanks for your help. I tried the fastboot flash boot boot.img
I got the following error:
sending 'boot' (2932 KB)... OKAY [ 0.496s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
Help!!!
Edited:
The error "Signature verify fail" only appear when there is "*** RELOCKED ***" shown. I put the hboot back to "*** UNLOCKED***" then when I tried the "fastboot flash boot boot.img", it succeed. However, when I reboot, instead of stucked at the white htc screen, it shows different boot screen (instead of the white HTC screen), but the phone did not go further after an hour.
I also tried "fastboot flash boot ..." in combination of recovery flashing but none works.
Click to expand...
Click to collapse
i also got that same problem by using the wrong boot.img.
make sure you use the boot.img that is in your custom rom folder and then flash it (the rom) via recovery (i also think you have to reflash recovery to do this but i'm not sure, for me it has been a learn by your mistakes project).
Unlock bootloader again ..then flash boot image at bootloader then reboot normally ..
Sent from my HTC Desire HD using xda app-developers app
No worries on Me!
Hello to all developers,
Since I go throw this discussion I found out you people need some information regarding unlock boot loader.
I have literally no idea when I rooted my phone and install custom ROM and what is CWM. You guys at least knows it more than me,I'm sure but what i noticed is to unlock bootloader doesn't really require token code to unlock using htcdev.
As i mention above you may unlock bootloader via some program like i used it when these all words are completely new for me. I went through kingroot(dot)net,that site is in chinese so using translator i tried to understand the meaning out of it. Underneath that site once you scroll it down you'll find some various different icons for other site. From there I found to go through mgyun(dot)com download and install software. Don't worry its in Chinese but once you connect your phone it will display HTC G10(a9191) in other words desire HD/inspire 4g.
Kindly look throw all app you'll find "LOCK" kind of a icon. Click on it and check your phone it will display yes/no option choose yes and press power button to unlock BOOT LOADER.
NO NEED ANY SORT OF HTCDEV. As I said these words are couple of weeks ago totally new for me.I did that 20-30 times but I didn't have any idea what so ever that why its needed and what for.
Few things for S-OFF and S-ON
S-OFF you have all access because security is OFF
NO BOOT.IMG require here.
S-ON you have security ON
Always flash boot IMG using adb or using fast boot drivers.
Thanks.
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