I am currently on 4.3 with TWRP. Could I flash the 4.4.2 factory image with the TWRP menu ?
lapocompris said:
I am currently on 4.3 with TWRP. Could I flash the 4.4.2 factory image with the TWRP menu ?
Click to expand...
Click to collapse
you can flash the ota zip in twrp.
choose your correct ota zip file there: http://forum.xda-developers.com/showthread.php?t=2380113
and flash it with twrp.
EDIT: you must have an unmodified system... if you have a custom kernel for example, flash the ota zip will failure.
or if you have xposed framework running it could give errors.
I downloaded the JSS15R → KOT49H zip file, in TWRP I did a factory reset then install the zip, but at the end it said that the flashing has failed.
lapocompris said:
I downloaded the JSS15R → KOT49H zip file, in TWRP I did a factory reset then install the zip, but at the end it said that the flashing has failed.
Click to expand...
Click to collapse
what says twrp exactly?
E:Error executing updater binary in zip '/sdcard/Download/
Error flashing zip '/sdcard/Download/365f8dadebf2b78
Updating partition detail...
lapocompris said:
E:Error executing updater binary in zip '/sdcard/Download/
Error flashing zip '/sdcard/Download/365f8dadebf2b78
Updating partition detail...
Click to expand...
Click to collapse
is there above this error also a message with a text like "/system/bin/..." has unexpected contents?
dusu84 said:
is there above this error also a message with a text like "/system/bin/..." has unexpected contents?
Click to expand...
Click to collapse
No
lapocompris said:
No
Click to expand...
Click to collapse
hmmm... ok weird.
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
or if you have root go to supersu settings and full unroot.
there are several reasons why an update could have failed. two of the most popular reasons you get an update failed error maybe because:
you may have downloaded the wrong version or the file may have been corrupted.
you might have deleted a system app or made changes to the system files.
EDIT:
if you know how to work with adb and fastboot you can try this: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
and then sideload the ota update zip.
I finally flashed the 4.4.2 factory image via fastboot.
Thanks for trying to help.
For future reference the ota comes in a flashable.zip but if you are trying to flash the factory image taken from Google site then it needs to be flashed through fastboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?
Did you reflash the ota after you flashed supersu?
What was the error message?
sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?
It will lose the option to blend milkshakes
church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.
datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.
Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Step one : Go to the right forum.
Wrong subforum, but basically it's because you're rooted. The easiest solution is to just flash the system.img file from the factory image via fastboot and you should be good to go :good:
Thread moved to the right sub-forum and to the right section...
arviverona said:
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Click to expand...
Click to collapse
ota updates only work on devices that are not modified i.e. patched but you can still be rooted (aosp browser, mods to system will bork any ota). if you do not know how to reverse the patch/mod you applied to you device you need to reflash a stock version of the system (search for stock images) then apply the ota.
OP: Uninstall stickmount (doing so will copy back the stock debuggerd), and try the OTA again.
Thanks guys!
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
arviverona said:
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
Click to expand...
Click to collapse
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
mdamaged said:
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
Click to expand...
Click to collapse
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Duffmantp said:
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Click to expand...
Click to collapse
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
mdamaged said:
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
Click to expand...
Click to collapse
Actually I dont have stickmount installed, if that makes a difference.
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Well then your debuggerd should be stock, and this is all just academic. If the update fails, it won't be due to the debuggerd (unless there is some other app I do not know about that messes with debuggerd and you have that installed).
Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
wantabe said:
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
Click to expand...
Click to collapse
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
mdamaged said:
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
Click to expand...
Click to collapse
That's it!
Hi all, I've found there is a system update as details below.
Software update : 1.54.707.2 (184.63 MB)
This update contains important enhancements and bug fixes, including:
- System enhancement
Should I proceed to download and install it with my device already rooted and Xposed module installed?
Here is the screen shot for the updates.
If it's a full ROM update then you are better off waiting until someone can extract the update from the OTA so don't chance into a possible.What carrier you on?
Sent from my Galaxy S3 using XDA Free mobile app
gumbyx84 said:
If it's a full ROM update then you are better off waiting until someone can extract the update from the OTA so don't chance into a possible.What carrier you on?
Sent from my Galaxy S3 using XDA Free mobile app
Click to expand...
Click to collapse
I am using 816x single sim and I dont think it's from my carrier?
Now already finished my backup on CWM.
smartzac said:
Hi all, I've found there is a system update as details below.
Software update : 1.54.707.2 (184.63 MB)
This update contains important enhancements and bug fixes, including:
- System enhancement
Should I proceed to download and install it with my device already rooted and Xposed module installed?
Click to expand...
Click to collapse
No... You'll need to unroot, remove xposed, reinstall all system apps if uninstalled.. For a successful update.
jithumon said:
No... You'll need to unroot, remove xposed, reinstall all system apps if uninstalled.. For a successful update.
Click to expand...
Click to collapse
Already search for the solutions but unable to find it for now. Looking for a guides for that.
smartzac said:
Already search for the solutions but unable to find it for now. Looking for a guides for that.
Click to expand...
Click to collapse
For what do you need a guide?
jithumon said:
For what do you need a guide?
Click to expand...
Click to collapse
I need a guides to unroot, remove Xposed module and how to reinstall back all system apps. Looking for a RUU for this right?
smartzac said:
I need a guides to unroot, remove Xposed module and how to reinstall back all system apps. Looking for a RUU for this right?
Click to expand...
Click to collapse
Unroot from su setting itself, uninstall xposed & try. If OTA fails, check recovery log(pressing volume up + power & release in stock recovery) that which app is creating problem.
I have all stock apps of 816d with me.
jithumon said:
Unroot from su setting itself, uninstall xposed & try. If OTA fails, check recovery log(pressing volume up + power & release in stock recovery) that which app is creating problem.
I have all stock apps of 816d with me.
Click to expand...
Click to collapse
Do u mean just click on Full Unroot option on SuperSU setting? I dont need to relocked the bootloader? And just unisntall Xposed from the apps manager?
smartzac said:
Do u mean just click on Full Unroot option on SuperSU setting? I dont need to relocked the bootloader? And just unisntall Xposed from the apps manager?
Click to expand...
Click to collapse
Yes for su & no need for bootloader relocking.
Uninstall Xposed & all its modules.
jithumon said:
Yes for su & no need for bootloader relocking.
Uninstall Xposed & all its modules.
Click to expand...
Click to collapse
How about the recovery? Should it back to stock after I removed the SuperSU and Xposed Modules? Or it will still keep the custom one?
smartzac said:
How about the recovery? Should it back to stock after I removed the SuperSU and Xposed Modules? Or it will still keep the custom one?
Click to expand...
Click to collapse
You'll need stock recovery also... Pick it from the OTA update file itself.
Here is the error found during installation,
"Finding update package...
E:unknown volume for path [INTERNALSDCARD:0/Download/OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867.zip]
E:Can't mount INTERNALSDCARD:0/Download/OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867.zip
Installation aborted.
Rebooting..."
smartzac said:
Here is the error found during installation,
"Finding update package...
E:unknown volume for path [INTERNALSDCARD:0/Download/OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867.zip]
E:Can't mount INTERNALSDCARD:0/Download/OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867.zip
Installation aborted.
Rebooting..."
Click to expand...
Click to collapse
I have the same error as well, and when checked its because of custom recovery. And im still cracking my head on how to revert back to stock recovery. the recovery from the update file does not work for me (or there is not recovery image) because its showing 0bytes for me
h3llrai53r said:
I have the same error as well, and when checked its because of custom recovery. And im still cracking my head on how to revert back to stock recovery. the recovery from the update file does not work for me (or there is not recovery image) because its showing 0bytes for me
Click to expand...
Click to collapse
So we are on the same boat here...
Will try again to check on how to revert back to stock recovery. Trying to get it from the OTA as suggested by jithumon
h3llrai53r said:
Will try again to check on how to revert back to stock recovery. Trying to get it from the OTA as suggested by jithumon
Click to expand...
Click to collapse
Dont forget to share the results here.
h3llrai53r said:
Will try again to check on how to revert back to stock recovery. Trying to get it from the OTA as suggested by jithumon
Click to expand...
Click to collapse
First copy the update file to pc. Then find the recovery.img in firmware.zip
smartzac said:
Here is the error found during installation,
"Finding update package...
E:unknown volume for path [INTERNALSDCARD:0/Download/OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867.zip]
E:Can't mount INTERNALSDCARD:0/Download/OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867.zip
Installation aborted.
Rebooting..."
Click to expand...
Click to collapse
jithumon said:
First copy the update file to pc. Then find the recovery.img in firmware.zip
Click to expand...
Click to collapse
Tried that but getting error that
Windows cannot open the folder.
The Compressed (zipped)folder OTA_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_WWE_1.54.707.2-1.49.707.1_release_388867\filmware.zip is invalid.
File size of filmware.zip is 21.0MB
I played around with cm had but decides to go back to stock. I installed with twrp and then got a update notice. I downloaded and trwp tried to install but fail. Use toolkit to load original recovery and downloaded uodate, not it says updating and then says recovery fail. And when phone boots up it ask to downloaded update. Any help would be appreciated
Sent from my SM-N920T using XDA-Developers mobile app
chibixzero said:
I played around with cm had but decides to go back to stock. I installed with twrp and then got a update notice. I downloaded and trwp tried to install but fail. Use toolkit to load original recovery and downloaded uodate, not it says updating and then says recovery fail. And when phone boots up it ask to downloaded update. Any help would be appreciated
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
If you are rooted. systemless or not, with or without xposed, the update will fail. Download the full rom from the mirror here and sideload it or flash it in twrp
manor7777 said:
If you are rooted. systemless or not, with or without xposed, the update will fail. Download the full rom from the mirror here and sideload it or flash it in twrp
Click to expand...
Click to collapse
I did flash it with TWRP. Download the stock from one plus.net and still get update fail
chibixzero said:
I did flash it with TWRP. Download the stock from one plus.net and still get update fail
Click to expand...
Click to collapse
With what error code? And what size was the zip you flashed?
manor7777 said:
With what error code? And what size was the zip you flashed?
Click to expand...
Click to collapse
the file size is 1.2 gigs from oneplus.net. There is no error code on TWRP and on the stock recovery it shows no errors just says Update fail
chibixzero said:
the file size is 1.2 gigs from oneplus.net. There is no error code on TWRP and on the stock recovery it shows no errors just says Update fail
Click to expand...
Click to collapse
Hmm, I've not run into that issue. An error 7 in twrp usually means the system partition is modified (e.g root, hence my previous suggestion) but that doesn't effect the full 1+ gb zip as it's not an OTA but rather the full rom. Try contacting oneplus support
Use TWRP, and install the full OxygenOS 3.2.2 zip (do not try to use the OTA update - that won't work and also do not install the OTA update version), and wipe cache and dalvik, then reboot
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
Verifying update package...
Installing update...
M60QCT.02.003.021
Verifying current system...
Package expects build fingerprint of htc/pmewl_00617/htcpmewl:6.0.1/MMB29M/761759.1:user/release-keys or htc/pmewl_00617/htc_pmewl:6.0.1/MMB29M/787791.1:user/release-keys; this device has htc/pmewl_00617/htcpmewl:6.0.1/MMB29M/748430.5:user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
nullo said:
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
Click to expand...
Click to collapse
Alrighty seems like I fixed it! I ended up flashing the EraseDevInfo zip in http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Not sure how I did the first update without flashing it that file last time?
nullo said:
Alrighty seems like I fixed it! I ended up flashing the EraseDevInfo zip in http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Not sure how I did the first update without flashing it that file last time?
Click to expand...
Click to collapse
Glad that worked for you. You don't always trip the verity mode check when you modify system. It seems to only occur when you modify system AND use a 100% stock kernel. So it makes sense that ota will work sometimes and not others.
Edit: wrong thread
nullo said:
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
Click to expand...
Click to collapse
Do you mind me asking how I can manually flash 1.82.605.6 to my device? I'm s-off/rooted, bootloader locked, flashed stock recovery (thinking I could get OTA, I was wrong). Ideally I'd like to not lose data, but all I'm really worried about is not losing s-off or bricking my phone. It seems like this must be common knowledge, because any time firmware is posted or linked with a ROM there are no instructions on how to actually install it. I would really appreciate some help, I'm stuck on 1.19.605.22!