Develop Bugs

Looking for NPPS25.137-93-14 fastboot firmware

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.

[RECOVERY] Unofficial build of TWRP by wzsx150

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.

10.0.5 boot.img?

Hey all! I'm trying to root my OnePlus 7t but I'm on 10.0.5 stock and I can't find a patched boot.img, or even a stock one to patch in Magisk. I'm on the global variant. If someone could point me in the right direction, that would be grand. I have already read mostly all the posts...

I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.

I just booted with an older one and flashed the latest magisk

Need 10.0.5 boot.img stock & magisk patched for indian varient
Hey .... Can you help me with the 10.0.5 boot.img , stock & magisk patched for indian varient HD1901 of 7t

ChongoDroid said:
I just booted with an older one and flashed the latest magisk
Click to expand...
Click to collapse
I had tried booting with 10.0.3 while on 10.0.5 , Did not turn out well .
Has anyone on 10.0.5 tried booting w/ the above 10.0.5 patched img ?

Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0

SkippRunning said:
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
Click to expand...
Click to collapse
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing

hightech316 said:
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
Click to expand...
Click to collapse
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images. You should only need to fastboot boot magisk_patched.img, then open Magisk Manager and install Magisk by choosing the direct install option in the list. You only need the steps I mentioned to have root, and if you flash it to A and B at once you can get stuck in a bootloop. I had that happen at one point from flashing both partitions, and I dont recommend trying it.

SkippRunning said:
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images.
Click to expand...
Click to collapse
Thanks , this can save a headache !

hightech316 said:
Thanks , this can save a headache !
Click to expand...
Click to collapse
Ya, I tried every relevant boot image I could find in the forums, and the device didnt work properly with any of them. The only one that allowed the device to boot successfully caused the wifi and sounds to not work. So I downloaded the full update from OnePlus and extracted it to a folder, then used payload dumper to extract all of the individual images out of the payload.bin file from OnePlus. I copied the boot.img into the phone storage and installed Magisk Manager, then patched the stock boot.img and copied it from the phone to my pc. Then I used fastboot boot magisk_patched.img to make sure the image I made would work. I booted the device and inside Magisk Manager I chose direct install in the list of options and everything went smoothly, and I didnt need to rely on finding images online that would hopefully work.

smokeythebear3 said:
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
Click to expand...
Click to collapse
Thanks a bunch for the share. That was the missing piece that I've been looking for. I have the HD1905 variant and I just used Magisk to patch the stock file you provided. After testing, I'm finally rooted. Thanks again.

OnePlus 7t 10.0.8/10.3.1 Magisk patched boot img

I've got the 7T tmo version unlocked via flashing Indian then int firmware. This is the 10.0.8 update from oxygen updater, pulled boot img from payload and patched with magisk. Enjoy.
Patched boot (global)
https://drive.google.com/file/d/1-CpEVcS2nJ7IhrOep6YibimgwZJRxvnI/view?usp=drivesdk
Stock boot (global)
https://drive.google.com/file/d/10X4okwoTVZltYJsOkGo0dv5QfdzU1LOM/view?usp=drivesdk
Full ota link (global)
https://drive.google.com/file/d/1-i5TfdU3Yx-VqSNLBMY5Xov_XYyubEIT/view?usp=drivesdk
________________________________________________________
Patched boot (India)
https://drive.google.com/file/d/10U_WEUiNhM8Maw_q9WTHiHTf7zwG23lO/view?usp=drivesdk
Stock boot (India)
https://drive.google.com/file/d/10UbrzFGWQsmM5ViuOmH-RebwWxHCAAoG/view?usp=drivesdk
Full ota (India)
https://drive.google.com/file/d/10O17sAyOa82nSiQ_yUvYS3QTMk8kG6Xv/view?usp=drivesdk
______________________________________________
European Patched boot 10.0.8:
https://drive.google.com/file/d/1zdBwlO74HT-D8y5yMmXYrW0mFiEtQN_v/view
European Stock:
https://drive.google.com/file/d/1OOSEfuGKrwGRKzsl-orSlVS2YUg4JyJR/view

This is Global (AA) right ? or Europe (BA) ?

bugra333 said:
This is Global (AA) right ? or Europe (BA) ?
Click to expand...
Click to collapse
Global AA

Reserved

Any chance you can create a patched img for the Indian version? Not able to find one.

sathya said:
Any chance you can create a patched img for the Indian version? Not able to find one.
Click to expand...
Click to collapse
I'm starting the download now. When I'm done I'll let you know

sathya said:
Any chance you can create a patched img for the Indian version? Not able to find one.
Click to expand...
Click to collapse
Posted patched up top make sure you grab the right one. I'll link the ota too

zeusofyork said:
Posted patched up top make sure you grab the right one. I'll link the ota too
Click to expand...
Click to collapse
Thanks so much!!! This will be very helpful for us to root!

bugra333 said:
This is Global (AA) right ? or Europe (BA) ?
Click to expand...
Click to collapse
Here You have for EUROPA
https://forum.xda-developers.com/oneplus-7t/how-to/oneplus-7t-10-0-8-magisk-patched-boot-t4055279

Verry food treat. One place for all versions

Flashing issues
Kondi_cool said:
Here You have for EUROPA
https://forum.xda-developers.com/oneplus-7t/how-to/oneplus-7t-10-0-8-magisk-patched-boot-t4055279
Click to expand...
Click to collapse
Hi,
I flashed the european patched boot.img and my phone keeps booting up into the home screen before going blank. It then will boot into fastboot and when i try reboot the phone the same thing happens again. It's also happened after i flashed the stock image to return the phone to normal. What should i do to try fix this?
TIA

Flashing Issues
I flashed Magisk patched boot (global) 10.0.8 for my OP7T (10.0.8 HD65AA) and all it's good. Well done

I am having problem with ota
It sas "root detected full package will be downloaden for install"
I did restore image in magisk.
How to proceed now

karayemis said:
I am having problem with ota
It sas "root detected full package will be downloaden for install"
I did restore image in magisk.
How to proceed now
Click to expand...
Click to collapse
It's not a problem, that's how it should work.
Just follow below for OTAs
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Sent from my OnePlus7TPro using XDA Labs

Hello, Sorry for the noobish question.
i'm about to use msm tool to restore my os to OOS 10.0.4(non-rooted). Can i directly flash v10.3.1 (magisk patched) on 10.0.4(non-rooted)?

I'm using Magisk Canary (custom channel: ht_tps://dgadelha.xyz/public/magisk.json) and it looks like it has no Option to perform: "Magisk Manager → Uninstall → Restore Images". Could you please advise on how to proceed from there?
Many thanks in advance

Lossyx said:
It's not a problem, that's how it should work.
Just follow below for OTAs
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So i have to download en install full oackage after restore image and then without booting install inactive slot ota?
Will this erase anything?
Thanks

karayemis said:
So i have to download en install full oackage after restore image and then without booting install inactive slot ota?
Will this erase anything?
Thanks
Click to expand...
Click to collapse
Yes, follow the instructions in the link I sent you.
And of course, it won't erase anything. I would have given you an heads up if it did.
Sent from my OnePlus7TPro using XDA Labs

the code is "fastboot flash boot whateverthenameis.img".

Tried to flash it, but i got the error "cannot load magisk_patched"...
Any ideas?
Thx a lot for your work!!!
Edit: Solved, it worked after rename the img.file to a shorter name...

Question Locked bootloader while in download mode boot loop

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.