Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?
jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion
I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app
freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.
Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.
Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?
I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't
Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?
Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image
Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?
Related
GDrive link to my collection (captured using a XT1683 - RETBR channel): https://drive.google.com/drive/folders/1UIfyIox6RMGT6m4YZaNrazryEoFnKGlS?usp=sharing
I cannot guarantee these packages will work on your G5 Plus. Only try using them if you are absolutely sure their are compatible with your phone, as it may be possible your device won't be able to be updated by future OTAs if you sideload the wrong zip. I'm posting these for research purposes - if anyone would like to capture the OTAs from their own G5 Plus we could compare them and maybe find out which variants receive identical firmwares.
My device is the Brazilian variant (XT1683) with 32GB/2GB, NFC, TV, dual sim and no compass. By comparing one of my files to a package from another thread, it seems this variant receives identical OTA packages to ones in the RETIN channel.
Anyone can capture their own OTAs! Just run adb logcat from a command prompt window (assuming you have ADB installed), run the check for updates on your phone and begin downloading the package. Copy the logcat contents to a text editor, search for "handleDownloadServiceRequest:downloadUrl" and access the URL with your browser. You may rename the downloaded file afterwards - look for "fileName" or "Blur_Version" in your logcat to get the correct filename.
I have build NPNS25.137-93-8
I'm trying to get past a soft brick. I had an unlocked bootloader.
Can I fix this with fastboot (I can get to both the bootloader and into TWRP, but my TWRP backup fails to write to the system..
salsolomon said:
I have build NPNS25.137-93-8
I'm trying to get past a soft brick. I had an unlocked bootloader.
Can I fix this with fastboot (I can get to both the bootloader and into TWRP, but my TWRP backup fails to write to the system..
Click to expand...
Click to collapse
You can but you need your actual firmware and I haven't seen any NPNS25.137-93-8 firmware uploaded until now.
There are some users who say they used an older firmware to capture OTA's but imho there's a risk of softbricking.
There's a NPNS25.137-93-4 firmware around, it's up to you to use it: https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Sent from my Moto G5 Plus using XDA Labs
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!
So this will work for european users who did not break their persist?
Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know
Battery performance is for fully happy and satisfied OVERWHELMING
will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat
will it work for indian version XT1686
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...
I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks
I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough
No risk no Win buddies
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie
Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,??
mednazim said:
Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,
Click to expand...
Click to collapse
Most probably, you will receive it in this century.. I think. :laugh:
I'll be serious now. Nobody knows when you will receive an update. It depends on your region mostly, but there are also few other factors which can delay it. However, if you don't want to wait anymore and have knowledge of flashing fastboot firmwares, full fastboot Oreo firmware (step-by-step tutorial included) for Moto G5 is already available here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244. Of course, nobody is responsible for any damage you make by flashing it.
it is necessary to unlock bootloader and install recovery for install update OREO ?
mednazim said:
it is necessary to unlock bootloader and install recovery for install update OREO ?
Click to expand...
Click to collapse
No, it isn't. According to posts in the other threads, there are at least 2 requirements to successfully update to Oreo through OTA (https://forum.xda-developers.com/g5...ase-opp28-t3849273/post77771786)#post77771786).
The first one is that system, boot and recovery partitions must be 100% unmodified - restoring doesn't help. If it's once modified, only a full reflash of stock firmware (with equal or newer build) will revert it to completely unmodified state. If you decide to install an update with one of these partitions modified - in the better case, update will refuse to install. In the worse one, it will install, but you will end up with hardbrick.
The second one, your build number must be NPPS25.137-93-2-5 (install script do the checking of the build number in the beginning of the OTA install. If it finds different value, installation will be stopped with some error showing up, but nothing happens, because the whole process of updating didn't start at all).
Thanks bro i will try
Hello!
Been studying forums for a couple days but can't seem to get to a definitive answer.
Here's all I want - get android 9.0 on my phone - I don't care about saving data, unlocking bootloader or not, etc. It can be a custom ROM as long as it's stable. Ideally I'd like to put the stock RETAIL version on it. There are so many posts and many of them end of last year when PIE dropped but I can't find something that really summarizes for this model.
1. How to unlock bootloader and root if need be (https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792)
2. How to flash stock PIE on this phone
3. How to install custom recovery
(How does Magisk play into all this)
4. Stable custom ROM if needed?
If I'm missing something obvious, I'm ok taking the heat, but, if not and someone has this phone and has some answers, I'd be grateful!
Thanks.
----------------------------------------------------------------------
UPDATE:
1. I unlocked my bootloader following moto's website - easily googleable
2. Then I just flashed the retail OEM via fast boot using commands - i.e., I downloaded the retail for 9.0, extracted in in adb folder (which has fastboot), booted phone into fastboot mode and flashed it all manually. So far it's working fine. It complains at boot about unlocked bootloader and I can't get OTA updates. I know I can still root it via guide above.
I'll post any updates as I have them.
MrRedPants said:
Hello!
Been studying forums for a couple days but can't seem to get to a definitive answer.
Here's all I want - get android 9.0 on my phone - I don't care about saving data, unlocking bootloader or not, etc. It can be a custom ROM as long as it's stable. Ideally I'd like to put the stock RETAIL version on it. There are so many posts and many of them end of last year when PIE dropped but I can't find something that really summarizes for this model.
1. How to unlock bootloader and root if need be (xx)
2. How to flash stock PIE on this phone
3. How to install custom recovery
(How does Magisk play into all this)
4. Stable custom ROM if needed?
If I'm missing something obvious, I'm ok taking the heat, but, if not and someone has this phone and has some answers, I'd be grateful!
Thanks.
----------------------------------------------------------------------
UPDATE:
1. I unlocked my bootloader following moto's website - easily googleable
2. Then I just flashed the retail OEM via fast boot using commands - i.e., I downloaded the retail for 9.0, extracted in in adb folder (which has fastboot), booted phone into fastboot mode and flashed it all manually. So far it's working fine. It complains at boot about unlocked bootloader and I can't get OTA updates. I know I can still root it via guide above.
I'll post any updates as I have them.
Click to expand...
Click to collapse
Can you elaborate on what retail version you used?
I have the same (XT1710-01 albus_C RETUS...... which actually says "albus_retail/albus" in recovery mode) and currently on 8.0.0/OPSS27.76-12-28-20/19.
When I try to side load via adb "ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I get an error saying: "footer is wrong", "signature verification failed" and "error 21".
Trying to load "Blur_Version.29.11.30.albus.retail.en.US" I got a version mismatch (albus vs albus_c).
You have to flash in via fastboot. Not in recovery.
Kidding...Figured I'd start off the banter on this topic. Excited to get mine and be on the bleeding edge but already anxious about loosing root for a while.
bacon612 said:
Kidding...Figured I'd start off the banter on this topic. Excited to get mine and be on the bleeding edge but already anxious about loosing root for a while.
Click to expand...
Click to collapse
Same! I do like to experience the phone exactly as it is out of the box for a little while first (otherwise how do I know what I want to mod?), but I hope root is available pretty quickly. It usually is with OnePlus devices, right?
haha, but the sooner the better!! cheers
My best guess is that root will be available upon receipt of the device. Magisk has already updated to patch the Samsung S21 Ultra (SD888) kernel, I'd imagine the kernel on the 9 Pro not to be that much different. TWRP on the other hand is probably no where close. Since the Chinese version of TWRP (LRTeam) stopped making recoveries before Android 11, I think a fully functional TWRP is a ways off. But we'll see... Mauronofrio has made TWRP work for many devices that weren't officially supported. There is also an app made by a kernel developer that can OC/UV the GPU. Haven't been able to use that just yet but hopefully soon!
EDIT: Looks like root is definitely good to go (dev thread with patched boot img for European and Indian versions).
Root should actually be available once u get the device. If there is an update, unlock bootloader first then get full OTA then extract the boot.img out of it and use magisk to patch then u can fastboot flash it.
Bradl79 said:
Root should actually be available once u get the device. If there is an update, unlock bootloader first then get full OTA then extract the boot.img out of it and use magisk to patch then u can fastboot flash it.
Click to expand...
Click to collapse
Yes. I had planned on doing this. Anyone seen a link to the full OTA? I'll extract and patch it for the US unlocked model. Nothing on oneplus.com support page yet
How do I unlock the bootloader?
My plan is to unlock bootloader as soon as I get the device than start using it, once Root / TWRP will become available I'll flash that.
Would it work? Or will I need to format before rooting?
Levi4cyber said:
How do I unlock the bootloader?
My plan is to unlock bootloader as soon as I get the device than start using it, once Root / TWRP will become available I'll flash that.
Would it work? Or will I need to format before rooting?
Click to expand...
Click to collapse
fastboot oem unlock? (to be confirmed)
It will format the data partition (if nothing has changed since my previous oneplus 3T).
Bradl79 said:
Root should actually be available once u get the device. If there is an update, unlock bootloader first then get full OTA then extract the boot.img out of it and use magisk to patch then u can fastboot flash it.
Click to expand...
Click to collapse
Can someone point me to an explanation of how to do this?
getting the full OTA (here on this forum, or on the oneplus website?)
extracting the boot.img (if it's more difficult than extracting it from a zip file?)
patching the boot with magisk (I've only applied magisk through recovery)
fastboot flash boot boot.img (that one I know )
Thanks.
clavelm80 said:
Can someone point me to an explanation of how to do this?
getting the full OTA (here on this forum, or on the oneplus website?)
extracting the boot.img (if it's more difficult than extracting it from a zip file?)
patching the boot with magisk (I've only applied magisk through recovery)
fastboot flash boot boot.img (that one I know )
Thanks.
Click to expand...
Click to collapse
Here is the guide I followed for my OnePlus 7 Pro. I assume it will be about the same.
[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro
Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk. Recommended to patch your own image read this Grab the latest Platform Tools HERE 1. Download a stock Oxygen OS ROM Zip from Here Or the general section of...
forum.xda-developers.com
I usually get the OTA from Oxygen Updater app, but it should also be on the OnePlus website.
There's a python script in the link above that extracts payload.bin in the OTA so that you can get to boot.img.
Install the latest Magisk app on your phone (previously Magisk Manager) and user it to patch boot.img: https://topjohnwu.github.io/Magisk/install.html
terlynn4 said:
Here is the guide I followed for my OnePlus 7 Pro. I assume it will be about the same.
[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro
Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk. Recommended to patch your own image read this Grab the latest Platform Tools HERE 1. Download a stock Oxygen OS ROM Zip from Here Or the general section of...
forum.xda-developers.com
I usually get the OTA from Oxygen Updater app, but it should also be on the OnePlus website.
There's a python script in the link above that extracts payload.bin in the OTA so that you can get to boot.img.
Install the latest Magisk app on your phone (previously Magisk Manager) and user it to patch boot.img: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Just need to get that system image so I can extract. Im on AA (international unlocked)
Same, I'm just here waiting for an AA system image. Impatient to get rooted and ensure L1 is working on this display!
Edit: It seems 9 Pro does NOT have hardware attestation which is great for those of us looking to root and keep our L1 certificate.
Can confirm,
fastboot oem unlock
worked to unlock bootloader like on past models. Waiting for that image now so we can actually do something.
Other variants already have root. We on AA (us unlocked) are still waiting for the image
It seems 9 Pro does NOT have hardware attestation which is great for those of us looking to root and keep our L1 certificate.
Nom Prophet said:
Can confirm,
fastboot oem unlock
worked to unlock bootloader like on past models. Waiting for that image now so we can actually do something.
Click to expand...
Click to collapse
Did you have to do anything special to get the fastboot command to work?
I went to developer options and enabled "OEM unlocking" and "USB debugging", then rebooted to fastboot mode and confirmed the device shows up, but when I run "fastboot oem unlock" I get this error:
FAILED (remote: Command not supported in default implementation)
Did I miss something?
terlynn4 said:
Did you have to do anything special to get the fastboot command to work?
I went to developer options and enabled "OEM unlocking" and "USB debugging", then rebooted to fastboot mode and confirmed the device shows up, but when I run "fastboot oem unlock" I get this error:
FAILED (remote: Command not supported in default implementation)
Did I miss something?
Click to expand...
Click to collapse
Make sure you have the latest fastboot and or latest Android developer suite installed
bacon612 said:
Make sure you have the latest fastboot and or latest Android developer suite installed
Click to expand...
Click to collapse
I just grabbed the latest platform-tools and tried again with the same results.
Actually I seem to be in Recovery Mode when I get that error. I started with the device booted and ran "adb reboot fastboot", and it took me to the menu where it shows the 3 languages (Recovery Mode, not Fastboot?). On that screen, "fastboot devices" shows the phone, but "fastboot oem unlock" gives an error.
From there, if I use the menu to boot to Fastboot Mode (where it says Fastboot Mode in red and says device state is locked), then "fastboot devices" doesn't show the phone anymore.
Fixed and unlocked now. I followed the following steps in the top answer here to install a different driver:
Android Fastboot devices not returning device
At the moment I would like to reinstall Android on my device(custom hardware device). I got the image files after building. But when I enter fastboot devices nothing returns. adb devices is worki...
stackoverflow.com
Odd that I didn't have this issue with my old phone since I was just flashing stuff with fastboot a few days ago. Older version or something, I guess.
terlynn4 said:
Fixed and unlocked now. I followed the following steps in the top answer here to install a different driver:
Android Fastboot devices not returning device
At the moment I would like to reinstall Android on my device(custom hardware device). I got the image files after building. But when I enter fastboot devices nothing returns. adb devices is worki...
stackoverflow.com
Odd that I didn't have this issue with my old phone since I was just flashing stuff with fastboot a few days ago. Older version or something, I guess.
Click to expand...
Click to collapse
Always gotta keep things up to date. I remember flashing a Motorola a while back that had me feeling frustrated and flummoxed only to find out that --while I had updated fastboot itself-- I had an out of date mfastboot, or whatever Motorola was using.