This is a tutorial for noobs. It is meant to provide information that you may or may not need, nonetheless it should get you from stock 7.1.1 to 8.0 Oreo regardless of your geographic location.
I am not responsible if you mess up your phone, however this is pretty safe since it has checks in place and will simply fail if you don't have the proper version of 7.1.1 on your phone.
METHOD 1 confirmed by @alypotter1 and @kingstu
A simplified way of updating using your device only. Untested by me but confirmed to be working.
Download
Move this zip file to the root directory of your internal storage
Go to Settings>Apps and Notifications>App permissions>Storage. In the top corner select the dots and activate 'Show system'. Find 'Motorola Update Services' and activate it
Reboot your device
The update should be detected by Update services automatically
METHOD 2
Prerequisites:
Your phone is up to date (Feb security patch-NPNS26.118-22-2-17)
Motorola Drivers - This is kinda a pain to find, most links take you to an old version not compatible with Windows 10
Moto Z Play Oreo update
ADB turned on-Developer options (Activate under About Phone>Build number hit repeatedly)-USB Debugging
Procedure:
1. Download the files, ADB is already included with the update file
2. Make sure you have Motorola drivers installed and ADB enabled
3. Unzip the files and open a command prompt in windows
4. In cmd, browse to the folder containing the files using cd (File location)-switch drives if you need to using D:, C:, etc
Your Phone:
1. Turn it off
2. Hold the power button and volume down until it starts in AP Fastboot mode
3. Hit Vol down until you see Recovery Mode
4. Hit Power button to enter it-You should see an Android on his back and 'No command'
5. Hit Power and Vol up at the same time to enter download mode - This may take a few tries, removing your case may make this easier
6. Press Vol down to get to 'Apply update from ADB' and hit the power button
7. Now you're ready to connect to your PC
Back to the PC:
1. Once connected windows should detect it and install the correct drivers (You should hear the windows 'new device' notification)
2. Type adb devices in the command window
You should see something like:
Code:
List of devices attached
ZY123SZC57D sideload
If not, you need to diagnose why windows is not detecting the device
3. Now type adb sideload update.zip
The phone will display progress updates as the update sideloads. This can take approx. 30 minutes (some have reported it taking up to an hour!). Resist the urge to assume it has hung at any point, walk away if you have to.
If I missed anything please let me know.
Alternate Google drive link-Use only if Mega is not working
Special thanks @talktosam for uploading the original update files
How to root 8.0.0
Details:
Code:
Version 8.0.0
Software Channel: Remains unchanged
Security patch: April 1st
Baseband: M8953_10238.63.04.83R ADDISON_ROW_CUST
Kernel: 3.18.71-perf-g174984b
Build: OPN27.76-12-22
scottdanpor said:
This is a tutorial for noobs. It is meant to provide information that you may or may not need, nonetheless it should get you from stock 7.1.1 to 8.0 Oreo regardless of your geographic location.
Prerequisites:
Motorola Drivers - This is kinda a pain to find, most links take you to an old version not compatible with Windows 10
Moto Z Play Oreo update
ADB turned on-Developer options (Activate under About Phone>Build number hit repeatedly)-USB Debugging
Procedure:
1. Download the files, ADB is already included with the update file
2. Make sure you have Motorola drivers installed and ADB enabled
3. Unzip the files and open a command prompt in windows
4. In cmd, browse to the folder containing the files using cd (File location)-switch drives if you need to using D:, C:, etc
Your Phone:
1. Turn it off
2. Hold the power button and volume down until it starts in AP Fastboot mode
3. Hit Vol down until you see Recovery Mode
4. Hit Power button to enter it-You should see an Android on his back and 'No command'
5. Hit Power and Vol up at the same time to enter download mode - This may take a few tries, removing your case may make this easier
6. Press Vol down to get to 'Apply update from ADB' and hit the power button
7. Now your ready to connect to your PC
Back to the PC:
1. Once connected windows should detect it and install the correct drivers (You should hear the windows 'new device' notification
2. Type 'adb devices' in the command window (without quotes)
You should see something like: List of devices attached
ZY123SZC57D sideload
If not, you need to diagnose why windows is not detecting the device
3. Now type 'adb sideload update.zip'
The phone will display progress updates as the update sideloads
If I missed anything please let me know.
Alternate Google drive link-Use only if Mega is not working
Special thanks @talktosam for uploading the original update files
Click to expand...
Click to collapse
welcome, may be this is our last soak test for z play... see u guys any custom rom threads..
talktosam said:
welcome, may be this is our last soak test for z play... see u guys any custom rom threads..
Click to expand...
Click to collapse
Yes this should be the last major update for Moto Z Play. Anybody looking for 8.1+ will need a custom rom.
So this update, which appeared today on retin, could be safely installed on reteu?
yaatzek said:
So this update, which appeared today on retin, could be safely installed on reteu?
Click to expand...
Click to collapse
Yes the update is the same, we just have to wait for it to be distributed to our devices. I'm on tkpca and it has not released yet on that channel.
After the update you will have version 8.0.0, and will still be on software channel reteu in your case. Security patch is April 1st.
scottdanpor said:
Yes the update is the same, we just have to wait for it to be distributed to our devices. I'm on tkpca and it has not released yet on that channel.
After the update you will have version 8.0.0, and will still be on software channel reteu in your case. Security patch is April 1st.
Click to expand...
Click to collapse
any software channel can update this ota safely... no matter retin, reteu, br etc
Hi all,
It worked for me!
Thanks to @scottdanpor for this post!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm on 7.1.1 June 1, 2017 security patch (NPN26.107). Wondering if this OTA will work for me.
boonhoong said:
I'm on 7.1.1 June 1, 2017 security patch (NPN26.107). Wondering if this OTA will work for me.
Click to expand...
Click to collapse
Give it a try, it will either install or fail to install without making any changes.
boonhoong said:
I'm on 7.1.1 June 1, 2017 security patch (NPN26.107). Wondering if this OTA will work for me.
Click to expand...
Click to collapse
Flashing this official Oreo OTA will likely fail, as your device does not have the correct build. You need a clean, fully stock firmware with either the Feb 2018 7.1.1 security patch (build NPNS26.118-22-2-17) or the Oreo last soak test patch (OPN27.76-12-22) to flash this:
Package expects build thumbprint of 8.0.0/OPN27.76-12-22/24:user/release-keys or 7.1.1/NPNS26.118-22-2-17/21:user/release-keys
Is there a guide on what to do with unlocked boothloaders? I'm on Oreo SOAK 2 (or maybe 3) with TWRP. How can I fully unroot, replace bootlader/recovery, and lock the device? There used to be a guide for Nougat, but since I updated to SOAK, I haven't been able to go back to stock.
goncalesi said:
Hi all,
It worked for me!
Thanks to @scottdanpor for this post!
Click to expand...
Click to collapse
what compile number did you have before installing this update?
fuelvolts said:
Is there a guide on what to do with unlocked boothloaders? I'm on Oreo SOAK 2 (or maybe 3) with TWRP. How can I fully unroot, replace bootlader/recovery, and lock the device? There used to be a guide for Nougat, but since I updated to SOAK, I haven't been able to go back to stock.
Click to expand...
Click to collapse
You need to unroot and restore stock recovery and move forward. Your best bet might be to just wait for 8.0 complete flash firmware. That's why I stayed away from the soak installs, can be a real hassle.
_heberlopez95 said:
what compile number did you have before installing this update?
Click to expand...
Click to collapse
I was with the feb/2018 security patch before the update
Hi guys! How long does the update takes?
Mine is at 58% (patching system image after verification on phone) for a long, long time.
Just asking, because I'm pretty sure it's not stuck.
Do you know if this will work on Verizon variant? (Moto Z Play Droid XT1635-01)
marcuspereira said:
Hi guys! How long does the update takes?
Mine is at 58% (patching system image after verification on phone) for a long, long time.
Just asking, because I'm pretty sure it's not stuck.
Click to expand...
Click to collapse
It takes quite a while, and it does hang for a while on 58%, just walk away for a bit.
rusa-raus said:
Do you know if this will work on Verizon variant? (Moto Z Play Droid XT1635-01)
Click to expand...
Click to collapse
My guess would be no. Verizon likes to do things differently.
I'm stuck at 77% for 10 minutes now :/
yaatzek said:
I'm stuck at 77% for 10 minutes now :/
Click to expand...
Click to collapse
Don't touch it.
Related
This is a Step by Step guide to update from Lollipop build N920AUCU2APB2 to Marshmallow build N920AUCU2BPE5
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2a If your current build is N920AUCU2APB2 download this update
2b If your current build is N920AUCS2APE3 download this update
2c. If coming from a different build number see Post #2 to manually ODIN back to PB2 then run the update in step 2a
******************
If you get "Error 403 Forbidden" on any of the downloads use the following work around:
Download the Chrome Extension 'User-Agent Switcher'
Once installed switch to the agent 'Googlebot (Googles Spider)'
Downloads will be working again
After the downloads have started switch the Agent back to 'Default'
******************
Thank you to @bmatney who uploaded the DL to here
MD5: 7941A2C689C5B141675593E3FA33FB9A
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload
For those of you coming from a different builds here are the other links for updating:
From N920AUCU2APB2 to APE3 https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2APE3
meek2100 said:
Here are the other update links people are asking for:
N920 Update File Links
(5.1.1) U2APB2 -> (6.0.1) 2BPE5 Credit to: ColoMtn
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2BPE5-UP
----------------------------------------
(5.1.1) 2AOJ1 -> (5.1.1) U2APB2 Credit to: meek2100
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2AOJ1-to-U2APB2-UP
----------------------------------------
(5.1.1) 2AOI6 -> (5.1.1) U2APB2 Credit to: meek2100
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2AOI6-to-U2APB2-UP
-----------------------------------------
(5.1.1) U2APB2 ODIN files for clean flash or restoring to STOCK can be found here. Credit to: Sunderwear
http://forum.xda-developers.com/att-galaxy-note5/general/note-5-marshmallow-odin-package-t3331843
------------------------------------------------------------------------------
Click to expand...
Click to collapse
ColoMtn said:
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Ensure your Note 5 is running Build: N920AUCU2APB2 this is the latest OTA available as of (5/16/16)
4. Download this to update from Lollipop PB2 ->PE5
Thank you to @bmatney who uploaded the DL to here
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd <Your Directory>
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload
Click to expand...
Click to collapse
I'm getting "cannot read 'marshmallow.zip' " error
i keep getting dm-verity verification failed update from adb is disabled
creedicd said:
I'm getting "cannot read 'marshmallow.zip' " error
Click to expand...
Click to collapse
Did you make sure the directory had no Spaces and also move the ADB drivers to the same directory?
There are also users reporting that renaming the file 'marshmallow.zip.zip' fixes the issue.
im new to adb. i have no idea lol
blane3298 said:
i keep getting dm-verity verification failed update from adb is disabled
Click to expand...
Click to collapse
A quick google search says you may need to re-download the update
Odin?
ColoMtn said:
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Ensure your Note 5 is running Build: N920AUCU2APB2 this is the latest OTA available as of (5/16/16)
4. Download this to update from Lollipop PB2 ->PE5
Thank you to @bmatney who uploaded the DL to here
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd <Your Directory>
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload
Click to expand...
Click to collapse
Thanks man - awesome stuff. Why Odin download? Needed at this stage? Or just ADB sideload?
tr8ze said:
Thanks man - awesome stuff. Why Odin download? Needed at this stage? Or just ADB sideload?
Click to expand...
Click to collapse
Just ADB sideload. Will update. Thanks!
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Will these steps work on an encrypted phone?
darktrancer said:
Will these steps work on an encrypted phone?
Click to expand...
Click to collapse
Not sure.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
I am on OJ1, do you think it will work? or is there any way to update from OJ1 to PB2, since I am not on the US and cant get OTA updates, thank you very much
any way this could be made into a odin flashable file?
mcepedaj said:
I am on OJ1, do you think it will work? or is there any way to update from OJ1 to PB2, since I am not on the US and cant get OTA updates, thank you very much
Click to expand...
Click to collapse
Try to update the url with in the original thread to reflect OJ1 and PB2 build numbers (can't look up the full build numbers right now). If that works use this same guide to apply the update.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
blane3298 said:
any way this could be made into a odin flashable file?
Click to expand...
Click to collapse
I don't know how to do that but side loading was fairly simple.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
so i can get up to the point of doing the "adb sideloade" command but i get the cannot read error. where can i locate the adb drivers? im new to adb and sideloading. thanks for the write up though.
bdevillier19 said:
so i can get up to the point of doing the "adb sideloade" command but i get the cannot read error. where can i locate the adb drivers? im new to adb and sideloading. thanks for the write up though.
Click to expand...
Click to collapse
Step 1
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
ColoMtn said:
Step 1
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
step 1 of the tools required section? i've done that numerous times. it says the driver is installed but doesnt give me any info as to where the drive is at. thanks for the reply
I'm trying to download the update from the Mega link provided earlier. It is taking SO LONG.
I'm getting impatient.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Working on getting apps reinstalled... AT&T loaded more **** on this firmware than they ever have before. Ridiculous.
So this is just gonna be a short and super simple guide on how to update your Shield TV to 5.2 without loosing root.
This guide requires preexisting root and I am not responsible for any devices bricked, damaged, or defective due to this guide. Use at your own risk.
Mouse and Root Required
First off you're gonna wanna grab the OTA for your device, Darcy or rather 2017 16gb model can be found here
Second you're going to want to follow this link and download FlashFire by ChainFire and install it. I recommend doing so by ADB but sideload works all the same.
put the downloaded OTA file somewhere you can find it on the internal storage for later use.
Next you're going to want to go into settings > Apps > FlashFire > Open
Once inside the app use a mouse to navigate to the red plus and select "Flash Zip or OTA"
Select the OTA zip
Leave all of the settings as they are and select the check mark
Finally hit flash and sit back and relax for roughly 10 minutes for the file to flash.
Thanks to:
God
@Chainfire for making the app
NVIDIA for the update and device
Also if anyone wanted to upload the file found within /data/data/com.nvidia.ota/app_download I could/will update the guide to include the other models which should work as well.
Would this work for say downgrading, or would it still brick the Device?
Ichijoe said:
Would this work for say downgrading, or would it still brick the Device?
Click to expand...
Click to collapse
You would need to tinker with the ota files and settings as far as turning on factory reset but at that point I would recommend just using twrp or factory images
Cameron581 said:
Also if anyone wanted to upload the file found within /data/data/com.nvidia.ota/app_download I could/will update the guide to include the other models which should work as well.
Click to expand...
Click to collapse
I already uploaded this small OTA file for Shield TV 2015 (NON-PRO) 2 days ago:
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
If you are right i guess Flashify (and TWRP app?) will also do the trick (successfully update a 5.1 rooted device).
It didn't work for my Shield TV 2015 16 GB rooted in 5.1.
I followed the instructions to the letter, the process seems to be ok but after it finished to reboot it's still in 5.1.
Maybe it's related to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I clicked in "ignore", the flashing begun and it rebooted.The whole process took 2 minutes and it finished at home screen with a message of an update detected.I checked: still on 5.1.
I tried again but this time accepting the initial message to flash the detected OTA:
A message appeared after i clicked OK: "Uncrypting OTA failed!" and that's all.
sammarbella said:
It didn't work for my Shield TV 2015 16 GB rooted in 5.1.
I followed the instructions to the letter, the process seems to be ok but after it finished to reboot it's still in 5.1.
Maybe it's related to this:

I clicked in "ignore", the flashing begun and it rebooted.The whole process took 2 minutes and it finished at home screen with a message of an update detected.I checked: still on 5.1.
I tried again but this time accepting the initial message to flash the detected OTA:
I clicked in "ignore", the flashing begun and it rebooted.The whole process took 2 minutes and it finished at home screen with a message of an update detected.I checked: still on 5.1.
I tried again but this time accepting the initial message to flash the detected OTA:

A message appeared after i clicked OK: "Uncrypting OTA failed!" and that's all.
Click to expand...
Click to collapse
Did you use your own file or did you use the one I provided? The shield 2017 file I used worked perfectly fine but that's also meant only for the 2017 version, Im gonna check something tonight whenever I get home and make sure I didn't use the modified version that removed the system check
Cameron581 said:
Did you use your own file or did you use the one I provided? The shield 2017 file I used worked perfectly fine but that's also meant only for the 2017 version
Click to expand...
Click to collapse
I'm not the smartest person on the block but i can still figure i must use the Shield TV 2015 OTA (NON-PRO) file not yours....for my Shield TV 2015 (NON-PRO)
Cameron581 said:
So this is just gonna be a short and super simple guide on how to update your Shield TV to 5.2 without loosing root.
This guide requires preexisting root and I am not responsible for any devices bricked, damaged, or defective due to this guide. Use at your own risk.
Mouse and Root Required
First off you're gonna wanna grab the OTA for your device, Darcy or rather 2017 16gb model can be found here
Second you're going to want to follow this link and download FlashFire by ChainFire and install it. I recommend doing so by ADB but sideload works all the same.
put the downloaded OTA file somewhere you can find it on the internal storage for later use.
Next you're going to want to go into settings > Apps > FlashFire > Open
Once inside the app use a mouse to navigate to the red plus and select "Flash Zip or OTA"
Select the OTA zip
Leave all of the settings as they are and select the check mark
Finally hit flash and sit back and relax for roughly 10 minutes for the file to flash.
Thanks to:
God
@Chainfire for making the app
NVIDIA for the update and device
Click to expand...
Click to collapse
Can this be used for the 2017 Pro model?
Cameron581 said:
Also if anyone wanted to upload the file found within /data/data/com.nvidia.ota/app_download I could/will update the guide to include the other models which should work as well.
Click to expand...
Click to collapse
Hey. Can you tell me if your guide is also working on the model 2015 (16GB) using the Recovery OS directly from Nvidia Download Center:
//developer.nvidia.com/gameworksdownload
Thanks for advice
jionny said:
Can this be used for the 2017 Pro model?
Click to expand...
Click to collapse
Here's my upload from my Nvidia Shield TV PRO 2017 5.2 OTA update: https://mega.nz/#!SB0GXZRS!c_0E0txCJYw2ISMy7wnIe--LfFIS_d4pEaSKU3Eg18E
Currently attempting this as I write, will post back if successful.
Edit, no luck. Figured as much though, I guess I'll just revert back to stock and keep my device unrooted from here on out.
Rooted 2017 16gb experience
I rooted my 2017 16gb Shield with the Nvidia Developers image (5.1) a while ago and have it working nicely. I downloaded the OTA zip and the apk from above. I too get the error message that the update finds block level OTA. Not wanting to harm my existing setup, I abandoned this method.
Nvidia just posted the rooted 5.2 image. I will backup my apps and install this image.
However, long term, the method posted here would be more to my liking, if it maintains the existing apps and user data. A TWRP kind of install would also be less work than adb.
Applied rooted 5.2 image via adb and it worked well. SU had to be reinstalled via TWRP. Upgrade had no effect on existing apps.
Does anyone have the 5.2 prerooted developer image for the 16GB 2015 shield tv? I can't download it from the site for some reason
Cestults said:
Does anyone have the 5.2 prerooted developer image for the 16GB 2015 shield tv? I can't download it from the site for some reason
Click to expand...
Click to collapse
You should pass the Nvidia loops to be aboard their Dev program.
I think it's only a matter of time to see the 5.2 rooted images uploaded to techspot along the previous versions:
http://www.techspot.com/drivers/driver/file/information/17759/
Cestults said:
Does anyone have the 5.2 prerooted developer image for the 16GB 2015 shield tv? I can't download it from the site for some reason
Click to expand...
Click to collapse
http://drivers.softpedia.com/get/gaming-consoles/NVIDIA/
I finally got this to work on a 16GB 2015 Shield Tv. I made some modifications to the directions but this method worked for me.
Mouse and Root Required
Grab the pre-rooted developer image for your device.
Second you're going to want to follow the original directions and download FlashFire by ChainFire and install it.
Next, put the downloaded Image somewhere you can find it on the internal storage for later use.
Next you're going to want to go into settings > Apps > FlashFire > Open
Once inside the app use a mouse to navigate to the red plus and select "Flash Firmware Package"
Select the Developer image zip
Leave all of the settings as they are and select the check mark. ( I kept the defaults, leaving Data unchecked. (Boot, Recovery, System, and Vendor checked)
Finally hit flash and sit back and relax for roughly 10 minutes for the file to flash.
Cestults said:
Leave all of the settings as they are and select the check mark. ( I kept the defaults, leaving Data unchecked. (Boot, Recovery, System, and Vendor checked)
Click to expand...
Click to collapse
In this way, you could stay with all the data and settings like on rooted firmware 5.1 (only now upgraded to 5.2) ?
mucke5 said:
In this way, you could stay with all the data and settings like on rooted firmware 5.1 (only now upgraded to 5.2) ?
Click to expand...
Click to collapse
Yep.
Cestults said:
I finally got this to work on a 16GB 2015 Shield Tv. I made some modifications to the directions but this method worked for me.
Mouse and Root Required
Grab the pre-rooted developer image for your device.
Second you're going to want to follow the original directions and download FlashFire by ChainFire and install it.
Next, put the downloaded Image somewhere you can find it on the internal storage for later use.
Next you're going to want to go into settings > Apps > FlashFire > Open
Once inside the app use a mouse to navigate to the red plus and select "Flash Firmware Package"
Select the Developer image zip
Leave all of the settings as they are and select the check mark. ( I kept the defaults, leaving Data unchecked. (Boot, Recovery, System, and Vendor checked)
Finally hit flash and sit back and relax for roughly 10 minutes for the file to flash.
Click to expand...
Click to collapse
Thanks, now I can keep my shield rooted. Little annoying how you can't simply use the OTA updates and root them anymore but oh well.
And I have the Nvidia Shield TV Pro console.
Cestults said:
I finally got this to work on a 16GB 2015 Shield Tv. I made some modifications to the directions but this method worked for me.
Mouse and Root Required
Grab the pre-rooted developer image for your device.
Second you're going to want to follow the original directions and download FlashFire by ChainFire and install it.
Next, put the downloaded Image somewhere you can find it on the internal storage for later use.
Next you're going to want to go into settings > Apps > FlashFire > Open
Once inside the app use a mouse to navigate to the red plus and select "Flash Firmware Package"
Select the Developer image zip
Leave all of the settings as they are and select the check mark. ( I kept the defaults, leaving Data unchecked. (Boot, Recovery, System, and Vendor checked)
Finally hit flash and sit back and relax for roughly 10 minutes for the file to flash.
Click to expand...
Click to collapse
Thank you very much!
I upgraded successfully my Shield TV 2015 16GB from 5.1 rooted to 5.2 rooted using the dev image rooted preserving my apps and data.
:good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Known Issues
You tell me
Requirements
Required firmware version is N971NKSU2HVE9.
Instructions
You can follow the instructions on the wiki page for d1: https://wiki.lineageos.org/devices/d1/install
Please remember to upgrade your firmware through Odin. Put the provided file in the BL slot.
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads
Builds: https://sourceforge.net/projects/lineageos-samsung-note10-5g/files/lineage-19.1/
GApps: https://wiki.lineageos.org/gapps.html
Firmware: https://sourceforge.net/projects/firmware-samsung-note10-5g/files/
Source
https://github.com/Rocky7842/android_kernel_samsung_exynos9820/tree/lineage-19.1
Contributors
Rocky7842
Linux4 for maintaining the trees for exynos982x devices.
LineageOS team
About Safetynet
The safetynet on this ROM can pass basic integrity, but not CTS.
Due to the official stance of LineageOS team, and spoofing the build fingerprint may causes issues because Android uses build fingerprint changes as a signal to clear and rebuild several caches, I will not put the modifications in the ROM itself. Instant I'll put the information here, you can choose to do it or not.
To pass CTS:
We have to install Magisk(or Lygisk), then install both Universal SafetyNet Fix and MagiskHidePropsConf modules.
Reboot, enter adb shell.
In adb shell, type in "props". Now Magisk should ask you for su, accept it.
Type in "1". Which is edit device fingerprint.
Type in "samsung/d1xks/d1x:12/SP1A.210812.016/N971NKSU2HVE9:user/release-keys".
Type in "y" to confirm.
Type in "n" to avoid reboot now.
Type in "b" to go back to main menu.
Type in "5". Which is add/edit custom props.
Type in "n". Which is new custom prop.
Type in "ro.build.version.security_patch".
Type in "2022-05-01".
Type in "y" to confirm.
Type in "y" to reboot.
Now the security patch date and build fingerprint should be what we set, and Safetynet should pass now.
Working, I can confirm
A working rom for d1x, am I dreaming?
jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Give it a try and you'll know if it's a dream or not.
jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Thanks to Rocky7842
jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Please give some feedback if you already try it.
Rocky7842 said:
Please give some feedback if you already try it.
Click to expand...
Click to collapse
Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!
JÅ“508 said:
Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!
Click to expand...
Click to collapse
What do you mean...? Just use magisk.
Rocky7842 said:
What do you mean...? Just use magisk.
Click to expand...
Click to collapse
i want to root my samsung note 10 n971n version. Maybe you can help me
I don't know where to download the root files.
Enable Developer Options
Under developer options enable OEM unlock
Download latest firmware for your phone
Go-to https://galaxyfirmware.com/model/SM-N971N/
Download the right file for your device (just choose one)
Download magisk
Once this is downloaded, we can install it.
With that done, extract. The contents of the firmware you downloaded earlier.
Copy the AP file onto your phone.
Now open magisk app and tap on the install button and, make sure that the recovery mode Option stays checked, now tap the next option to bring us to the method which lets us select and patch a file.
Locate that AP file and then load it up into magic before tapping. The, let's go button.
After magisk is done patching the files..
Now you're going to be told that there is an output file, You just need to make sure that we look at where this file is and copy it to your PC.
Put the device into download mode,
Now extract the Odin program and open it
connect phone to PC
disable the auto reboot option under options tab
Locate the firmware that was downloaded and the patched file.
start loading these files into Odin.
click the BL button and load the file that begins with the letters BL.
Remember the same with the CSC and we need to load the CSC file (not the home CSC file).
Now click the AP button right here, but instead of loading, the AP file, instead we're going to load the AP file magisk patched.
there is a progress bar on the phone itself as well on the PC.
So once you get a green pass message
Device is not going to reboot because we need to manually reboot to instantly however.
With Odin finished, unplug USB cable. now, We're going to press the VOLUME DOWN and the SIDE BUTTON till the screen go black, let go of the VOLUME DOWN button while still holding the SIDE BUTTON and press and hold the VOLUME Up button. So you're gonna press these two buttons to force the device to reboot.
After reboot locate and open magisk
VoLTE Supported?
Alexis Levin said:
VoLTE Supported?
Click to expand...
Click to collapse
VoLTE is not supported.
New build uploaded. Security patch date is now 2022-11-05.
I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.
ngfuong said:
I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.
Click to expand...
Click to collapse
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.
Rocky7842 said:
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.
Click to expand...
Click to collapse
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?
ngfuong said:
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?
Click to expand...
Click to collapse
Please try re-download the file. If it still fails, try install the "20221023" build.
I didn't test the "20221113" version since I'm doing the bring up of A13. There's a possibility that the file was corrupt in the uploading procedure. No one reports that so far, though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
StatiXOS for Redmi K40 | Mi 11X | POCO F3 (alioth/aliothin)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Changing the intensity of haptics does not work.
Battery stats in Settings show nothing.
Please report anything else you run into!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
Detailed Flashing instructions in Post #3
Download the fastbootimage zip
Unlock your bootloader, and reboot to bootloader
Type in
Bash:
fastboot format:f2fs --fs-options=casefold,projid
[This will format all of the data in your phone including internal storage (photos, files, everything!)] (Skip this step if you are coming from a previous build)
Connect your phone to PC and type in
Bash:
fastboot update statix_alioth-XXXXXX-13-v6.1-TIRAMISU-img.zip
(XXXXXX denotes the date of the build)
Wait for a while until the flashing process completes, it will reboot your device
Enjoy!
Note: This ROM has GApps!
Spoiler: Stay in touch with our Telegram channels!
Official Releases & Announcements Channel
Android version: 13
Linux Kernel Version: 4.19.157
Source code: GitHub
Kernel Source code: GitHub
Code Review: Gerrit
Changelogs
6 February 2023
Initial build
7 February 2023
February 2023 Security patch
11 February 2023
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
23 April 2023
April Security Patch
Upgraded blobs to MIUI 14.x
Better pickup sensor implementation
Multi-Gen LRU enabled by default
Several Battery optimisations
5 May 2023
May Security Patch
Fixed the random reboot issues faced by some users
Detailed Flashing instructions:
NOTE: These instructions are for first time users only! If you are upgrading from previous StatiX Builds, you DO NOT NEED TO FORMAT DATA!
To flash StatixOS, you need these pre-requisites:
A PC with ADB/Fastboot installed
Redmi K40/Mi 11X/POCO F3 device
USB Cable
StatiXOS Build
Backup your internal storage before this process.
This guide assumes you are coming from MIUI 13.x with an unlocked bootloader.
For Windows Users:
Download SDK platform tools for Windows (do not use the latest platform tools, use any older than the r34) and extract it to anywhere you like.
Install ADB/Fastboot Drivers
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, navigate to the extracted platform-tools
In the folder you need to check if there are some dll files and a few executables (.exe files). We're majorly concerned with adb.exe and fastboot.exe.
Whilst pressing Shift key, Right click in the folder, and there shall be an option to "Open powershell window here" or "Open Command Prompt here"
In the powershell window, type in .\adb.exe devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about, just repeat the command)
Once the device is authorised, type in .\adb.exe reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in .\fastboot.exe format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
For Linux Users:
Install adb and fastboot according to your distro, and install proper udev rules.
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, open Terminal
In the terminal window, type in adb devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about)
Once the device is authorised, type in adb reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Type in fastboot devices, you'll get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in fastboot format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in fastboot update ''path/to/StatiXOS/Build/zip'' (replace path/to/StatiXOS/Build/zip with actual path to the fastboot images zip file).
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
NOW FIXED By using Post no. 10
I wish you well with this rom and look forward to future updates
many thanks Murali
johnr64 said:
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
I wish you well with this rom and look forward to future updates
many thanks Murali
Click to expand...
Click to collapse
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method.
Always having a PC is a good thing when flashing a ROM, as you can quickly restore your device to a working state without any worries if your device goes into bootloop (which should not happen with statix).
do you have some screenshots for this on poco f3? please post them
Update!
Changelog:
February 2023 security patch
Download from OP
exodius48 said:
do you have some screenshots for this on poco f3? please post them
Click to expand...
Click to collapse
Screenshots have been attached to OP
m_vaisakh said:
Update!
Changelog:
February 2023 security patch
Download from OP
Click to expand...
Click to collapse
Murali,
Your FAST.
Hi Murali,
I use a small standalone ADB program to install Temporary Recovery.
I have modified it a bit and added some basic adb FastBoot commands,
i have now included your install files as well:
-------------------------- UPDATED ! -------------------------
Now confirmed working
================================================================================
. ---------- Connect your phone to a PC in FASTBOOT mode to use this program ----------
.
.
Select Option:
.=========
.
1) Install TWRP Recovery (Remember to MOUNT SD Card in TWRP, wait 3 seconds and plug in your OTG adaptor)
2) Install OrangeFox Recovery (Remember to MOUNT SD Card in OFRecovery, wait 3 seconds and plug in your OTG adaptor)
3) Fastboot Devices
4) Reboot Bootloader
5) Reboot Recovery
6) Reboot
7) ADB Command line:
8) (WARNING)------------------ Format:f2fs
9) (WARNING)------------------ Install Statix_alioth-XXXX-XXXX XXXX-TIRAMISU-img.zip
10) Exit
.
.
. -To enter FASTBOOT, Power Off your Phone followed by Pressing and holding the Power and Volume down Buttons for 3 seconds,
.
.------------- Please read the INSTALL.txt file ---------------
.
Type option:
================================================================================
Also included in the .7z file are Magisk V25.2 and Migrate-GPE.
Download and unzip:
Statix-XXXX-XXXX-TIRAMISU + TEMP TWRP - OrangeFox (FASTBOOT) V1.0
Download Statix_Alioth-XXXX-XXXX-TIRAMISU, Rename it to rom.zip
and copy into the Statix_Alioth-XXXX-XXXX-TIRAMISU + TWRP - OrangeFox (FASTBOOT) V1.0.7 Folder.
Using this method, it is now easy to install this ROM as Murali explained and add Recovery if needed,
Thank you Murali for all your hard work,
I hope users find this little proggie helpful.
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from OP
m_vaisakh said:
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from
Apps in playstore not updating . always shows try again. Facebook messanger chats not loading .
Click to expand...
Click to collapse
Doesn't look like a statix issue to me. Did you format data using the given commands?
m_vaisakh said:
Doesn't look like a statix issue to me. Did you format data using the given commands?
Click to expand...
Click to collapse
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
gulmeli said:
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
Click to expand...
Click to collapse
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
m_vaisakh said:
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
Click to expand...
Click to collapse
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
gulmeli said:
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
Click to expand...
Click to collapse
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
m_vaisakh said:
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
Click to expand...
Click to collapse
Thank You Very much. it works fine now thanks again for the beautiful rom for great device.
Hi,
I tried the rom today,
the things i found:-
it seems to take a long time between the Poco F3 Logo and the boot animation,
i wasn`t able to find Face Unlock in the security setting,
Using the "Standalone ADB program" has made a massive difference,
as it simplifies every thing for me.
The rom is good but is in need of some TLC (Tender Loving Care),
I look forward to the next update,
Thank you again for all your hard work
m_vaisakh said:
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method...
Click to expand...
Click to collapse
I think you could explain also that this ROM uses vendorboot-as-recovery.
Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!
ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.
H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.
Do you have boot.img instead i rather have temp root
i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root
SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07
So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???