Database Develop

[INFO] Nexus 5 OTA Help-Desk

..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OTA Help-Desk
*5.1.1 LMY48B Available*
*5.1 LMY47I Available*​
*5.1 LMY47D Available*
This thread is only for OTA help and nothing else!
Flash stock recovery before proceeding
​.​
NOTE: If You are a rooted non-stock user I suggest you look at @rootSU's thread before proceeding as his method for rooted users is far less prone to cause issues.
http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876
First, let's talk about what an OTA is:
An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have it up and running, with the latest software.
We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.
Now that you have read the important info above, Let's update your Nexus 5!
In order for the OTA to apply successfully without intervention; you must be completely stock
From 4.4.4 KTU84P
Current Bootloader: HHZ11k
Current Radio M8974A-2.0.50.1.16
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
From 4.4.3 KTU84M
Current Bootloader: HHZ11k
Current Radio:M8974A-2.0.50.1.13
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
Note: Literally any modification will break the OTA. Xposed, DPI, build.prop, volume mod, etc. ANYTHING!
Seriously, I'm not joking guys.
If you meet the above criteria, the OTA will complete successfully.
If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.
Current OTA's
5.1.1 LMY48B from LMY47D: https://dl.dropboxusercontent.com/u/33560221/OTA_update_from_lmy47d_to_lmy48b.zip
5.1 LMY47I from 5.0.1 LRX22C: http://android.clients.google.com/packages/ota/google_hammerhead/90bd789f499ea5ad33510c568ec920aae7214d34.signed-hammerhead-ota-LMY47I-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0.1 LRX22C: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0 LRX21O: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
Legacy OTA's
5.0.1 LRX22C from 5.0 LRX210: http://goo.gl/eoV0GE
5.0.1 LRX22C-from-KTU84: http://android.clients.google.com/packages/ota/google_hammerhead/6dadaf477bab65f42f5681b03bd535f431594b95.signed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
5.0 LRX21O-from-4.4.4 r2 KTU84Q: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
Thanks @pppp6071
5.0 LRX21O-from-4.4.4 KTU84P: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
Thanks @saberdragon18
4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Thanks @sucro
http://forum.xda-developers.com/showpost.php?p=46289250&postcount=1 Thanks @oldblue910
These are the most common scenarios. If you aren't sure where you fit, feel free to ask.
NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions.
Scenario #1
You are completely stock. Unlocked/locked bootloader. No root permissions.
Continue to Section A
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Scenario #3
You are stock, with Xposed Framework installed.
Continue to Section C
Scenario #4
You are stock, with a custom kernel and/or old radio and no other modifications.
Continue to Section D,1
Scenario #5
You are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.
Continue to Section D,2 or See 2nd Post (Special Scenario #1) **Special Scenario #1 is not updated yet**
Scenario #6
You are running a Custom ROM
Continue to Section D,3
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. It's attached at the bottom of this. Also Starting with Android 5.0 you must sideload the OTA through a stock recovery. Custom recoveries for now will error out.
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press and hold POWER, and then press volume up and release. The menu will appear. Select “apply update from adb
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Section C: Uninstalling Xposed Framework
Use the Xposed Framework Installer to remove the framework before applying the OTA.
Go into Xposed Framework, Framework-> Uninstall (it will restore the original file "app_process") then reboot.
NOTE: If you just uninstall Xposed Framework (the app itself), even after a reboot the "app_process" file (in /system/bin) is still the modified one by Xposed Framework, the original file is not restored.
Xposed Installer and info can be found here.
Once Xposed is uninstalled; jump back up to Section A on stock recovery (5.0 and above) and Section B on custom recovery (4.4.4 and below).
Thanks @Hammer_Of_The_Gods & @C3C076
Section D: Let’s get back to stock
1) Flash the stock boot.img and/or radio.img (whatever is applicable) from the factory image using fastboot. Also flash recovery.img if updating to 5.0
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img
fastboot flash recovery recovery.img
NOTE: Some custom kernels will modify files in /system/ If this is the case you will see a status 7 error and the file modified. The easiest way to fix this is to flash the system.img
2) Replace the stock kernel or .apk(s) you removed or modified.
If you don't have a backup of removed or modified apk(s) flash the system.img
Note: These must be the exact versions that shipped with the rom.
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
3) Flash the KOT49H stock image. Follow abaaaabbbb63's guide if you need help.
--------------------------------------------------------------------------------------------------------------------
After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:
Section A if you are running stock recovery.
Section B if you are running a custom recovery (for 4.4.4 OTAs and below only).
Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.
FAQ
Q: When in Recovery/Bootloader the phone isn't listed in Windows Device Manager.
A: Uninstall all current N5 drivers and install the Universal Naked driver. Turn on USB Debugging in Developer Settings and boot to recovery
Q: I'm seeing a status 7 error when trying to install the OTA
A: Look at the error closely. It will describe on the file it is failing at. Post the file path so we can help resolve the issue.
Q: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?
A: Flash the custom recovery of your choice in fastboot and use it to regain root permissions
Q: I've tried everything, but I'm still getting status 7 errors.
A: Unfortunately you may have to start from scratch. Follow Section C1.
Q: I flashed a .zip file that modified (insert mod here.) Will I the OTA install successfully?
A: No, any modification at all will cause the OTA to fail.
Q: Why do I get a "cannot read update.zip" error when trying to sideload?
A: If you named the file update.zip, the actual name would be update.zip.zip. Windows auto names extensions by default. That could be your problem. If not try another usb cable or a different usb port. If that still doesn't work, make sure you type exactly what you renamed the file. You may have made a typo. It is also case-sensitive.
UPDATED: 6/19/14 - Updated for KTU84P

..
Special Scenario #1
If you are running the stock ROM, rooted, with a custom kernel, and you want to retain root after the OTA; follow this great detailed walkthrough by @Lettuce!
If it helps you, make sure you thank him on the original post, located here:
http://forum.xda-developers.com/showpost.php?p=48212456&postcount=2681) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) download Latest SuperSU from http://download.chainfire.eu/supersu
5) put SuperSU.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install latest SuperSu.zip
18) clear dalvik and cache
19) reboot phone​UPDATED: 1/25/15

Good job :thumbup:Nice to see you here
Sent from my NEXUS 5

Scenario #2: Will I receive a message ?
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).

If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.

david31262 said:
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).
Click to expand...
Click to collapse
I believe the new versions of recovery will ask to keep the custom recovery and/or root. We'll see how the custom recoveries handle the OTA on the N5 and I'll update the post accordingly.
BirchBarlow said:
If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.
Click to expand...
Click to collapse
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel.
Sent from my Nexus 5 using Tapatalk

What about cf auto root? From the description it looks like that only adds the root apps and nothing else.

El Daddy said:
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel. Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.

Evo_Shift said:
What about cf auto root? From the description it looks like that only adds the root apps and nothing else.
Click to expand...
Click to collapse
BirchBarlow said:
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.
Click to expand...
Click to collapse
Cf-auto root and super su should be fine as they don't modify the kernel.
Sent from my Nexus 5 using Tapatalk

Nice!!
Every time someone mentions me, I regret choosing this username.

abaaaabbbb63 said:
Nice!!
Every time someone mentions me, I regret choosing this username.
Click to expand...
Click to collapse
Yeah, I regretted mentioning you.
Thank you copy & paste.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.

maxal said:
Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.
Click to expand...
Click to collapse
As long as everything is stock an unlocked bootloader does not effect an OTA.
Sent from my Nexus 5 using XDA Premium 4 mobile app

El Daddy said:
Nexus 5 OTA Help-Desk​
Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C
Scenario #4
You are running a Custom ROM
Continue to Section C
Section C: Let’s get back to stock
You have two options to do this:
Option #1 Flash the KRT16M stock image. Follow @abaaaabbbb63 guide if you need help.
If you want to keep data intact flash only the boot.img, system.img, and recovery.img (optional)
OR
Option #2 Replace the stock images or .apk(s) you removed or modified.
Note: These must be the exact versions that shipped with the rom.
Click to expand...
Click to collapse
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.

Synyster06Gates said:
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.
Click to expand...
Click to collapse
That is correct.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
That is correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did it... everything booted correctly, my apps and settings were still there, but for what ever reason - my APN settings will not stay. I save it, and it takes me back to an empty menu. Any ideas?

Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Tried that. Says it's done, nothing comes up.
I tried searching for network as well but that didn't work either. The wifi works, but no network.
I restored a backup I made last night and it still isn't working. Any ideas?
Tried to do a system wipe then restore again
E: Unable to mount '/cache'

Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed it. I went ahead and flashed the stock cache.img as well and all is working. Some how I guess the cache corrupted or deleted.

[ROM]HTC One Software Update - 4.06.651.4 (Android KitKat) -OTA and ODEX Stock ROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here it is the newest ota software update.
(Download)
Sprint Odex Stock Rom - rooted/busybox added with init.d supported
This was pulled from my device after the updated then restored to stock settings.It has not been reflashed yet so make sure to make a backup before flashing
(DOWNLOAD ODEX ROM)
puertoblack2003

just want to add the stock recovery v 3.05.651.6 so that you can flash the OTA update without issues and benefit.
(Download)

This for real?
Sent from my unknown using Tapatalk

Wyley87 said:
This for real?
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Yes, it is. After install 3.05 update, it's display te new update to 4.4.2

Hmmm what country are you in?
Sent from my unknown using Tapatalk
---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ----------
And what website is the screen shot from?
Sent from my unknown using Tapatalk
---------- Post added at 06:09 PM ---------- Previous post was at 06:04 PM ----------
Nevermind. I did some Googling
Sent from my unknown using Tapatalk

puertoblack2003 said:
just want to add the stock recovery v 3.05.651.6 so that you can flash the OTA update without issues and benefit.
(Download)
Click to expand...
Click to collapse
I'm stock, rooted, S-ON, TWRP Recovery.
Can I just flash the stock recovery, then take the OTA w/o any issues, then re-root, or just re-flash TWRP?
Thanks

aschlect said:
I'm stock, rooted, S-ON, TWRP Recovery.
Can I just flash the stock recovery, then take the OTA w/o any issues, then re-root, or just re-flash TWRP?
Thanks
Click to expand...
Click to collapse
Yes, that is what I did.
Sent from my Nexus 7

aschlect said:
I'm stock, rooted, S-ON, TWRP Recovery.
Can I just flash the stock recovery, then take the OTA w/o any issues, then re-root, or just re-flash TWRP?
Thanks
Click to expand...
Click to collapse
I tried this and it just sits at the fastboot screen when I try to install the OTA update. Top of the screen says TAMPERED RELOCKED SECURITY WARNING.

curtisimo said:
I tried this and it just sits at the fastboot screen when I try to install the OTA update. Top of the screen says TAMPERED RELOCKED SECURITY WARNING.
Click to expand...
Click to collapse
Did you take the OTA from the Settings>Systems Updates after you reinstalled stock recovery or did you try flashing the OTA?
---------- Post added at 01:41 PM ---------- Previous post was at 01:22 PM ----------
satur9ine said:
Yes, that is what I did.
Sent from my Nexus 7
Click to expand...
Click to collapse
Are you S-ON or S-OFF?

aschlect said:
Did you take the OTA from the Settings>Systems Updates after you reinstalled stock recovery or did you try flashing the OTA?
---------- Post added at 01:41 PM ---------- Previous post was at 01:22 PM ----------
Are you S-ON or S-OFF?
Click to expand...
Click to collapse
I took the OTA update through Software Updates. Is there a way to flash the zip with stock recovery?

curtisimo said:
I took the OTA update through Software Updates. Is there a way to flash the zip with stock recovery?
Click to expand...
Click to collapse
Not that I know of. I'm thinking we need to be S-OFF to be able to take the OTA after re-flashing the stock recovery. I think that is why it is not working.

aschlect said:
Not that I know of. I'm thinking we need to be S-OFF to be able to take the OTA after re-flashing the stock recovery. I think that is why it is not working.
Click to expand...
Click to collapse
Only need:
Guru Stock htc sprint + stock recovery - 3.04. ( Flash with custom recovery, after this, you have a stock recovery)
Check your phone, install via OTA 3.05.
Later, check again, and install the new version 4.06..
This is for S-OFF.
Final, install via ADB, the custom recovery, install SU, and you have 4.4.2 htc sprint + root access + custom recovery :victory::highfive:

Nevermind

kloriahdez said:
Only need:
Guru Stock htc sprint + stock recovery - 3.04. ( Flash with custom recovery, after this, you have a stock recovery)
Check your phone, install via OTA 3.05.
Later, check again, and install the new version 4.06..
This is for S-OFF.
Final, install via ADB, the custom recovery, install SU, and you have 4.4.2 htc sprint + root access + custom recovery :victory::highfive:
Click to expand...
Click to collapse
how is guru stock installed? Is it an RUU that is flashed through fastboot? my phone is currently on factory shipped software 1.29.651.10 and HBOOT 1.44. Will guru update those?

aschlect said:
I'm stock, rooted, S-ON, TWRP Recovery.
Can I just flash the stock recovery, then take the OTA w/o any issues, then re-root, or just re-flash TWRP?
Thanks
Click to expand...
Click to collapse
I did this w/ exactly the same setup and the OTA recognized my phone as stock and installed without issue. I actually downloaded the OTA first , then flashed stock recovery, reboored system and then accepted the install notification.
Sent from my HTCONE using XDA Premium 4 mobile app

vnv01 said:
I did this w/ exactly the same setup and the OTA recognized my phone as stock and installed without issue. I actually downloaded the OTA first , then flashed stock recovery, reboored system and then accepted the install notification.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
worked perfectly! Thanks!

aschlect said:
worked perfectly! Thanks!
Click to expand...
Click to collapse
didn't work for me. oh well.
will have to flash thru TWRP i guess.

riggsandroid said:
didn't work for me. oh well.
will have to flash thru TWRP i guess.
Click to expand...
Click to collapse
Did u use these steps?:
Download Software Update
Install Stock 3.05.651.6 recovery
Install Software Update

aschlect said:
Did u use these steps?:
Download Software Update
Install Stock 3.05.651.6 recovery
Install Software Update
Click to expand...
Click to collapse
yes sir.
DL update. get prompt to install.
fastboot flash the recovery from the latest update 3.05
reboot to system, accept install and it fails. I did have some apps frozen, would that do it? I don't see how. I'm preparing to flash one of the stock custom roms now.

riggsandroid said:
yes sir.
DL update. get prompt to install.
fastboot flash the recovery from the latest update 3.05
reboot to system, accept install and it fails. I did have some apps frozen, would that do it? I don't see how. I'm preparing to flash one of the stock custom roms now.
Click to expand...
Click to collapse
I didn't fastboot flash - I installed the 3.05 recovery zip file using TWRP. Maybe try that? Are you S-OFF or ON?

Install OTA 4.4.2 with rooted phone and TWRP 2.7.0

I've got a One with twrp 2.7 and rooted running on stock Android 4.3 .
Today I got the message that 4.4.2 is available as an OTA update.
I tried to install the OTA update but when in TWRP and selecting the update I got the message update failed.
Do I need to go back to the original bootimage before I can run the OTA update ?
Or is there another way with the need tp reinstall everything afterwards

deboopi2 said:
I've got a One with twrp 2.7 and rooted running on stock Android 4.3 .
Today I got the message that 4.4.2 is available as an OTA update.
I tried to install the OTA update but when in TWRP and selecting the update I got the message update failed.
Do I need to go back to the original bootimage before I can run the OTA update ?
Or is there another way with the need tp reinstall everything afterwards
Click to expand...
Click to collapse
You need to flash the stock recovery for your 4.3 version then re download and install the ota. You can re flash twrp later

mb_guy said:
You need to flash the stock recovery for your 4.3 version then re download and install the ota. You can re flash twrp later
Click to expand...
Click to collapse
Well, I reinstalled the stock recovery image from 3.62.401.1 and tried again.
After downloading the ota it restarts the phone and starts the update.
When the progress bar is at about 25% I get a red exclamation icon and the update stops.
How to solve this ?
I did s-off and unlock with firewater and used twrp to istall supersu, I did not install a custom rom

deboopi2 said:
Well, I reinstalled the stock recovery image from 3.62.401.1 and tried again.
After downloading the ota it restarts the phone and starts the update.
When the progress bar is at about 25% I get a red exclamation icon and the update stops.
How to solve this ?
I did s-off and unlock with firewater and used twrp to istall supersu, I did not install a custom rom
Click to expand...
Click to collapse
You could also try this. Assuming that you have the Europe version, with original cid etc. as you haven't posted fastboot getvar all.
http://androidnews.co.in/2014/01/28/downloadandroid-4-4-2-kitkat-ota-european-htc-one-4-19-401-8/
Or here is full rom
http://www.androidpt.com/index.php?/topic/44670-htc-one-stock-rom-4194018-kitkat-442-htc-sense-55/

Also if your S-On. Your bootloader needs to be Locked/Relocked, and not rooted

bored_stupid said:
Also if your S-On. Your bootloader needs to be Locked/Relocked, and not rooted
Click to expand...
Click to collapse
root privileges doesn't matters, but root will be loss after ota.
---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------
deboopi2 said:
Well, I reinstalled the stock recovery image from 3.62.401.1 and tried again.
After downloading the ota it restarts the phone and starts the update.
When the progress bar is at about 25% I get a red exclamation icon and the update stops.
How to solve this ?
I did s-off and unlock with firewater and used twrp to istall supersu, I did not install a custom rom
Click to expand...
Click to collapse
Have you modified or deleted some /system files? if yes then the ota will fail the md5 checksum and abort its installation. If you have some missing stock apps, it may also prevent you to update the phone for the same reason.

alray said:
root privileges doesn't matters, but root will be loss after ota.
---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------
Have you modified or deleted some /system files? if yes then the ota will fail the md5 checksum and abort its installation. If you have some missing stock apps, it may also prevent you to update the phone for the same reason.
Click to expand...
Click to collapse
Well I changed /system/customize/ACC/default.xml the sku code , should I look for the orignal file, SKU is 42 in the original.
They also told me to clear the cache.
What to try first : clear cache and if this does not work the default.xml file?

deboopi2 said:
Well I changed /system/customize/ACC/default.xml the sku code , should I look for the orignal file, SKU is 42 in the original.
They also told me to clear the cache.
What to try first : clear cache and if this does not work the default.xml file?
Click to expand...
Click to collapse
Restore the default file, as @alray suggested that is why th ota isn't working. you can also clear cache as it's just going to rebuild.

mb_guy said:
Restore the default file, as @alray suggested that is why th ota isn't working. you can also clear cache as it's just going to rebuild.
Click to expand...
Click to collapse
Any idea where I can find this default file, I forgot to backup the file before making changes
The SKU was set for 42 = Western Europe.
I have 3.62.401.1

deboopi2 said:
Any idea where I can find this default file, I forgot to backup the file before making changes
The SKU was set for 42 = Western Europe.
I have 3.62.401.1
Click to expand...
Click to collapse
Why don't you just backup your data and run the full ruu from the link previously given.

mb_guy said:
Why don't you just backup your data and run the full ruu from the link previously given.
Click to expand...
Click to collapse
+1 what he said
backup your data/media files and run the latest ruu:
http://androidruu.com/getdownload.php?file=M7/RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe

[GUIDE] How to add root access & and keep official OTA updates | 4.16.401.10

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some users like to keep their phones running the most official and stock system. Sadly, current Superuser installation process is a little bit more complicated then it was in the past (f.g. su binary needs to be running as a daemon). Flashing official SuperSu package makes OTA updates for the particular device impossible to be installed, because every OTA package during the installation process checks the integrity (with SHA-1) of each file on the system partition. Current SuperUser packages are modifying at least one file on the system partition: system/etc/install_recovery.sh. With that modified file, OTA installation will fail and you won't be able to update your device with the latest software. Additionally, SuperUser access is not always enough. It's good to have adb secure disabled and this can be done in the ramdisk inside boot.img.
Device rooted with the above method should have no problems installing latest official OTA update because:
a) OTA update checks for files integrity, but it doesn't check if any extra files were added to the system partition
b) OTA update doesn't check the integrity of the boot.img, so you can even flash a custom kernel if you want​
Keep in mind that once you change or remove any file from the system partition you won't be able to receive OTA updates. You can only add new files, but you can't modify/remove existing ones.​
Details:
boot.img source: 4.16.401.10
Target device: HTC One M8 (0P6B10000)
Target device OS version: 4.16.401.10
Included in the package:
Latest SuperSu app (Superuser.apk) and binaries (su, daemonsu)
Proper init.d script to run daemonsu binary as a daemon
Special wp_mod.ko kernel module to disable HTC system RW protection
Proper init.d script to insert the wp_mod.ko module into the kernel
Busybox
Sysrw/sysro binaries
Custom boot image:
Disabled ro.adb.secure and ro.secure
Disabled USB debugging icon on statusbar
Enabled USB debugging by default
Init.d support
Removed trigger command to execute install_recovery.sh to prevent stock recovery from being re-installed after each system reboot
Installation guide (bootloader has to be unlocked)
Extract the downloaded .rar package (boot.img, stock_recovery.img, Root_and_BusyBox.zip and Read_Me.txt)
Flash custom recovery of your choice
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode
Flash Root_and_BusyBox.zip package in the custom recovery
Flash stock_recovery.img using fastboot flash recovery stock_recovery.img command in the fastboot mode
Reboot the device
​
Credits:
Chainfire for the SuperSu
flar2 for the wp_mod.ko module
XDA:DevDB Information
[GUIDE] How to add root access & and keep official OTA updates | 4.16.401.10, Tool/Utility for the HTC One (M8)
Contributors
mike1986.
Version Information
Status: Stable
Created 2014-05-18
Last Updated 2015-02-28

Cheers for this Mike but which file is it in your downloads section?

Cheers Mike, Informative as always!

lasikie said:
Cheers for this Mike but which file is it in your downloads section?
Click to expand...
Click to collapse
Will be there very soon!

Uploaded http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html

I was under the impression this would be an all in one tool but looks like I still need to do a few things in preparation of this.
I am currently completely stock. What are the exact steps I should take to install this?

lasikie said:
I was under the impression this would be an all in one tool but looks like I still need to do a few things in preparation of this.
I am currently completely stock. What are the exact steps I should take to install this?
Click to expand...
Click to collapse
Could this be any simpler?
Installation guide (bootloader needs to be relocked)
Extract downloaded .rar package
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode
Flash Android_Revolution_HD_Root_and_BusyBox.zip package in the custom recovery of your choice
Reboot the device

Installation guide (bootloader needs to be relocked) - How do I do this?
Extract downloaded .rar package
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode - How do I access Fastboot mode?
Flash Android_Revolution_HD_Root_and_BusyBox.zip package in the custom recovery of your choice - When do I install this custom recovery?
Reboot the device
I'm not trying to be awkward just not use to some of this terminology and don't want to ruin my phone.
Maybe an idiots guide is what I need.

lasikie said:
Installation guide (bootloader needs to be relocked) - How do I do this?
Extract downloaded .rar package
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode - How do I access Fastboot mode?
Flash Android_Revolution_HD_Root_and_BusyBox.zip package in the custom recovery of your choice - When do I install this custom recovery?
Reboot the device
I'm not trying to be awkward just not use to some of this terminology and don't want to ruin my phone.
Maybe an idiots guide is what I need.
Click to expand...
Click to collapse
http://www.htcdev.com/bootloader
Also typo in my guide, bootloader needs to be unlocked. Correcting now.

Just a question, I remember that when i rooted my m7 or my one x, i had to reinstall all apps, and contacts were lost.. with this process does the info also is erase?

jorzavfa said:
Just a question, I remember that when i rooted my m7 or my one x, i had to reinstall all apps, and contacts were lost.. with this process does the info also is erase?
Click to expand...
Click to collapse
Unlocking the bootloader will remove all your data. If you have bootloader already unlocked, no data will be lost.

mike1986. said:
Unlocking the bootloader will remove all your data. If you have bootloader already unlocked, no data will be lost.
Click to expand...
Click to collapse
Ok great yes thats true, well im not sure i just bought the phone and i havent touch it for anything, i will check if the bootloader is unlocked, which i think no ..

jorzavfa said:
Ok great yes thats true, well im not sure i just bought the phone and i havent touch it for anything, i will check if the bootloader is unlocked, which i think no ..
Click to expand...
Click to collapse
If it's a brand new device then it has locked bootloader.

If I already have rooted M8 and s-off ,supercid, but with another method is safe to flash boot.img and Android_Revolution_HD_Root_and_BusyBox.zip package? will assume can install OTA after?

4onu said:
If I already have rooted M8 and s-off ,supercid, but with another method is safe to flash boot.img and Android_Revolution_HD_Root_and_BusyBox.zip package? will assume can install OTA after?
Click to expand...
Click to collapse
Yes it's safe but I can't guaranty that the previous method you used won't prevent your device from installing official OTA update.

I rooted my phone using thod: https://www.youtube.com/watch?v=WuHFcGvUjwA and s-off using this method: https://www.youtube.com/watch?v=--Hlms1BuPg
If I do everything that is in this topicfrom you, will I be able to update through OTA? And do you maybe know when int. version will get the 1.54.401.9 update? I would like to do an ota and then flash latest arhd when it will be available...

CrazyCypher said:
I rooted my phone using thod: https://www.youtube.com/watch?v=WuHFcGvUjwA and s-off using this method: https://www.youtube.com/watch?v=--Hlms1BuPg
If I do everything that is in this topicfrom you, will I be able to update through OTA? And do you maybe know when int. version will get the 1.54.401.9 update? I would like to do an ota and then flash latest arhd when it will be available...
Click to expand...
Click to collapse
Yes, you will be able to receive OTA. I'm now doing a little update to the first post.
1.54.401.9 or newer will be soon available, also next ARHD will be based on it.

mike1986. said:
Yes, you will be able to receive OTA. I'm now doing a little update to the first post.
1.54.401.9 or newer will be soon available, also next ARHD will be based on it.
Click to expand...
Click to collapse
I have a brand new HTC ONE M8, which is unlocked only. I didn't do any rooting yet
the details of the firmware are below:
HTC ONE M8 version 1.54.401.5
CID HTC_001
Can i flash the philz recovery then and do all your steps afterwards using the rooting_tools_htc rar file?
thanks

mike1986. said:
Yes, you will be able to receive OTA. I'm now doing a little update to the first post.
1.54.401.9 or newer will be soon available, also next ARHD will be based on it.
Click to expand...
Click to collapse
Thx for the quick answer... Also, the OTA will update everything, including firmware and everything right?
So after that I can easily flash the new version of ARHD without separately flashing new firmware, radio, etc?

krihoum said:
I have a brand new HTC ONE M8, which is unlocked only. I didn't do any rooting yet
the details of the firmware are below:
HTC ONE M8 version 1.54.401.5
CID HTC_001
Can i flash the philz recovery then and do all your steps afterwards using the rooting_tools_htc rar file?
thanks
Click to expand...
Click to collapse
yep

NEM-L51 (Android 7.0/EMUI 5.0) OTA update fails

Hi,
I have a rooted NEM-L51 (with TWRP 3.1.1-0 as recovery) running Android 7.0/EMUI 5.0 (build number NEM-L51C432B350).
A new OTA update is available (build number NEM-L51C432B355) but after downloading and rebooting to recovery (TWRP) to apply it, it fails with the following error:
Code:
script aborted: assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
Updater process ended with ERROR: 7
I googled it but couldn't find anything that seems useful. You'll find attached the complete log (I was using TWRP 3.1.0-2 at the time and has since upgraded, thinking it could be related to it).
Does anyone have any idea about what's going wrong here?
Could it be because the system partition has been modified in the process of rooting the phone (I'm thinking about that because of the 'block_image_verifiy(.../system...)') — note that I was able to apply OTA updates on my rooted device in the past?
Thanks!

You have magisk or SuperSU?!

why you trying to install updates on twrp....

Try useing stock recovery from the update.

PalakMi said:
You have magisk or SuperSU?!
Click to expand...
Click to collapse
SuperSU, v2.82.
thelous said:
why you trying to install updates on twrp....
Click to expand...
Click to collapse
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
AlexMihai26 said:
Try useing stock recovery from the update.
Click to expand...
Click to collapse
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?

Try magisk!

In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?

fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
Click to expand...
Click to collapse
Update.app with stock recovery, zip with twrp

sclarckone said:
SuperSU, v2.82.
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Click to expand...
Click to collapse
Yep

PalakMi said:
Try magisk!
Click to expand...
Click to collapse
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash.
Click to expand...
Click to collapse
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_data_public.zip (around 13 MB) which seems to contain updates for Honor system apps.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
fishnchips2 said:
Are you using the openkirin twrp?
Click to expand...
Click to collapse
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^

I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Twrp and root were lost during the update because the rom replaces them with its own files in the first boot. I don't know why the ota updates worked before.

Because you can hide root with magisk.

fishnchips2 said:
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
Click to expand...
Click to collapse
Just to be clear, these files I mentioned in my previous post are the one downloaded by the OTA updater of EMUI (and TWRP fails on flashing the first one, update.zip) so I shouldn't flash them with TWRP, right?
I'm a bit confused about this because if ZIP files are supposed to be used with TWRP and the APP files with the stock recovery, why did the EMUI OTA updater download ZIP files (I would expect it to download files as if I had a stock recovery)?
fishnchips2 said:
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Click to expand...
Click to collapse
So these are the files flashable with TWRP (in that case I don't need the stock recovery)? The ones corresponding to the upgrade I'm looking for seem to be the following:
The OTA one seems to be exactly the same update.zip that was downloaded by the EMUI OTA updater. Should I try the FullOTA variant?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry if I sound a bit meticulous but I'd rather not brick my phone and understand what I'm doing. ^^

The error you're getting is error 7 which means the rom is supposedly incompatible with your device. As this is the official update, I have no idea why this error is coming up. I think that once you get past that error, twrp should be fine flashing the zip file.
The difference between ota files and fullota files is that a fullota contains most of the files needed by the rom while the ota only replaces files that have changed. As you are on b350 nougat already, an update to b355 should only need a normal ota update.
Don't worry about asking questions, it's good that you're cautious with your phone.?
---------- Post added at 09:52 PM ---------- Previous post was at 09:45 PM ----------
EDIT!!!
Sorry I was wrong in the previous reply. Twrp can't flash an ota update because it only replaces some files, whereas twrp will flash the entire system. However, a fullota file should work (haven't tried??).
This also explains why it had error 7: the manufacturer doesn't want someone accidentally flashing an incremental update as a full rom.
More info is here : https://twrp.me/faq/officialota.html
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
Further edit : I believe that you have to wipe certain partitions (system and cache?) before flashing an update because 'dirty flashing' doesn't always fully replace everything and causes issues later. However this may be different for stock roms. Nevertheless, always make a backup!
Hopefully final edit: a dirty flash means that you don't wipe data first. This should be fine for an official update. Opinions vary on wiping system, cache and dalvik but I think the recovery should do that for you.

Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.

PalakMi said:
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
Click to expand...
Click to collapse
Yup I believe so

Honor devices are one of the most complicated when it comes to flashing ROMs.

I know ? at least it isn't the s8 exynos version. I hear you can't even unlock the bootloader on that.

Yeah, however, I wish honor makes it simple with upcoming devices (like OnePlus)

sclarckone said:
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
Click to expand...
Click to collapse
Use Huawei update extractor,and you should find a recovery.img