I've searched and searched and can't find this topic so here goes...
I have the DE and it is rooted. I'd like to install the OTA as I'm still running stock otherwise. Do I have to unroot to get it to install? For fun I tried loading it with CWM and that just locked it up.
Thoughts or threads I've missed?
im curious too :/ the only way i could update was unrooting and for that the only way i could do so, was restoring a backup from CWM, i couldnt falsha RUU or ZIP :/
would be great if some one help us to find out how to unroot (an easier way) or apply OTA even rooted (guess this is not possible :/)
eltoffer said:
im curious too :/ the only way i could update was unrooting and for that the only way i could do so, was restoring a backup from CWM, i couldnt falsha RUU or ZIP :/
would be great if some one help us to find out how to unroot (an easier way) or apply OTA even rooted (guess this is not possible :/)
Click to expand...
Click to collapse
As far as I know, OTA should work fine if you have ONLY rooted and NOT installed any custom recovery. So I believe restoring stock recovery could make your phone receive the OTA. I could be wrong too.
shahul_555 said:
As far as I know, OTA should work fine if you have ONLY rooted and NOT installed any custom recovery. So I believe restoring stock recovery could make your phone receive the OTA. I could be wrong too.
Click to expand...
Click to collapse
Hmmm then I'm a bit confused, I believe I have stock recovery installed, I haven't done anything other than backup and root. I just tried running the update from the prompt and it sends me to CWM. Maybe I'm misunderstanding what stock recovery is?
thepktrckt said:
Hmmm then I'm a bit confused, I believe I have stock recovery installed, I haven't done anything other than backup and root. I just tried running the update from the prompt and it sends me to CWM. Maybe I'm misunderstanding what stock recovery is?
Click to expand...
Click to collapse
CWM is a custom recovery, hence why it's not working
Sent from my Nexus 4 using xda premium
EddyOS said:
CWM is a custom recovery, hence why it's not working
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
D'oh! My bad.
In attempt to get the stock recovery back I've tried the RUU that should be for the 64GB DE edition but it keeps throwing an error. Is Brightstar US WWE RUU 3.4.10 v4.1 1.29.1540.3 the wrong one?
thepktrckt said:
D'oh! My bad.
In attempt to get the stock recovery back I've tried the RUU that should be for the 64GB DE edition but it keeps throwing an error. Is Brightstar US WWE RUU 3.4.10 v4.1 1.29.1540.3 the wrong one?
Click to expand...
Click to collapse
First things first is your phone the developer edition? Sorry to ask a silly question just want to make sure you are not trying to flash the wrong firmware to your phone.
You can find the stock recovery under the development thread and you can flash this with fastboot flash recovery recovery.img (in fastboot mode of course)
for a DE, you have to lock its bootloader and then using RUU to get it back to stock, or just fastboot flash the stock recoery image to override your custom recovery, both are working to update OTA according to my test.
Sent from my HTC One using xda app-developers app
I posted this in another section a couple days ago on how I did the OTA with my DE.
Now you do have to push a stock recovery to get it working but then after you load the OTA you can go back and push TWRP or CWM. I then reflashed supersu but not sure if I needed to or not.
You don't need to lock the bootloader on the DE edition.
MG
moregadget said:
I posted this in another section a couple days ago on how I did the OTA with my DE.
Now you do have to push a stock recovery to get it working but then after you load the OTA you can go back and push TWRP or CWM. I then reflashed supersu but not sure if I needed to or not.
You don't need to lock the bootloader on the DE edition.
MG
Click to expand...
Click to collapse
relocking bootloader is needed for the RUU way, for reflashing stock recovery way, it is not necessary.
Sent from my HTC One using xda app-developers app
zhangke said:
relocking bootloader is needed for the RUU way, for reflashing stock recovery way, it is not necessary.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I don't understand why you'd have to lock a bootloader for a device that came with it unlocked from the factory? Even the ruu from HTC for the DE requires you to lock the bootloader?
MG
moregadget said:
I don't understand why you'd have to lock a bootloader for a device that came with it unlocked from the factory? Even the ruu from HTC for the DE requires you to lock the bootloader?
MG
Click to expand...
Click to collapse
Actually I don't understand either, but it is true, I failed several times to use RUU gettting back stock before re-locking my DE, I guess HTC developer does not apply any special code for the DE RUU program, you can have a try if you have a chance to do so.
Dang I already relocated and RUU'd it... Oh well next time.
Thanks though!!
Sent from my Nexus 4 using xda app-developers app
Related
I'm on a GPe with custom kernel and recovery and root. I'm trying to take the OTA and I've flashed back to a stock kernel, but it doesn't seem to "take."
Sweep2wake still works even after a flash. This is the most confusing part for me. It even sticks after a kernel flash and factory reset.
Sent from my HTC One using xda premium
eallan said:
I'm on a GPe with custom kernel and recovery and root. I'm trying to take the OTA and I've flashed back to a stock kernel, but it doesn't seem to "take."
Sweep2wake still works even after a flash. This is the most confusing part for me. It even sticks after a kernel flash and factory reset.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Are you trying to take the OTA directly through the Device OTA option or via this thread?: http://forum.xda-developers.com/showthread.php?t=2390319
If you're doing it direct through the phone it wont work without stock kernel and recovery. If you download the OTA in the thread I linked and follow the instructions it should work.
Donjuanal said:
Are you trying to take the OTA directly through the Device OTA option or via this thread?: http://forum.xda-developers.com/showthread.php?t=2390319
If you're doing it direct through the phone it wont work without stock kernel and recovery. If you download the OTA in the thread I linked and follow the instructions it should work.
Click to expand...
Click to collapse
That's part of the question. Why won't flashing the stock kernel fix it and erase stuff like sweep2wake?
Sent from my HTC One using xda premium
This is ridiculously aggravating.
I've got a stock kernel, stock recovery, OTA file on my SD card in about 3 different places.
Every time i boot to recovery it tries to mount hte storage 5 times and fails. Then clicking install from any location (cache, sd, phone storage) just says "invalid operation" and the phone reboots. Whats the problem here??
eallan said:
This is ridiculously aggravating.
I've got a stock kernel, stock recovery, OTA file on my SD card in about 3 different places.
Every time i boot to recovery it tries to mount hte storage 5 times and fails. Then clicking install from any location (cache, sd, phone storage) just says "invalid operation" and the phone reboots. Whats the problem here??
Click to expand...
Click to collapse
Sounds like you have an issue with your stock something (recovery/kernel/hboot). If you're on a GPe One just flash the RUU for 4.2.2 and then try again.
Donjuanal said:
Sounds like you have an issue with your stock something (recovery/kernel/hboot). If you're on a GPe One just flash the RUU for 4.2.2 and then try again.
Click to expand...
Click to collapse
Yeah, I think I'll do that. I just don't know what it could be, all i changed was the kernel (to get logo as recent apps.)
Thanks.
Did you relock the bootloader? If you want to use OTA's, bootloader has to be locked in order for it to install.
eallan said:
Yeah, I think I'll do that. I just don't know what it could be, all i changed was the kernel (to get logo as recent apps.)
Thanks.
Click to expand...
Click to collapse
Are you using a custom launcher? logo to recent apps isnt a mapping I'm aware of.
cee43ja1 said:
Did you relock the bootloader? If you want to use OTA's, bootloader has to be locked in order for it to install.
Click to expand...
Click to collapse
I'm on an ATT HTC ONE converted to GPe via S-OFF so my bootloader wasn't locked when I installed the OTA.
Donjuanal said:
I'm on an ATT HTC ONE converted to GPe via S-OFF so my bootloader wasn't locked when I installed the OTA.
Click to expand...
Click to collapse
But you have S-OFF. That bypasses bootloader anyways. Doesn't matter if the bootloader is locked then; S-OFF will eliminate the security checks.
cee43ja1 said:
But you have S-OFF. That bypasses bootloader anyways. Doesn't matter if the bootloader is locked then; S-OFF will eliminate the security checks.
Click to expand...
Click to collapse
Ohh, Ok, that makes sense then.
Hi guys...
So I've been searching for a fix for my google play edition htc one... I'm currently on stock 4.2.2, I unlocked the bootloader, installed CWM, rooted the device, installed a custom kernel. Everything was perfectly fine until I wanted to install 4.3 on my phone. I never flashed anything but the kernel to this phone. (since I knew cm10.2 would need time to get massaged) I am having problem flashing any rom onto my phone.
I got the OTA, I tried installing that, and in the middle of the install, the android icon goes from the blue swirl to the android lying down dead.
I tried uninstalling the kernel... no good. I reflashed the stock 4.2.2 recovery, no luck. I tried to RUU the phone (after relocking the device), and it fails with the message (remote: 12 signature verify fail). I get the same error w/ the 4.2.2 and 4.3 RUU... (both from the conversion to google edition thread)
I gave up on going w/ stock after trying several times. I downloaded the cm10.2 official nightly for the m7ul, transferred the zip file, and installed it thru CWM but I get the "Status 7" error that says "assert failed: getprop("ro.product.device") == m7 II etc. etc. I checked my build.prop and my ro.product.device is set to m7.... just like how it is supposed to be....
Is there anything I'm doing wrong here? Do you guys have any idea why I am unable to flash anything?? Any kind of help is appreciated.
Thank you in advance.
Install twrp or cwm again. Install nammit94's stock 4.2.2 rom. Put stock recovery back. Software update should install 4.3 then. The ruu won't work to restore you because it's a user made unsigned package and only works on s-off devices. Just installing stock kernel probably failed because there are non stock modules left over in /system nammit94's rom should set things right
gunnyman said:
Install twrp or cwm again. Install nammit94's stock 4.2.2 rom. Put stock recovery back. Software update should install 4.3 then. The ruu won't work to restore you because it's a user made unsigned package and only works on s-off devices. Just installing stock kernel probably failed because there are non stock modules left over in /system nammit94's rom should set things right
Click to expand...
Click to collapse
Why not just flash a stock 4.3 ROM and mor worry about OTA
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Why not just flash a stock 4.3 ROM and mor worry about OTA
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
he want's back to stock I assumed. But yeah that works too, Turge has a stock 4.3 rom.
Thanks for the reply guys. I am downloading turges rom.. Hopefully it'll flash. But even if it does flash... does that mean I won't be able to go back to stock gpe state thru ruu?
Sent from my HTC One using Tapatalk 4
idealz said:
Thanks for the reply guys. I am downloading turges rom.. Hopefully it'll flash. But even if it does flash... does that mean I won't be able to go back to stock gpe state thru ruu?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I think you can go back to stock, but read first. There are posts for how to do it. I think your mistake was you tried to flash an OTA with a custom recovery, doesn't work..ll
There is no ruu for an s-on htc one Google edition. You have to be very careful. Make a nandroid.
I tried flashing the stock recovery back before applying ota too.. Can you point me to the right thread?? I've been searching but can't seem to find the right info... BTW I think turges ROM worked.. Not sure why cm didn't
Sent from my HTC One using Tapatalk 4
gunnyman said:
There is no ruu for an s-on htc one Google edition. You have to be very careful. Make a nandroid.
Click to expand...
Click to collapse
OK that's what I was starting to think.. I do have some backups but that doesn't really take me back to complete stock state... I guess I'll just wait for the 1.54 s-off
Sent from my HTC One using Tapatalk 4
idealz said:
OK that's what I was starting to think.. I do have some backups but that doesn't really take me back to complete stock state... I guess I'll just wait for the 1.54 s-off
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
a stock backup + stock recovery, which is flashable should be fine.
I have a backup of post-rooting stock and I tried using that with the ota with stock recovery... But that didn't work.. I guess I should've backed up prior to rooting? Not sure if it makes a difference... Is there an easy way to unroot other than ruu?
Sent from my HTC One using Tapatalk 4
idealz said:
I have a backup of post-rooting stock and I tried using that with the ota with stock recovery... But that didn't work.. I guess I should've backed up prior to rooting? Not sure if it makes a difference... Is there an easy way to unroot other than ruu?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Flash Nammit94's unrooted 4.2.2 ROM
Thanks gunny. Found that ROM.. Had dig a little since his user name was Namit1994. I'll try this out later...
Back to the cm10.2 problem... Any reason why my gpe wouldn't flash it?
Sent from my HTC One using Tapatalk 4
idealz said:
Thanks gunny. Found that ROM.. Had dig a little since his user name was Namit1994. I'll try this out later...
Back to the cm10.2 problem... Any reason why my gpe wouldn't flash it?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
status7 could be from any number of issues, probably best to ask in the CM10.2 thread
All,
I am pulling my hair out, I decided to root my phone today so I could delete the default APN's, I have tried CWM and also TWRP.
All was fine, as soon as I installed Busybox something went horribly wrong, my phone will not boot up and just displays the "HTC Logo" I can get to the boot menu and boot to either CWM or TWRP. However there is nothing I can do within there, I cannot find a RUU for my model (CID is Orange) I have found a nandroid backup but CWM/TWRP refuses to see it via OTG and I have tried lots of USB Sticks.
I really do not know what to do next, I cannot turn S-OFF as HBOOT is 1.54
What can I do, I have read thread after thread.
Is there a default recovery.img or one for my carrier as I cannot find it.
Many thanks,
Dale
Managed to restore a nandroid, but I have no touch screen!
Tried clearing cache etc, have currently got a mouse plugged in to it to control it, there is an OTA available so going to try that.
DaleR said:
Managed to restore a nandroid, but I have no touch screen!
Tried clearing cache etc, have currently got a mouse plugged in to it to control it, there is an OTA available so going to try that.
Click to expand...
Click to collapse
Don't try it with a custom recovery. You'll need to relock your bootloader too.
No touchscreen is a firmware issue. The nandroid you restored will be an old one not compatible with the latest firmware..
Sent from my HTC One using xda premium
redbull123 said:
Don't try it with a custom recovery. You'll need to relock your bootloader too.
No touchscreen is a firmware issue. The nandroid you restored will be an old one not compatible with the latest firmware..
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thank you for the reply
I've re-locked the bootloader.
What do I do next?, I cannot find a later nandroid backup anywhere
DaleR said:
Thank you for the reply
I've re-locked the bootloader.
What do I do next?, I cannot find a later nandroid backup anywhere
Click to expand...
Click to collapse
Just for now for the sake of getting a working phone I would just flash a 4.2.2 stock ROM, or Sense-based Rom. You'll need to unlock your bootloader again obviously.
Sent from my HTC One using xda premium
redbull123 said:
Just for now for the sake of getting a working phone I would just flash a 4.2.2 stock ROM, or Sense-based Rom. You'll need to unlock your bootloader again obviously.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks for the reply, was up till 3am trying to get around this and got it going eventually.
That's what I have done for now, I sideloaded a stock Sense ROM which came with a stock recovery.img, guess I have to wait for a S-OFF for 1.54 if it ever happens.
htc one deleted os
DaleR said:
Thanks for the reply, was up till 3am trying to get around this and got it going eventually.
That's what I have done for now, I sideloaded a stock Sense ROM which came with a stock recovery.img, guess I have to wait for a S-OFF for 1.54 if it ever happens.
Click to expand...
Click to collapse
i have done the same deleted the os off my htc one (CID o2 ) and can not find a the same kind of rom I can get into recovery and have twrp but side loader just says loading and my laptop wont see my phone keeps saying htc mtp driver fail any chance u can let me know how you did yours thanks
If you find your PC/laptop is not seeing the phone then ensue you have the latest drivers on the PC
mini sdk
http://goo.gl/T6InE
HTC Driver version 4.2.0.001
Some folks find Hasoon's All in One very useful - a grate bit of kit
http://forum.xda-developers.com/showthread.php?t=2183942
I would like to install the AT&T OTA of 4.4.2 but have a custom recovery and am unable to upgrade. I am rooted with the stock 4.3 ROM and have the twrp recovery installed. I have S-ON. I've searched around trying to find a way to get this to work but can't seem to figure it out. I've tried looking around for an AT&T 4.3 stock recovery to try and flash it but can't seem to find one. The one from the Dev sticky page is not available for download. Can someone detail the steps I have to perform to get the 4.4.2 OTA from AT&T. Thanks in advance.
[SOLVED]
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else.
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
SaHiLzZ said:
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
Click to expand...
Click to collapse
Awesome, that's what I wanted to hear. I'm going to give that a shot. Thank you
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
SaHiLzZ said:
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
Click to expand...
Click to collapse
I flashed my recovery but recovery now just gets a read triangle with the exclamation
Let the phone download OTA and apply it
sent from my mobile device
SaHiLzZ said:
Let the phone download OTA and apply it
sent from my mobile device
Click to expand...
Click to collapse
Doing now.
It downloaded and attempted to install, then failed half way. Anything else I have to do before I update? Do I have to lock my bootloader again or unroot?
Sent from my HTC One using xda app-developers app
Yea lock bootloader
sent from my mobile device
No dice. Same deal.
Sent from my HTC One using xda app-developers app
Text/Photo of the error?
SaHiLzZ said:
Text/Photo of the error?
Click to expand...
Click to collapse
It doesn't give me an error. The OTA downloads, reboots and gets to a triangle with the green arrows inside and starts installing, then about 25% of the way it stops and goes to a red triangle. I'm thinking the MD5 to one of my files may be failing. I installed an edit to the framework sometime ago to get the hotspot working (that's the only change to the stock rom I've made). It doesn't really give me an error message though.
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
SaHiLzZ said:
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
Click to expand...
Click to collapse
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
SMaximus7 said:
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
Click to expand...
Click to collapse
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
mb_guy said:
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
Click to expand...
Click to collapse
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
SMaximus7 said:
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
Click to expand...
Click to collapse
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
mb_guy said:
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
Click to expand...
Click to collapse
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
SMaximus7 said:
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
Click to expand...
Click to collapse
Ya, I was lucky, had a nandroid . But you are right the recovery in the ota is too new.
Solved
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else. Thanks everybody for chiming in.
Hey, just seen that sense 6 will get pushed out beginning may 12th in canada. My question is that my phone has an unlocked bootloader, is rooted, but not s-off. I havn't installed a new rom. has the same as after i unlocked bootloader. Will I be able to install the update when it is pushed?
Howie3045 said:
Hey, just seen that sense 6 will get pushed out beginning may 12th in canada. My question is that my phone has an unlocked bootloader, is rooted, but not s-off. I havn't installed a new rom. has the same as after i unlocked bootloader. Will I be able to install the update when it is pushed?
Click to expand...
Click to collapse
Until you have the stock recovery ...you can install the update when it is pushed
As you've stated that you phone is rooted then you might've flashed TWRP or CWM to do it so
flash back the stock recovery of your model and you are good to go...
Did you unlock via htcdev ?
Sent from my HTC_PN071 using Tapatalk
I have twrp and did unlocked via HTC dev
Sent from my HTC One using XDA Free mobile app
i have the latest hboot as well. i didnt actually unlock and root until after the last OTA update.
Howie3045 said:
Bell Canada HTC One, want to flash the stock recovery back so that i can get the Sense 6 update. Phone is rooted and unlocked with HTC dev but does not have S-off. been running into issues with hboot 1.56 in that regard and cant get S-off to work. Anyway. From what I gather the OTA update wont work without the stock recovery. How do I know which one to install
Click to expand...
Click to collapse
You need the stock recovery that match your fw version. I.e if you are on 3.23.666.1 then you need the recovery from this version.
Here is a collection of stock recovery. If you can't find yours, you can extract the recovery.img from the previous ota. The recovery packed in the upcoming ota update might also work.
my software number now says 4.19.666.8. im as up to date as i can be through bell so if i flash an old recovery will it cause problems? or will i just get an OTA update to bring it back to the latest version
Howie3045 said:
my software number now says 4.19.666.8. im as up to date as i can be through bell so if i flash an old recovery will it cause problems? or will i just get an OTA update to bring it back to the latest version
Click to expand...
Click to collapse
then flash the 4.19.666.8 stock recovery. an older recovery might work, not for sure. Or the recovery packed in the upcoming ota might also work.
I think I'm a little over my head now. Lol. I think I'm also missing some of the apps that were removed after the HTC dev unlock. Not good.
Sent from my HTC One using XDA Free mobile app
Howie3045 said:
I think I'm a little over my head now. Lol. I think I'm also missing some of the apps that were removed after the HTC dev unlock. Not good.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you'll probably have to restore these app if you want to update. The ota updater script md5 check these apps. If they are not on your phone, the ota installation will probably fail because of MD5 mismatch.
See this post from arhd if you want more details
Ota update will not apply until and unless you have pure stock rom.
e.g. If your phone is pure stock you unlock its bootloader it will remove some apps which are installed in preload. Now if you relock the bootloader and flash stock recovery the ota update will not be applied as during flashing ota update check for these apps whether they are installed in preload or not. For ota updates to applied succesfully you need to run RUU of your model then flash ota.
Sent from my HTC One using XDA Premium 4 mobile app
asking me to do the update now. im really not sure what exactly i need to do to get it now
alright ive found a nandroid backup for bell 3.23.666.1 and i also have the recovery to go with it. if i run that nandroid and flash the recovery do ya'll think i can then get the OTA?
alright i tried this any couldnt get it to work. i flashed the recovery then rebooted phone. it asked to do the 4.19.666.8 update then rebooted, went to recovery but it was still TWRP recovery and not stock. so before getting to far involved i reflashed the nandroid i made this morning.
the whole not being able to s-off with hboot 1.56 is a bit of a pain. ive tried rumrunner and firewater with no luck.
so troubleshooting purposes i should add that i dont care about the tampered bar or anything like that. i dont have to send it back i just want the sense 6 ota. l
Howie3045 said:
alright i tried this any couldnt get it to work. i flashed the recovery then rebooted phone. it asked to do the 4.19.666.8 update then rebooted, went to recovery but it was still TWRP recovery and not stock. so before getting to far involved i reflashed the nandroid i made this morning.
the whole not being able to s-off with hboot 1.56 is a bit of a pain. ive tried rumrunner and firewater with no luck.
so troubleshooting purposes i should add that i dont care about the tampered bar or anything like that. i dont have to send it back i just want the sense 6 ota. l
Click to expand...
Click to collapse
I already told you run ruu of your phone. Then you will be able to apply ruu.
Sent from my HTC One using XDA Premium 4 mobile app
Unfortunately a RUU of 4.19.666.8 is hard to come by
Howie3045 said:
Unfortunately a RUU of 4.19.666.8 is hard to come by
Click to expand...
Click to collapse
I haven't seen one yet, the CWR backup was the best I could find.
Maybe someone who has Sense 6 will make and upload a TWRP or CWR backup.
Howie3045 said:
alright i tried this any couldnt get it to work. i flashed the recovery then rebooted phone. it asked to do the 4.19.666.8 update then rebooted, went to recovery but it was still TWRP recovery and not stock
Click to expand...
Click to collapse
Then you didn't flash stock recovery... Either the recovery you flashed was not stock, or you didn't flash it right.
Now that I think about it after the flash it didn't do anything so I had to hold the power for 10 seconds. After that I panicked and just reverted back to my nandroid from that morning.
Sent from my HTC One using XDA Free mobile app