Hi, I have bought used here in Italy a op3, when turn on in the display I can see a message about the bootloader unlock, and so I think that the previously owner have unlocked the unit. Now I have a problem with the update, I have tried with ota and with USB but the phone stop the update and show me the message installation failed, then I can only reboot. How I can relock the Bootloader? Thanks in advance for your help.
before you re-lock the bootloader you should make sure that you are running the stock oxygenOS rom and receovery, see below:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
alchemist76 said:
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
Click to expand...
Click to collapse
you might be running OOS 3.2.2 stock but still have a custom recovery - boot into recovery first just to confirm that you have the stock recovery as well
still if you have a custom recovery, it's easier to get update. Just download the full rom and flash it with TWRP (I don't think there is another custom recovery), it won't wipe the data. Even if the previous owner did a slight modification on OOS 3.2.2, it will overwrite it.
updates can be downloaded many days before the OTA appear on the phone.
Ok I think that I have a custom recovery, TWRP working with non rooted phone? I have checked and my phone not have root. Please can you explain how I can update through TWRP?
if you want to stay unlocked and use TWRP that's fine, but note that you will need to MANUALLY UPDATE every time if you're on the stock OOS ROM.
if you are not comfortable with this, follow the instructions on the link i sent you to get back to full stock with stock recovery as well, so updates OTA work correctly.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
alchemist76 said:
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
Click to expand...
Click to collapse
sorry, im not really sure what you mean, but if you're following the instructions on that post step by step and verifying what you get it should work.
You need to successfully flash the full zip to get the stock rom+recovery on there
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
alchemist76 said:
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
Click to expand...
Click to collapse
the bootloader being locked or unlocked is irrelevant - your issue is your non-stock recovery.
the full Oxygen OS zip includes the stock recovery from OnePlus, which OTA updates are programmed to use to automatically update your phone.
since you have TWRP recovery instead, you'll need to download and manually flash OxygenOS
download the full ZIP for 3.2.4 from this thread and flash it via TWRP recovery:
http://forum.xda-developers.com/oneplus-3/how-to/oxygen-os-3-2-4-released-t3437911
Related
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
ahmadsraj said:
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete or change any files and apps that is build-in on system.
Even you want to delete apps made from telecom operators IS NOT PERMITTED!
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
missile0407 said:
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete any files and apps that is build-in on system.
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
Click to expand...
Click to collapse
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
craig0r said:
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
Click to expand...
Click to collapse
Hello,
I have the same question as the OP. Everything seems to make sense when following this post. My question is even though I will just boot into recovery without ever flashing the recovery am I really able to disconnect my phone from the computer? It seems like the recovery files are actually on the computer so I would need to keep the phone connected while I install the supersu.zip
Thank you for the help
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
exad said:
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
Click to expand...
Click to collapse
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
SouthBayBruin said:
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
Click to expand...
Click to collapse
There's no reason you *can't* leave it plugged in, but yeah, when you run the fastboot command it loads the custom recovery into RAM, and the connection to your computer is doing nothing for you. I give my personal guarantee that it's 100% safe to disconnect after recovery's loaded. But again, if leaving it plugged in makes you more comfortable, it won't hurt.
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
SouthBayBruin said:
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
Click to expand...
Click to collapse
http://download.chainfire.eu/396/SuperSU
zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
KaranNavani said:
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
Click to expand...
Click to collapse
Dude, do the research yourself. I don't know how many more times this has to be said. There's nothing special you have to do, just apply the OTA update when prompted
ok, I got stock 4.4.4 but with root, bootloader is locked..
I wanna be able to receive the OTA update what do I need to do in order to be able to receive that?
or do I need to unlock the bootloader, install a recovery and flash lollipop threw that?
If you have stock system, kernel, and recovery, (no altered system files, either) being rooted won't keep you from getting the OTA. Locked/unlocked bootloader doesn't matter. If you rooted with SuperSu, just use its settings to uninstall root (you'll lose it anyway). However, I think you have to unlock bootloader to reroot, which, of course, will wipe your device. The OTA zip is now available for adb sideload if you're interested.
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Cobra11Murderer said:
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Click to expand...
Click to collapse
OTA won't wipe regardless of how you get it--over the air or sideloaded. Wug's will wipe unless you tell it not to (Options>Flash Stock>Enable no wipe). He also has the LRX21P build available. IMO, one way isn't better than another.
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
You probably already did all this, but you have to specifically send command to lock boot loader. I don't get how your device wasn't recognized through stock recovery but is on NRT, but it doesn't matter. Just use the kit which is what you probably did.
What you should do is back up what you need and want, then unlock the bootloader. You're not gonna get root without it on Android L since it requires a custom kernel.
Cobra11Murderer said:
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
Click to expand...
Click to collapse
Based on this, I assumed you unlocked your bootloader since first posting. NRT recognizes the device, right? Have you gotten it all sorted out yet.
idk why adb sideloading would kick the connection out, then the pc would say nexus 7 but wrong driver?, anyways i just went ahead and flashed the factory image using flash stock + unroot since I had it all backed up anyways, and that went great now I got lollipop on it, and should be able to root no probs now
thanks everyone, I hope i dont have a issue with adb again, im not sure if it was the samsung cord or what but it kept disconnecting at that part asking for a driver.. funny thing everything from bootloader, fastboot and all worked great with the driver that I installed using the steps in the toolkit..
Glad it's all good. Root with the toolkit. Just for the heck of it, you may want to try running CMD from wug's ADB folder. I've experienced just the opposite with older versions of the kit. NRT wouldn't recognize device. I'd go to CMD and device recognized. Return to NRT, all good again.
alrighty will do!, thanks for all your help
Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.
Hi,
Problem starting oneplus 3, let me explain.
1) purchased oneplus3, 4 months ago.
2) Rooted,updated oxygen 3.2.8 with TWRP recovery3021 and super SU 2.74-2
3) updated oxygen4.00 with twrp32128 and super SU 2.79SR2 everything was fine.
4) Received OTA update through VPN for oxygen 4.0.1 (30mb), installed but unable start instead it was always going into twrp mode.
5) i changed twrp recovery back to 3021 and install stock oxygen 3.2.8,was working fine.
6) Now i wanted to UNROOT the device and back to stock so that i can get OTA Oxygen 4 and 4.0.1.
7) i followed steps below,
a) downloaded oxygen 3.2.1 and stock recovery.img
a) fastbootloader, and connect device.
b) fastboot devices
c) fastboot fastboot flash recovery recovery.img
d) fastboot oem lock - when i used this command and accept YES, screen got black and no further instruction for ADBsideload.
8) i used to restart the device in recovery but black screen, fastboot loader working.
FASTBOOT MODE
PRODUCT NAME - ....
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - .....
SECURE BOOT - enabled
DEVICE STATE - locked
9) and if i start the device in normal it asked for screen pattern lock but my existing unlock pattern doesnt work.
10) by using all the chance for screen pattern unlock it showed DECRYPTION UNSUCCESSFULL, clicked on RESET PHONE but again screen black in recovery mode.
11) NOW if i start my device it again shows DECRYPTION UNSUCCESSFULL and asking for RESET PHONE......
What to do now.....
regards,
Zahir
use the mega unbrick guide method 2, always work
Don't panic mate!
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
Thanks mirko8054, I will let you know soon......
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
mirko8054 said:
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
Click to expand...
Click to collapse
thanks a lot, I will do accordingly.
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
just wanted to highlight the things you did that caused the issue
1- flashing the stock rom through twrp, it's possible specially with the latest TWR0-11 but not advisable, you better always flash stock recovery and then sideload rom (full rom not update) and then fast boot TWRP back and reflash root... any other method always causes issues...
2- the 30mg updates do not work on a rooted device
3- unrooting without immediately sideloading rom will always cause the black screen and loop to recovery, it's not required to unroot unless you want to go back to full stock experience...
4- this the biggest problem you made, you relocked the devices bootloader, you also did it while the device has a lot of issues (some mentioned above) so the device bricked instantly, if you are planning on unlocking the device again ...NEVER NEVER relock the device again , there's no need to do that , all you need to do to go back to a full stock experience is to wipe everything in TWRP , flash stock recovery then wipe everything again from there, then sideload full rom (latest stable version) , then for good majors in the new rom recovery wipe everything agian and boot to system and from system do a factory reset. then recharge your device to 100% and re encrypt it if it's not...after that you're 100% on a full stock exerience and will receive ota and it'll work... and at that state only (without root or TWRP) you can relock the bootloader (which is gain not necessary at all, there's no benefit to it)
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs