Related
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.
All I wanted was to upgrade my Rooted M7 to the latest software upgrade, so long short story I flashed recovery to TWRP and my M7 got stuck on logo. I know that I should install a ROM, but I don't know which one I should download and how to install it. How can I fix that? FYI you are talking to a noob :crying:.
Additional Information:
UNLOCKED
M7_UL S-ON
HBOOT 1.57
OS 6.09.401.11
HTC_J15
TWRP 3.0
More Information:
I have downloaded theses files see if I can use it:
cm-12.1-20160217-NIGHTLY-m7.zip
cm-12.1-20160217-NIGHTLY-m7-recovery.img
Android_Revolution_HD-One_93.0_ef29f7.zip
Flash_recovery_7.15.401.1.rar
One_M7_7.15.401.1_stock_system_dump.zip
One_All-In-One_Kit_v3.1.rar(Hasoon2000)
And I have this update from a long time I think it was downloaded from my M7:
OTA_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2-6.09.401.11_release_4217922wykl7uamtts1919.zip
I had a big problem in update too, I had an error I think it was in xbin dexdump something like that. I'll remember it when I can update.
Note: Anyone can help me should help me from this problem to the end of updating my M7.
Thanks in Advance
mohdhasan3 said:
All I wanted was to upgrade my Rooted M7 to the latest software upgrade, so long short story I flashed recovery to TWRP and my M7 got stuck on logo. I know that I should install a ROM, but I don't know which one I should download and how to install it. How can I fix that? FYI you are talking to a noob :crying:.
Additional Information:
UNLOCKED
M7_UL S-ON
HBOOT 1.57
OS 6.09.401.11
HTC_J15
TWRP 3.0
More Information:
I have downloaded theses files see if I can use it:
cm-12.1-20160217-NIGHTLY-m7.zip
cm-12.1-20160217-NIGHTLY-m7-recovery.img
Android_Revolution_HD-One_93.0_ef29f7.zip
Flash_recovery_7.15.401.1.rar
One_M7_7.15.401.1_stock_system_dump.zip
One_All-In-One_Kit_v3.1.rar(Hasoon2000)
And I have this update from a long time I think it was downloaded from my M7:
OTA_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2-6.09.401.11_release_4217922wykl7uamtts1919.zip
I had a big problem in update too, I had an error I think it was in xbin dexdump something like that. I'll remember it when I can update.
Note: Anyone can help me should help me from this problem to the end of updating my M7.
Thanks in Advance
Click to expand...
Click to collapse
Are you able to access TWRP recovery?
If you can you can use my Nandroid backup here. https://www.androidfilehost.com/?fid=95897840722641162
Extract the zip on your desktop. You should get a folder and a zip file.
Copy the folder to the TWRP Backups folder on your device using MTP in TWRP.
Location :- /TWRP/BACKUPS/XXXXXXXXXXX/.
Return to twrp home screen and select restore. Then select my backup. Once that's complete you should be good. Reboot from recovery. TWRP may ask if you want to root the device at this point but it's best to wait until after the updates are installed.
To install the ota you need to flash the Stock recovery back to the device. You will find it in the zip file that came with the backup.
Open the zip file on your pc and extract the recovery.img. Copy it to your fastboot folder and flash it like twrp
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Once that's done reboot the device and it should be ready to receive OTA updates. You will need to install 4 or 5 updates to bring your device to the latest. So just keep going untill no more are available. Once you've installed all the updates. Reflash TWRP and root the phone :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
Copy the folder to the TWRP Backups folder on your device using MTP in TWRP.
Location :- /TWRP/BACKUPS/XXXXXXXXXXX/.
Return to twrp home screen and select restore. Then select my backup. Once that's complete you should be good. Reboot from recovery. TWRP may ask if you want to root the device at this point but it's best to wait until after the updates are installed.
To install the ota you need to flash the Stock recovery back to the device. You will find it in the zip file that came with the backup.
Open the zip file on your pc and extract the recovery.img. Copy it to your fastboot folder and flash it like twrp
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Once that's done reboot the device and it should be ready to receive OTA updates. You will need to install 4 or 5 updates to bring your device to the latest. So just keep going untill no more are available. Once you've installed all the updates. Reflash TWRP and root the phone :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for replying, the file you provided is damaged I think, it should be 1.2 gb but I can download only about 88 mb of the file and its damaged. By the way, I wonder how can I copy the folder to TWRP using MTP
mohdhasan3 said:
Thanks for replying, the file you provided is damaged I think, it should be 1.2 gb but I can download only about 88 mb of the file and its damaged. By the way, I wonder how can I copy the folder to TWRP using MTP
Click to expand...
Click to collapse
The uploaded file is fine. It's been downloaded and used many times. How are you downloading it? Through your browser or with a download manager?
Newer versions of TWRP recovery allow MTP connection while in twrp. This allows you to copy files to the device in recovery mode just like if you were doing it in Android. I have not used TWRP 3.0. myself so can't confirm it supports MTP. I'll check and get back to you :good:
@mohdhasan3 can you provide a link the the TWRP 3.0 download you flashed please?
Sent from my HTC One using Tapatalk
Danny201281 said:
The uploaded file is fine. It's been downloaded and used many times. How are you downloading it? Through your browser or with a download manager?
Newer versions of TWRP recovery allow MTP connection while in twrp. This allows you to copy files to the device in recovery mode just like if you were doing it in Android. I have not used TWRP 3.0. myself so can't confirm it supports MTP. I'll check and get back to you :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Dear Danny,
Could you check the link for me or upload it to another site, because I checked the two links in Mozilla and Opera with download manager and without with VPN and without its always about 88 mb file
This is the link for TWRP 3.0:
https://dl.twrp.me/m7/twrp-3.0.0-0-m7.img.html
I see now the MTP Device yeah it just like you said. I can see a TWRP folder and a TWRPS File with no name inside the folder. So I'll add a new folder naming Backup and wait for your working link.
By the way, thanks for helping I appreciate your effort
mohdhasan3 said:
Dear Danny,
Could you check the link for me or upload it to another site, because I checked the two links in Mozilla and Opera with download manager and without with VPN and without its always about 88 mb file
This is the link for TWRP 3.0:
https://dl.twrp.me/m7/twrp-3.0.0-0-m7.img.html
I see now the MTP Device yeah it just like you said. I can see a TWRP folder and a TWRPS File with no name inside the folder. So I'll add a new folder naming Backup and wait for your working link.
Click to expand...
Click to collapse
I e checked it and your right, there seems to be an issue with the Mirrors. I can upload it again but unfortunately I'm still waiting for my fiber broadband upgrade so it may take some time to upload. I will update you here once it's ready
Unless I can find somthing else where that you can use :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
I e checked it and your right, there seems to be an issue with the Mirrors. I can upload it again but unfortunately I'm still waiting for my fiber broadband upgrade so it may take some time to upload. I will update you here once it's ready
Unless I can find somthing else where that you can use :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Phew.... I thought it was my bad day
mohdhasan3 said:
Phew.... I thought it was my bad day
Click to expand...
Click to collapse
I have started the upload but I also found another backup here https://www.androidfilehost.com/?fid=95864024717072880
Although since its not my own I can't guarantee its full stock. But worth a try while your waiting. You can still use the I can provide the Stock recovery no problem it's only 12mb
Sent from my HTC One using Tapatalk
Danny201281 said:
I have started the upload but I also found another backup here https://www.androidfilehost.com/?fid=95864024717072880
Although since its not my own I can't guarantee its full stock. But worth a try while your waiting. You can still use the I can provide the Stock recovery no problem it's only 12mb
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok, I'm downloading it now I'll keep you in touch :highfive: :good:
@Danny201281 By the way, when I entered TWRP before maybe an hour there is something popped up asking I think to be able to do modifications by swiping the arrow or to Keep System Read Only, so I pressed Keep System. I don't know what is it but I hope that I didn't messed up again.
mohdhasan3 said:
Ok, I'm downloading it now I'll keep you in touch :highfive: :good:
@Danny201281 By the way, when I entered TWRP before maybe an hour there is something popped up asking I think to be able to do modifications by swiping the arrow or to Keep System Read Only, so I pressed Keep System. I don't know what is it but I hope that I didn't messed up again.
Click to expand...
Click to collapse
No it's fine for the moment. But if you are going to use custom roms after the update you will want to change it to read/write :good:
Were you able to figure out how to use mtp in twrp to copy the files to the device?
Here's a link to the Stock recovery https://www.dropbox.com/s/iej6thyyjakwgjc/recovery.img?dl=0
Sent from my HTC One using Tapatalk
Danny201281 said:
No it's fine for the moment. But if you are going to use custom roms after the update you will want to change it to read/write :good:
Were you able to figure out how to use mtp in twrp to copy the files to the device?
Here's a link to the Stock recovery https://www.dropbox.com/s/iej6thyyjakwgjc/recovery.img?dl=0
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes, I'm. Now I'm extracting the zip then I'll copy the folder as you said to TWRP/BACKUPS/********* :good:
Updating Progress:
Putting the folder in TWRP/BACKUPS/"In Here" will not work. So I did a backup to see where it goes. After it completed, the Backup saved in TWRP/BACKUPS/SH35********(Device Serial[1])/2016-02-19--11-28-11(Today's Date)/"In Here". Then I replaced this Backup Files with the Nandroid Backup Files.
[1] Device Serial can be found with ADB writing in the command prompt opened from the ADB folder location after connecting the device to the PC and enabling USB debugging "adb devices"
You succeeded -my bro- in restoring my M7 again to normal thank you very much :victory:, but still didn't reach my goal I'll continue now in progressing and will keep you in touch :good:
Updating Progress 1:
After I downloaded the latest OTA, I installed it. M7 rebooted then it went to the recovery that showed up with red triangle, pressed the three combinations Power + Volume Up + Volume Down I got the recovery menu, then I wiped cache partition and the red triangle went to I think green likely circle. Rebooted, tried again it starts to updating then after maybe about a quarter of the updating bar red triangle showed up again saying installation aborted. Rebooted, then tried again -here is my problem from long time- OTA was deleted after I went to check for updates now I'm downloading again and will try one more time. I need your help my brother @Danny201281
Updating Progress 2:
Same. Installation aborted after almost half-quarter of the updating bar then red triangle again. Help is appreciated.
I think I know the solution now, but first the error is same like this except the Package:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.102.008
Package expects build fingerprint of htc/vodafone_uk/m7:4.4.3/KTU84L/366813.9:user/release-keys
or htc/vodafone_uk/m7:5.0.2/LRX22G/476210.2:user/release-keys;
this device has htc/vodafone_uk/m7:4.4.3/KTU84L/366813.5:user/release-keys.
Installation aborted.
Write host_mode:0 done
The one had this error fixed it and said that he installed the wrong recovery
As you can see that your link OS is 6.09.401.11 but the link you provided OS is 6.09.401.12 maybe thats why the recovery is different from each other. What do you say
mohdhasan3 said:
You succeeded -my bro- in restoring my M7 again to normal thank you very much :victory:, but still didn't reach my goal I'll continue now in progressing and will keep you in touch :good:
Updating Progress 1:
After I downloaded the latest OTA, I installed it. M7 rebooted then it went to the recovery that showed up with red triangle, pressed the three combinations Power + Volume Up + Volume Down I got the recovery menu, then I wiped cache partition and the red triangle went to I think green likely circle. Rebooted, tried again it starts to updating then after maybe about a quarter of the updating bar red triangle showed up again saying installation aborted. Rebooted, then tried again -here is my problem from long time- OTA was deleted after I went to check for updates now I'm downloading again and will try one more time. I need your help my brother @Danny201281
Updating Progress 2:
Same. Installation aborted after almost half-quarter of the updating bar then red triangle again. Help is appreciated.
I think I know the solution now, but first the error is same like this except the Package:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.102.008
Package expects build fingerprint of htc/vodafone_uk/m7:4.4.3/KTU84L/366813.9:user/release-keys
or htc/vodafone_uk/m7:5.0.2/LRX22G/476210.2:user/release-keys;
this device has htc/vodafone_uk/m7:4.4.3/KTU84L/366813.5:user/release-keys.
Installation aborted.
Write host_mode:0 done
The one had this error fixed it and said that he installed the wrong recovery
As you can see that your link OS is 6.09.401.11 but the link you provided OS is 6.09.401.12 maybe thats why the recovery is different from each other. What do you say
Click to expand...
Click to collapse
Normally such a small difference shouldn't cause a problem but let's try the correct recovery I found a firmware zip download link below ?
Download this firmware zip. https://www.androidfilehost.com/?fid=23991606952612395
Extract it on your pc and use the recovery from it. It will then match your Rom
Sent from my HTC One using Tapatalk
Danny201281 said:
Normally such a small difference shouldn't cause a problem but let's try the correct recovery I found a firmware zip download link below ��
Download this firmware zip. https://www.androidfilehost.com/?fid=23991606952612395
Extract it on your pc and use the recovery from it. It will then match your Rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
FINALLY I UPDATED MY M7 :victory:!!
I made a great progress. I opened the OTA that I had from the start -its the same as the latest OTA I was downloading- and opened the firmware.zip and extracted the recovery.img from it, flashed, downloaded OTA again from device, installed it, and succeeded in upgrading to the latest OTA. I recommend for anyone have this problem too to download the latest OTA from device, copy it to desktop, extract recovery.img from firmware.zip inside the OTA, flash, then install update and it will work PERFECTLY :good:
I don't know how to thank you my brother you are GREAAAT :fingers-crossed:. Thank you very very much. All credits goes to @Danny201281 for fixing my device.
If you may could I use more of your services?
If I can how can I install ROMs and how can I S-OFF M7?
mohdhasan3 said:
FINALLY I UPDATED MY M7 :victory:!!
I made a great progress. I opened the OTA that I had from the start -its the same as the latest OTA I was downloading- and opened the firmware.zip and extracted the recovery.img from it, flashed, downloaded OTA again from device, installed it, and succeeded in upgrading to the latest OTA. I recommend for anyone have this problem too to download the latest OTA from device, copy it to desktop, extract recovery.img from firmware.zip inside the OTA, flash, then install update and it will work PERFECTLY :good:
I don't know how to thank you my brother you are GREAAAT :fingers-crossed:. Thank you very very much. All credits goes to @Danny201281 for fixing my device.
If you may could I use more of your services?
If I can how can I install ROMs and how can I S-OFF M7?
Click to expand...
Click to collapse
Yes you can now flash custom lollipop roms, the process is fairly simple. Choose the Rom you want. Download it and copy it to your devices storage. Reboot TWRP recovery and install the Rom.
To gain s-off your only option is Sunshine app. It's not free to use unfortunately but its very simple and effective.
All other methods have either been patched against by HTC or discontinued by there developers. Rumrunner still works but only for devices with hboot 155 or below. ?
Sent from my HTC One using Tapatalk
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
Code:
E:footer is wrong
E:signature verification failed
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Deleted
Anyone have any suggestions?
Bump
Someone has to have some sort of suggestions I could try... would flashing a custom rom on do anything or is this related to the KNOX security stuff?
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Nergal di Cuthah said:
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Click to expand...
Click to collapse
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
lordofbeond said:
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
Click to expand...
Click to collapse
Not in manager in actual twrp
Nergal di Cuthah said:
Not in manager in actual twrp
Click to expand...
Click to collapse
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
This thread is probably your answer
lordofbeond said:
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-framework-install-galaxy-s4-sch-t3425615
lordofbeond said:
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Click to expand...
Click to collapse
Hola. i just did this on vz GS4 i545:
use FlashFire for everything. make sure you have a titanium backup of your apps and data for after you flash new ROM. here are the steps:
1. Flash Fire Zip or OTA stock of1 deodexed ROM from here: http://forum.xda-developers.com/gal...1-keeproot-t3182544/post62413212#post62413212
it will spend 10 to 15 minutes on the red Verizon splash screen.
2. reload from titanium at this point.
3. install xposed 3.0alpha4.apk from the xposed forum page.
4. flashfire zip or ota Arter97's xposed v65 sdk21 arm arter97 V5 krait.zip
this last step took about 35 minutes to upgrade all 260 plus apps i have.
make sure you have the proper uninstaller loaded too just in case. i put mine on the ext sd card in case i needed to load it from recovery. though that might not work because of the unsigned issue.
Folks,
I recently purchased a preowned HTC One M9 in good shape. The phone does not appear to have been rooted, s-offed or any such thing. It looks bone stock. It currently has Android 6.0 on it. and software number 3.39.531.41
It has been over a month since t-mobile has rolled out the nougat update for the HTC One-M9 and I have not received any update on the phone. I constantly keep checking if the phone has an update available but the phone always says no update available. I gave up on the OTA being rolled out for the phone so I downloaded the Nougat RUU which is 4.27.531.6 .
When I follow the procedure for installing the update I got a signature error 132 . Now I know that error shows up when the phone is rooted or is s-off or any such thing but my phone seems to be completely stock. Does anyone know why I cant install the RUU or receive OTA updates to Nougat for my phone?
I think I figured it out. I contacted T-Mobile support who told me to contact HTC since the HTC servers are responsible for pushing out updates. So I contacted HTC customer support and shared my IMEI with the representative. She looked up some information on the HTC database using the IMEI number and told me that my phone was a store demo phone and that demo phones are blocked from receiving updates from the HTC servers. Oh well.
Hello,
Just got the same phone with same error. If someone provides me with 0PJAIMG.ZIP, I can test and see how it goes. So far update from phone >> didn't work; RUU update >> didn't work. same error
Thanks
I had the same problem some time a go what you have to do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA. But my receives the OTA alright but could neither install that or RUU
amptronic said:
I had the same problem some time a go what you have do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA.
Click to expand...
Click to collapse
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
dohcvtec said:
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
Click to expand...
Click to collapse
did it work?? I'm having same problem..
smilesintears77 said:
did it work?? I'm having same problem..
Click to expand...
Click to collapse
Did anyone get any solution for this error? I am having the same issue
Thanks
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i think first decrypt RUU then manually flash whole Nougat ROM.
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
m_abbas25 said:
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
Click to expand...
Click to collapse
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
vbcomer said:
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
Click to expand...
Click to collapse
I think your recovery file is damaged. Thou i am novice in this but i think you should run RUU of existing rom it may repair your recovery then try this method.
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
vbcomer said:
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
Click to expand...
Click to collapse
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Ok. I was able to install 3.39.531.41. I will try the OTA now
m_abbas25 said:
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Click to expand...
Click to collapse
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
Click to expand...
Click to collapse
I don't know much now but we can try RUU of 3.39.531.41. It should solve your recovery. But the question is where you can download that?? Try finding a link mean while i am uploading it to my google drive then i will share link. Since i am in third world country it will take time. I will update you as soon as it is uploaded
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
Thanks
Click to expand...
Click to collapse
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Thank you much! I will try everything you suggested now. I really appreciate your help!
dbs25 said:
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Click to expand...
Click to collapse
I downloaded the RUU from above link [https://www.androidfilehost.com/?fid=24438995911969398], but after installing, the phone went from 3.39.531.41 back to 3.39.531.7. Was the above zip file really the 531.41 version?
I tried to reinstall the 0PJAIMG for 531.41 downloaded earlier, but the phone said signature error.
I tried to install using the OTA zip from this link [http://fotadl-az.htc.com/secure/OTA_...kwvabkx6lv.zip] from Recovery mode but the phone said "E3001: Package expects build fingerprint of htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.41:user/release-keys or htc/himaul_tmous/htc_himaul:7.0/NRD90M/869604.6:user/release-keys; this device has htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.7:user/relea
E:Error in /sideload/package.zip (Status 7)
Installation aborted
You have any idea to go back to 531.41? Since the OTA message seemed to indicate it expected a 531.41 version?
Thanks
Ok. I was able to get back to 3.39.531.41 by getting the 0PJAIMG from AndroidFileHost.
After that, I went to Recovery Mode (using pwr + vol up after seeing the red triangle), chose Apply Update from SDCard, selected the OTA file for 4.27.531.6. This time It didn't give any error, at the end it appeared to get stuck for a long time at the line Script Succeeded Result was [/preload]. After about an hour, I turned off the phone and on again, now it is stuck at HTC logo splash screen.
Questions here:
1. Was the phone really stuck at the "script succeeded" line?
2. Didn't I wait long enough?
3. What should I have done at that time when it stopped at that "script succeeded" line?
4. What should I do at this splash screen? It has been like that for the last 10 minutes
Thanks
Hi,
in order to use some of my apps (SwiftBackup, AFWall+...) I unlocked the bootloader of my sweet, installed TWRP and rooted it using magisk.
Working fine so far, but when the device shows up an update (actually I am on 12.5.1 Global), the update file gets downloaded and then the device restarts.
But instead of updating, TWRP is entered.
Could please anyone advice me on how to apply the update?
I found the file downloaded, but I do not want to install something without knowledge (it is a company cell phone).
Best regards and thanks in advance,
Otto
sagaranuj said:
it happens because the phone doesn't have the official recovery installed anymore. When the phone boots and enters twrp, select the downloaded zip file (of miui update) and install it as you would do for a custom rom.
you might have to root the phone again though.
Click to expand...
Click to collapse
not work OTA update zip fule on twrp
seems like that :-(
I think, a custom ROM will be better anyhow...