Related
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?
It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks
Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.
Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.
Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).
relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.
ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.
The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.
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.
I'm trying to update my Redmi Note 8 Pro global from 12.0.8 to 12.5.1 manually since it doesn't find new updates no matter what i do.
I downloaded the ROM and selected it in "Choose update package", it tries to verify the update for a few seconds then just show me the message "Can't verify update. Couldn't verify update package." or "Can't verify update. Can't flash this stable ROM."
I tried to install it via USB flashing it with mi flash tool, still got the same message.
Does anyone know a fix for this, or at least why this is happening? Any help are appreciated.
Unlock bootloader, download the appropriate ROM for your version of smartphone (fastboot version), delete the check from the flash bat and you can flash. First try flashing, see if it boots. If everything is OK, you can try flash and lock.
Fytdyh said:
Unlock bootloader, download the appropriate ROM for your version of smartphone (fastboot version), delete the check from the flash bat and you can flash. First try flashing, see if it boots. If everything is OK, you can try flash and lock.
Click to expand...
Click to collapse
is there any way to do this without unlocking bootloader?
If you are scared of losing the warranty, you wont once you relock the bootloader. Any other way, you ve tried it and it didn't work
Fytdyh said:
If you are scared of losing the warranty, you wont once you relock the bootloader. Any other way, you ve tried it and it didn't work
Click to expand...
Click to collapse
It's not about the warranty, it's about my bank apps that might not work with the bootloader unlocked.
I'm going to do some research on how to unlock and lock the bootloader, as I didn't know it was possible to lock it again. Thank you for your help!
Fytdyh said:
If you are scared of losing the warranty, you wont once you relock the bootloader. Any other way, you ve tried it and it didn't work
Click to expand...
Click to collapse
Hello, i saw ur comment and made this acc.. can u guide me how to unlock mi10t and like explain whole process from A to Z? I dont wanna brink my phone. And also please guide me how to relock it again as well. Thank you. (I dont want to unlock my phone but its been like more than a year that i havent received a single update, not even a security patch).
Swatyoyo said:
Hello, i saw ur comment and made this acc.. can u guide me how to unlock mi10t and like explain whole process from A to Z? I dont wanna brink my phone. And also please guide me how to relock it again as well. Thank you. (I dont want to unlock my phone but its been like more than a year that i havent received a single update, not even a security patch).
Click to expand...
Click to collapse
I fear that you might have misunderstood me. You cannot relock the bootloader while running a modified stock rom/custom rom. You can only relock the bootloader on a stock rom.
Fytdyh said:
I fear that you might have misunderstood me. You cannot relock the bootloader while running a modified stock rom/custom rom. You can only relock the bootloader on a stock rom.
Click to expand...
Click to collapse
What is the process? Like i found the official rom of my mi 10t but idk how to unlock and relock in fact im worried about bricking my phone and if i able to do stuff right im worried i wont get OTA updated about unlocking my phone
Swatyoyo said:
What is the process? Like i found the official rom of my mi 10t but idk how to unlock and relock in fact im worried about bricking my phone and if i able to do stuff right im worried i wont get OTA updated about unlocking my phone
Click to expand...
Click to collapse
Are you running the latest stock version of your rom? Then, if you plan on using a smartphone with a locked bootloader, you already are. With a locked bootloader you won't get unofficial updates.
Fytdyh said:
Are you running the latest stock version of your rom? Then, if you plan on using a smartphone with a locked bootloader, you already are. With a locked bootloader you won't get unofficial updates.
Click to expand...
Click to collapse
The issue is.. im using miui 12 (12.0.11.0) with security patch or January 2021. Xaiomi blocked/stopped the upgrade from android 10 to 11.
Which version of mi10t?
Fytdyh said:
Which version of mi10t?
Click to expand...
Click to collapse
Press on all specs and see model name.
Fytdyh said:
Press on all specs and see model name.
Click to expand...
Click to collapse
M2007J3SY
Follow these guides
1. https://www.guidetoroot.com/unlock-...ets_Unlock_the_bootloader_on_the_Xiaomi_Phone
if it says wait a week, wait a week.
2. download latest fastboot rom available for your phone (your model is Mi 10T Global):
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
3. download latest miflash and install
Xiaomi Flash Tool - Official Mi Flash Tool
Download the latest and Official Xiaomi Flash Tool from the Official Xiaomi Flash Tool Website.
xiaomiflashtool.com
4. after selecting the rom, first select "clean all" and flash. if it boots and everything works, retry and select "clean all and lock". why ? if you lock the first time and it doesnt boot, you need to take it to service.
Fytdyh said:
Follow these guides
1. https://www.guidetoroot.com/unlock-...ets_Unlock_the_bootloader_on_the_Xiaomi_Phone
if it says wait a week, wait a week.
2. download latest fastboot rom available for your phone (your model is Mi 10T Global):
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
3. download latest miflash and install
Xiaomi Flash Tool - Official Mi Flash Tool
Download the latest and Official Xiaomi Flash Tool from the Official Xiaomi Flash Tool Website.
xiaomiflashtool.com
4. after selecting the rom, first select "clean all" and flash. if it boots and everything works, retry and select "clean all and lock". why ? if you lock the first time and it doesnt boot, you need to take it to service.
Click to expand...
Click to collapse
Tyvm i will give this one a try
Fytdyh said:
Follow these guides
1. https://www.guidetoroot.com/unlock-...ets_Unlock_the_bootloader_on_the_Xiaomi_Phone
if it says wait a week, wait a week.
2. download latest fastboot rom available for your phone (your model is Mi 10T Global):
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
3. download latest miflash and install
Xiaomi Flash Tool - Official Mi Flash Tool
Download the latest and Official Xiaomi Flash Tool from the Official Xiaomi Flash Tool Website.
xiaomiflashtool.com
4. after selecting the rom, first select "clean all" and flash. if it boots and everything works, retry and select "clean all and lock". why ? if you lock the first time and it doesnt boot, you need to take it to service.
Click to expand...
Click to collapse
Hi im back again. So im waititng for 1 week for my device to unlock. Soooo as its my first time doing stuff like this.. i was going through A LOT of new stuff and found xiaomi.eu rom r better in performance than global one. So i got 2 questions i hope u dont mind me asking them here.
1. Eu rom is really better than global? (Btw EEA = ea rom on this website:- https://xiaomifirmwareupdater.com/archive/miui/apollo/ ) ??
2. I heard to get eu rom i need something like twrp and adp something.. but can i get ea room from recovery just like global rom (method u mentioned above. Bcz ur method seems SUPER easy than eu rom one).
Swatyoyo said:
Hi im back again. So im waititng for 1 week for my device to unlock. Soooo as its my first time doing stuff like this.. i was going through A LOT of new stuff and found xiaomi.eu rom r better in performance than global one. So i got 2 questions i hope u dont mind me asking them here.
1. Eu rom is really better than global? (Btw EEA = ea rom on this website:- https://xiaomifirmwareupdater.com/archive/miui/apollo/ ) ??
2. I heard to get eu rom i need something like twrp and adp something.. but can i get ea room from recovery just like global rom (method u mentioned above. Bcz ur method seems SUPER easy than eu rom one).
Click to expand...
Click to collapse
The rom from Xiaomi.eu is a custom rom. Xiaomi.eu is a group of enthusiasts who modify the stock Xiaomi rom, adding and removing features. Make no mistake, that's a custom rom. Close the bootloader with that one installed and you hard brick your device. The method I told you is the official one, which makes downgrading and upgrading your phones super easy. Now, if you want to flash a different version of the stock rom to your phone and lock the bootloader afterwards, be careful. There were reports that nothing happened and everything worked, but unfortunately not that many. A different stock rom might have a different cell tower reception, not adjusted to your country. So you might get less reception.
Fytdyh said:
The rom from Xiaomi.eu is a custom rom. Xiaomi.eu is a group of enthusiasts who modify the stock Xiaomi rom, adding and removing features. Make no mistake, that's a custom rom. Close the bootloader with that one installed and you hard brick your device. The method I told you is the official one, which makes downgrading and upgrading your phones super easy. Now, if you want to flash a different version of the stock rom to your phone and lock the bootloader afterwards, be careful. There were reports that nothing happened and everything worked, but unfortunately not that many. A different stock rom might have a different cell tower reception, not adjusted to your country. So you might get less reception.
Click to expand...
Click to collapse
Ah i got it thank you soooooo much for the clarification. I will go for your method because i want to lock my phone again. I will report back after installing everything. Thank you
Fytdyh said:
The rom from Xiaomi.eu is a custom rom. Xiaomi.eu is a group of enthusiasts who modify the stock Xiaomi rom, adding and removing features. Make no mistake, that's a custom rom. Close the bootloader with that one installed and you hard brick your device. The method I told you is the official one, which makes downgrading and upgrading your phones super easy. Now, if you want to flash a different version of the stock rom to your phone and lock the bootloader afterwards, be careful. There were reports that nothing happened and everything worked, but unfortunately not that many. A different stock rom might have a different cell tower reception, not adjusted to your country. So you might get less reception.
Click to expand...
Click to collapse
Hey today my phone unlocks so i will be doing the update. I just wanted to ask that on website:- https://xiaomifirmwareupdater.com/archive/miui/apollo/ there is miui updates (i downloaded a fastboot 5.2g latest one 12.5.10.0) and firmware of 150mbs. So i have to install both firmware and miui rom? Or just stock miui rom? I read somewhere that firmware is for user which come from very old stock rom to latest one. So how to install firmware?
Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it
I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..
You can use https://flash.android.com/ to flash with a computer.
So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..
Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .
Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?
@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)
Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.
So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something
Just curious
Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol
Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.
Had same problem, tried installing it twice and gave up