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
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.
okay so i am pretty new still to flashing firmwares and using fastboot in general. I have the cricket version of the moto g6 play (forge) and noticed that i could not unlock the bootloader through moto's website . i noticed that the model number for the cricket version of the xt1922-9 was the same as the retail version from motorola . which on the website says has the ability to unlock . so i tried to flash the stock retail firmware for the retail and the most update verision being android pie XT1922-9_JETER_RETUS_9.0_PPPS29.118-68-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ended up flashing everything succesfully other than the boot.img and all of the system.img files and when i try and reboot the phone to recovery it says failed to pass validation back to fastboot . and the baseband section in fastboot now says not found . can someone help me with how i can flash all the correct files so i can get the phone just to boot up again.
You flashed everything except the boot.img and the system.img files?? That means you mixed up two FWs on one device...
Try flashing this FW for jeter_cricket from mirrors.lolinet.com
https://mirrors.lolinet.com/firmware/moto/jeter/official/Cricket/XT1922-9_JETER_A_CRICKET_9.0_PCPS29.118-63-2_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml.zip
WoKoschekk said:
You flashed everything except the boot.img and the system.img files?? That means you mixed up two FWs on one device...
Try flashing this FW for jeter_cricket from mirrors.lolinet.com
Click to expand...
Click to collapse
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
jesheesh said:
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
Click to expand...
Click to collapse
What is "not successfully"? Could you explain it more detailed, please? There's always an output message in terminal
jesheesh said:
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
Click to expand...
Click to collapse
You could try LMSA flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
You could try LMSA flash rescue option
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i'll download it and try it out
jesheesh said:
i'll download it and try it out
Click to expand...
Click to collapse
I'll also go ahead and copy and paste the output for you here as well.
Sorry it takes me so long to reply . Most of my tinkering time is eaten up with my other phone I have that just so happens to be the only model variant that can't unlock its boot loader hence no root or twrp ... :/
But anyway yeah I'm gonna try the tool and paste those lines of fast boot code for you. One sec.
How to flash fastboot rom in my Mi 11x.
I tried to flash rom using mi flash tool but anti rollback error comes.
Pleased help me how to flash rom using fastboot rom/
saurabh9897 said:
How to flash fastboot rom in my Mi 11x.
I tried to flash rom using mi flash tool but anti rollback error comes.
Pleased help me how to flash rom using fastboot rom/
Click to expand...
Click to collapse
edit the .bat file to remove the ARB commands
keyoke87 said:
edit the .bat file to remove the ARB commands
Click to expand...
Click to collapse
please guide me how to?
my ARB is 1
saurabh9897 said:
please guide me how to?
Click to expand...
Click to collapse
open the .bat file in notepad and remove this portion (depending on whether u use flash_all or flash_all_lock bat file)
also, please note to flash ONLY the original region of the firmware version to prevent bricking your device if you are using flash_all_lock.bat
keyoke87 said:
open the .bat file in notepad and remove this portion (depending on whether u use flash_all or flash_all_lock bat file)
also, please note to flash ONLY the original region of the firmware version to prevent bricking your device if you are using flash_all_lock.bat
Click to expand...
Click to collapse
ok let me try
actually right now i am on xiomi.eu 12.5.4 and my phone is not charging
i also visit to service centre also but they said that its a software issue but it is now out of warrenty as you unlock the bootloader
saurabh9897 said:
actually right now i am on xiomi.eu 12.5.4 and my phone is not charging
i also visit to service centre also but they said that its a software issue but it is now out of warrenty as you unlock the bootloader
Click to expand...
Click to collapse
flash back the original firmware and lock back bootloader
as i have mentioned, let me remind again, please only flash only the original region firmware of your device else if u lock your bootloader then you will have a bricked device. you can only lock your bootloader after flashing the original region of your firmware.
for example: your device comes with global firmware originally, u can only flash global fastboot rom, if u flash india firmware and lock your bootloader, you will brick your device
ok i m trying
keyoke87 said:
flash back the original firmware and lock back bootloader
as i have mentioned, let me remind again, please only flash only the original region firmware of your device else if u lock your bootloader then you will have a bricked device. you can only lock your bootloader after flashing the original region of your firmware.
for example: your device comes with global firmware originally, u can only flash global fastboot rom, if u flash india firmware and lock your bootloader, you will brick your device
Click to expand...
Click to collapse
this is coming
i edit flash_all_lock
i edited this
help me please
Check if your adb drivers are installed at device manager
installed
i just wanted to fix my battery problem
use mi flash tool 2017.4.25 version & u dont even need to remove arb lines.
i visit service centre and they flash using EDL mode.
But i dont wana google dialer and messages in my phone.
Is there any solution to remove this and try alternative apps.
is here anyone who can help me?
saurabh9897 said:
is here anyone who can help me?
Click to expand...
Click to collapse
Hello, what is the region of your smartphone (Global, European, Chinese or Other)?
saurabh9897 said:
is here anyone who can help me?
Click to expand...
Click to collapse
1- Download this version of MiFlashTool : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
2- Download you're version of Mi11x in this website (choose the fastboot) : https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.0.4.0.RKHINXM/
3- Extract the tgz file to get folder with Images and other stuff
4- Launch XiaomiFlashTool and install Drivers
5- Select the folder with you're rom
6- Select CleanAllandLock if u need or select CleanAll
7- Click on flash
8- Wait and ENJOY!!!
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.