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.
Spice Dream Uno android 5.1.1 official OTA link captured!!!
LINK:-
https://android.googleapis.com/pack...-spice-mi498h-LMY47V-from-LMY47O.a818932c.zip
Instructions:-
Make sure u are on Stock 5.1 (LMY47O) & u have stock recovery
Place the ota zip in sdcard
Reboot to stock recovery
select apply update from sdcard
TA_DA!! U have android 5.1.1 running on your phone.
Credits:-
@mukeshpurohit
status 7 error
I am rooted and having stock recovery stock rom but while installing getting status 7 error.What to do?
There is an option in supersu to perform full unroot and then try again ( remember stock LMY47O recovery is required )
ujwal.p said:
There is an option in supersu to perform full unroot and then try again ( remember stock LMY47O recovery is required )
Click to expand...
Click to collapse
try that too but not working
The only thing I can imagine is that system files have been modified... Otherwise it should work..
Sent from my Mi-498 using XDA Forums
Error
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
aditya_chachad said:
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
Click to expand...
Click to collapse
Hmmm, try after full unroot, if that also doesnt work. There is one more method mentioned by people in the group. ie First flash the stock 5.1(LMY47O) ota and then on top of that flash 5.1.1 OTA, it will work.
How to successfully update to 5.1.1
Hey
Thanks for the suggestion :good: I managed to install 5.1.1 on my device.
My findings:
Before Lollipop, while updating from an OTA update, Google made android only check the system partition details to verify their OTA updates and that the installed version was the correct one.
However, with 5.0 Lolipop they introduced a new method of system checking. For each OTA update, the updater in recovery checked the file in the /system/bin/install-recovery.sh for its legit data. So any rooting or messing with the kernel or any part of the system made changes to it.
If any of the data is wrong or changed, the updater generates an error which most of us are getting. You won't even be able to manually flash the image as the system does not grant access to any recovery to patch the zip.
Even just installing SuperSU will change the data. A full unroot wont work as unrooting dosen't set back the default value for the files!! Only chance is if you have the stock image. without any messing around.
Sadly, I am not a professional developer and I don't know why Google did so?
The method that I used:
I flashed a stock image from another Spice Dream Uno device that my Dad has (that's silly) and restored the original system files.
And VOILA!, my OTA works just fine and I am on 5.1.1 now!
Edit: The updater checks every file in /system folder !! So if u even modify a stock apk, it will give an error.
Please Hit "Thanks" if this information was helpful!
aditya_chachad said:
Hey
Thanks for the suggestion :good: I managed to install 5.1.1 on my device.
My findings:
Before Lollipop, while updating from an OTA update, Google made android only check the system partition details to verify their OTA updates and that the installed version was the correct one.
However, with 5.0 Lolipop they introduced a new method of system checking. For each OTA update, the updater in recovery checked the file in the /system/bin/install-recovery.sh for its legit data. So any rooting or messing with the kernel or any part of the system made changes to it.
If any of the data is wrong or changed, the updater generates an error which most of us are getting. You won't even be able to manually flash the image as the system does not grant access to any recovery to patch the zip.
Even just installing SuperSU will change the data. A full unroot wont work as unrooting dosen't set back the default value for the files!! Only chance is if you have the stock image. without any messing around.
Sadly, I am not a professional developer and I don't know why Google did so?
The method that I used:
I flashed a stock image from another Spice Dream Uno device that my Dad has (that's silly) and restored the original system files.
And VOILA!, my OTA works just fine and I am on 5.1.1 now!
Edit: The updater checks every file in /system folder !! So if u even modify a stock apk, it will give an error.
Please Hit "Thanks" if this information was helpful!
Click to expand...
Click to collapse
Can you give the link for the system file I think I'm gonna try ur step...post the link ASAP.✌✌✌✌✌
& tell me how did you restore the system either using custom recovery or stock.
or
can you backup the current 5.1.1 system and post the Link...✌✌✌✌
SathishKies said:
Can you give the link for the system file I think I'm gonna try ur step...post the link ASAP.
& tell me how did you restore the system either using custom recovery or stock.
or
can you backup the current 5.1.1 system and post the Link...
Click to expand...
Click to collapse
As I mentioned, I had my stock recovery and system image backed up. I used custom recovery to restore my stock system.
For the safer side, I did do a full unroot from SuoerSU, which u can find it in the settings of SuperSU.
One thing I prefer is I never flash a recovery directly to my device.
Whenever I need custom recovery ( I use TWRP btw), I open it by using
Code:
fastboot boot TWRP.img
or whatever your file name is.
I then restored my backup from TWRP. In your case if you didn't backup your system before rooting then try flashing the stock system images from the links below.
After flashing the stock system, your OTA should work just fine.
There are many other threads where u can find the stock images.
Link for 5.1.1 flashable.
http://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Link for Lollipop 5.1 stock image.
http://forum.xda-developers.com/cro...general/lmy47o-stock-rom-android-one-t3076777
If the stock images don't work for you then please tell me. I will backup my system and provide it.
I have yet another workaround way which is a bit complex. I'll post that too if this method didn't help you.
Hit Thanks if this helped you!!:good:
aditya_chachad said:
As I mentioned, I had my stock recovery and system image backed up. I used custom recovery to restore my stock system.
For the safer side, I did do a full unroot from SuoerSU, which u can find it in the settings of SuperSU.
One thing I prefer is I never flash a recovery directly to my device.
Whenever I need custom recovery ( I use TWRP btw), I open it by using
Code:
fastboot boot TWRP.img
or whatever your file name is.
I then restored my backup from TWRP. In your case if you didn't backup your system before rooting then try flashing the stock system images from the links below.
After flashing the stock system, your OTA should work just fine.
There are many other threads where u can find the stock images.
Link for 5.1.1 flashable.
http://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Link for Lollipop 5.1 stock image.
http://forum.xda-developers.com/cro...general/lmy47o-stock-rom-android-one-t3076777
If the stock images don't work for you then please tell me. I will backup my system and provide it.
I have yet another workaround way which is a bit complex. I'll post that too if this method didn't help you.
Hit Thanks if this helped you!!:good:
Click to expand...
Click to collapse
Hey man I tried it but, seriously its going to bootloop. If you provide the system backup of current OS & if its not much of a trouble give it as a recovery restorable file the flashable zip is not workin out for me. I believe that ur posting the 5.1.1 backup plz post it... :fingers-crossed::fingers-crossed:
SathishKies said:
Hey man I tried it but, seriously its going to bootloop. If you provide the system backup of current OS & if its not much of a trouble give it as a recovery restorable file the flashable zip is not workin out for me. I believe that ur posting the 5.1.1 backup plz post it... :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hey,
Sorry to hear that the previous method didn't work.
Your device is probably going into bootloop because of the remains of your previous system and the dalvik-cache. Try clearing that once.
I am providing you with both the system recoveries below.
Link for Lollipop 5.1 system backup:
https://goo.gl/NkAxwo
Link for Lollipop 5.1.1 system backup:
https://goo.gl/TL6EqU
Link for TWRP custom Recovery for Spice Dream Uno (sprout):
https://dl.twrp.me/sprout/twrp-2.8.6.0-sprout.img
These backups are directly from TWRP Recovery, so I don't know how you will use them.
You can't just copy these folders on your ext sd card and do a restore from TWRP as it won't recognize it as a system backup (as far as I know).
So basically, what I did was, I made a fool out of TWRP!!
You can follow these steps too.
First download the files from the required given links and place it in a new folder.
1. Start your device into TWRP cutom recovery.
2. Keep your device plugged in to a PC. Do not unplug your device until the whole restoration process completes!! And create a system backup of your device using TWRP. DO NOT use compression and DO NOT check md5. Do not reboot the device after the backup!!
3. After a successfull system backup, you will get a folder it your ext sd card mostly in ext_sdcard\TWRP\BACKUPS\Mi498HA14090161\<recovery_name>
4. Locate the folder on a PC and open it. There will be six files in the folder. Replace these files with the backup files that I provided you with in the download.
5. Now go to Restore option in TWRP and you will find the backup that you just created. The backup name will be the same but the system images will be changed as we just replaced the system and boot files.
6. Select the backup and restore.
Reboot your device after a successful backup and you should now have a fresh un-mod system.
You can directly use the 5.1.1 system image, but I suggest, you use the 5.1 system backup and update to 5.1.1 OTA.
And for the bootloop problem, I prefer backing-up the data of my device and do a complete system wipe. Wipe off the data, system partition and cache. This sholud set your device to a untouched state and hopefully there won't be any further problems.
Hit thanks if this helped you!! :good:
aditya_chachad said:
Hey,
Sorry to hear that the previous method didn't work.
Your device is probably going into bootloop because of the remains of your previous system and the dalvik-cache. Try clearing that once.
Click to expand...
Click to collapse
Everything worked as a dime if you backed up stock recovery that came with 5.1.1 post me tat took✌✌✌✌
SathishKies said:
Everything worked as a dime if you backed up stock recovery that came with 5.1.1 post me tat took
Click to expand...
Click to collapse
Feels good to help a fella!! :good: :good: :good:
How to update manually to Lollipop 5.1.1 for release key error and other errors
aditya_chachad said:
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
Click to expand...
Click to collapse
Youtube Search for teckspotindia "Android One Release Key Error | Update Lollipop 5.1.1 Error | Micromax Canvas A1 | Dream UNO"
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
manojnagendra said:
I am rooted and having stock recovery stock rom but while installing getting status 7 error.What to do?
Click to expand...
Click to collapse
How to update manually to Lollipop 5.1.1 for release key error and other errors
Youtube Search for teckspotindia "Android One Release Key Error | Update Lollipop 5.1.1 Error | Micromax Canvas A1 | Dream UNO"
i've got the x510 with 2gb of ram version. it came with the latest October update presintalled build 20151012. till now checking for update doesn't reflect the Marshmallow update.
recovery is not working (even by adb it goes to an android pic with no text or No Command available)
tried flashing recovery, no luck, reflashed all the available stock roms on the forum with no luck neither, no recovery and no marshmallow update
all flashing was done through SP Flash, with format or download only, no difference. stock original cable was used, vcom drivers present and SP tool read the phone perfectly.
X510-D5110-Androidone-20150824, X510-D5110-Androidone-20151012, X510-A1-FIX-20150824.
i even tried flashing twrp and pushing the Marshmallow update through it which never succeeded
any idea ? hint ? help item that i can do ?
yacbos said:
i've got the x510 with 2gb of ram version. it came with the latest October update presintalled build 20151012. till now checking for update doesn't reflect the Marshmallow update.
recovery is not working (even by adb it goes to an android pic with no text or No Command available)
tried flashing recovery, no luck, reflashed all the available stock roms on the forum with no luck neither, no recovery and no marshmallow update
all flashing was done through SP Flash, with format or download only, no difference. stock original cable was used, vcom drivers present and SP tool read the phone perfectly.
X510-D5110-Androidone-20150824, X510-D5110-Androidone-20151012, X510-A1-FIX-20150824.
i even tried flashing twrp and pushing the Marshmallow update through it which never succeeded
any idea ? hint ? help item that i can do ?
Click to expand...
Click to collapse
You must be in 2015 December 5.1.1 update to Install Marshmallow. 20150824 or 20151012 will NOT support directly install MM.
So update to 2015 December update. If you cant find through OTA, just manually download the OTA from forum (search somewhere).
to access recovery : go to adb and reboot to recovery. U will see the Android Logo without any text. Here press the Power and Volume+ button for 5 seconds and leave the keys. u will see the recovery menu.
I am using Spice dream uno mi-498 H with stock ota. Never unlocked boot-loader or rooted my phone. Yesterday my phone went into bootloop.
I tried factory reset through recovery but still the problem remained.
I downloaded a marshmallow ROM and tried to update it via sd card. It was stuck on "verifying update package" but I tried several times and at last it threw error as -
Cant install this package (Thu Sep 24 22:31:53 UTC 2015) over newer build (Fri Aug 12 02:08:39 UTC 2016).
Error in /sideload/package.zip
(status 7)
Please give me link of latest stock ota ROM
Screenshot of recovery option - http://m.imgur.com/i6ZZTfG
6.0.1/MOB31E/3142026 (in case it is unreadable in pic)
you have two options...either give it to service center or unlock ur bootloader,flash twrp by ice fire,flash the stcok rom for the ota installer
Chetan Lodha said:
you have two options...either give it to service center or unlock ur bootloader,flash twrp by ice fire,flash the stcok rom for the ota installer
Click to expand...
Click to collapse
I will go for the second option. Please clear my doubts about unlocking bootloader. I read several posts on xda regarding that but still needs some clarification.
1. It is not necessary to enable USB debugging. Am I Right?
2. I downloaded Android one toolkit but it is not detecting my phone. Probably drivers are not installed ?
If yes then how to install drivers? I tried pda net but it is asking for usb debugging.
bip847 said:
I am using Spice dream uno mi-498 H with stock ota. Never unlocked boot-loader or rooted my phone. Yesterday my phone went into bootloop.
I tried factory reset through recovery but still the problem remained.
I downloaded a marshmallow ROM and tried to update it via sd card. It was stuck on "verifying update package" but I tried several times and at last it threw error as -
Cant install this package (Thu Sep 24 22:31:53 UTC 2015) over newer build (Fri Aug 12 02:08:39 UTC 2016).
Error in /sideload/package.zip
(status 7)
Please give me link of latest stock ota ROM
Screenshot of recovery option - http://m.imgur.com/i6ZZTfG
6.0.1/MOB31E/3142026 (in case it is unreadable in pic)
Click to expand...
Click to collapse
Hello,
What zip did you tried to install via stock recovery?
FYI - you can't just flash any OTA [Like 6.0* via MOB31E] you must need a custom recovery to do that.
Okay, if it's still looping like infinitely, just try installing custom recovery via fastboot... And once you get custom recovery like twrp, perform a clean wipe and flash full stock zip.
If you still failed, then simply visit a service centre near by and ask them for downgrade it to either Kitkat or 5.1 LP.
I'm not gonna recommend you to use SPFT yourself, Cuz there are Buncha cases over here.. ie; phone got hard bricked while using SPFT... So just visit a service centre nearby and fix it.
Update - I was passionate about stock ROM as I wanted to reciece ota updates. Unfortunately things went in a different way. After trying few stock ROM which failed to install, finally I decided to use a custom ROM. I unlocked the OEM, flashed TWRP recovery and then cyanogen mode.
Welcome me to the CM community.
In first hour of my use, I am missing FM radio along with ota. Also the screen seems dull even if I turn off LiveDisplay. Any quick suggestions for new users of CM?
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