Hi
I have a European HTC One, with stock HTC HBOOT 1.54.
TWRP 2.6.3.0
And I flashed a pure GPE 4.3 ROM with no root.
Like many people I got the last OTA notification.
When I try to install it. It gets stuck at the end of the reboot countdown (in the system).
Can I do this security update?
Maybe by doing it through TWRP? It is a minor update so it should be OK, no?
Thanks for your help.
You need the stock recovery to flash the OTA
EddyOS said:
You need the stock recovery to flash the OTA
Click to expand...
Click to collapse
You mean the HTC stock recovery or the GPE stock recovery?
GPe, you can get it in the GPe RUU thread
EddyOS said:
GPe, you can get it in the GPe RUU thread
Click to expand...
Click to collapse
I put the Stock GPE recovery. No change. It still gets stuck at the end of the reboot countdown (in the system).
Can't I install the update with another method?
Nope. You could download the OTA file, copy it to the internal memory and flash it from the stock recovery manually and see if that works. Worked fine for me the other day (but I've since gone back to Sense)
Related
Hey all , minutes ago the 4.4 update was downloaded via OTA on my converted GPE htc one. I pressed install and when it went to recovery i get the error message "set metadata recursive" error , and the device dosnt even boot anymore. Any ideas what might be the problem ?
Izzymane said:
Hey all , minutes ago the 4.4 update was downloaded via OTA on my converted GPE htc one. I pressed install and when it went to recovery i get the error message "set metadata recursive" error , and the device dosnt even boot anymore. Any ideas what might be the problem ?
Click to expand...
Click to collapse
Sounds like you have a custom recovery? If so try stock GE recovery
Sent from my HTC One using Tapatalk
Nah I have the android guy with a red exclamation mark
Wow.. That's a lot of people with same issue.
SaHiLzZ said:
Wow.. That's a lot of people with same issue.
Click to expand...
Click to collapse
I have the exact same problem. I can get into the stock recovery but my device is not recognized in fastboot or adb
I got the same error when attempting to sideload 4.4 on my phone which I had previously converted to 4.3 GPE (rooted) using the instructions in the developer's forum. Guess it's time to do a full reflash.
I guess doing a full reflash is not gonna fix it. I would suggest flashing the stock recovery again and give it another shot.
Izzymane said:
I guess doing a full reflash is not gonna fix it. I would suggest flashing the stock recovery again and give it another shot.
Click to expand...
Click to collapse
are you guys s-on or s-off, newest 4.4 seems to bootloop with S-On devices!!
nkk71 said:
are you guys s-on or s-off, newest 4.4 seems to bootloop with S-On devices!!
Click to expand...
Click to collapse
I'm s-off with rumrunner
Then why not flash the full 4.4 RUU zip from GPE conversion thread?
SaHiLzZ said:
Then why not flash the full 4.4 RUU zip from GPE conversion thread?
Click to expand...
Click to collapse
True but I prefer OTA's , they just make more sense
Izzymane said:
I'm s-off with rumrunner
Click to expand...
Click to collapse
seems like lots of issues with 4.4,
from @makbil:
It seems only s-off, 4.4 compatible recovery and a clean flash are required. If all 3 are not met -> bootloop
Click to expand...
Click to collapse
EDIT: just noticed you're supposed to be 100% stock (converted), so the above quote shouldnt apply to you, i guess, sorry
could someone list the correct things to do to make a clean conversion?
thnaks
I'm also S-off with rumrunner, H-boot 1.54.
Flashed the RUU for 4.4 and all is fine. Luckily I backed up the data I cared about beforehand, just in case.
Hi - im a bit of a newb at this so bear with me!
i recently unlocked my bootloader and installed a stock 4.3 JWR66Y.H1 gpe rom and TWRP.
i am now getting the OTA notification but when i try to update it boots in to twrp, flashes the update, reboots and then i end up with a weird green screen. i have restored a backup in twrp back to 4.3, and everytime i try and install the update it does the same thing.
the phone is s-on - i have tried to s-off using rumrunner but it doesnt seem to like the rom and wont work (im on hboot 1.54).
any help would be greatly appreciated in getting the update to flash properly.
blackic3 said:
Hi - im a bit of a newb at this so bear with me!
i recently unlocked my bootloader and installed a stock 4.3 JWR66Y.H1 gpe rom and TWRP.
i am now getting the OTA notification but when i try to update it boots in to twrp, flashes the update, reboots and then i end up with a weird green screen. i have restored a backup in twrp back to 4.3, and everytime i try and install the update it does the same thing.
the phone is s-on - i have tried to s-off using rumrunner but it doesnt seem to like the rom and wont work (im on hboot 1.54).
any help would be greatly appreciated in getting the update to flash properly.
Click to expand...
Click to collapse
Make sure you follow all the instructions for rumrunner. You can't flash any unsigned firmware on s-on. Try manually flashing the update. Download the update and flash in recovery.
Ktan188 said:
Make sure you follow all the instructions for rumrunner. You can't flash any unsigned firmware on s-on. Try manually flashing the update. Download the update and flash in recovery.
Click to expand...
Click to collapse
so to clarify - the ota update is failing because the phone is s-on?
i have flashed the elemental kernel and will try rumrunner again later if thats the case.
4.4 rom
blackic3 said:
so to clarify - the ota update is failing because the phone is s-on?
i have flashed the elemental kernel and will try rumrunner again later if thats the case.
Click to expand...
Click to collapse
Having same issue, is there a ROM that can be loaded instead of going through ota update. I can't get s off to work no matter what I try
You MUST get S-OFF before you get 4.4 OTA, as if things go south, you are in big do-do. Read the last 5-6 pages and you will get an idea.
So do NOT install OTA until you have S-OFF and unlocked bootloader..
soff trouble
SaHiLzZ said:
You MUST get S-OFF before you get 4.4 OTA, as if things go south, you are in big do-do. Read the last 5-6 pages and you will get an idea.
So do NOT install OTA until you have S-OFF and unlocked bootloader..
Click to expand...
Click to collapse
How do I get soff doesn't seem to work no matter what I try
Hello,
I'm having an issue on my device. Whenever I flash it with a GPE rom, I get stuck in a boot loop. This ONLY happens with GPE roms. I can flash a rom with Sense 5.x and it works fine. This only started as of last week. Prior to that, I had flashed a GPE rom back in late December and it ran fine. Is there a fix to this? Or should I just stick to roms with Sense?
Izaku said:
Hello,
I'm having an issue on my device. Whenever I flash it with a GPE rom, I get stuck in a boot loop. This ONLY happens with GPE roms. I can flash a rom with Sense 5.x and it works fine. This only started as of last week. Prior to that, I had flashed a GPE rom back in late December and it ran fine. Is there a fix to this? Or should I just stick to roms with Sense?
Click to expand...
Click to collapse
update your recovery to TWRP 2.6.3.3 for anything related to KitKat
Izaku said:
Hello,
I'm having an issue on my device. Whenever I flash it with a GPE rom, I get stuck in a boot loop. This ONLY happens with GPE roms. I can flash a rom with Sense 5.x and it works fine. This only started as of last week. Prior to that, I had flashed a GPE rom back in late December and it ran fine. Is there a fix to this? Or should I just stick to roms with Sense?
Click to expand...
Click to collapse
Are you S-Off, 4.4 GPE require S-Off (in addition to recovery mentioned by @clsA)
clsA said:
update your recovery to TWRP 2.6.3.3 for anything related to KitKat
Click to expand...
Click to collapse
I've been running TWRP 2.6.3.3 from the get go. That's taken care of.
nkk71 said:
Are you S-Off, 4.4 GPE require S-Off (in addition to recovery mentioned by @clsA)
Click to expand...
Click to collapse
Just checked and realized I have S-On. This should be the problem. Thanks a bunch!
Izaku said:
Just checked and realized I have S-On. This should be the problem. Thanks a bunch!
Click to expand...
Click to collapse
no problem, maybe time to s-off
if you're having trouble with rumrunner, maybe check out @tobesedated recommendations: http://forum.xda-developers.com/showthread.php?t=2606577
and you can hit the thanks button for the posts you found useful
My phone right now is unlocked and with s-off. I was thinking I could relock the bootloader and run RUU to go back to complete stock (with S-OFF). My question is can I install the tmo update with S-OFF? Has anyone done this before? Or do I have to go back to S-ON in order to install the update?
I know that rumrunner does not work with HBOOT 1.56.
Any help would greatly be appreciated, thank you.
b1969 said:
My phone right now is unlocked and with s-off. I was thinking I could relock the bootloader and run RUU to go back to complete stock (with S-OFF). My question is can I install the tmo update with S-OFF? Has anyone done this before? Or do I have to go back to S-ON in order to install the update?
I know that rumrunner does not work with HBOOT 1.56.
Any help would greatly be appreciated, thank you.
Click to expand...
Click to collapse
don't think S-OFF or unlocked matters, just stock rom and recovery required
if i run RUU will that give me stock recovery?
b1969 said:
if i run RUU will that give me stock recovery?
Click to expand...
Click to collapse
If you have a ruu for your currently installed rom, you can extract the recovery from the zip and install.
Otherwise
http://forum.xda-developers.com/showthread.php?t=2545227
Pick the one that matches your current rom version
b1969 said:
My phone right now is unlocked and with s-off. I was thinking I could relock the bootloader and run RUU to go back to complete stock (with S-OFF). My question is can I install the tmo update with S-OFF? Has anyone done this before? Or do I have to go back to S-ON in order to install the update?
I know that rumrunner does not work with HBOOT 1.56.
Any help would greatly be appreciated, thank you.
Click to expand...
Click to collapse
My phone is unlocked/S-OFF. On the previous OTA updates, all I had to do was reflash the stock recovery and the updates proceeded normally, installed just fine. On this new OTA update to 4.4.2, however, that didn't work. I tried relocking the bootloader, flashed the stock recovery... nothing worked (it would get the red slash during the recovery part of the OTA update). Evidently, T-Mobile/HTC are now much more picky about modified devices.
So, to get the OTA to work, I had to run the last RUU from T-Mobile. That, of course, wiped my phone clean, but installed a locked fresh 4.3.1 ROM (still S-OFF). Then the OTA update ran perfectly, resulting in the 4.4.2 OS installed. Then I unlocked it, flashed TWRP recovery and rooted it. It's working beautifully.
Fuzi0719 said:
My phone is unlocked/S-OFF. On the previous OTA updates, all I had to do was reflash the stock recovery and the updates proceeded normally, installed just fine. On this new OTA update to 4.4.2, however, that didn't work. I tried relocking the bootloader, flashed the stock recovery... nothing worked (it would get the red slash during the recovery part of the OTA update). Evidently, T-Mobile/HTC are now much more picky about modified devices.
So, to get the OTA to work, I had to run the last RUU from T-Mobile. That, of course, wiped my phone clean, but installed a locked fresh 4.3.1 ROM (still S-OFF). Then the OTA update ran perfectly, resulting in the 4.4.2 OS installed. Then I unlocked it, flashed TWRP recovery and rooted it. It's working beautifully.
Click to expand...
Click to collapse
Thank you for the information.
Fuzi0719 said:
So, to get the OTA to work, I had to run the last RUU from T-Mobile. That, of course, wiped my phone clean, but installed a locked fresh 4.3.1 ROM (still S-OFF). Then the OTA update ran perfectly, resulting in the 4.4.2 OS installed. Then I unlocked it, flashed TWRP recovery and rooted it. It's working beautifully.
Click to expand...
Click to collapse
4.3.1???
Im only on 4.3 and cant update. Ex:3.24.531.3
no-root, Unlocked and s-off only
Hey guys. So I flashed Android 4.4.3 (KitKat) - latest official HTC One 6.09.401.12 (WWE) firmware (84.x series) to my Att HTC M7. I unlocked bootloader and rooted prior to that. Installed TWRP recovery. I didn't back up my original OS nor do a nandroid back up.
When I first flash it was 1/2 ok. I was able to get to the setup wizard on the rom. Then it reboot to recovery. All I can get is bootloader and recovery.
in order for adb sideload or just adb to work the steps I have to take are peculiar. I stumbled on this today. I have to connect my usb cable when the M7 is off. I boot into the bootloader via *power button and *volume down. Then I select fastboot, then I go back and select recovery. When it boots to recovery then I touch advanced and my device shows up. Also my OTG connection works fine.
So I downloaded the stock version odexed. I get errors on install. Actually I get errors trying to install any rom now. I've tried to unzip and rezip using winrar. Any clues as what I should try now? I wanted to post a pic of my bootloder info and the error message but alas I dont have 10 post.
BOOTLOADER
***TAMPERED***
***unlocked****
m7_ul S-on RH
HBOOT 1.57.0000
RADIO 4M.27.3218.14
OS 5.13.502.3
Error i get
E: unable to open zip file
error flashing zip '/usb-otg/one_.......
Thanks
MackadociousPrime38 said:
Hey guys. So I flashed Android 4.4.3 (KitKat) - latest official HTC One 6.09.401.12 (WWE) firmware (84.x series) to my Att HTC M7. I unlocked bootloader and rooted prior to that. Installed TWRP recovery. I didn't back up my original OS nor do a nandroid back up.
When I first flash it was 1/2 ok. I was able to get to the setup wizard on the rom. Then it reboot to recovery. All I can get is bootloader and recovery.
in order for adb sideload or just adb to work the steps I have to take are peculiar. I stumbled on this today. I have to connect my usb cable when the M7 is off. I boot into the bootloader via *power button and *volume down. Then I select fastboot, then I go back and select recovery. When it boots to recovery then I touch advanced and my device shows up. Also my OTG connection works fine.
So I downloaded the stock version odexed. I get errors on install. Actually I get errors trying to install any rom now. I've tried to unzip and rezip using winrar. Any clues as what I should try now? I wanted to post a pic of my bootloder info and the error message but alas I dont have 10 post.
BOOTLOADER
***TAMPERED***
***unlocked****
m7_ul S-on RH
HBOOT 1.57.0000
RADIO 4M.27.3218.14
OS 5.13.502.3
Error i get
E: unable to open zip file
error flashing zip '/usb-otg/one_.......
Thanks
Click to expand...
Click to collapse
Ok so i don't know why but after 4 tries I was able to flash a ROM. But its an ATT stock ROM I got it from the att ROM section. But I'm on tmobile
MackadociousPrime38 said:
Ok so i don't know why but after 4 tries I was able to flash a ROM. But its an ATT stock ROM I got it from the att ROM section. But I'm on tmobile
Click to expand...
Click to collapse
You won't receive ota update on an at&t phone if you are not on the at&t network.
What is your custom recovery version?
I would achieve s-off using Sunshine so you can fully convert your phone to another version which doesn't require a specific carrier to receive update like the WWE version (x.xx.401.x) or the Developer version (x.xx.1540.x)
alray said:
You won't receive ota update on an at&t phone if you are not on the at&t network.
What is your custom recovery version?
I would achieve s-off using Sunshine so you can fully convert your phone to another version which doesn't require a specific carrier to receive update like the WWE version (x.xx.401.x) or the Developer version (x.xx.1540.x)
Click to expand...
Click to collapse
So I achieved s off using Sunshine. Changed cid and mid to corresponding t-mobile spec. Flashed the RUU for t-mobile from the HTC website download. Now when I flash the RUU I suppose it takes out my recovery and flashed a stock recovery?
I had TWRP but now I have some weird recovery. Last time I went into it and I rebooted out it factory reset my HTC. Pain in the ass more than anything.
I was thinking I could flash a ROM and see if it performs as or better than the RUU. The only benefit of using the stock tmobile is OTA updates right?
Oh and since I don’t have twrp anymore should can I reflash that? I would like to make a backup of my OS before I start screwing around.
MackadociousPrime38 said:
So I achieved s off using Sunshine. Changed cid and mid to corresponding t-mobile spec. Flashed the RUU for t-mobile from the HTC website download. Now when I flash the RUU I suppose it takes out my recovery and flashed a stock recovery?
Click to expand...
Click to collapse
Yes, a ruu will re-write all stock software and firmware to the phone (system, recovery, kernel, radio, bootloader, drivers, and so on)
I had TWRP but now I have some weird recovery. Last time I went into it and I rebooted out it factory reset my HTC. Pain in the ass more than anything.
Click to expand...
Click to collapse
You can't do much using stock recovery except a factory reset. Stock recovery is needed for ota updates but if you are already on last version you don't reallt need it anymore and you can reflash twrp over it.
I was thinking I could flash a ROM and see if it performs as or better than the RUU. The only benefit of using the stock tmobile is OTA updates right?
Click to expand...
Click to collapse
If you already flashed the latest t-mobile ruu (lollipop), you will not receive any more ota updates. Lollipop 5.0.2 Sense 6 should be the last version for the M7. At least flashing the ruu was not a waste of time since it upgraded your firmware; newer custom roms requires the latest firmware to work properly.
Oh and since I don’t have twrp anymore should can I reflash that? I would like to make a backup of my OS before I start screwing around.
Click to expand...
Click to collapse
Yep I would relfash twrp and make a backup before trying other toms. You can always revert back to stock using the same ruu if you don't have a backup.