Related
Hello, I made a mistake and I format system and recovery in my zenfone ze500cl. I tried to update the firmware via fastboot but it tell me:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Without a recovery for me its impossible to flash the firmware zip , i need to flash the stock recovery to flash the zip from the sd card. Please help me!!!!
It''s work for me and save my zenfone 2 e att
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
****990 said:
It''s work for me and save my zenfone 2 e att
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
Click to expand...
Click to collapse
It doesn't help me, one of the link is broken. I need to flash a recovery, but all the twrp , cwm i found don't flash. Does anyone has the stock recovery.img? ?
waltermaffy said:
It doesn't help me, one of the link is broken. I need to flash a recovery, but all the twrp , cwm i found don't flash. Does anyone has the stock recovery.img? ?
Click to expand...
Click to collapse
[news]
It's works!!!!! Thank you very much! You save my phone :good:
Sent from my zf2e[ze500cl] using Tapatalk
You welcome....
I have zenfone 2e Z00D with WW firmware.
The recovery launcher didn't work for me.
It completes the process but nothing happens, no recovery loads.
Do I need stock recovery?
@Ak-0 First just unlock your bootloader, then flash twrp, then cm.... Here all the links you'll need http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my LG-D415 using XDA-Developers mobile app
robot_head said:
@Ak-0 First just unlock your bootloader, then flash twrp, then cm.... Here all the links you'll need http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my LG-D415 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried unlocking my bootloader first, but nothing changes. The boot screen stays the same and doesn't turn white. It's the Intel boot screen.
I tried to downgrade to MM fron nougat using autoscript and and phone is showing badkey on a blank screen. How to fix it and revive my phone?
Have you tried to use Odin to try to get to PB1?
Sent from my XT1650 using Tapatalk
SoccerRef12 said:
Have you tried to use Odin to try to get to PB1?
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
http://www.stechguide.com/downgrade-moto-z-play-from-android-nougat-to-marshmallow/
i follwed this thread
Sorry. Odin is for Samsung. Wrong thread. ?
Sent from my XT1650 using Tapatalk
leoavi94 said:
http://www.stechguide.com/downgrade-moto-z-play-from-android-nougat-to-marshmallow/
i follwed this thread
Click to expand...
Click to collapse
Flash stock boot.img in fastboot
Via command
Fastboot flash boot boot.img ..
prins29 said:
Flash stock boot.img in fastboot
Via command
Fastboot flash boot boot.img ..
Click to expand...
Click to collapse
sir can u please elaborate?
prins29 said:
Flash stock boot.img in fastboot
Via command
Fastboot flash boot boot.img ..
Click to expand...
Click to collapse
sir now its showing N/A. What to do next?
leoavi94 said:
sir now its showing N/A. What to do next?
Click to expand...
Click to collapse
After showing N/A didn't the device boot in to system?
If not .. than you have to flash the whole firmware again.
prins29 said:
After showing N/A didn't the device boot in to system?
If not .. than you have to flash the whole firmware again.
Click to expand...
Click to collapse
the nougat firmware hat i downloaded has 3 folders
config
meta
system
boot.img
whereas when i search on google how to flash stock firmware , they have a lot of files to execute command with.
leoavi94 said:
the nougat firmware hat i downloaded has 3 folders
config
meta
system
boot.img
whereas when i search on google how to flash stock firmware , they have a lot of files to execute command with.
Click to expand...
Click to collapse
Flash mashmallow firmware than update to nougat via OTA
prins29 said:
Flash mashmallow firmware than update to nougat via OTA
Click to expand...
Click to collapse
sir shoukd i use the instructions mentioned here?
http://www.stechguide.com/downgrade-moto-z-play-from-android-nougat-to-marshmallow/
leoavi94 said:
sir shoukd i use the instructions mentioned here?
http://www.stechguide.com/downgrade-moto-z-play-from-android-nougat-to-marshmallow/
Click to expand...
Click to collapse
i tried the steps again but its showing N/a again.
Use official Motorola instructions here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Or the instructions here under the "Unbricking / Stock" section: https://forum.xda-developers.com/moto-z-play/how-to/howto-moto-z-play-unlock-root-t3508547
This one has instructions too: https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
felipevsw said:
Use official Motorola instructions here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Or the instructions here under the "Unbricking / Stock" section: https://forum.xda-developers.com/moto-z-play/how-to/howto-moto-z-play-unlock-root-t3508547
This one has instructions too: https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
Click to expand...
Click to collapse
Thank you very much. You are a life saver. I installed that russian firmware and at least now it has revived.
whenevr i restart my device it shows that your device is unlocked and cant be trusted
id: bad key
cant this screen be removed?
leoavi94 said:
Thank you very much. You are a life saver. I installed that russian firmware and at least now it has revived.
whenevr i restart my device it shows that your device is unlocked and cant be trusted
id: bad key
cant this screen be removed?
Click to expand...
Click to collapse
Yes. You need to install a custom boot logo with the following command:
Code:
fastboot flash logo <FILE>.bin
You can get boot logos for our device here:
- https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
- https://forum.xda-developers.com/moto-z-play/themes/bootlogo-powered-lineage-t3575133
felipevsw said:
Yes. You need to install a custom boot logo with the following command:
Code:
fastboot flash logo <FILE>.bin
You can get boot logos for our device here:
- https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
- https://forum.xda-developers.com/moto-z-play/themes/bootlogo-powered-lineage-t3575133
Click to expand...
Click to collapse
Thank you. I have 2 question, if you could answer these that would be of great help.
1) is there any way to bring the phone back in warranty?
2) I installed the russian firmware and if i wish to install Indian firmware, any idea where can i get it? i searched almost everywhere but couldnt find it.
version is npn25.137-15-2
First of all, this thread is in the wrong section. This section is for development only, and you're not developing anything here. Move this thread to the General Q&A section.
Second, you didn't read the post I linked. The second link has 2 links for repositories with many factory images. Since I'm in a good mood, here's one with many choices for you: https://mirrors.lolinet.com/firmware/moto/addison/official/
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
vibraniumdroid said:
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
Click to expand...
Click to collapse
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
ROM_HUNTER said:
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
Click to expand...
Click to collapse
does not work
vibraniumdroid said:
does not work
Click to expand...
Click to collapse
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
flashallthetime said:
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
Click to expand...
Click to collapse
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
vibraniumdroid said:
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
Click to expand...
Click to collapse
Hard bricked for sure
flashallthetime said:
Hard bricked for sure
Click to expand...
Click to collapse
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
vibraniumdroid said:
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
Click to expand...
Click to collapse
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
so you are sure that it is impossible to make a flashable zip of bootloader. Maybe it is just my computer I'll try booting of linux on usb and then see if fastboot can see it.
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
how do you fix a hardbrick?
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
flashallthetime said:
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Have you tried using these albus (Z2 Play) blank flashes as mentioned here to repair your bootloader? https://forum.xda-developers.com/showpost.php?p=73402033&postcount=181
https://forum.xda-developers.com/showpost.php?p=73411048&postcount=206
These may hopefully get your device to the point where it's recognised in fastboot and you can then flash the stock ROM via fastboot.
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
You don't. That's why it's called a hard brick.
flashallthetime said:
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
Click to expand...
Click to collapse
booted of linux from a usb and that worked 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.
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.