This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
Try Wipe Cache - Dalvik - Data on TWRP
I know you'll need to reinstall everything but hey may fix your bootloop problem
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
TeutonJon78 said:
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
Click to expand...
Click to collapse
LoL, so dislike auto-correct , Thanks for the mention
DrakenFX said:
LoL, so dislike auto-correct , Thanks for the mention
Click to expand...
Click to collapse
My early morning phone typing always look like I've had a stroke.
I wonder if we really need to wipe "Cache" anymore. I haven't seen any phone even using it lately. It just sits there basically empty since they moved everything to be stored in the Davlik one on the Data partition. I know on my Nexus 4 it basically just takes up 560 MB doing nothing but storing one recovery log file. Does TWRP use it for something during install?
TeutonJon78 said:
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
Click to expand...
Click to collapse
Man people are so impatient, yes here we go, first bootloop....
---------- Post added at 07:39 PM ---------- Previous post was at 07:32 PM ----------
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
You are gonna have to wait until someone provides a working (flashable) backup of B20_boot, I'm guessing yours is corrupted or had user error, here I summon:
@DrakenFX @jkuczera @swehes @peramikic
Does anyone has a clean flashable B20_boot from your TWRP backups? This guy bootlooped after trying to restore his. I would give him mine, but will probably not get my Axon 7 Gray shipped until wednesday from B&H.
---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
And did you already tried clearing cache and data?
B4oE said:
When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
Do you see the ZTE logo?
I have the backups already made up, I believe this might be what you need:
jcadduono said:
heres some STOCK fastboot flashables 4 funsies: https://idlekernel.com/flash-tools/firmware/ailsa_ii_A2017U/B20/
Click to expand...
Click to collapse
jkuczera said:
Do you see the ZTE logo?
I have the backups already made up, I believe this might be what you need:
Click to expand...
Click to collapse
Is "system.img" the stock, out-of-the-box OS?
daneoleary said:
Is "system.img" the stock, out-of-the-box OS?
Click to expand...
Click to collapse
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
I apologize for not responding sooner. I was busy at work. Someone sent me a zip to flash through TWRP, which I will upload later, and then my bootloop issue was resolved. Apparently, the problem is with TWRP. Hopefully, everything will get ironed out soon. Other than that, I'm still having a good time (although frustrating at times) tinkering with my Axon 7.
B4oE said:
I apologize for not responding sooner. I was busy at work. Someone sent me a zip to flash through TWRP, which I will upload later, and then my bootloop issue was resolved. Apparently, the problem is with TWRP. Hopefully, everything will get ironed out soon. Other than that, I'm still having a good time (although frustrating at times) tinkering with my Axon 7.
Click to expand...
Click to collapse
Looking forward for your fix to help other members down the road! THANK YOU!
Jose-MXL said:
Looking forward for your fix to help other members down the road! THANK YOU!
Click to expand...
Click to collapse
Attached is the file I flashed.
jkuczera said:
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
Click to expand...
Click to collapse
B20_Boot only makes changes to boot.img and recovery.img
B4oE said:
Attached is the file I flashed.
Click to expand...
Click to collapse
Who sent it to you?
rczrider said:
Who sent it to you?
Click to expand...
Click to collapse
I honestly do not remember their name. Someone I spoke to through Freenode (http://webchat.freenode.net/?channels=twrp) simply told me to flash that zip. I just renamed it before flashing because I have a huge collection of zips for various devices. Hopefully, the one that has it can respond to my post. He/She was very helpful too!
jkuczera said:
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
Click to expand...
Click to collapse
xtermmin said:
B20_Boot only makes changes to boot.img and recovery.img
Click to expand...
Click to collapse
No, it modifies system:
From the updater script:
Code:
ui_print("Patching system image after verification.");
show_progress(0.550000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("Failed to update system image.");
show_progress(0.050000, 10);
ui_print("Patching fastboot.img image...");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
ui_print("Patching boot image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/boot:45946154:b5154bbd9bf32de3d1e2a287df025a483bf3c50f:45942058:c31f24136f92263b578c19356df513650a12befc",
"-", c31f24136f92263b578c19356df513650a12befc, 45942058,
b5154bbd9bf32de3d1e2a287df025a483bf3c50f, package_extract_file("patch/boot.img.p"));
ui_print("Patching recovery image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/recovery:44545326:5ce0d08c1e4efdaf65879574d74611d569fa036f:44541230:a13824adb7464c22637b70ddb8b0991ff365ab4c",
"-", a13824adb7464c22637b70ddb8b0991ff365ab4c, 44541230,
5ce0d08c1e4efdaf65879574d74611d569fa036f, package_extract_file("patch/recovery.img.p"));
set_progress(1.000000);
It alters system.img, fastboot.img, boot.img, and recovery.img. By the looks of it, it modifies system.img a fair amount. Just fixing fastboot wouldn't be a 50+ MB patch.
TeutonJon78 said:
No, it modifies system:
From the updater script:
It alters system.img, fastboot.img, boot.img, and recovery.img. By the looks of it, it modifies system.img a fair amount. Just fixing fastboot wouldn't be a 50+ MB patch.
Click to expand...
Click to collapse
I'm blind. I stand corrected.
B4oE said:
I honestly do not remember their name. Someone I spoke to through Freenode (http://webchat.freenode.net/?channels=twrp) simply told me to flash that zip. I just renamed it before flashing because I have a huge collection of zips for various devices. Hopefully, the one that has it can respond to my post. He/She was very helpful too!
Click to expand...
Click to collapse
it might have been me that linked it (i'm the maker of the zip as it shows you in the console flash ) but yeah that's our go-to when someone says they flashed twrp and their system won't boot. it means they swiped to enable system modifications. we should probably go about extending the warning on the swipe to enable modifications page since devices that come with marshmallow out of factory will bootloop after swiping if you don't flash supersu or the no-verity-opt-encrypt zip. (the zip disables system integrity verification in your boot image, allowing you to boot after making modifications)
you can find the original, and updates if/when i make them at https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/
you can also follow history at https://github.com/jcadduono/lazyflasher/commits/no-verity-opt-encrypt
jcadduono said:
it might have been me that linked it (i'm the maker of the zip as it shows you in the console flash ) but yeah that's our go-to when someone says they flashed twrp and their system won't boot. it means they swiped to enable system modifications. we should probably go about extending the warning on the swipe to enable modifications page since devices that come with marshmallow out of factory will bootloop after swiping if you don't flash supersu or the no-verity-opt-encrypt zip. (the zip disables system integrity verification in your boot image, allowing you to boot after making modifications)
you can find the original, and updates if/when i make them at https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/
you can also follow history at https://github.com/jcadduono/lazyflasher/commits/no-verity-opt-encrypt
Click to expand...
Click to collapse
Awesome! Well, THANK YOU because I was bootlooped for several hours. You helped me so much!
Does anyone has TWRP backup ? I tried the stock fastboot backups and manage to flash system.img and boot.img files but I am still stuck on ZTE Logo Screen.
Related
Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.
For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.
So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?
So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
There is a whole thread dedicated to this update in general.
lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse
nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.
So I just noticed there's a new TWRP build up for us! Just thought I'd throw this out there, not sure what's different.
https://dl.twrp.me/shamu/
the only change is "Bring back /misc"
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
8zabi said:
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
Click to expand...
Click to collapse
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
psycho_asylum said:
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
Click to expand...
Click to collapse
Flashify is usually good for that!
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
tsjanda said:
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Put phone into bootloader mode. Hold shift and right click to "Open command window here" where you have ADB and your TWRP file (assuming Windows PC). Type "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Dopamin3 said:
..... "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Click to expand...
Click to collapse
That's the most basic method, but with the app FlashFire you don't need a PC.
NLBeev said:
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
Click to expand...
Click to collapse
Thank you for this. If you are using Tapatalk latest app it opens the link in its own browser and the download is only 6.92k. Opening in chrome beta and downloading gets the whole file downloaded.
Sent from my Pixel XL using Tapatalk
NLBeev said:
That's the most basic method, but with the app FlashFire you don't need a PC.
Click to expand...
Click to collapse
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Strephon Alkhalikoi said:
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Click to expand...
Click to collapse
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
NLBeev said:
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
Click to expand...
Click to collapse
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Strephon Alkhalikoi said:
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Click to expand...
Click to collapse
That's imaginable, because I had to edit the post.
I have made a mistake; didn't check the file size. After reboot to recovery, I noticed that a corrupt IMG was flashed.
EDIT
Version 3.0.3-0 available see next post.
TWRP-recovery version 3.0.3-0 for Nexus 6 available.
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img.html
3.1.0-0
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img.html
What's new:
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Installed version 3.1.0-0. With all the changes themes need to be reworked. Also, there are rumblings in the XDA article discussion thread that Aroma does not work on this recovery. I'll have to check that.
EDIT: Aroma working perfectly here, as far as I can tell.
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
only one way to know, so try it and report back
wase4711 said:
only one way to know, so try it and report back
Click to expand...
Click to collapse
Will do when I am home later on tonight then report back.
chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
Usually, yes. I would backup up personal data onto PC before trying.
I take no credit for any of this. Monkey saw, monkey did. MAKE SURE YOU FULLY READ THE ORIGINAL POSTS AS THE MONKEY MAY HAVE OMITTED SOMETHING. If you are clueless, not good at following instructions, or apprehensive you might want to pass. If you managed to already get unlocked and TWRPed, I imagine you are good to go. Still, if you break your phone, it's on you.
1. Do a TWRP backup.
2. Flash one of the choices here (READ THE ENTIRE THREAD) :
https://forum.xda-developers.com/moto-x-style/development/rom-marshmallow-6-0-september-2016-t3536120
REBOOT.
I went with the Deodexed one. Check out the Mods too. I added Viper.
3. Get Systemless Root back using using the flash-able Script in Post #8 here (READ ALL 1st):
https://forum.xda-developers.com/moto-x-style/general/systemless-root-info-t3373864
3a. Direct Link here:
https://forum.xda-developers.com/attachment.php?attachmentid=3809946&d=1468261256
REBOOT
I was still stock but Rooted with Xposed and I successfully Dirty Flashed. OP still recommends a CLEAN Install. After running the script, the phone came back looking the same. I did lose my custom Boot Animation and Viper so I re-flashed them. I also flashed the latest SU just to be sure i had the latest. Probably makes no difference.
Build now says MPHS24.49-18-8 and security Patch 09/01/2016.
Be sure and thank the OP's for the flash-able Update and the Systemless script.
THANK YOU OP'S,
Monkey
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
acejavelin said:
...Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
G_Man18 said:
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
Click to expand...
Click to collapse
No... That's fine. I mean you can't flash the full system image via fastboot.
acejavelin said:
No... That's fine. I mean you can't flash the full system image via fastboot.
Click to expand...
Click to collapse
Thanks for the quick response. I am surprised how many people get in trouble when TWRP backups are easy to do and can get you going when you screw up--which does happen to all of us. I post little but do read quite a bit in these forums; most of my questions have already been answered. You say you will nudge people in the right direction, but from what I have seen, no one on here answers as many questions so meticulously as you. Thanks!
acejavelin said:
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
robn30 said:
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
Click to expand...
Click to collapse
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
acejavelin said:
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
Click to expand...
Click to collapse
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
robn30 said:
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
Click to expand...
Click to collapse
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
acejavelin said:
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
Click to expand...
Click to collapse
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
robn30 said:
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
Click to expand...
Click to collapse
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
robn30 said:
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
schneid said:
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
Click to expand...
Click to collapse
Pretty sure there is a post in here somewhere that has a link to the 24.221.4 recovery, but I just used the one in this full firmware download. Just extracted the recovery.img file only and flash it using fastboot. Here is the link.
https://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
This is what I found accidentally by myself. There is actually an easy way to flash the OTA update if you are too lazy to find a download link for the zip file(like me).
Required: TWRP(Always use the latest version to avoid problems), Any file manager
1. Download the update in settings through OTA. (Make sure full zip file is downloaded which normally exceeds 1GB.)
2. After finishing the download, open your file manager and enable the Show Hidden Files function.
3. Go to Internal Storage and find the folder named .Ota then copy the zip file to any directory you like.(Visible one which is not hidden.)
4. Reboot to TWRP and flash the zip file you downloaded, Magisk/SuperSU and other mods you like.
5. Wipe Dalvik and Cache
6. Reboot
7. Enjoy the update.
Ps: You should root your device before rebooting to prevent the TWRP from getting overwritten by stock recovery.
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4
counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct? I guess that could be the blah blah blah part of Step 4
Click to expand...
Click to collapse
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.
DawoodSahi said:
No, TWRP remains. Flash the full rom, flash magisk/su and reboot to recovery then to system.
And isn't this the simple basic procedure to flash the rom on a rooted device(?) I wonder how to used to do it before and also that you can find the latest rom update on downloads.oneplus.net - can't you?
Plus won't this trigger dm verity and encryption? Because I usually wait for the modified boot.img for the latest update which disables dm verity and forced encryption.
Click to expand...
Click to collapse
The DM Verity is usually okay because of magisk patching the boot image
counterfeit187 said:
The DM Verity is usually okay because of magisk patching the boot image
Click to expand...
Click to collapse
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, usually. Just make sure you don't let it reboot before you flash magisk or SuperSU
what if we have flashed a kernel?
DawoodSahi said:
So are you saying if I simply flash the complete rom and then magisk, it won't trigger dm verity thing?
Click to expand...
Click to collapse
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Ramith96 said:
what if we have flashed a kernel?
Click to expand...
Click to collapse
You mean you're currently on a custom kernel? If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.
Diatomix98 said:
Yes, what @counterfeit187 said was right. I have personally tried it last night by flashing only magisk after the update and after the bootup my device is still unencrypted.
Click to expand...
Click to collapse
Yup I updated last night, just flashing the open beta 14 zip and magisk in TWRP before reboot.
counterfeit187 said:
Well need to flash the TWRP image again so that recovery doesn't get replaced by default, correct?
Click to expand...
Click to collapse
If you root before rebooting (after flashing the full update zip), TWRP will remain. If you don't root, it will overwrite TWRP with stock recovery.
The whole process is already described (and in better detail) here: https://forum.xda-developers.com/showpost.php?p=70084260&postcount=3
Although admittedly, the info is not that obvious to find.
---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------
Diatomix98 said:
This is what I found accidentally by myself. It's been told countless time that we should not update through OTA if our phone is rooted which will most probably brick the phone. However there is actually an easy way to flash the OTA update
Click to expand...
Click to collapse
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
Diatomix98 said:
If so just follow the exact procedures and flash back your kernel which is the "blablabla" in the instruction.
Click to expand...
Click to collapse
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.
When we flash again doesn't it replace the twrp with the stock recovery?
redpoint73 said:
What is meant by this (the sentence I've highlighted in red font), is if you try to flash the "partial" or "patch" OTA (less than 1 GB), it will soft brick the phone (fixable if you flash the full update zip). Therefore, rooted and/or TWRP users should only flash the "full" update zip (> 1 GB).
If you get the update notification, the system should detect you have TWRP, and download only the full zip.
---------- Post added at 11:57 AM ---------- Previous post was at 11:48 AM ----------
It's completely unclear what is meant by "blablabla"
If the intent is to post a useful tutorial, the steps should be clear for everyone.
Click to expand...
Click to collapse
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here. That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.
Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
If by "it" you mean the recovery, then as it was mentioned a few posts earlier, NO, TWRP remains.
Unleashed by ONEPLUS 3T rooted
Diatomix98 said:
Yep, you are right it was a misunderstanding as I have been reading quite some posts mentioning how their phones got bricked when updating through OTA. I should have understood the whole situation better, my bad here.
Click to expand...
Click to collapse
No worries. I understand the confusion, as I agree the info in some threads isn't specific enough.
Diatomix98 said:
That "blablabla" actually means other mods that we are flashing along like Arise Sound and etc which are neither important nor will they affect the update. Anyway, I am going to edit the op. Thanks for the advic though.
Click to expand...
Click to collapse
You're certainly welcome. Again, your tutorial will most certainly be useful to a lot of folks; as it will make the info easier to find. So having the best info (and easy to understand) is good all around. :good:
---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------
Ramith96 said:
When we flash again doesn't it replace the twrp with the stock recovery?
Click to expand...
Click to collapse
Already answered a couple times in this thread.
If you update and immediately root, TWRP will remain.
If you update, and don't root, then yes TWRP may be replaced with stock recovery.
failed
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.
thesishir said:
I tried that exact procedure but couldn't get past the boot animation for about half an hour so reverted back to the nandroid backup.
Note: I have the latest twrp and it worked on previous update but couldn't execute this time.
Click to expand...
Click to collapse
Did you verify the downloaded update file was larger than 1 GB?
redpoint73 said:
Did you verify the downloaded update file was larger than 1 GB?
Click to expand...
Click to collapse
Yes I did! The file size is 1.43 gb to be exact but still no luck
thesishir said:
Yes I did! The file size is 1.43 gb to be exact but still no luck
Click to expand...
Click to collapse
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
redpoint73 said:
Not sure why it's not booting. But you might try to download the full update again, and install in TWRP (wipe Dalvik and cache, then flash): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
Click to expand...
Click to collapse
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.
thesishir said:
I have tried it several times with official downlaod provided by my phone and also with official op website but it tries to boot and freezes at the boot logo (the one where two dots follow each other) so I am here at last in a hope to fix this.
Click to expand...
Click to collapse
Only other think I can think of, is to do a full wipe (data, Dalvik, cache - the default wipe in TWRP). But you may not like that.
Or make sure you are on latest TWRP 3.1.1-2, or reflash TWRP.
I really just want to root stock. I have the Boost Mobile Perry.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).
I really don't care about encryption.
guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img
i have the moto e4 mkt which no verity version do i have to flash ?
Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.
madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome