Related
so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do
ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.
echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.
ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?
Hi. I have a A5 2017. I recently changed from the Russian 7.0 to the German Rom and the baseband and also the imei disappeared. I've got ROMs from all the sites and I'm still the same. Any solution?
I can´t have root. I can not install twrp. I have the error only official released binaries ...
PS: I can not change the bootloader. I have the error sw rev ...
I can only flash Ap.The 4 files together I can not
I can install the 4 files + pit but at the moment of starting the mobile it takes me to the recovery and later says things like ...:
- / efs invalid argument
-dm-verity fail ...
Any solution? I'm desperate
deleted
DaniPS2002 said:
Hi. I have a A5 2017. I recently changed from the Russian 7.0 to the German Rom and the baseband and also the imei disappeared. I've got ROMs from all the sites and I'm still the same. Any solution?
I can´t have root. I can not install twrp. I have the error only official released binaries ...
PS: I can not change the bootloader. I have the error sw rev ...
I can only flash Ap.The 4 files together I can not
I can install the 4 files + pit but at the moment of starting the mobile it takes me to the recovery and later says things like ...:
- / efs invalid argument
-dm-verity fail ...
Any solution? I'm desperate
Click to expand...
Click to collapse
The issue seems to be a combination of incorrect firmware and bad /Efs partition..
The dm-verity issue is because you haven't flashed the correct firmware.
The EFS error may also be erroneous, but if you've been messing with the wrong firmware and PIT files it's possible you've caused this error by messing up your partition structure and corrupting the EFS partition.
You really need to obtain the correct firmware for your region and possibly flash it with the PIT file if you've messed up your partition structure.
flozge said:
Hi try to root your phone with Kingroot and install TWRP via TWRP app
EDIT: Have you enabled OEM Unlock in Developer Options?
Click to expand...
Click to collapse
Hello! Thanks for your answer. I'm on Android 7.0 and I remember that kingroot no longer worked. I have the oem unlock option enabled. Now my phone has turned on but the wifi and fingerprints work partially. The system is unusable after 15 minutes of being used. It is progressively slowing down
ashyx said:
The issue seems to be a combination of incorrect firmware and bad /Efs partition..
The dm-verity issue is because you haven't flashed the correct firmware.
The EFS error may also be erroneous, but if you've been messing with the wrong firmware and PIT files it's possible you've caused this error by messing up your partition structure and corrupting the EFS partition.
You really need to obtain the correct firmware for your region and possibly flash it with the PIT file if you've messed up your partition structure.
Click to expand...
Click to collapse
Hi. Thank you very much for your help. My phone is an Italian version and I decided to change the firmware to the Russian version and since then the phone has generated all those errors. I would appreciate very much if you could give me a solution to this problem. Thank you
DaniPS2002 said:
Hi. Thank you very much for your help. My phone is an Italian version and I decided to change the firmware to the Russian version and since then the phone has generated all those errors. I would appreciate very much if you could give me a solution to this problem. Thank you
Click to expand...
Click to collapse
Which Italian firmware are you trying to flash?
ashyx said:
Which Italian firmware are you trying to flash?
Click to expand...
Click to collapse
This. A520FXXU2BQH4/A520FVFG2BQH2 on 7.0 3 aug
DaniPS2002 said:
This. A520FXXU2BQH4/A520FVFG2BQH2 on 7.0 3 aug
Click to expand...
Click to collapse
Can you post a screen shot of the device screen after flashing the whole firmware?
ashyx said:
Can you post a screen shot of the device screen after flashing the whole firmware?
Click to expand...
Click to collapse
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
DaniPS2002 said:
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
Click to expand...
Click to collapse
Please send me the efs.tar
flozge said:
Please send me the efs.tar
Click to expand...
Click to collapse
This is the efs. Try it
EDIT:Flash in CP
DaniPS2002 said:
This is the efs. Try it
EDIT:Flash in CP
Click to expand...
Click to collapse
Thanks
DaniPS2002 said:
Let me see you. The phone now I have it working. That is, I had to install an generic a520f efs.tar for odin so that the system could start(this efs folder is empty obviously) Now what I'm looking for is how to restore the imei and in the process remove system crashes * wifi forget passwords, fingerprints do not work ... and the system does not work or does not respond within 15 minutes. The efs.tar that I have gotten makes verifying the DM verity successful only the first time. Already the second time you access the recovey I have the error dm verity error. I feel the misunderstanding
Click to expand...
Click to collapse
Guessing you made it work with only flashing the ap, and you still have the sw rev error, what you can do is download a XXUx being the last x the number of the device on the error, for instance, if the error is "Device 4 Binary 3" You want to flash an XXU4.
Good luck.
@DaniPS2002 I am waiting for a z3x box 29 crack when I have found one I tell you
flozge said:
@DaniPS2002 I am waiting for a z3x box 29 crack when I have found one I tell you
Click to expand...
Click to collapse
Perfect! Many thanks! Is there news about version 29? It is precisely the version that adds support to our model
DaniPS2002 said:
Perfect! Many thanks! Is there news about version 29? It is precisely the version that adds support to our model
Click to expand...
Click to collapse
It gives already 30 but our device is since 29 supported
flozge said:
It gives already 30 but our device is since 29 supported
Click to expand...
Click to collapse
News mate?
DaniPS2002 said:
News mate?
Click to expand...
Click to collapse
No but I think 3weeks or less is a crack available
Can someone give me an backup of the efs partiton with twrp of a520f please?
no need efs backup, since it is stored anywhere on stock rom.
if u get it, so you are good to go with odin.
Hey, recently I booted up my phone and it said custom binary locked by frp lock, or something along those lines, since then I came a lot further/closer to fixing it. As now when I boot it up says: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
When i try to download/reflash new software it fails because it's blocked by FRP lock, anyway to fix this?
Thanks in advance.
Achlyss said:
Hey, recently I booted up my phone and it said custom binary locked by frp lock, or something along those lines, since then I came a lot further/closer to fixing it. As now when I boot it up says: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
When i try to download/reflash new software it fails because it's blocked by FRP lock, anyway to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Can u flash original firmware via odin?
FaisalR29 said:
Can u flash original firmware via odin?
Click to expand...
Click to collapse
No, because I get blocked by the frp lock
Extract the firmware with a different archiver.
Ensure the download hasn't been interrupted and download it with something else.
Otherwise, the firmware might actually not be original. It has to be a stock touchwiz/samsung experience rom to pass FRP (in Odin). Not a custom rom.
Bryan48765 said:
Extract the firmware with a different archiver.
Ensure the download hasn't been interrupted and download it with something else.
Otherwise, the firmware might actually not be original. It has to be a stock touchwiz/samsung experience rom to pass FRP (in Odin). Not a custom rom.
Click to expand...
Click to collapse
Hmm, it could be that, but do you have any idea on where to get stock firmware with speeds higher than 15 Kbps
Achlyss said:
Hmm, it could be that, but do you have any idea on where to get stock firmware with speeds higher than 15 Kbps
Click to expand...
Click to collapse
Even though 15 is written, actual speeds should be much higher than 15 and resumable.
Bryan48765 said:
Even though 15 is written, actual speeds should be much higher than 15 and resumable.
Click to expand...
Click to collapse
I just found another way to download the firmware, and it worked! Thank you so much, although now i don't have a proper excuse to buy the OnePlus 6T
Achlyss said:
I just found another way to download the firmware, and it worked! Thank you so much, although now i don't have a proper excuse to buy the OnePlus 6T
Click to expand...
Click to collapse
I have same problem bro... please help me how you fixed it?
Ulic said:
I have same problem bro... please help me how you fixed it?
Click to expand...
Click to collapse
Hey man, i just downloaded the official firmware, and flashed it regurarly through odin, you have to make sure the firmware is stock, otherwise it will not work.
Hey, could you tell me where you downloaded the firmware faster?
Hifty said:
Hey, could you tell me where you downloaded the firmware faster?
Click to expand...
Click to collapse
I used this tool https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 even though it says its deprecated it still worked fine for me.
Updato.com
Tried everything. Searched through the webs for past couple of days. Everything failed.
Majority of articles are from times of Ancient Rome. None work and are outdated.
Reflashed stock with nand erase and pit file. Checked and failed.
Tried root related solutions? Checked and failed.
Searched modem file. Failed.
Downgrade to prev version? No longer plausible. Due to BIT.
I flashed and reflashed with odin numerious of times. Nothing. Useless. Absolutely useless.
did u solve it?
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Mighty_Rearranger said:
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Click to expand...
Click to collapse
any luck?
dronkit said:
any luck?
Click to expand...
Click to collapse
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
applesucksLmao said:
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
Click to expand...
Click to collapse
You mean like flashing an older modem? How can I do that?
Mighty_Rearranger said:
You mean like flashing an older modem? How can I do that?
Click to expand...
Click to collapse
its the CP file in odin
try flashing one from may or august.. don't try november or newer
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Mighty_Rearranger said:
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Click to expand...
Click to collapse
Could you flash it with a magisk modified rom?
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
OK I tried doing that and now phone is bootlooping with secure check fail md1img error, that's the anti-downgrade thing complaining. No luck down the downgrade hallway.
I think the only option is to wait for a possible solution from the Magisk people or check if a future update somehow fixes the problem.
Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
how do you check them from recovery? I was able to see them once after a botched flashing, entering download mode, there was a "show barcode" option or something like that.
I have read in an older thread in this forum, some guy solved it by downgrading, but to a version which is impossible to downgrade to for us, because our phones already came with the AUJ4 firm, and acannot go back.
applesucksLmao said:
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
Click to expand...
Click to collapse
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
dronkit said:
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
Click to expand...
Click to collapse
if someone manages to create twrp for a32 4g maybe there's a way back
applesucksLmao said:
if someone manages to create twrp for a32 4g maybe there's a way back
Click to expand...
Click to collapse
TWRP lets you bypass the binary version check?
Mighty_Rearranger said:
TWRP lets you bypass the binary version check?
Click to expand...
Click to collapse
i don't know probably, and we could get a backup from someone with a not fricked phone and edit it to our imeis
Hello. I am Japanese. This is my first time to start a thread on XDA, so I don't know a lot of things, but please help me.
I am using the Korean version of Zfold3 (SM-F926N).
I would like to write the Singapore version of SM-F926B ROM on it.
I have tried using Odin, but I get a mysterious error and cannot write it.
Is there any good way to do this?
Let me tell you a way, but I must tell you, after the F926N is unlocked, you can't use the camera. The specific steps are: swipe the latest official F926N, unlock the bl and kg locks, and then place the latest AP and CSC of the F926B in the AP and CSC items of odin, at the same time, place vbmeta in the userdata, and then flash these
You can download vbmeta at xda
Gadgelogger said:
Hello. I am Japanese. This is my first time to start a thread on XDA, so I don't know a lot of things, but please help me.
I am using the Korean version of Zfold3 (SM-F926N).
I would like to write the Singapore version of SM-F926B ROM on it.
I have tried using Odin, but I get a mysterious error and cannot write it.
Is there any good way to do this?
Click to expand...
Click to collapse
hi friend, did you succeed ?
zwenchao_1989 said:
Let me tell you a way, but I must tell you, after the F926N is unlocked, you can't use the camera. The specific steps are: swipe the latest official F926N, unlock the bl and kg locks, and then place the latest AP and CSC of the F926B in the AP and CSC items of odin, at the same time, place vbmeta in the userdata, stumble guys and then flash these
Click to expand...
Click to collapse
I tried loading vbmeta and doing it the way you said. Everything is fine. Thanks for your sharing. It's really helpful to me
vhsslime said:
I tried loading vbmeta and doing it the way you said. Everything is fine. Thanks for your sharing. It's really helpful to me
Click to expand...
Click to collapse
hope you succeed, I just want to confirm whether the camera function or not after the flashing, please remember to share your experience when you finish, thank you so much.
freeman1007 said:
hope you succeed, I just want to confirm whether the camera function or not after the flashing, please remember to share your experience when you finish, thank you so much.
Click to expand...
Click to collapse
Camera does not work after unlocking