Develop Bugs

Moto z play (xt1635-03) transformation 64 GB ROM + 3GB RAM

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?

Is there any safe method to update MEE7S using global rom yet?

I'm using RN5 chinese edition, but currently I'm using global stable rom.
I've just read that the new update will brick chinese phones running global stable rom. Is there any way to avoid the brick / recover from such thing?

Where did You read that ?
As far as i know, as long as you have unlocked bootloader you can install global mui on chinese device. Just leave your bootloader unlocked

Do not update before you unlocked the Bootloader.
Unlocked first then update.
If you see the problem (stuck in recovery mode).. You must flashing china rom first via fastboot metode. Then flash global rom...
I have tested. (Mee7s)

MikiGry said:
Where did You read that ?
As far as i know, as long as you have unlocked bootloader you can install global mui on chinese device. Just leave your bootloader unlocked
Click to expand...
Click to collapse
This is the article I read: Article

ruditremonti said:
Do not update before you unlocked the Bootloader.
Unlocked first then update.
If you see the problem (stuck in recovery mode).. You must flashing china rom first via fastboot metode. Then flash global rom...
I have tested. (Mee7s)
Click to expand...
Click to collapse
I see that you have MEE7S, which is the exact same device as the one I use.
So, did you succeed on upgrading the first time? Please tell me more. Do you use fastboot method (bypassing ARB first with dummy image or not) or how?

My Redmi Note 5 Bricked after MIUI 10 update
MikiGry said:
Where did You read that ?
As far as i know, as long as you have unlocked bootloader you can install global mui on chinese device. Just leave your bootloader unlocked
Click to expand...
Click to collapse
My phone gave me an option to update and it downloaded the image and then asked to restart so I did like have done in the past for v9 incremental updates.
It download the new ROM and I accepted the Restart Phone. After restarting I got a warning message at the bottom of the screen in red "This MIUI version can't be installed on this device" and the options are:
1. Reboot, which just brings me back to this same screen on startup.
2. Wipe Data. This goes through a wipe storage but it doesn't make any difference and just brings me back to the same screen after a restart.
3. Connect with MIAssistant. With MiPCSuite installed, it doesn't connect and just hangs.
Chatting to Mi Support, they tell me they don't recognise the phone even though I provided the IMEI number and the fact it is less than 1 year old. I bought it off Ebay new unused.
So now I have a bricked useless phone. Well done Xiaomi

@moby17
Can you boot your phone into fastboot mode ?
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
gamalkevin said:
This is the article I read: Article
Click to expand...
Click to collapse
Well.That"s new
This article has a one flaw. Were those devices officialy unlocked or fake-unlocked ?

Well it goes into Fastboot screen but just sits there.
MikiGry said:
@moby17
Can you boot your phone into fastboot mode ?
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
Well.That"s new
This article has a one flaw. Were those devices officially unlocked or fake-unlocked ?
Click to expand...
Click to collapse
Well it goes into Fastboot screen but just sits there. I remember it did one update when it was still MIUI 9 something earlier this year and right after that an annoying message would show up a few times a day near the top saying it wasn't an official Rom. I just touched on close and it would carry on working fine. The update to MIUI 10 was in settings, system update section.
Since then someone recommended flashing it back to v9 and using MI's rom flash app MiFlash I'm in the process of flashing it now. The small green progress bar has gone all the way to the end but in Result column it is still showing "Flashing". after 2 hours. Not sure if it's completed or not, will leave it alone for another few hours before rebooting it.

moby17 said:
Well it goes into Fastboot screen but just sits there. I remember it did one update when it was still MIUI 9 something earlier this year and right after that an annoying message would show up a few times a day near the top saying it wasn't an official Rom. I just touched on close and it would carry on working fine. The update to MIUI 10 was in settings, system update section.
Since then someone recommended flashing it back to v9 and using MI's rom flash app MiFlash I'm in the process of flashing it now. The small green progress bar has gone all the way to the end but in Result column it is still showing "Flashing". after 2 hours. Not sure if it's completed or not, will leave it alone for another few hours before rebooting it.
Click to expand...
Click to collapse
Is your device a chinese version with global rom and fake-unlocked bootloader ?
Which rom are you trying to flash ? China or Global ? ARB 4 or ARB 3 ?

MikiGry said:
Is your device a chinese version with global rom and fake-unlocked bootloader ?
Which rom are you trying to flash ? China or Global ? ARB 4 or ARB 3 ?
Click to expand...
Click to collapse
What is fake-unlocked bootloader exactly? Currently I have it unlocked (from what I know), and am on MIUI global before the latest update. Probably ARB 4.
I'm low-key hesitant to upgrade, because I don't want to wipe my phone in case anything bad happen, and worse, bricking.

I'm in the UK and it was a Global Rom.
gamalkevin said:
What is fake-unlocked bootloader exactly? Currently I have it unlocked (from what I know), and am on MIUI global before the latest update. Probably ARB 4.
I'm low-key hesitant to upgrade, because I don't want to wipe my phone in case anything bad happen, and worse, bricking.
Click to expand...
Click to collapse
I wouldn't upgrade it if I were you, you might brick it too.
I'm trying to flash it with a rom, any rom would do to get it back to a working condition but I haven't been able to flash it. I'm using MiFlash, I've tried China, Global, both newer 10 versions and the 9 without success.
I'm not sure what you mean by ARB 3 and 4.
There seems to be 2 types of ROMs available to down load. One for MiFlash
i.e whyred_global_images_9.6.20_20190620.0000.00_9.0_global_006620721b and the 10.x version which has 1 folder called Images and a list of .bat files
flash_all.bat
flash_all_except_data.bat
flash_all_lock.bat and a dozen more files.
and another miui_HMNote5Global_9.6.20_9d5e732488_9.0 and Chgina rommiui_HMNote5_V10.3.1.0.PEICNXM_38eb804e2b_9.0
with
Folders Firmware-Update, META-INFO and compatabily.zip
a boot.img file and another 6 files. For instance system.new.dat.br, system.patch.dat

gamalkevin said:
I see that you have MEE7S, which is the exact same device as the one I use.
So, did you succeed on upgrading the first time? Please tell me more. Do you use fastboot method (bypassing ARB first with dummy image or not) or how?
Click to expand...
Click to collapse
I have try upgrading from ota & flash rom via twrp but stuck in mi logo.
Then i trying flash china rom first (10.3.4.0 stable oreo) via fastboot method, let it booting and flash global rom (10.3.1.0 stable pie) via fastboot method too.
Succeed, no stuck in mi logo..

ruditremonti said:
I have try upgrading from ota & flash rom via twrp but stuck in mi logo.
Then i trying flash china rom first (10.3.4.0 stable oreo) via fastboot method, let it booting and flash global rom (10.3.1.0 stable pie) via fastboot method too.
Succeed, no stuck in mi logo..
Click to expand...
Click to collapse
Okay. Thanks for the information.

Redmi Note 8 Pro freezing in Android 10

Hi. I got a Redmi Note 8 Pro Global version and I updated it to Android 10 manually. Problem is I am getting random freezes everyday. I would like to go back to Android 9 because these freezing is very annoying and ruining my experience. I am not sure if this is related to MIUI or Android 10 itself. I've done factory reset and reset via recovery mode as well. Still the same. Are any instructions to go back to Android 9?
I've read in some forums that Android 10 has some issues even in pixel devices where if an app freezes, it brings down the whole OS. Mine freeze about 10 seconds, sometimes more. It's happening very randomly in different apps so it is very difficult to replicate.

joenefloresca said:
Hi. I got a Redmi Note 8 Pro Global version and I updated it to Android 10 manually. Problem is I am getting random freezes everyday. I would like to go back to Android 9 because these freezing is very annoying and ruining my experience. I am not sure if this is related to MIUI or Android 10 itself. I've done factory reset and reset via recovery mode as well. Still the same. Are any instructions to go back to Android 9?
I've read in some forums that Android 10 has some issues even in pixel devices where if an app freezes, it brings down the whole OS. Mine freeze about 10 seconds, sometimes more. It's happening very randomly in different apps so it is very difficult to replicate.
Click to expand...
Click to collapse
use indian version android 10 which is on miui v11.0.2.0.
It works fluently without any problem but keep in mind that preloader and other safety file is for Android 9. If you use them before flashing anything in android 10. Then it might brick your device. Even magisk brick some person device in android 10. So be safe before doing modification in it. Until preloader and lk will be available for it.

Hi. Thanks for the suggestion but what if I want to go back to Android 9 Global version? Just want to back to previous version when I got it out of the box. I don't want to flash or use other region roms. Just want to go back to Android 9. Is there any available steps or instructions out there? Can't seem to find one.
1hekill0r said:
use indian version android 10 which is on miui v11.0.2.0.
It works fluently without any problem but keep in mind that preloader and other safety file is for Android 9. If you use them before flashing anything in android 10. Then it might brick your device. Even magisk brick some person device in android 10. So be safe before doing modification in it. Until preloader and lk will be available for it.
Click to expand...
Click to collapse

joenefloresca said:
Hi. Thanks for the suggestion but what if I want to go back to Android 9 Global version? Just want to back to previous version when I got it out of the box. I don't want to flash or use other region roms. Just want to go back to Android 9. Is there any available steps or instructions out there? Can't seem to find one.
Click to expand...
Click to collapse
You can easily go back to android 9 global version by flashing fastboot rom via fastboot. You can flash fastboot rom just via mi flash tool by flashing lk and preloader before flashing rom or you can easily flash every image one by one manually in fastboot mode, Just by using command like fastboot flash system system.img, fastboot flash cust cust.img and so on. It is very easy. Hope it work for you.

Thanks for this. I've been following instructions from this link https://c.mi.com/ph/miuidownload/detail?guide=2. I think you are also referring to this one. I already followed instructions but I am now stuck in the unlocking method which says I need to wait 168 hours.
You mentioned I can flash img files one by one, is still possible when without unlocking the the device first via miui unlock tool?
1hekill0r said:
You can easily go back to android 9 global version by flashing fastboot rom via fastboot. You can flash fastboot rom just via mi flash tool by flashing lk and preloader before flashing rom or you can easily flash every image one by one manually in fastboot mode, Just by using command like fastboot flash system system.img, fastboot flash cust cust.img and so on. It is very easy. Hope it work for you.
Click to expand...
Click to collapse

joenefloresca said:
Thanks for this. I've been following instructions from this link https://c.mi.com/ph/miuidownload/detail?guide=2. I think you are also referring to this one. I already followed instructions but I am now stuck in the unlocking method which says I need to wait 168 hours.
You mentioned I can flash img files one by one, is still possible when without unlocking the the device first via miui unlock tool?
Click to expand...
Click to collapse
Nope you have to first unlock bootloader. But as I read sp flash tool can work without unlocking bootloader. So if you have fastboot than first flash preloader and lk and then you can use sp flash tool without authorised account. But I am not sure if it work then inform me also. And if it don't work you have to first unlock bootloader.

The experience posted by this user only reinforces my general impression not to do a major upgrade (even an "official" one pushed by the manufacturer) on any phone that one uses for primary use, unless you want to get involved in the whole rooting process and all the time and risk that entails.
In my experience, the original version of android that ships with a device, and subsequent minor fixes, are the most adapted to the phones specs. Despite claims otherwise, every major upgrade involves more resource use, since it was designed with the latest hardware in mind. It will therefore almost certainly degrade the performance of a phone, even one not that old. I have had this happen in every phone I have owned. And unless your phone is rooted, you can not downgrade the OS.
So when MIUI 12 comes out, with Android 10, I will definitely wait for others to do it first and wait for the feedback, maybe I'll just pass on it. Right now my RN8P works great, and the additional "features" of android 10 add no functionality whatsoever. Why screw around with something that already works great?
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
BTW the above is true on Apple devices, too, in my experience.

Question How come we don't have root and twrp yet?

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.

OnePlus 7T Wifi broken after re-flashing stock rom

So I tried rooting my OnePlus 7T yesterday and first downgraded from android 12 to 10 (build number Oxygen OS 10.0.13.HD64BA), then tried to root it and I ended up getting a screen that said QUALCOM Crashdump Mode. After trying to search for an answer how to fix it, I tried to re-flash the phone with the stock rom, which I got from here taking the latest Europe version - https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-7t.3979213/
I entered fastboot mode, and ran flash-all but when I watched a video on how to do it, I was taken to a different screen. I think I was maybe the advanced boot options screen (I had to pick a language then reboot to fastboot or recovery). After rebooting, I unlocked the phone and the wifi is now broken.
I saw a guide on here that said I had to do something about important partitions (not sure what that means), so I'm not sure I am correctly re-flashing the phone from the correct stock rom and can't find a thread that makes total sense to me. Any help would be great

MSM Tool
After restoring upgrade to the last OOS 11 (11.9.1 I think)
Then follow the links I gave you on your other thread .

Tomcar said:
MSM Tool
After restoring upgrade to the last OOS 11 (11.9.1 I think)
Then follow the links I gave you on your other thread .
Click to expand...
Click to collapse
Thanks for the help again.
I've downloaded the EU 10.0.13 MSM tools (as I downgraded my oneplus 7T to this) and it told me "device not match image"
What version of MSM do I need? I checked other links attached on similar forms and more often I only see an option for 7T for 10.0.03 or 10.0.15. I don't know what I'm doing wrong.

https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
One of them should fit.
Or, if only WiFi is broken, upgrade to 11.0.5.1. and use the MSM Tool for that.
What's you're phone? HD1903?
I think you've flashed the wrong Firmware like India on Europe or vice versa.

Ignore me, I got it to work using a different MSM version (10.0.15). Will go back and try follow your instructions to root as best I can