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.
Related
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
Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.
I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One
Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder
Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.
Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.
kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!
bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.
kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.
help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance
Hello, I have HTC One Intl (see my signature) on everything stock. Phone is S-off and rooted. Yesterday I had seen 4.3 OTA notification, downloaded it and tried to install, but installation failed in recovery (red triangle with exclamation). I've tried it several times, but no luck - phone reboots to recovery, installation process begins and fails at ~30 per cent.
Help me find out, why it happens (maybe i can find installation log somewhere, but don't know where to search) and how to install this update.
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Guich said:
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Click to expand...
Click to collapse
Recovery is stock.
Can I use Voodoo OTA Rootkeeper to temporary unroot? At least it gives such possibility, don't know will it work or not.
Is locked/relocked bootloader obligatory? if yes, I will search how to relock it again.
Thanks.
valery.m said:
Hello, I have HTC One Intl (see my signature) on everything stock. Phone is S-off and rooted. Yesterday I had seen 4.3 OTA notification, downloaded it and tried to install, but installation failed in recovery (red triangle with exclamation). I've tried it several times, but no luck - phone reboots to recovery, installation process begins and fails at ~30 per cent.
Help me find out, why it happens (maybe i can find installation log somewhere, but don't know where to search) and how to install this update.
Click to expand...
Click to collapse
Guich said:
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Click to expand...
Click to collapse
Dont mean to intrude, but I'm pretty sure he can leave the bootloader unlocked, even root I think
He does need to have stock recovery, stock rom (including the preloaded apps that get deleted when unlocking), I think that's about it.
valery.m said:
Recovery is stock.
Can I use Voodoo OTA Rootkeeper to temporary unroot? At least it gives such possibility, don't know will it work or not.
Is locked/relocked bootloader obligatory? if yes, I will search how to relock it again.
Thanks.
Click to expand...
Click to collapse
I don't know i never used this app.
Yeah, probably bootloader relocked is necessary
nkk71 said:
Dont mean to intrude, but I'm pretty sure he can leave the bootloader unlocked, even root I think
He does need to have stock recovery, stock rom (including the preloaded apps that get deleted when unlocking), I think that's about it.
Click to expand...
Click to collapse
Mate i have a friend that with s-off needed a relocked bootloader for OTA.
I'm not sure.
but i think is better upgrading with a flash or firmware and rom.
Guich said:
I don't know i never used this app.
Yeah, probably bootloader relocked is necessary
Mate i have a friend that with s-off needed a relocked bootloader for OTA.
I'm not sure.
but i think is better upgrading with a flash or firmware and rom.
Click to expand...
Click to collapse
Hey @Guich, I personally havent tried, but did some searching a while back (while helping someone with a similar problem), and I think it did work with unlocked bootloader, I also just found this: http://forum.xda-developers.com/showthread.php?t=2306880
nkk71 said:
Hey @Guich, I personally havent tried, but did some searching a while back (while helping someone with a similar problem), and I think it did work with unlocked bootloader, I also just found this: http://forum.xda-developers.com/showthread.php?t=2306880
Click to expand...
Click to collapse
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Why turn to stock for rooted another time?
Guich said:
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Why turn to stock for rooted another time?
Click to expand...
Click to collapse
You're right :good: With s-off, so no problems locking/unlocking etc
@nkk71 Thanks for thread, I will try to restore that APKs and flash OTA again.
valery.m said:
@nkk71 Thanks for thread, I will try to restore that APKs and flash OTA again.
Click to expand...
Click to collapse
make sure the "preload" apps are for your version, mate!!
If you signature is correct: "ROM: Stock 2.24.401.8 (Android 4.2.2)" Maybe just best to use the Guru Reset ROM.
EDIT: I recommend full backup to PC first though, just in case!!
Guich said:
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Click to expand...
Click to collapse
I want phone to do it itself It can "see" the OTA update - so let it to flash! :laugh:
nkk71 said:
make sure the "preload" apps are for your version, mate!!
If you signature is correct: "ROM: Stock 2.24.401.8 (Android 4.2.2)" Maybe just best to use the Guru Reset ROM.
EDIT: I recommend full backup to PC first though, just in case!!
Click to expand...
Click to collapse
Yes, of course, i will search apps for my ROM version and backup it to PC before doing anything.
Signature is correct, i've taken it from fastboot screen.
valery.m said:
Yes, of course, i will search apps for my ROM version and backup it to PC before doing anything.
Signature is correct, i've taken it from fastboot screen.
Click to expand...
Click to collapse
fastboot screen only shows your firmware, you also need a stock ROM (you can check which version you have in Settings -> About -> etc.)
nkk71 said:
fastboot screen only shows your firmware, you also need a stock ROM (you can check which version you have in Settings -> About -> etc.)
Click to expand...
Click to collapse
Same version there
ROM is stock, it was updated via OTAs from 4.1.2 to 4.2.2. All was fine.
Only my customization is rooting, s-off and unlocking bootloader.
valery.m said:
Same version there
Click to expand...
Click to collapse
then you may just be missing the "preloaded" apps, here's an idea, why not dirty flash (ie no WIPE) the Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
BTW: the reason I mentioned the backup to PC, is one time I flashed stock recovery (and accessed it), and i was unpleasantly surprised it wiped my internal storage.
nkk71 said:
then you may just be missing the "preloaded" apps, here's an idea, why not dirty flash (ie no WIPE) the Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
BTW: the reason I mentioned the backup to PC, is one time I flashed stock recovery (and accessed it), and i was unpleasantly surprised it wiped my internal storage.
Click to expand...
Click to collapse
Thanks for the idea, i will try it!
valery.m said:
Thanks for the idea, i will try it!
Click to expand...
Click to collapse
Good luck, and if you do (and wanna help the rest of the community) can you try with both ROOT and unlocked bootloader first, and see if it works.
I know it's a bit of a hassle but at least you would be able to confirm if ROOT or unlocked bootloader are interfering with the update
unlocked bootloader will not interfere with ota,did it myself
sent from my s-off 801n M7_UL
steelmaggot said:
unlocked bootloader will not interfere with ota,did it myself
sent from my s-off 801n M7_UL
Click to expand...
Click to collapse
Can you describe the whole procedure?
Sorry guys, i'm not so patient - so flashed new firmware from OTA's zip archive, flashed TWRP and then flashed ARHD. I'm happy now
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.
So I have a bell m7. Because of this I can't simply use an RUU I have a stock rom 4..19.666.8 which is sense 5.5 android 5.3.
I've tried to S-OFF several times to no avail. firewater says that It wont work on my device. I also have tried to flash stock recoveries to be able to do the OTA and it fails after about half way with the red triangle. I'm assuming this is because of a miss matched recovery and software versions.
Any ideas?
Your bootloader is unlocked correct?
Ajxx16 said:
Your bootloader is unlocked correct?
Click to expand...
Click to collapse
Yes
bobruels44 said:
Yes
Click to expand...
Click to collapse
when you are in stock recovery, press volume up then power and you will see which assert is failing during the ota update installation.
If you are unlocked usually the reason is because it deletes some of the apps on your phone. The OTA's want it fully stock so if it's missing any of them it will fall over. Find out what files are missing. Then you just need to copy those apps from at OTA file for your software version which you should be able to find online
Sent from my HTC One using XDA Premium 4 mobile app
alray said:
when you are in stock recovery, press volume up then power and you will see which assert is failing during the ota update installation.
Click to expand...
Click to collapse
It turns out it was the user apps, but now it's saying '/data/preload/HtcRingtoneTrimer.apk has unexpected contents'
I've tried a few different versions, any ideas?