i was rooted with twrp custom recovery installed. i wanted to unroot my phone so i flash the recovery and locked he bootloader again and now im trying to sideload the latest oos to my phone but it keeps failing. everytime i plug my device in i get a popup saying to insatll device drivers and when i let it do it abd its successful i still get a sideload failed error. what am i doing wrong?
envious86 said:
i was rooted with twrp custom recovery installed. i wanted to unroot my phone so i flash the recovery and locked he bootloader again and now im trying to sideload the latest oos to my phone but it keeps failing. everytime i plug my device in i get a popup saying to insatll device drivers and when i let it do it abd its successful i still get a sideload failed error. what am i doing wrong?
Click to expand...
Click to collapse
- Unlock the BL again
- Flash modded TWRP
- Flash stock OOS rom using TWRP (TWRP will be replaced by stock recovery!)
-Check if everything wroks as it should
-Relock the BL
-DONE
LS.xD said:
- Unlock the BL again
- Flash modded TWRP
- Flash stock OOS rom using TWRP (TWRP will be replaced by stock recovery!)
-Check if everything wroks as it should
-Relock the BL
-DONE
Click to expand...
Click to collapse
probably a stupid question but how do i unlock the bootloader again?
envious86 said:
probably a stupid question but how do i unlock the bootloader again?
Click to expand...
Click to collapse
Just like the time before.
fastboot oem unlock
LS.xD said:
Just like the time before.
fastboot oem unlock
Click to expand...
Click to collapse
OK I'll try thanks.
hi,
sorry if i am asking this quesiton in the wrong category
so i have a a520f that had frp, i succeeded to unlock the frp but for some reason i don't have an imei
and when trying to flash it, it can only flash without the BL file in odin
if i flash any unnofficial file (twrp, root stuff) it gets stuck in bootloop and can't boot in recovery mode
i have a z3x box and if manage to root it i would be able to restore its imei
thank you in advance for yout help
Hi.
OEM of my device is lock.
I can flash twrp image but I cant open recovery mode.
Can u help me?
To answer your question in the title yes, any software you wish to install on a locked phone must be signed and twrp and custom roms are not.
Hello ,i have a problem whit my a5 2017
I have updated my phone to latest version of oreo , before doing this i disabled oem unlock but i got twpr installed in my phone .
Now after the oreo update the phone is a brick , i have no command screen and if i try to enter recovery i have this message :
#fail to open recovery_(cause no such file or directory)#
Now i am on the latest version of bootloader , oem locked and frp lock active whit an infinite bootlop.
I tried to extract recovery file of latest oreo update whit cmd l4z command , success , i flashed it but still no recovery
If i try to flash twpr i get an error : custom binary locked by frp lock on download mode screen
Adb does not recognize my phone i can't unlock oem from adb
I tried to install stock firmwares a lot of times but the problem still persist
What can i do?
gd9719 said:
Hello ,i have a problem whit my a5 2017
I have updated my phone to latest version of oreo , before doing this i disabled oem unlock but i got twpr installed in my phone .
Now after the oreo update the phone is a brick , i have no command screen and if i try to enter recovery i have this message :
#fail to open recovery_(cause no such file or directory)#
Now i am on the latest version of bootloader , oem locked and frp lock active whit an infinite bootlop.
I tried to extract recovery file of latest oreo update whit cmd l4z command , success , i flashed it but still no recovery
If i try to flash twpr i get an error : custom binary locked by frp lock on download mode screen
Adb does not recognize my phone i can't unlock oem from adb
I tried to install stock firmwares a lot of times but the problem still persist
What can i do?
Click to expand...
Click to collapse
I suggest try to download another stock rom and try again with it.
matkali said:
I suggest try to download another stock rom and try again with it.
Click to expand...
Click to collapse
i have done this 13 times and the problem still.
gd9719 said:
i have done this 13 times and the problem still.
Click to expand...
Click to collapse
Download from here:
https://www.sammobile.com/samsung/galaxy-a5-2017/firmware/#SM-A520F
matkali said:
I suggest try to download another stock rom and try again with it.
Click to expand...
Click to collapse
I finally booted up my phone and unlocked oem
but network is not working , everytime i update my firmware recovery is missing and i have to install recovery manually (only twpr work , stock recovery not working cause of bootloader)
i have tried to unpack recovery from lz4 stoc files ( latest update) create a tar whit 7 zip and flash it , flash success but still no recovery.
after erasing screen after update i have no command whit failed to load recovery no such file or directory
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.