Related
hi Guys,
Hope someone can help me here. I'm currently on :-
- Stock asian rom (4.1.2),
- Bootloader unlocked,
- Rooted ,
- S-ON,
- CWM.
Hboot details are : 1.44 June 13 rel.
Now there is a new 4.2.2 rom release for my region (OTA_M7_UL_JB_50_S_hTC_Asia_WWE_2.24.707.1-1.29.707.16_R_P_release_325138_signedjx8qygc6il8gpe9q)
which I would like to upgrade to.
So I've done the following trying to upgrade:-
1). unzipped the 4.2.2 rom and extract the recovery.img from the zip file.
2). Flash the recovery area via fastboot flash recovery recovery.img
3). Boot back into the phone and perform the OTA upgrade.
4). Phone restarts and goes into recovery and installs with the progress bar. An icon shows 2 arrows shaped like a circle, one pointing up another pointing down with another arrow inside it pointing downwards.
5). progress bar shows it progresses up to around 30% and it just stays there . I've waited for more than 1hr but nothing happens. progress bar still stays the same.
6). Had to force shutdown via holding the power button and phone restarts, it automatically went into the recovery screen again with the progress bar but it progresses abit and then the 2 arrow icon changes into a triangle icon.
7). I force shutdown the phone again and it booted back to the phone home screen after a while as though nothing has happened.
Hope someone can point out what I'm doing wrong here.
Would love to have 4.2.2 in my phone. I would still like to stick to the stock rom for now so using other ROMs is out of the question.
Thanks in advance.
Might be the lost apps after unlocking the bootloader!
Did you install the lost APK's that are lost during the wipe because of unlocking the bootloader? (like the calculator, voice recorder, htc ringtone trimmer etc) These apps get lost during the wipe and are required to perform OTA's. So unzip the attachment, copy all the APK's to your phone and install all of them and then try to do the update and see if it works.
RTIT said:
Did you install the lost APK's that are lost during the wipe because of unlocking the bootloader? (like the calculator, voice recorder, htc ringtone trimmer etc) These apps get lost during the wipe and are required to perform OTA's. So unzip the attachment, copy all the APK's to your phone and install all of them and then try to do the update and see if it works.
Click to expand...
Click to collapse
Thanks for the files.. but my current version 4.1.2 stock rom originally does not come with those appz... do i need to still install them first?. I'm thinking whether do i need to relock my bootloader or sumthing...
ircghost said:
Thanks for the files.. but my current version 4.1.2 stock rom originally does not come with those appz... do i need to still install them first?. I'm thinking whether do i need to relock my bootloader or sumthing...
Click to expand...
Click to collapse
No these apps come with the HTC One out of the box, but when you unlock the bootloader these apps get wiped with your internal storage so you have to reinstall them. And no you do not have to relock your bootloader for the OTA update to work, you only need stock recovery, stock ROM and the missing apps, and if all of these are present you can do the OTA update.
You can read here about the deleted apps during unlocking the bootloader http://www.expertreviews.co.uk/smar...-unlocking-deletes-apps-blocks-future-updates
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Quantumstate said:
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Click to expand...
Click to collapse
You must be on stock recovery in order to OTA update. Try going into adb and flashing back to stock recovery and it should work.
Make sure you have mfastboot set up and working, if you need the file respond to this post and I can supply it for you.
Download the stock recovery from here (and make sure it's in your "android" folder)
Boot your phone into fastboot with
adb reboot bootloader
Click to expand...
Click to collapse
-OR-
While the phone is off, hold the PWR button and the Volume Down buttons at the same time for ~5 seconds. Release the PWR button ONLY and continue holding Volume Down until you see the fastboot screen.
Next
Then in adb on your computer perform:
mfastboot flash recovery *filename*
mfastboot reboot
Click to expand...
Click to collapse
When it reboots into the OS it should try to install the update again, like you said it was doing. When it reboots it should update correctly via stock recovery.
Emphasis on should. I can't guaruntee this will work but this is based on my prior knowledge and experience. Good luck and report back with success/problems!
Quantumstate said:
I got a message on my XT1053 Dev that there's a system update. (I'm running stock) I let it download, and then it wanted to reboot. Ok, but it came up in TWRP. I tried rebooting from TWRP every way, but it would not go into maintenance so it could flash the new firmware.
Now whenever I boot it normally, it comes up, and then immediately shuts down, I guess because it wants to upgrade.
What is wrong with this thing?
Click to expand...
Click to collapse
There's nothing wrong with this thing....
All of the guides here exist for a reason. One responsibility you have once you have decided to root your device or install custom recovery, is that when a new OTA comes out, you must check back here at XDA to see what the procedure for installing it is.
All of the guides here tell you that you MUST have stock recovery in order to accept any updates.
Here's how you will fix it:
Boot into TWRP. Clear your cache. This will prevent the constant reboots.
Now, use fastboot to flash back the stock recovery. You will need to download the 4.4.2 SBF for your XT1053 from here: http://sbf.droid-developers.org/phone.php?device=0
Extract the archive. You only need one file: recovery.img
You should already have the android SDK installed since you unlocked your BL and flashed TWRP. Use fastboot to flash the stock recovery:
fastboot flash recovery recovery.img
Now you can accept the OTA from your phone. You may need to go to Settings > About Phone > System Updates and re-download it.
The OTA should now successfully install (assuming you aren't using Xposed or made any other modifications).
Now, you can flash TWRP recovery back. Let us know how it works out for you...
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Quantumstate said:
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Click to expand...
Click to collapse
The GSM Developer edition uses the SAME exact software as the T-Mobile version. The T-Mobile variant has zero bloat, and no carrier branding. The only difference between the two is that you don't lose your warranty when you unlock the GSM Dev edition.
You're looking for the XT1053 T-Mobile SBF
http://sbf.droid-developers.org/phone.php?device=0
Quantumstate said:
Thanks, but the update was unsuccessful.
I seem to remember that the update checks existing files, and if one has the wrong CRC it fails. Well I'm stock but rooted. It is a develoepr's phone and there is no developer's image on those sites.
Click to expand...
Click to collapse
I always seem to have something in /system that messes with the ota update. In addition to flashing stock recovery to replace twrp, I also flash system.img (with mfastboot only) from the same sbf as you get the recovery.img. Then the ota goes through without a hitch.
Still Errors at the robot with spinning diamond heart, even with TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml/recovery.img.
Looking around it seems that here are some rules. I think I'm violating #2: "Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall." I've removed most of the G**gle junk since I don't trust them.
So if this is what they require, Hell with them. If it were possible to put multiboot on the Moto X I would have done it a long time ago. Maybe I can apply this OTA update in some other way? Without going through their rinky-dink tests?
Quantumstate said:
Still Errors at the robot with spinning diamond heart, even with TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml/recovery.img.
Looking around it seems that here are some rules. I think I'm violating #2: "Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall." I've removed most of the G**gle junk since I don't trust them.
So if this is what they require, Hell with them. If it were possible to put multiboot on the Moto X I would have done it a long time ago. Maybe I can apply this OTA update in some other way? Without going through their rinky-dink tests?
Click to expand...
Click to collapse
You are correct on the manifest.
Instead, just flash the entire stock SBF (TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25). The manual method is easiest.
Or you could just flash the system.img as the earlier poster suggested.
This will revert to stock, and you will have to reinstall your apps, but the OTA WILL work afterwards. You really should consider just 'freezing' the google apps instead of removing them this time...
The only other way you will be able to install the OTA is to put all the gapps back on...but I doubt you made a backup, right?
mfastboot flash system system.img
that should be all you need (beside stock recovery, of course). Then take the update, and finally do whatever mods you want remembering that you will HAVE to un-do the mods to be able to accept future OTAs without returning to 100% stock again.
Good Luck
Flashing system.img will not require you to reinstall your downloaded apps, just apps you installed as system apps via root access. Downloaded apps are in the /data/app partition that is not affected by a system.img flash.
I finally went this route. I'm not putting up with their OTA requirements; I'll get the upgrade without them. Although, that 4.3 sure has alot of G**gle and Motorola bloatware to remove.
With Xposed, GravityBox (and other modules) I now have the flexibility I was looking for.
Now all I need is a better dialer than the crappy G**gle one, and secure SMS.
Fresh off the servers, here is the 4.4.4 OTA for the Moto G XT1045_US
Link: 4.4.4 OTA_XT1045.
Enjoy.
rawtek said:
Fresh off the servers, here is the 4.4.4 OTA for the Moto G XT1045_US
Link: 4.4.4 OTA_XT1045.
Enjoy.
Click to expand...
Click to collapse
Is this just a flashable zip?
nklenchik said:
Is this just a flashable zip?
Click to expand...
Click to collapse
Yes, however it needs the stock recovery.
Out of curiosity how does one actually flash the OTA ?
IF I let the System Download the OTA, it will reboot, have an error and not complete the install. (using the stock recovery)
If I Push the update via ADB and use CWMR it tells me there is a footer error.
If I open the update with WinRAR or 7zip I get an unexpected End of archive.
Is the OTA itself Broken in some way (which is what it appears to be to me on the surface), or have other people gotten it to work on the XT1045 ?
I am Running the Stock rom, with the stock recovery. I even did a factory firmware Flash (though I cannot seem to relock the boot loader, everything else completes)
MissyVixen said:
Out of curiosity how does one actually flash the OTA ?
IF I let the System Download the OTA, it will reboot, have an error and not complete the install. (using the stock recovery)
If I Push the update via ADB and use CWMR it tells me there is a footer error.
If I open the update with WinRAR or 7zip I get an unexpected End of archive.
Is the OTA itself Broken in some way (which is what it appears to be to me on the surface), or have other people gotten it to work on the XT1045 ?
I am Running the Stock rom, with the stock recovery. I even did a factory firmware Flash (though I cannot seem to relock the boot loader, everything else completes)
Click to expand...
Click to collapse
just noticed that on mind as on my wife moto G she was able to download and install via system updates without a hitch and she is running stock even with a locked bootloader and the install complete with no errors however when trying to flash on mines with stock recovery and a unlocked bootloader it produces the same error, only thing different is the boot loader being unlocked on mines. I'll look a little more into this after work..will keep ya posted.
I installed 4.4.4 on my XT1045 without any problems last night, via the OTA update notification I received. My bootloader was unlocked. Full details here.
I got the update thru the regular update from the y XT1045 rooted with TWRP 2.7 1 0 the system ask me If I want to update, I say yes, on reboot got stuck on the Twrp push reboot system the phone reboot and shut down to get back to T W R P
after turning phone off the phone says Update unsuccessful
how to install from the recovery?
any solution?
guliver365 said:
I got the update thru the regular update from the y XT1045 rooted with TWRP 2.7 1 0 the system ask me If I want to update, I say yes, on reboot got stuck on the Twrp push reboot system the phone reboot and shut down to get back to T W R P
after turning phone off the phone says Update unsuccessful
how to install from the recovery?
any solution?
Click to expand...
Click to collapse
You need to use the stock recovery for this, not TWRP. Try castuis' instructions and see if they work for you too. Let us know if they do or don't.
Reverted back to stock before updating via OTA, no issues here. 64GB SanDisk finally works in 4.4.4. I am having an issue where the 64GB isn't really working in recoveries, like philz CWM or TWRP. Anyone got an idea what that's about? I figured if the card worked with 4.4.4 using the new kernel, the recoveries should also be fine.
Slinkwyde said:
You need to use the stock recovery for this, not TWRP. Try castuis' instructions and see if they work for you too. Let us know if they do or don't.
Click to expand...
Click to collapse
Revert it to stock Recovery, started the upgrade process again, after the reboot the update started but stopped to one third and gave me an error.
guliver365 said:
Revert it to stock Recovery, started the upgrade process again, after the reboot the update started but stopped to one third and gave me an error.
Click to expand...
Click to collapse
Finnaly working.:laugh: I got to reinstall a fresh copy of the stock firmware and the update went well just had to root it again and change the nasty warning about unlocked device
My XT1045 has an unlocked bootloader, TWRP in lieu of the stock recovery, and it's rooted. I also run Xposed.
I downloaded the 4.4.4 update via the official OTA process after being notified.
I further uninstalled my Xposed framework files. After rebooting, I realized I'd also need my stock recovery back.
After (visiting this forum and) reconsidering, I don't want to bother installing my update at this time.
Anybody know how I can revert those pesky dialogs asking me to install the update?
I think it's gonna do it every time I reboot.
danny8 said:
My XT1045 has an unlocked bootloader, TWRP in lieu of the stock recovery, and it's rooted. I also run Xposed.
I downloaded the 4.4.4 update via the official OTA process after being notified.
I further uninstalled my Xposed framework files. After rebooting, I realized I'd also need my stock recovery back.
After (visiting this forum and) reconsidering, I don't want to bother installing my update at this time.
Anybody know how I can revert those pesky dialogs asking me to install the update?
I think it's gonna do it every time I reboot.
Click to expand...
Click to collapse
Delete the OTA zip located in /cache using a root explorer. Or you can 'fastboot erase cache'.
People have reported success with OTA using Philz recovery. But i suppose that requires flashing a recovery which is the same effort as flashing stock recovery. Note: A modified system partition may still cause OTA error on stock recovery, and you may have to restore stock system partition by flashing system.img from your stock firmware.
I tweaked the updater script on mine to eliminate the stock recovery stuff before flashing with TWRP, and it seemed to work :
Code:
http://rhysw.com/peregrine/xt1045-4.4.4.norecovery.zip
Usual disclaimers apply; back up your device first ! Diff the changed updater script vs. the stock one. Do not use if you don't know what an updater script is.
Gentlemen..Not sure why all the reverting to stock recovery is needed, if your device is on TWRP..please help me to understand.?
Here's what I done with one of my XT1045's in a matter of few minutes..keeping my other XT1045 on 4.4.3 for awhile longer..
Running TWRP v2.7.1.0_peregrine (shabby penguin) version..
With this zip copied to the storage in the device, installed from TWRP, rebooted and never lost Root..simple, quick, painless..
Absolutely did NOTHING (except update framework) to XPosed, Gravity Box [KK 3.1.7], Advanced Power Menu [6.0a_r1], AcDisplay [2.4.7], Android L Navigation Bar [6.1], GPSNotifications [2.9]..
ONLY thing I had to do was update Framework..kept Root with no problems either..
This is 4.4.4_21.11.56 in flashable, installable zip format..
Here >> https://docs.google.com/file/d/0B67RS0BDBp_iOWhZdGlmWXpOQW8/edit?usp=docslist_api
sent by my Jelly Bean_ 4.1.2_98.72.16
(Root Exploit) XT912 Droid RAZR Maxx
Update fails
I have both the stock rom and stock recovery installed but I cannot get the OTA update to complete without an error and if I try to manually run the update from the stock recovery I also get the same error. The error is...
Verifying current system...
"/system/app/Drive.apk" has unexpected contents.
Installation aborted
I have gone as far as removing the drive.apk from my device altogether but it still gives me the same error. I have tried installing a fresh copy of the drive.apk but the same error occurs. I am at the end of my ideas. Anyone else run into this or have any suggestions?
USCanthony said:
I have both the stock rom and stock recovery installed but I cannot get the OTA update to complete without an error and if I try to manually run the update from the stock recovery I also get the same error. The error is...
Verifying current system...
"/system/app/Drive.apk" has unexpected contents.
Installation aborted
I have gone as far as removing the drive.apk from my device altogether but it still gives me the same error. I have tried installing a fresh copy of the drive.apk but the same error occurs. I am at the end of my ideas. Anyone else run into this or have any suggestions?
Click to expand...
Click to collapse
If you remove any system apps, the OTA will fail everytime. When you installed the apk, did you set it as a system app? Did you change the permissions back to how they should be?
charesa39 said:
If you remove any system apps, the OTA will fail everytime. When you installed the apk, did you set it as a system app? Did you change the permissions back to how they should be?
Click to expand...
Click to collapse
Ahhh...thank you....this is beginning to make a little more sense but also brings up another question. According to Titanium backup, the original Drive.apk was a system file but updates to that apk now reside in [root]/data/app/. I never installed drive.apk form the Play Store and then made it a system file so I have to assume that the original drive.apk that is sitting with all the other system files is part of the stock rom. There is a possibility that it could be a different version than what cam with the stock rom though since I did perform a merge of updated apk's from that location into the [root]/system/app/ folder several months ago but I have no idea if the drive.apk was one of those that I merged because I do not remember what apk's were merged. Does the OTA look for what it has been told is the version that existed in the "system/app" folder of the ROM it is updating and if it finds any other version it will fail (which means that merging any apk's is an OTA killer)? I had also deleted several Motorola apk's from the stock rom that are bloated system files such as "Alert" and "Assist" but I have Titanium backup's of those files so restoring them is not a problem. Is it possible that the drive.apk error is an erroneous error because drive.apk was simply the last file it checked before the script bailed because of those missing files?
USCanthony said:
Ahhh...thank you....this is beginning to make a little more sense but also brings up another question. According to Titanium backup, the original Drive.apk was a system file but updates to that apk now reside in [root]/data/app/. I never installed drive.apk form the Play Store and then made it a system file so I have to assume that the original drive.apk that is sitting with all the other system files is part of the stock rom. There is a possibility that it could be a different version than what cam with the stock rom though since I did perform a merge of updated apk's from that location into the [root]/system/app/ folder several months ago but I have no idea if the drive.apk was one of those that I merged because I do not remember what apk's were merged. Does the OTA look for what it has been told is the version that existed in the "system/app" folder of the ROM it is updating and if it finds any other version it will fail (which means that merging any apk's is an OTA killer)? I had also deleted several Motorola apk's from the stock rom that are bloated system files such as "Alert" and "Assist" but I have Titanium backup's of those files so restoring them is not a problem. Is it possible that the drive.apk error is an erroneous error because drive.apk was simply the last file it checked before the script bailed because of those missing files?
Click to expand...
Click to collapse
I don't think it checks the version of the app. I think it just checks whether the apk is there, and if the permissions are correct. This is why I never actually delete system apps. I'll just disable them in the stock settings app, or freeze them with TiBu. I assume that all the apps that came loaded on the phone (including the Motorola ones you mentioned) need to be present in order for it to update, or at least the apps that don't give you the option to uninstall them in the stock settings app, meaning they can only be disabled.
can someone pull out the boot.img from a 4.4.4 updated xt1045, and share with me? thanks.
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
prdog1 said:
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
Click to expand...
Click to collapse
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash either, right? It certainly seems like an exploit worthy of my time to patch, but I was trying to avoid the data loss :/
rvrzl said:
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash, right? It certainly seems like an exploit worth of my time to patch, but I was trying to avoid the data loss :/
Click to expand...
Click to collapse
You can fastboot flash the corresponding factory images. Skip the userdata data image and will will not wipe data. OTA's are worthless if gonna run root and recovery. Someone may make a TWRP flashable. Would have to search for it.
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
rvrzl said:
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
Click to expand...
Click to collapse
If you're running root, fastboot flash the system.img only. If you don't run a custom kernel, you probably should also fastboot flash the boot.img too.
Keep supersu on your sdcard and after flashing system DO NOT boot the rom. Boot straight into TWRP and flash supersu
If you boot rom install-recovery.sh will install stock recovery on first boot. .flashing super su amended this script so that won't happen.
You can also flash the radio.img. Your choice.
rvrzl said:
I have an unlocked & rooted Nexus 6 (T-Mo, I My build number is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP,
Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Click to expand...
Click to collapse
For OTA's the device needs to be unrooted and complete stock. Including 'recovery'. So flashing with TWRP-recovery will not work.
An alternative is to flash only the new system.img with fastboot.
FWIW, recovery flashable updates are here:
http://forum.xda-developers.com/showthread.php?t=3066052
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
You can flash the OTA all day anyway you want but if you are not stock it won't take. Only other way is one of the flashable TWRP versions that were linked to. And right now looks like that thread is down for update.
danarama said:
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
Click to expand...
Click to collapse
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
rvrzl said:
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
!
Click to expand...
Click to collapse
Because of this, I did the update twice; different methods, to see of there are possible differences.
Differences between official OTA and flashing the new system.img only.
Update 1: Flashing only the new system image (1,7 Gb) with fastboot.
Update 2: Return to stock LMY47Z and install official OTA (24,2 Mb)
Both updates have the same results. Data and apps were kept but there were changes:
a. Changes in build.prop gone (DPI, Wifi interval);
b. Standard icons because the DPI value 384 was changed to 560;
c. BGN-launcher replaced. Google Now launcher became white again;
d. Root gone (SuperSu and Busybox);
(Update 2. Of course returning to stock, replaces the custom kernel).
After rerooting the N6 the following actions were needed after both update methods:
- edit the file: system/build.prop to change the dpi and wifi interval;
- reflash/reinstall: BGN-Launcher, SuperSU and Busybox;
- uninstall updates of the Google app to get BGN-launcher working;
- replacing icons from drawer to start screen.
So when you have made changes to the system, like DPI settings, an update will leave your data alone, but not the settings.
Clawz114 said:
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
Click to expand...
Click to collapse
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
That said, the only reason not to flash the rightbversiin is if the download link.is down or you have a local copy of a different version anyway.
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
How are you trying to flash the OTA?
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
What is the error?
danarama said:
[snip]
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
Click to expand...
Click to collapse
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
danarama said:
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
Click to expand...
Click to collapse
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
danarama said:
How are you trying to flash the OTA?
Click to expand...
Click to collapse
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
danarama said:
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Click to expand...
Click to collapse
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
efrant said:
What is the error?
Click to expand...
Click to collapse
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
efrant said:
What is the error?
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
Click to expand...
Click to collapse
I believe it changed for lollipop OTA's. I don't think it had changed for kitKat.
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Clawz114 said:
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
Click to expand...
Click to collapse
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
danarama said:
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
Click to expand...
Click to collapse
I'm going to have to do just that by the looks of it.
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Clarification:
Version: EVA-L19C636B381 (everything's stock: BOOT, RECOVERY, RECOVERY2, SYSTEM)
Would like to update to: B390
Issue: Getting "Software install failed" error message after downloading through System Update
** Used to have TWRP and root. Flashed stock IMGs
Update:
Issue solved! Please see last post for the update/solution.
thedarkinvader said:
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Click to expand...
Click to collapse
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
zgfg said:
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
Click to expand...
Click to collapse
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
thedarkinvader said:
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
Click to expand...
Click to collapse
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
zgfg said:
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
Click to expand...
Click to collapse
Yeah, that's what I did. Basically, everything's stock already. That's why I don't understand why I'm still getting the error message.
You can try downloading the full stock rom package and manually update with the dload method.
noalt said:
You can try downloading the full stock rom package and manually update with the dload method.
Click to expand...
Click to collapse
Hi noalt! Thanks for the response.
Yeah, kinda wondering if that'll work. For the dload method, does it really require an SD card? Also, for the dload method, it is okay to get the latest full package instead? (Upon checking using Firmware Finder, the latest one is B395 or B396)
Any steps that I can follow to do a sort of "clean install"? As in free of any modifications? In short, some kind of steps as alternative for using System Update (which I can't use due to the error message I'm getting)?
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
noalt said:
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
Click to expand...
Click to collapse
I see. Regarding the dload method, if by sd-card you're referring to the internal memory, I'm afraid I've tried that (creating a dload folder and putting nothing else but the UPDATE.APP file inside) and I'm getting a Software Install Failed error message as well. :crying:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
noalt said:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
Click to expand...
Click to collapse
Ah yes, that's the one that I have yet to try (as I don't have an SD card, the other spare phone that I have is a 5s).
UPDATE:
I eventually was able to install EVA-L19C363B395!
Initially, I was having issues with the partitions (as I tinkered around a bit with TWRP) and was stuck with the Huawei logo and not proceeding with the booting. So what I did was I flashed BOOT.img, SYSTEM.img, RECOVERY.img, and RECOVERY2.img from the stock B381 (use the Huawei Update Extractor to get it from the UPDATE.APP file from the update.zip (the large file), do some Googling to find it here in XDA . Then I was still experiencing the said issue so I used the stock recovery's features: "Wipe data/factory reset" and "Wipe cache partition" to sort of repair the issues with the partitions (didn't know how to properly do it in TWRP.
Then B381 booted and was able to access USB debugging (initially had issues with this as well, after flashing images, Settings app kept on crashing when trying to access Security and Developer options).
And then finally followed the HWOTA procedure made by @Atarii. Make sure that you're going to use the proper recovery file for your version (L09, L19, etc). According to the steps, being rooted is also required so I used @zgfg's SuperSU 2.82 permissive (https://mega.nz/#F!w41RmZKB!IG53JadhjUKgFK8anbctIw). Make sure to flash it before flashing the nocheck recovery file.
And voila! That should do it. Based on what I'm seeing, root has been removed after doing the HWOTA procedure, same goes for TWRP, and bootloader's locked again.
Thanks to all of those who responded and credit goes to @Atarii and @zgfg for the procedure and file/link.