Related
Hello guys , I'm sort of a newbie to android rooting and custom Roms and stuff.So I wanted to root my HTC one(international version) , I successfully unlocked my bootloader , after that I didn't flash a custom recovery , I just rebooted . I saw that I had received an ota update , therefore I tried to update my one . After about a few minutes the installation cancelled and it shows a triangle with a red exclamation mark . I have stock Rom but I suspect it's because of unlocking the bootloader , coz unlocking it deletes a few built in apps . So is there any way I can successfully update my one ? Please take note that I'm a *noob* haha
nazeer786 said:
Hello guys , I'm sort of a newbie to android rooting and custom Roms and stuff.So I wanted to root my HTC one(international version) , I successfully unlocked my bootloader , after that I didn't flash a custom recovery , I just rebooted . I saw that I had received an ota update , therefore I tried to update my one . After about a few minutes the installation cancelled and it shows a triangle with a red exclamation mark . I have stock Rom but I suspect it's because of unlocking the bootloader , coz unlocking it deletes a few built in apps . So is there any way I can successfully update my one ? Please take note that I'm a *noob* haha
Click to expand...
Click to collapse
first read this post so you understand how ota update works
Unlocking the bootloader wipe /data partition including preloaded htc app in /data/preload. In some ota updates, these app are patched. If the updater script of the ota can't find these files (or they don't match because they were modified) the ota installation will abort --> red triangle.
Same for the thousand of system files, if some are missing or modified, ota installation will abort.
You need to know which file(s) is causing the ota install to fail. See this post how to find which file is missing or have unexpected content.
then you need to find each missing/modified files and push them to the right location and setting permission correctly (rw-r--r--).
i.e if the updater script reports (from stock recovery):
Code:
check /data/preload/calculator.apk failed, error, No such file or directory ()
calculator.apk is missing
this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
i.e if the updater script reports:
Code:
"/data/preload/calculator.apk" has unexpected contents
calculator.apk have unexpected content (corrupted or modified file)
in this case again this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
you must do it for all files that are causing the ota installation to fail
or in some cases, it will be simpler just to use a ruu, a guru reset rom or a nandroid backup to restore your phone and then do the ota update.
or you can use a custom rom with latest version.
Thanks alot
alray said:
first read this post so you understand how ota update works
Unlocking the bootloader wipe /data partition including preloaded htc app in /data/preload. In some ota updates, these app are patched. If the updater script of the ota can't find these files (or they don't match because they were modified) the ota installation will abort --> red triangle.
Same for the thousand of system files, if some are missing or modified, ota installation will abort.
You need to know which file(s) is causing the ota install to fail. See this post how to find which file is missing or have unexpected content.
then you need to find each missing/modified files and push them to the right location and setting permission correctly (rw-r--r--).
i.e if the updater script reports (from stock recovery):
Code:
check /data/preload/calculator.apk failed, error, No such file or directory ()
calculator.apk is missing
this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
i.e if the updater script reports:
Code:
"/data/preload/calculator.apk" has unexpected contents
calculator.apk have unexpected content (corrupted or modified file)
in this case again this mean you must find the right calculator.apk for your software version and push it to /data/preload/ and set permission correctly.
you must do it for all files that are causing the ota installation to fail
or in some cases, it will be simpler just to use a ruu, a guru reset rom or a nandroid backup to restore your phone and then do the ota update.
or you can use a custom rom with latest version.
Click to expand...
Click to collapse
Thank you , I will look at the options above , I just have one more question , I read somewhere that ota's are most of the time just patch files , so is it possible that probably later on there is a whole new system update , not patches , if that's the case then I suppose the ota will not look for any modifications as it will simply just install the new version ?
nazeer786 said:
Thank you , I will look at the options above , I just have one more question , I read somewhere that ota's are most of the time just patch files , so is it possible that probably later on there is a whole new system update , not patches , if that's the case then I suppose the ota will not look for any modifications as it will simply just install the new version ?
Click to expand...
Click to collapse
ota updates always patch existing files. If you want to do a full installation, you might want to use a RUU.
nazeer786 said:
Hello guys , I'm sort of a newbie to android rooting and custom Roms and stuff.So I wanted to root my HTC one(international version) , I successfully unlocked my bootloader , after that I didn't flash a custom recovery , I just rebooted . I saw that I had received an ota update , therefore I tried to update my one . After about a few minutes the installation cancelled and it shows a triangle with a red exclamation mark . I have stock Rom but I suspect it's because of unlocking the bootloader , coz unlocking it deletes a few built in apps . So is there any way I can successfully update my one ? Please take note that I'm a *noob* haha
Click to expand...
Click to collapse
Try this stock Rom http://forum.xda-developers.com/showthread.php?p=53773615#post53773615
Thanks for this , I will try this Rom out , but first I will have to install a custom recovery
Sent from my HTC One using XDA Free mobile app
nazeer786 said:
Thanks for this , I will try this Rom out , but first I will have to install a custom recovery
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
if you choose to flash a rom, I recommend you to use twrp recovery version 2.6.3.3. older version don't work with newer rom, and newer version of twrp have some bugs, so better to use 2.6.3.3
Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.
Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates
csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.
city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743
So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again
I'm wondering if it's worth it. Version 23.201.2.en.us
I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
To take the ota you have to reflash the full 5.1 firmware for verizon.
You can't have root nor a modified sytem for OTAs to work. So you need back all those apps you removed and get rid of root.
Sent from my XT1095 using Tapatalk
jonnythan said:
I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.
Click to expand...
Click to collapse
dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Please review the first post in that thread as the ROM is partially debloated and has SuperSU and Xposed pre-installed. GApps have been removed and you need to install your own. It is possible with the files posted to have a full stock install but you'll need the instructions from that thread to accomplish that.
mikeoswego said:
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Click to expand...
Click to collapse
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.
jonnythan said:
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.
Click to expand...
Click to collapse
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
Click to expand...
Click to collapse
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?
mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?
dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?
Click to expand...
Click to collapse
jonnythan said:
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?
Click to expand...
Click to collapse
The two smaller zips are the bootloader and modem firmware, the rom and kernel are in the xt1096-5.1-23.32-25-5-2_1.zip file. You could extract the boot.img file from the zip and flash it with fastboot. If you want the full ROM and want to flash SuperSU yourself and remove whatever bloat yourself, then use xt1096-full-stock-23.32-25-5-2.img.7z file; you can flash the image file within that archive with current versions of fastboot. (Or, using 7zip, you could delete the system.img file from xt1096-5.1-23.32-25-5-2_1.zip then rename the .img file in xt1096-full-stock-23.32-25-5-2.img.7z to system.img and place it in xt1096-5.1-23.32-25-5-2_1.zip. Then you would TWRP flash that, it would update your kernel (boot.img) and install the system partition just as if you took the OTA on the stock system.) Like AGISCI said above, the only way to use the OTA directly is on an unmodified stock system.
Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?
jonnythan said:
Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?
Click to expand...
Click to collapse
You must flash the full firmware like was mentioned earlier. It is impossible to do the update with a modified system.
Sent from my XT1095 using Tapatalk
I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.
I flashed the system .img file and it just updated my system without wiping anything. Seems to be working fine, but I had to reflash SuperSU.
desertcat said:
I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.
Click to expand...
Click to collapse
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.
desertcat said:
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.
Click to expand...
Click to collapse
THANK YOU!!! After being stuck on vacation for a week with this !#@[email protected]#$ update bugging me to install it every couple of minutes this fix stopped the problem.
Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1804.252[/U] on primary device. Also I will try to help out in case of issues.
If on Custom Rom then visit THIS THREAD to first return back to Stock Rom.
If you want to DOWNGRADE then visit THIS THREAD to revert to older firmware.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system update WITHOUT LOOSING DATA.
How to ,
Backup important app data like whatsapp chats etc. (precautionary step & is not needed, but better be safe).
Download latest modified system update file - WW-15.2016.1902.340.
Download decrypt.zip from HERE.
Download Magisk from HERE .
Reboot to TWRP.
Flash the ROM file.
Flash decrypt.zip file.
Flash Magisk zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
No partition is required to be wiped before or after flashing these files.
Also you do not have to uninstall Magisk before the procedure.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
Older full firmware packages :
WW-15.2016.1805.309 (14th June 2018)
WW-15.2016.1805.311 (04th July 2018)
WW-15.2016.1805.316 (16th July 2018)
WW-15.2016.1805.318 (23rd July 2018)
WW-15.2016.1808.323 (21st August 2018)
WW-15.2016.1808.326 (06th Sept 2018)
WW-15.2016.1808.327 (20th Sept 2018)
WW-15.2016.1809.331 (17th Oct 2018)
WW-15.2016.1810.334 (02nd Nov 2018)
WW-15.2016.1810.337 (20th Nov 2018)
WW-15.2016.1811.338 (19th Dec 2018)
WW-15.2016.1901.339 (22nd Jan 2019)
.A.V.i.n.a.S.h. said:
Modified full firmware packages (New packages will be added as they are available on Asus site) :
WW-15.2016.1805.309 (24th June 2018)
Click to expand...
Click to collapse
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Tolay said:
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Click to expand...
Click to collapse
I am on data pack right now .. tomorrow I will have WiFi access.
I will download and compare ZB602KL version full rom and reply back if I find a difference.
As far as I know, both versions are same but let me check once. I will let you know
first i remove my magisk or not,or flash without removing magisk
plz tell me full procedure to flash
.A.V.i.n.a.S.h. said:
I am on data pack right now .. tomorrow I will have WiFi access.
I will download and compare ZB602KL version full rom and reply back if I find a difference.
As far as I know, both versions are same but let me check once. I will let you know
Click to expand...
Click to collapse
Same here , ZB602KL variant.
Courious about different..
rajesh.880889 said:
plz tell me full procedure to flash
Click to expand...
Click to collapse
Yes .. flash without removing Magisk as we do not want to setup Magisk again.
We will reflash Magisk during installation.
Please follow given sequence of flash .. Rom - Decrypt - Magisk :good:
Tolay said:
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Click to expand...
Click to collapse
Please refer to other guide -- [ROM][STOCK][ZB601KL/ZB602KL] TWRP flashable Stock ROM
This guide is for those who are on Stock ROM. Process is little different.
Randyshare said:
Same here , ZB602KL variant.
Courious about different..
Click to expand...
Click to collapse
The method is applicable for both ZB601KL and ZB602KL .. Confirmed
how to flash rom steps
plz steps for rom flashing what to delete what to have,
i am on stock rom and magisk installed
rajesh.880889 said:
plz steps for rom flashing what to delete what to have,
i am on stock rom and magisk installed
Click to expand...
Click to collapse
Please follow the steps as in first post.
You should have TWRP along with Stock rom which you have I believe.
Download the 3 files mentioned in first post - ROM + Decrypt + Magisk and keep them in storage.
Reboot to TWRP and flash files in below seqeunce -
Stock_X00T_Patch_May_Version_309_TWRP.zip
decrypt.zip
Magisk-v16.0.zip
Do not wipe anything in TWRP before or after installation .. do not uninstall Magisk or anything else.
Just flash the files are reboot.
Other than the changes to the update script, are there any other changes you have done? The script output in twrp says 'patching system image that is modified by ....."
So I am wondering if you made changes to the system.img file too?
candiesdoodle said:
Other than the changes to the update script, are there any other changes you have done? The script output in twrp says 'patching system image that is modified by ....."
So I am wondering if you made changes to the system.img file too?
Click to expand...
Click to collapse
No changes .. it is just for testing .. I have not created the entire ROM so I mentioned this is Guide section and not the ROM development section.
Also the new file I have updated has no such message but just a message to identify the ROM change. You must have the old version which was there on Sunday.
.A.V.i.n.a.S.h. said:
No changes .. it is just for testing .. I have not created the entire ROM so I mentioned this is Guide section and not the ROM development section.
Also the new file I have updated has no such message but just a message to identify the ROM change. You must have the old version which was there on Sunday.
Click to expand...
Click to collapse
I downloaded last night only. About 24 hrs ago. I am referring to the first line In the script. See the SS
Also who made the new zip? I am interested in finding out what changes are being made if any other than the updater script.
candiesdoodle said:
I downloaded last night only. About 24 hrs ago. I am referring to the first line In the script. See the SS
Also who made the new zip? I am interested in finding out what changes are being made if any other than the updater script.
Click to expand...
Click to collapse
New zip name - Stock_X00T_Patch_May_Version_309_TWRP.zip
As already mentioned, the message was put just to let me know if the flashed file is changed one or original one from Asus.
I am taking Asus original rom and doing modification in update-script and if needed will make changes to boot.img (replacing with old boot image from Asus) and any other file to keep Magisk+TWRP to be working after update. I test the update for some time and then share it with all.
I will mention any substantial changes if any (for v309 no changes are there).
I have no intention to change what Asus has provided.
Purpose is to provide stock tested firmware for easy update at one stop .. and an easy way for people to come back to stock ROM.
.A.V.i.n.a.S.h. said:
New zip name - Stock_X00T_Patch_May_Version_309_TWRP.zip
As already mentioned, the message was put just to let me know if the flashed file is changed one or original one from Asus.
I am taking Asus original rom and doing modification in update-script and if needed will make changes to boot.img (replacing with old boot image from Asus) and any other file to keep Magisk+TWRP to be working after update. I test the update for some time and then share it with all.
I will mention any substantial changes if any (for v309 no changes are there).
I have no intention to change what Asus has provided.
Purpose is to provide stock tested firmware for easy update at one stop .. and an easy way for people to come back to stock ROM.
Click to expand...
Click to collapse
Thanks for confirmation. Great work
update ota automatic
hey after i follow your guide, can i get automatic update ftom system udpate?
hi.
can you make a guide on how you modify the zip file?
i successfully used it to update from 247 to 309
Kionaru said:
hey after i follow your guide, can i get automatic update ftom system udpate?
Click to expand...
Click to collapse
You will get update notifications .. no issue. But the update will not flash if you have TWRP and Magisk.
I will provide TWRP flashable file (after testing) in this thead in future. So expect the update within 48 hrs after new update (full ROM for the OTA) is relased by Asus.
To flash OTA there is an excellant guide HERE you can follow that to flash OTA (i.e. delta file). In this thread you can get full file.
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1804.252[/U] on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system update WITHOUT LOOSING DATA.
If you are coming from Custom ROM then
How to ,
Backup important app data like whatsapp chats etc. (precautionary step & is not needed but better be safe).
Download modified system update file from
[*]Download decrypt.zip from
[*]Download Magisk from
[*]Reboot to TWRP.
[*]Flash the ROM file.
[*]Flash decrypt.zip file.
[*]Flash Magisk zip file.
[*]Reboot & Enjoy.
[*](optional) If you want to boost up by debloating then
No partition is required to be wiped before or after flashing these files.
Also you do not have to uninstall Magisk before the procedure.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
Dude, i'm on Stock - 14.2016.1804.305 with TWRP & Magisk. will it work on me?
Thanks
boneyd26 said:
Dude, i'm on Stock - 14.2016.1804.305 with TWRP & Magisk. will it work on me?
Thanks
Click to expand...
Click to collapse
Yes .. it is for all those who are on stock ROM.
You can update from any past version i.e. v247,v252 &v305 to v309
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Maybe Oxygen Updater has full download link?
BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.
Did you flash stock recovery to both slots the last time?
g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?
BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.