Related
Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api
would i be able to just flash this if i wanted to with twrp. just curious.
Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
dang. okay
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
do we just flash in twrp? Thank you by the way
No it's a stock ota you have to use HTC recovery.
rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.
Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.
bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted
Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.
bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.
Radio
Any chance someone can please post a flashable zip with the new t-mo radio?
Where would I get the stock recovery for this fw and update. I want to root but keep my ota
Now CM appear to have disabled their links to official roms, updates & kernels for older builds, I've mirrored them all on AndroidFileHost and put the links in one post so that they're easy to find.
There are different files for each ROM: signed fastboot flashable zips, signed zips, OTA incremental update zips., boot-debuggable images and stock recovery images.
Signed fastboot flashable zips: These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot. Due to changes in bootloader, don't use them to upgrade from CM 11S to CM 12S or downgrade from CM 12S to CM 11S.
Signed zips: Normal recovery-flashable zips that contains just the system and kernel (they won't overwrite your data partition).
OTA incremental update zips: These are recovery-flashable zips that update your rom to a newer version. To check which version you are running, look at the ro.build.version.incremental line in your /system/build.prop file and then update incrementally.
Boot-debuggable images: These are boot images (kernels) that enable adb root and the developer menu options. To be flashed via fastboot.
Stock recovery images: These are stock recovery images which are recommended for applying OTA incremental update zips. To be flashed via fastboot.
NOTE: Both Yureka & Yureka Plus share same firmware, but don't use pre-cm-12.0-YNG1TAS34J builds on Yureka Plus - the device will be soft-bricked!
Signed fastboot flashable zips
cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS34J-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
cm-11.0-XNPH05Q-tomato-signed-fastboot.zip
cm-11.0-XNPH52O-tomato-signed-fastboot.zip
Signed zips
cm-12.1-YOG4PAS8A4-tomato-signed-224c88c4ef.zip
cm-12.1-YOG4PAS3JM-tomato-signed.zip
cm-12.0-YNG1TAS34J-tomato-signed.zip
cm-12.0-YNG1TAS1K0-tomato-signed.zip
cm-12.0-YNG1TAS0W0-tomato-signed.zip
cm-11.0-XNPH05Q-tomato-signed.zip
OTA incremental update zips
YOG4PAS8A4 from YOG4PAS3JM: cm-tomato-04864afef4-to-5242dd42b2-signed.zip
YOG4PAS6ZA from YOG4PAS3JM: cm-tomato-04864afef4-to-f758a6e288-signed.zip
YOG4PAS3JM from YNG1TAS34J: cm-tomato-c991cd279d-to-04864afef4-signed.zip
YOG4PAS3JM from YNG1TAS1K0: cm-tomato-00b2e333e8-to-04864afef4-signed.zip
YNG1TAS34J from YNG1TAS1K0: cm-tomato-00b2e333e8-to-c991cd279d-signed.zip
YNG1TAS1K0 from YNG1TAS0W0: cm-tomato-56deeca328-to-00b2e333e8-signed.zip
XNPH05Q from XNPH52O: cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip
Boot-debuggable images
cm-12.1-YOG4PAS8A4-tomato-boot-debuggable-8bc066a691.img
cm-12.1-YOG4PAS3JM-tomato-boot-debuggable.img
cm-12.0-YNG1TAS34J-tomato-boot-debuggable.img
cm-12.0-YNG1TAS1K0-tomato-boot-debuggable.img
cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
cm-11.0-XNPH05Q-tomato-boot-debuggable.img
cm-11.0-XNPH52O-tomato-boot-debuggable.img
Stock recovery images
cm-12.1-YOG4PAS8A4-tomato-recovery.img
cm-12.1-YOG4PAS3JM-tomato-recovery.img
cm-12.0-YNG1TAS34J-tomato-recovery.img
cm-12.0-YNG1TAS1K0-tomato-recovery.img
cm-12.0-YNG1TAS0W0-tomato-recovery.img
cm-11.0-XNPH05Q-tomato-recovery.img
cm-11.0-XNPH52O-tomato-recovery.img
Credits
@Spannaa for the inspiration.
@AndroidFileHost for the hosting.
YU for the device.
Cyanogen for making the OS.
Reserved for future.
First post updated; added YNG1TAS1K0 build.
Can't flash the YNG1TAS1K0 from YNG1TAS0W0 ota update,
Installations error on custom recovery and stock recovery too
how do i verify that latest S1k0 fastboot update is authentic sir??
you said that they have disabled the updates so any way to verify?
sal_rc said:
Can't flash the YNG1TAS1K0 from YNG1TAS0W0 ota update,
Installations error on custom recovery and stock recovery too
Click to expand...
Click to collapse
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
milav said:
how do i verify that latest S1k0 fastboot update is authentic sir??
you said that they have disabled the updates so any way to verify?
Click to expand...
Click to collapse
I haven't told that CM has disabled the updates; instead they periodically removes old updates. Files related to YNG1TAS1K0 are directly grabbed from CM server, so they are 100% authentic.
Titokhan said:
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
Should I do factory reset too afterwards?
Click to expand...
Click to collapse
@sal_rc
Not mandatory, but you can.
Titokhan said:
@sal_rc
Not mandatory, but you can.
Click to expand...
Click to collapse
my bootloader will be locked again? Right?
@sal_rc
No, flashing OTA will not re-lock the bootloader.
Titokhan said:
@sal_rc
No, flashing OTA will not re-lock the bootloader.
Click to expand...
Click to collapse
I was afraid I'd have to do it all over again
Thanks anyways
Titokhan said:
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
I haven't told that CM has disabled the updates; instead they periodically removes old updates. Files related to YNG1TAS1K0 are directly grabbed from CM server, so they are 100% authentic.
Click to expand...
Click to collapse
thnks bro as being latest update i request you to provide fastboot link direct from cm server old links can be on androidfilehost thats good
thnks for links btw dnlding latest fastboot files now
cheers
What are these bootable image??
I am in twrp recovery with sandy kernel in lollipop 5... Can you please tell how to go back to stock recovery for the updating latest ota. Thanks in advance
Titokhan said:
Reserved for future.
Click to expand...
Click to collapse
hey bro i am on 5.0.2.i want to flash stock kernel can you please tell me which one should i flash ? and which process should i follow ?
using fastboot but what is the command ?
@m_rajaganesh
Depends on the build version; it would be better to install latest stock recovery via fastboot & then flash the full OTA manually.
@ashish_zarekar
Tell me the exact build number. Choose the appropriate one & flash:
Code:
fastboot -i 0x1ebf flash boot boot.img
Titokhan said:
@m_rajaganesh
Depends on the build version; it would be better to install latest stock recovery via fastboot & then flash the full OTA manually.
@ashish_zarekar
Tell me the exact build number. Choose the appropriate one & flash:
Code:
fastboot -i 0x1ebf flash boot boot.img
Click to expand...
Click to collapse
build number is "LRX22G"
cyanogen os version "12.0-YNG1TAS1K0".
ashish_zarekar said:
build number is "LRX22G"
cyanogen os version "12.0-YNG1TAS1K0".
Click to expand...
Click to collapse
Then download cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip, extract boot.img from it & flash.
Titokhan said:
Then download cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip, extract boot.img from it & flash.
Click to expand...
Click to collapse
can i download direct boot.img from your list and flash it via fastboot ?
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.
Hello everyone I need help
How I install gsi ROM like hydrogen oxygen
In mi a2 lite daisy I have twrp but now I have miui ROM
Can I flash without reflash firmware in pc ? More options like a flash vendor boot or what thanks have a nice day my slot is A/B but boot set in (B)
robin_vilensky_ said:
Hello everyone I need help
How I install gsi ROM like hydrogen oxygen
In mi a2 lite daisy I have twrp but now I have miui ROM
Can I flash without reflash firmware in pc ? More options like a flash vendor boot or what thanks have a nice day my slot is A/B but boot set in (B)
Click to expand...
Click to collapse
First of all many users are confusing rom with firmware, the whole rom is flashed through fastboot or EDL (although OTA updates could be flashed through recovery) while the firmware is a small set of files that can be flashed through recovery in form of zips.
What I did to boot many GSIs out there? although any of them satisfied due to many bugs comparing with the developed custom roms for Daisy.
- Go to recovery and backup just the boot partition.
- Then format data.
- Then advanced wipe; data, system and cache/ART Dalvik cache.
- Transfer GSI to your device using any convenient method (transferring file or copying to your external SDcard)
- Flash the GSI on System Image partition.
- Restore the boot partition.
- Flash only the firmware zip (version may vary) Never I needed to flash the whole rom.
- Flash DFE.
- Switch to the other slot and reboot.
- If device won´t boot it could be required to flash a proper vendor version through fastboot. Pay attention to the slot that you flashed before to target the same slot if you need to flash this partition.
With this method I could boot to OneUI, Moto, nubia, ZenUI, HydrogenOS and Xperia while I can´t on ZUIOS and didn´t try with FlymeOS
Can I flash firmware via twrp ? Thanks
robin_vilensky_ said:
Can I flash firmware via twrp ? Thanks
Click to expand...
Click to collapse
Yes, this is why they´re done this way, to updates just some essential partitions, there is a thread here where you can download them.
SubwayChamp said:
Yes, this is why they´re done this way, to updates just some essential partitions, there is a thread here where you can download them.
Click to expand...
Click to collapse
,
Thank you ! You can send me link for firmware zip for twrp ? Thanks and it's not removed the twrp?
robin_vilensky_ said:
,
Thank you ! You can send me link for firmware zip for twrp ? Thanks and it's not removed the twrp?
Click to expand...
Click to collapse
I'm now far from a pc, under Guides section you can find it.
Doing this way you won't need to reflash TeamWin.
SubwayChamp said:
I'm now far from a pc, under Guides section you can find it.
Doing this way you won't need to reflash TeamWin.
Click to expand...
Click to collapse
From here it's okay ? https://c.mi.com/oc/miuidownload/detail?device=1700354 for twrp
SubwayChamp said:
I'm now far from a pc, under Guides section you can find it.
Doing this way you won't need to reflash TeamWin.
Click to expand...
Click to collapse
Thank you bro iam fine thanks for helping
robin_vilensky_ said:
From here it's okay ? https://c.mi.com/oc/miuidownload/detail?device=1700354 for twrp
Click to expand...
Click to collapse
I´m back, the link is to download the whole rom.
Remember the difference between rom and firmware that I mentioned before?.
This is the link for firmwares https://forum.xda-developers.com/mi-a2-lite/how-to/firmware-updates-daisy-t3975879
Anyway you´ll need sometimes the whole rom and sometimes it´ll be enough flashing just the firmware.
SubwayChamp said:
I´m back, the link is to download the whole rom.
Remember the difference between rom and firmware that I mentioned before?.
This is the link for firmwares https://forum.xda-developers.com/mi-a2-lite/how-to/firmware-updates-daisy-t3975879
Anyway you´ll need sometimes the whole rom and sometimes it´ll be enough flashing just the firmware.
Click to expand...
Click to collapse
Thanks for help bro big respect
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.