Related
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
Does anyone have an idea when the S7 active potentially might see Oreo via OTA update?
Is it hard to install on your own via root or whatever?
Thanks.
jj8279 said:
Does anyone have an idea when the S7 active potentially might see Oreo via OTA update?
Is it hard to install on your own via root or whatever?
Thanks.
Click to expand...
Click to collapse
you can already use stock recovery to flash it... Just make sure you flash the previous OTA updates until BRB5 are the last 4 characters of your baseband in settings -> about -> software info
I'm running the first oreo listed on that link on my S7 Active, not sure if the others will work, but once you are on BRB5, just copy the oreo zip to the root of your MICRO SD card, reboot into stock recovery, select install zip from sd card, and select the file... to do this, you cannot be rooted, if your system status shows as custom, flash nougat with odin... if you need it the odin files as well asall previous OTA updates are listed in the website as well. Just remove /OTA/Oreo from the end of the url
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/OTA/Oreo/
let me know how it goes, i'm happy with it, it has the S8 style launcher and app icons, and the new AOD, but unfortunately, no live infinity wallpapers :/
remember to hit thanks
HI
any one have Oreo stock rom? My S7 active can't go into recovery mode, only can use ODIN to flash. thanx
troublesome said:
HI
any one have Oreo stock rom? My S7 active can't go into recovery mode, only can use ODIN to flash. thanx
Click to expand...
Click to collapse
There is no s7 active oreo rom in ODIN flashable format available yet, but you can update by flashing nougat, and flashing two ota flashable zip files in stock recovery. If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. You can then copy this zip file to your phone's external micro sd card, without extracting it, and use stock recovery mode (turn off, then volume up + home + power) to "apply update from sd card", or if you don't have a micro sd card, click "apply update from adb" and look up "how to use adb sideload" on google. Once it's done updating, do the same thing with this zip file, using stock recovery and "apply update from sd card" or using "apply update from ADB", and you will be on android 8.0 oreo. you can always use the first file you downloaded to go back to stock nougat if you don't like oreo, but it's working great for me!
remember to hit thanks, and if you want to support me, consider donating to me by clicking here!
I need rom what had bootloader 3 because my phone was brick.my phone lost recovery mode but it has download mode.i must odin my phone by rom bootloader 3.Can you have it? Share me.Tks bro !
jacoblong09 said:
If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. [/URL]
Click to expand...
Click to collapse
It doesn't work, but still thank you
troublesome said:
It doesn't work, but still thank you
Click to expand...
Click to collapse
It should work, make sure you have the usb drivers installed, the LATEST VERSION of odin (older versions may get stuck), and make sure your phone is in download mode (hold down power + volume down + home until a blue screen appears. click volume up). Then, open odin, connect your phone, and add the four .tar.md5 files extracted from the link you quoted. It works for me, but if it doesn't, try this file instead. let me know how it goes
jacoblong09 said:
It should work, make sure you have the usb drivers installed, the LATEST VERSION of odin (older versions may get stuck), and make sure your phone is in download mode (hold down power + volume down + home until a blue screen appears. click volume up). Then, open odin, connect your phone, and add the four .tar.md5 files extracted from the link you quoted. It works for me, but if it doesn't, try this file instead. let me know how it goes
Click to expand...
Click to collapse
Dear Sir:
Just FYI~
https://forum.xda-developers.com/showpost.php?p=76331898&postcount=610
https://forum.xda-developers.com/s7...sm-g891a-ota-updates-firmware-t3540866/page59
troublesome said:
Dear Sir:
Just FYI~
https://forum.xda-developers.com/showpost.php?p=76331898&postcount=610
https://forum.xda-developers.com/s7...sm-g891a-ota-updates-firmware-t3540866/page59
Click to expand...
Click to collapse
Oh, i see. You're on bootloader version 3. In that case, there is most likely nothing you can do to fix the phone. Just wait patiently for an odin flashable version of oreo for the s7 active, which should have bootloader 3 out of the box, and that should work. At this point, it is simply a waiting game. I really can't do anything for you, wish I could, but I unfortunately do not have the knowledge to modify bootloader versions yet. So, patience is key. Cheers!
troublesome said:
Dear Sir:
Just FYI~
https://forum.xda-developers.com/showpost.php?p=76331898&postcount=610
https://forum.xda-developers.com/s7...sm-g891a-ota-updates-firmware-t3540866/page59
Click to expand...
Click to collapse
actually, has anyone confirmed if unlocking the aboot allows bootloader downgrades on the s7 active? i also found this on the download site: https://cloud.mail.ru/public/BGy7/gKs4xzhRE/root/unlockg891aboot.tar
Try flashing this in the AP slot in odin to unlock the aboot partition, then flash the nougat from the link i gave before, using just the AP file from the firmware in the AP slot, and don't use the BL, CP, OR CSC slots
jacoblong09 said:
actually, has anyone confirmed if unlocking the aboot allows bootloader downgrades on the s7 active? i also found this on the download site: https://cloud.mail.ru/public/BGy7/gKs4xzhRE/root/unlockg891aboot.tar
Try flashing this in the AP slot in odin to unlock the aboot partition, then flash the nougat from the link i gave before, using just the AP file from the firmware in the AP slot, and don't use the BL, CP, OR CSC slots
Click to expand...
Click to collapse
I tried it before, does not work, either, actually I tried everything on the site.lol
i have an idea.... i'll try taking a backup of my working oreo installation and converting it into a flashable tar file for odin...
can you tell me what error the phone shows when you try to flash the nougat? does it have a sw rev check fail or secure check fail?
jacoblong09 said:
i have an idea.... i'll try taking a backup of my working oreo installation and converting it into a flashable tar file for odin...
can you tell me what error the phone shows when you try to flash the nougat? does it have a sw rev check fail or secure check fail?
Click to expand...
Click to collapse
sw rev check fail and only fail in BL part
http://protoss.myds.me/download/s7_active.jpg
then just don't flash the BL, flash everything else, let me know if it works
jacoblong09 said:
then just don't flash the BL, flash everything else, let me know if it works
Click to expand...
Click to collapse
If odin BRA7 and you don't flash file BL.It will run PASS but your phone will brick when your phone was on rom RD4 (8.0).Last month ,I try do it.
You don't try it !
---------- Post added at 02:53 AM ---------- Previous post was at 02:12 AM ----------
jacoblong09 said:
i have an idea.... i'll try taking a backup of my working oreo installation and converting it into a flashable tar file for odin...
can you tell me what error the phone shows when you try to flash the nougat? does it have a sw rev check fail or secure check fail?
Click to expand...
Click to collapse
I like your idea.You can help me do it .tks bro !
dothanhanloc said:
If odin BRA7 and you don't flash file BL.It will run PASS but your phone will brick when your phone was on rom RD4 (8.0).Last month ,I try do it.
You don't try it !
---------- Post added at 02:53 AM ---------- Previous post was at 02:12 AM ----------
I like your idea.You can help me do it .tks bro !
Click to expand...
Click to collapse
i realize now that the issue with my idea is... root... root is not achieved on oreo yet... and the firmware.mobi website upload to dropbox doesn't work, just refreshes after clicking start upload. So i'm stuck. But, if somebody could provide an image i could flash to root oreo on the s7 active, i will be able to make an odin .tar.md5
but i can not without root :/
One other thing you could try is extracting the ota zip for oreo you previously had, take the boot.img from it, compress the boot.img into a tar file, and then try flashing that with odin, in the AP slot. let me know how it goes, my phone is in a boot loop cause i tried an older root method :/
luckily, i used an earlier oreo OTA file, so i'm still on BL2
troublesome said:
sw rev check fail and only fail in BL part
http://protoss.myds.me/download/s7_active.jpg
Click to expand...
Click to collapse
Ok, after lots of digging through the ota zip, i believe i may have one step towards a solution.
But i need you to check it, as if it does work, it will update my phone to bootloader 3, which i would rather not do, since you already have bootloader 3, and it can't worsen the situation
now that i think about it, i could try flashing this on my currently installed marshmallow, after rooting, then try making the odin .tar.md5, but with the bootloader 3, so you can downgrade back to marshmallow. what do you think?
Try flashing the attached bootloader file, which i made for bootloader 3:
let me know if it works, thanks.. i might have a method for the system, too
EDIT NO STOP! i forgot a bin file, fixing now
EDIT 2 OK, SHOULD BE ALL GOOD NOW!
EDIT 3 I'M BRICKED NOW, but did see the new bootloader android logo at the bottom after flashing, then black screen qualcomm 9008
---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------
jacoblong09 said:
you can already use stock recovery to flash it... Just make sure you flash the previous OTA updates until BRB5 are the last 4 characters of your baseband in settings -> about -> software info
I'm running the first oreo listed on that link on my S7 Active, not sure if the others will work, but once you are on BRB5, just copy the oreo zip to the root of your MICRO SD card, reboot into stock recovery, select install zip from sd card, and select the file... to do this, you cannot be rooted, if your system status shows as custom, flash nougat with odin... if you need it the odin files as well asall previous OTA updates are listed in the website as well. Just remove /OTA/Oreo from the end of the url
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/OTA/Oreo/
let me know how it goes, i'm happy with it, it has the S8 style launcher and app icons, and the new AOD, but unfortunately, no live infinity wallpapers :/
remember to hit thanks
Click to expand...
Click to collapse
Hey I'm already running BRB5, do i need to rename the zip to update.zip or anything like that? also how do I send it to the root of the sd card, I just copied it into the regular file, does it need to be sent through a computer?
sultanmurad said:
---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------
Hey I'm already running BRB5, do i need to rename the zip to update.zip or anything like that? also how do I send it to the root of the sd card, I just copied it into the regular file, does it need to be sent through a computer?
Click to expand...
Click to collapse
Nah, use stock to flash CRC7 AS IS, NOT ANYTHING NEWER... My phone is now pernaneantly bricked due to me flashing an older bootloader from a new one
jacoblong09 said:
Nah, use stock to flash CRC7 AS IS, NOT ANYTHING NEWER... My phone is now pernaneantly bricked due to me flashing an older bootloader from a new one
Click to expand...
Click to collapse
Oh that sucks, is there any way to flash it back to original stock through adb? I think I'll just wait for the software update to come through the carrier, I don't wanna risk that
AND THANKS FOR THE QUICK REPLY!! I was minutes away from flashing CRD4, you saved me big time
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.
Doesn't XT1685 equal G5 Plus?
Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs
Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.
leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs
Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!
I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.
Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.
leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.
wzsx150's TWRP was released but I didn't see a thread here, so here's recovery that everyone would flash.
MEGA mirror: https://mega.nz/#F!g4NX3QQD!mU5-gR9Eu4A8YSR9jEu5PQ
DISCLAIMER:
This is build for the CN variant of ROG Phone 2, I don't know if it works on other variants, but it's possible to restore the official recovery back to your phone.
Current version is 3.3.1-1004.
Original post on https://weibo.com/6033736159/I9XKmocRd
I am on latest ww rom, and it boots to twrp, then instantly reboots to stock recovery.
Nevermind, jut did a backup!!!!!!!!!!!!!!
How do we flash this?
Cammarratta said:
How do we flash this?
Click to expand...
Click to collapse
Fastboot flash boot recovery.img
suzook said:
Fastboot flash boot recovery.img
Click to expand...
Click to collapse
The whole process requires ROM's boot.img to participate and I think recovery-TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img-tmp isn't a complete file, so you shouldn't just flash that directly to your phone. I wish I know how to decrypt the batch file and localize it in English so non Chinese speakers would use it too. I'll make a simple guide if the original developer doesn't make a English one.
FYI: The current build of this TWRP only has Simplified Chinese and English language, also has a modified splash image with author's info on it.
zestybaby said:
The whole process requires ROM's boot.img to participate and I think recovery-TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img-tmp isn't a complete file, so you shouldn't just flash that directly to your phone. I wish I know how to decrypt the batch file and localize it in English so non Chinese speakers would use it too. I'll make a simple guide if the original developer doesn't make a English one.
FYI: The current build of this TWRP only has Simplified Chinese and English language, also has a modified splash image with author's info on it.
Click to expand...
Click to collapse
Rename the file...delete the -tmp. That should be self explanatory, and the 1st screen that pops up when twrp boot. CLEARLY has a language button. press it, select english. Simple. The Author of this, has been around forever.
suzook said:
I am on latest ww rom, and it boots to twrp, then instantly reboots to stock recovery.
Nevermind, jut did a backup!!!!!!!!!!!!!!
Click to expand...
Click to collapse
So does it work on ww?
is there a way to fix touch input not working on twrp?
Cammarratta said:
is there a way to fix touch input not working on twrp?
Click to expand...
Click to collapse
Working fine here
Cammarratta said:
is there a way to fix touch input not working on twrp?
Click to expand...
Click to collapse
So i had to reflash and now my touch isnt working. You gets yours working?
Yeah. I reflashed and made sure there was no lock screen set or fingerprint and now it's working. Makes updating Roma really easy since since I'm in the latest we rom.
Cammarratta said:
Yeah. I reflashed and made sure there was no lock screen set or fingerprint and now it's working. Makes updating Roma really easy since since I'm in the latest we rom.
Click to expand...
Click to collapse
So I've bought the tencent version CN, which will arrive soon but with WW rom flashed on it. So I can just download latest WW update and flash the zip through TWRP, correct?
Yes. If you have this twrp you can flash and it'll update it.
Can I just check, with ROG phone II we don't use 'fastboot flash recovery recovery.img' , we instead use 'Fastboot flash boot recovery.img' to flash this twrp? Sorry, but I'm used to the fastboot flash recovery, so just wanted to make sure... Thanks
It's just that @suzook said it needs to be 'fastboot flash boot recovery.img'
Oh yes, and also, I'm guessing BL must be unlocked to flash this recovery?
EDIT: Nevermind about the flashing process, I see there is no seperate recovery partition to flash and the twrp img is the same size as the extracted rom boot img, so yes, it should be as @suzook mentioned.
I'd still like to confirm that flashing twrp MUST have BL unlocked, or not?
@reg66 I suggest you use this method first https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765
reg66 said:
Can I just check, with ROG phone II we don't use 'fastboot flash recovery recovery.img' , we instead use 'Fastboot flash boot recovery.img' to flash this twrp? Sorry, but I'm used to the fastboot flash recovery, so just wanted to make sure... Thanks
It's just that @suzook said it needs to be 'fastboot flash boot recovery.img'
Oh yes, and also, I'm guessing BL must be unlocked to flash this recovery?
EDIT: Nevermind about the flashing process, I see there is no seperate recovery partition to flash and the twrp img is the same size as the extracted rom boot img, so yes, it should be as @suzook mentioned.
I'd still like to confirm that flashing twrp MUST have BL unlocked, or not?
Click to expand...
Click to collapse
Bl absolutely needs to be unlocked, otherwise the recovery won't flash.
ermacwins said:
@reg66 I suggest you use this method first https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765
Click to expand...
Click to collapse
Yep, no worries, I'll use that apk to unlock BL, but is the rest of it necessary? My phone will already have FP changed to WW by seller (Giztop)..
reg66 said:
Yep, no worries, I'll use that apk to unlock BL, but is the rest of it necessary? My phone will already have FP changed to WW by seller (Giztop)..
Click to expand...
Click to collapse
My opinion? Bl unlock, completely reflash the ww rom yourself, this way your fresh, and know it's done properly.
Now we need custom roms ??
This recovery installs OK for me on my CN phone converted to WW rom, but if I use the TWRP "Root Phone" option in Advanced to root and install Magisk, it disables the Wifi, and after rebooting the phone it goes into a bootloop that I can't recover from (not even restoring from TWRP backup) and I have to reflash WW rom to recover. I repeated this refleash/reroot process 3 or 4 times and it happened every time with breaking wifi and then reboot failing.
So it works, but I wouldn't use the built-in rooting yet until it is ironed out.
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Am i doomed?
cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.