Develop Bugs

[LUX][STOCK][6.0.1] MPDS24.107.70.1-5 (1. Jan 2017 security level) TWRP backup

Since there doesn't appear to be any full stock firmwares for the January Patch around
Retail ASIA, DUAL SIM variant
Does not contain supersu or anything else
How it was made:
Flashed stock firmware LUX_RETASIA_DS_6.0.1_MPD24.107-70-1_cid7_subsidy-DEFAULT_CFC.info and then sideloaded the OTA package MPDS24.107-70-1-5
The only thing i have changed is the bootlogo (removed the pesky bootloader unlocked screen), but i am unsure if that's even in the backup contents
How to install:
I suggest grabbing a LUX_RETASIA_DS_6.0.1_MPD24.107-70-1 firmware and flashing that first, just so you don't get boot or modem issues
(you can get it here https://firmware.center/firmware/Motorola/Moto X Play/Stock/XT1562/)
(instructions on how to flash here at the bottom https://github.com/motoxplay/stock)
You need a TWRP recovery flashed (https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656)
Extract, put the folder on your device next to your own TWRP backups, reboot recovery, restore from it.
Download:
https://mega.nz/#!Bxk31KiR!xdVWV1M-06xfatAUetjeY94p1qArhiSefa4ezj4431c

AtomicStryker said:
Since there doesn't appear to be any full stock firmwares for the January Patch around
Retail ASIA, DUAL SIM variant
Does not contain supersu or anything else
How it was made:
Flashed stock firmware LUX_RETASIA_DS_6.0.1_MPD24.107-70-1_cid7_subsidy-DEFAULT_CFC.info and then sideloaded the OTA package MPDS24.107-70-1-5
The only thing i have changed is the bootlogo (removed the pesky bootloader unlocked screen), but i am unsure if that's even in the backup contents
How to install:
I suggest grabbing a LUX_RETASIA_DS_6.0.1_MPD24.107-70-1 firmware and flashing that first, just so you don't get boot or modem issues
(you can get it here https://firmware.center/firmware/Motorola/Moto X Play/Stock/XT1562/)
(instructions on how to flash here at the bottom https://github.com/motoxplay/stock)
You need a TWRP recovery flashed (https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656)
Extract, put the folder on your device next to your own TWRP backups, reboot recovery, restore from it.
Download:
https://mega.nz/#!Bxk31KiR!xdVWV1M-06xfatAUetjeY94p1qArhiSefa4ezj4431c
Click to expand...
Click to collapse
Is it possible to get the MPDS24.107-70-1-5 firmware to flash since, I tried flashing the MPD24.107-70 firmware and it is just throwing error left right and center, invalid signed image, preflash validation failed. I'm really stuck in what should be my next step

Presumably, getting the correct firmware for your device. I never had any issues and i re-flashed a single slot device to dual slot...

Not +ve response
siddharthnair96 said:
Is it possible to get the MPDS24.107-70-1-5 firmware to flash since, I tried flashing the MPD24.107-70 firmware and it is just throwing error left right and center, invalid signed image, preflash validation failed. I'm really stuck in what should be my next step
Click to expand...
Click to collapse
The method you've mentioned above. It's quiet helpful. But it's not success in my device.
I'm using Moto X play XT1562, dual sim and Location : India. Stock Rom with : 6.0.1 Marshmallow. Help me to flash with stock Rom ASAP Dude.

RohithAbi said:
The method you've mentioned above. It's quiet helpful. But it's not success in my device.
I'm using Moto X play XT1562, dual sim and Location : India. Stock Rom with : 6.0.1 Marshmallow. Help me to flash with stock Rom ASAP Dude.
Click to expand...
Click to collapse
You can download all the tools and stock ROM (MM) from my google drive link below. I have included the steps and commands to be executed.
ADB Drivers, USB Drivers, steps and commands : https://drive.google.com/open?id=0B5a7fC9ekt7seWF5SkVMNUIwTmc
Stock Rom (adb flash file) : https://drive.google.com/open?id=0B5a7fC9ekt7sVHF4VFdEdUlQcms

Can I get the modem of mpds24? Thanks

ZETROzky said:
Can I get the modem of mpds24? Thanks
Click to expand...
Click to collapse
Sorry, I don't have it..

Stock Recovery needed
Shibin_1985 said:
You can download all the tools and stock ROM (MM) from my google drive link below. I have included the steps and commands to be executed.
ADB Drivers, USB Drivers, steps and commands : https://drive.google.com/open?id=0B5a7fC9ekt7seWF5SkVMNUIwTmc
Stock Rom (adb flash file) : https://drive.google.com/open?id=0B5a7fC9ekt7sVHF4VFdEdUlQcms
Click to expand...
Click to collapse
Can you please upload just the recovery.img file for Moto X Play Marshmallow 6.0.1? I need the stock recovery image in order to get the Nougat OTA update.

Can you post the stock `recovery.img` as a separate file?
AtomicStryker said:
Since there doesn't appear to be any full stock firmwares for the January Patch around
Retail ASIA, DUAL SIM variant
Does not contain supersu or anything else
Click to expand...
Click to collapse
---------- Post added at 10:46 AM ---------- Previous post was at 10:39 AM ----------
Shibin_1985 said:
You can download all the tools and stock ROM (MM) from my google drive link below. I have included the steps and commands to be executed.
ADB Drivers, USB Drivers, steps and commands : https://drive.google.com/open?id=0B5a7fC9ekt7seWF5SkVMNUIwTmc
Stock Rom (adb flash file) : https://drive.google.com/open?id=0B5a7fC9ekt7sVHF4VFdEdUlQcms
Click to expand...
Click to collapse
Is the build number MPDS24.107.70.1-5?
If so can you also post the stock `recovery.img` as a separate file? Thanks

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

I can't Lock Bootloader (Mediapad M2 10 A01W)

Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.

ma2crmam said:
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
Click to expand...
Click to collapse
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!

ma2crmam said:
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
Click to expand...
Click to collapse
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs

5m4r7ph0n36uru said:
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?

ma2crmam said:
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
Click to expand...
Click to collapse
Glad it helped and yes it is not so expensive regarding the fact that there are all sorts of official firmware (mostly leaked ones) available for a lot of manufacturers.
The CUST reference at the end if the firmware version can be found in settings > about the tablet in the very last line. Mine is in German, So translated this line would state something like adapted/customized version. D001 is definitely Western Europe,this should be fine.
If not familiar how to install it google or search the forum for dload method. It will tell you what to do.
Sent from my HTC U11 using XDA Labs

I've done:
1. Get the correct firmware (version ...B007) and extract the RECOVERY.IMG and UPDATE.APP.
2. Flash the RECOVERY with Fastboot and install the UPDATE with the "dload" in the SD.
3. Reboot in RECOVERY MODE, wipe all and restore factory settings.
4. Then, the tablet was updated via OTA to the ...B008 version.
Then, positive:
1. The OTA works fine.
2. I was abble to install the Nextlix App and the HBO Spain App plays videos. Both didn't work before.
3. If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: SAFE
Then, negative:
1. I can't relock the Bootloader yet. When I try to relock (fastboot oem relock CODE) and the answer was again: FAILED (Remote: root type is risk)
Well, for normal use that's enough, but... THE RELOCK is becoming personal!!!

Moto Z Play RETEU stuck on bootloader with bad key.

Phone was on stock 7.1.1, July 1st patch with TWRP installed. I've wanted to remove TWRP in oreder to receive OTAs so I flashed stock 7.0 boot.img and recovery and now my phone is stuck in bootloader with bad key message when I try to start the phone. Flashing modified logo.bin didn't help. I'm guessing I need correct stock boot.img. Any ideas?

ViperX85 said:
Phone was on stock 7.1.1, July 1st patch with TWRP installed. I've wanted to remove TWRP in oreder to receive OTAs so I flashed stock 7.0 boot.img and recovery and now my phone is stuck in bootloader with bad key message when I try to start the phone. Flashing modified logo.bin didn't help. I'm guessing I need correct stock boot.img. Any ideas?
Click to expand...
Click to collapse
It should be this one, I just have DL it from Motorola 3 days ago
https://androidfilehost.com/?w=profile&uid=529152257862699209

@fablebreton
Hi, what is the difference between these files?
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_1.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_2.zip

shamu17 said:
@fablebreton
Hi, what is the difference between these files?
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_1.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_2.zip
Click to expand...
Click to collapse
It is the same firmware, Second file + third = First file. Just smaller zips
because DL 1,8G sometimes can be difficult, and anyway we have to unzip to flash with fastboot.
But if you have a good internet connexion, just DL the first file, it is the original one, untouched

fablebreton said:
It is the same firmware, Second file + third = First file. Just smaller zips
because DL 1,8G sometimes can be difficult, and anyway we have to unzip to flash with fastboot.
But if you have a good internet connexion, just DL the first file, it is the original one, untouched
Click to expand...
Click to collapse
Thanks for sharing, regards

Pre-rooted Boot Image OP7T European HD65BA 10.0.7

Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T European version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own European OP7T.
Link : https://www.androidfilehost.com/?w=files&flid=303273

*delete*

Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img

Worked well, got my phone rooted yesterday.
Lähetetty minun HD1903 laitteesta Tapatalkilla

click4dylan said:
Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img
Click to expand...
Click to collapse
USA version is HD65AA ? Can you send the product code and I will try

Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751

Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.

paulo_snower said:
Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.
Click to expand...
Click to collapse
NO! First time you unlock your bootloader thats wipe your device, not when flashing a boot.img

it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.

nicoilboss said:
it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.
Click to expand...
Click to collapse
click4dylan said:
Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751
Click to expand...
Click to collapse
zanderzone said:
USA version is HD65AA ? Can you send the product code and I will try
Click to expand...
Click to collapse
Sorry for being late. Please try this : https://forum.xda-developers.com/oneplus-7t/how-to/pre-rooted-boot-image-op7t-global-t4009305

Thanks, I found the instructions on how to do it already and took the Global boot image. I am just booting it with fastboot boot instead of flash. Just being cautious is all.

Same situation over there, trying either boot or flash the image, the phone reboots itself into bootloader. Stock 10.0.6.
Enviado desde mi HD1903 mediante Tapatalk

What is the difference between global and European? And can i still update ota after flashing this?

Hello !
Thanks for the guide !
I successfully installed Magisk, but once I install Riru core and EdXposed, my OP7T also gets stuck and boots only into fastboot. After wiping everything to factory reset, my phone is back to normal.
Is EdXposed working with this version of Magisk ?
(OpenPlus 7T HD65BA 10.0.6)
Thanks for help
Edit : problem solved with this method.

Excellent.
Many thanks @zanderzone

Can i still update ota in settings adter installing this version? Or will i loose root everytime?

karayemis said:
Can i still update ota in settings adter installing this version? Or will i loose root everytime?
Click to expand...
Click to collapse
Most likely you won't get any notifications if there are updates. You won't be able to use incremental updates.
But you can keep root flashing magisk right after the update before rebooting your phone.

could someone help me? I got the european version but if i try to boot the magisk_patched.img i just get stuck in fastboot mode and if i try to flash the patched image i get stuck in fastboot mode and i've to flash again the stock boot.
I also tried the global one but without any results.
Thanks
edit. I have the HD65BA 10.0.6 version

I was able to boot using your magisk_patched.img using "fastboot boot magisk_patched.img", but WIFI doesn't work now. I haven't inserted the SIM yet so I am unable to install magisk (it can't connect to download it). Is it only my case, or did it happen to anyone else? Any fixes?
Or is ir a temporary thing and after installing magisk it will work (WIFI)?
EDIT: with "fastboot boot Stock_boot.img" I get the same WIFI problem. Rebooting normally makes WIFI work again.
EDIT2: I tried it with the SIM on and the process was perfect. Thank you for that patched boot image and the tutorial!!!

Any chance @zanderzone that you could put a 10.0.7 version up?
I lost root with the recent update...
I found the detailed instructions too late.
Detailed instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Many thanks