Related
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
plainbum said:
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
Click to expand...
Click to collapse
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
quinciebee said:
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
Click to expand...
Click to collapse
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
plainbum said:
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
Click to expand...
Click to collapse
How did you flash CM13, and did you flash the 09/19 build?
quinciebee said:
How did you flash CM13, and did you flash the 09/19 build?
Click to expand...
Click to collapse
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
plainbum said:
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
Click to expand...
Click to collapse
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Delete
quinciebee said:
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Click to expand...
Click to collapse
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
plainbum said:
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
Click to expand...
Click to collapse
Is the BOG5 firmware stock? If so, you shouldn't have flashed it. If you still have TWRP and root, take these steps to clean flash to CM13.
1. Boot to TWRP, wipe all but your External Storage (SD Card)
2. Flash CM13 09/19 zip
3. Flash the boot image from CM13 07/24
(Click on install image, select the boot.img file, you will then see two choices: boot and recovery, select boot only, then swipe to flash.)
4. Flash gapps and SuperSU zip
5. Reboot
The rapid blinking was happening because you need the boot image from 07/24 in order for the rom to load properly. I'd post the boot image for you, but it exceeds the file size limit. To get the boot image, download the CM13 07/24 build, unzip the file, and extract the boot.img file to your SD card, along with everything else that you want to flash. Let me know if you need me to provide more details on any of the steps.
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
plainbum said:
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
Click to expand...
Click to collapse
What do you see when you try to boot into recovery?
Hi quinciebee,
I posted this before I borked my phone, before you started helping me.
How I got here was I was trying to upgrade the firmware so I could them flash The ne 7.1.1 "EmotionOS"
I was following the instruction here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Specifically where is says:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
It flashed fine and then I installed the EmotionOS and all went well but I could NOT get 4G LTE to work, only 3G.
So I abandoned it and reflashed a backup of the CM 13 I was running since May 25.
I was good on cm13 but I got errors when I was in settings and tried to go into "Security"
Im all god now and I will be trying to get back to 6.0 and then 7.1.1 after my house guests leave.
The phone is running fine in 5.1.1.
THanks again!
https://support.t-mobile.com/docs/DOC-27648
Android Security Updates
Phone Samsung GALAXY Note3
Model SM-N900T
PDA Version N900TUVSFPL1
CSC Version N900TTMBFPL1
PHONE Version N900TUVSFPL1
Region TMB
Country USA (T-Mobile)
Build Date 12.12.2016
Changelist 6005498
OS Lollipop
OS Version 5.0
If anyone tried using CF-root successfully, leave a confirmation below.
I'm interested too if anyone flashes please report back asap. Doesn't seem like much seeing as the rom is still 5.0 not 5.1 or 6 so more than likely its just 300 mb of "security updates".
Just an update: the new PL1 firmware can be rooted by CF-auto-root.
One more update: the android security patch level is still 2016-09-01, the same as the SPH3 firmware. Don't know why they say this is an "android security update"in the description.
I thought the android security patch level should be 2016-12-01 since it was built on 2016-12-12.
i couldnt ge the cf-root to work on mine. it says theres a dev error. is there a newer version to use?
bb031577 said:
i couldnt ge the cf-root to work on mine. it says theres a dev error. is there a newer version to use?
Click to expand...
Click to collapse
Odin flash the cf-root tar file.
googlephone said:
Odin flash the cf-root tar file.
Click to expand...
Click to collapse
I did that 3times and it keeps giving me the same error message. I think I'm using the wrong tar file. I'm using the one for n900TTMBFOB6. Is there a different one for N900TTMBFPL1?
bb031577 said:
I did that 3times and it keeps giving me the same error message. I think I'm using the wrong tar file. I'm using the one for n900TTMBFOB6. Is there a different one for N900TTMBFPL1?
Click to expand...
Click to collapse
Should be the same.
I downloaded here:https://download.chainfire.eu/354/CF-Root
Unzip the file and Odin flash the tar.md5 file only, not the zip file.
THANK YOU VERY MUCH IT WORKED PERFECTLY. It must have been the file i downloaded from before.
Baseband not updaing
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Did anyone try flashing roms through TWRP? if so what do you guys use?
macster2075 said:
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Click to expand...
Click to collapse
The baseband should be PL1 but the android security patch level should still be 2016-09-01.
macster2075 said:
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Click to expand...
Click to collapse
I think that you have to power off the phone and boot into download mode from the power off state. Otherwise, the bootloader and baseband won't update.
frequentc said:
I think that you have to power off the phone and boot into download mode from the power off state. Otherwise, the bootloader and baseband won't update.
Click to expand...
Click to collapse
In order to install the update, I had to get into download mode.
macster2075 said:
In order to install the update, I had to get into download mode.
Click to expand...
Click to collapse
Right.. but it makes a difference if you reboot into download mode (while the phone's still on) or have the phone turned off and then boot directly into download mode (volume-down + home + power).
frequentc said:
Right.. but it makes a difference if you reboot into download mode (while the phone's still on) or have to phone turned off and then boot directly into download mode (volume-down + home + power).
Click to expand...
Click to collapse
Yes.. I had to do that in order to re-root using CF-Root and also to flash the recovery.
Is this ROM based on Android 5.1.1 like others are speculating? If this is just 5.0, I'm saying "Screw Touchwiz", and staying on my AOSP Nougat...
AndroidHacker99 said:
Is this ROM based on Android 5.1.1 like others are speculating? If this is just 5.0, I'm saying "Screw Touchwiz", and staying on my AOSP Nougat...
Click to expand...
Click to collapse
Still 5.0
Is it possible to take only the most update modem (CP) from this?
I am looking to flash the latest modem for Tmo US Note 3.
Maybe flashing via Odin in the CP button?
elyranon said:
Did anyone try flashing roms through TWRP? if so what do you guys use?
Click to expand...
Click to collapse
FlashFIre. Many older posts talk MOP, TWRP, etc. At least with this hardware and firmware, FlashFire is all I use. (Much gratitude to Chainfire.)
hapa8o8 said:
Is it possible to take only the most update modem (CP) from this?
I am looking to flash the latest modem for Tmo US Note 3.
Maybe flashing via Odin in the CP button?
Click to expand...
Click to collapse
Code:
# Install Heimdall and print pit
sudo apt install heimdall
heimdall detect
heimdall print-pit --no-reboot > pit.txt
# Extract binaries from firmware package
head -z -n -1 N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar.md5 > N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar
tar -xvf N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar
Lastly, review the pit file and pick the partitions/files you want to flash. Use the tool you're most comfortable with to do the job.
Many posts refer to the necessity of bootloaders and modems being compatible. So I have not (and would not) flash just the modem. Er, that is unless someone else already did it and reported success.
(PS. Wish *I* could walk out my door and do the Haiku Stairs, a bucket list item.)
Phone was on stock 7.1.1, July 1st patch with TWRP installed. I've wanted to remove TWRP in oreder to receive OTAs so I flashed stock 7.0 boot.img and recovery and now my phone is stuck in bootloader with bad key message when I try to start the phone. Flashing modified logo.bin didn't help. I'm guessing I need correct stock boot.img. Any ideas?
ViperX85 said:
Phone was on stock 7.1.1, July 1st patch with TWRP installed. I've wanted to remove TWRP in oreder to receive OTAs so I flashed stock 7.0 boot.img and recovery and now my phone is stuck in bootloader with bad key message when I try to start the phone. Flashing modified logo.bin didn't help. I'm guessing I need correct stock boot.img. Any ideas?
Click to expand...
Click to collapse
It should be this one, I just have DL it from Motorola 3 days ago
https://androidfilehost.com/?w=profile&uid=529152257862699209
@fablebreton
Hi, what is the difference between these files?
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_1.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_2.zip
shamu17 said:
@fablebreton
Hi, what is the difference between these files?
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_1.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_2.zip
Click to expand...
Click to collapse
It is the same firmware, Second file + third = First file. Just smaller zips
because DL 1,8G sometimes can be difficult, and anyway we have to unzip to flash with fastboot.
But if you have a good internet connexion, just DL the first file, it is the original one, untouched
fablebreton said:
It is the same firmware, Second file + third = First file. Just smaller zips
because DL 1,8G sometimes can be difficult, and anyway we have to unzip to flash with fastboot.
But if you have a good internet connexion, just DL the first file, it is the original one, untouched
Click to expand...
Click to collapse
Thanks for sharing, regards
Hi,
Could anybody extract boot.img from OTA experience 8.0 (Pie) before installing it, so patched boot could be generated by Magisk?
I'm using SATV 2015.
Thanks!
Hi,
attached the (unpatched) boot.img that was in my update.
Shield 2015 16GB
Already patched mine, but did not dare to flash yet, because I am waiting for the backup...
Regards
Chaos
hardwarechaos said:
Hi,
attached the (unpatched) boot.img that was in my update.
Shield 2015 16GB
Already patched mine, but did not dare to flash yet, because I am waiting for the backup...
Regards
Chaos
Click to expand...
Click to collapse
Thanks!
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Hi
sash11 said:
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Click to expand...
Click to collapse
Just hit the same problem with my 2015 :-/
Regards
Chaos
hardwarechaos said:
Hi
Just hit the same problem with my 2015 :-/
Regards
Chaos
Click to expand...
Click to collapse
nVidia did something to protect against rooting. After I flashed stock boot.img and booted into the OS, magisk manager was gone.
https://forums.geforce.com/default/topic/1158216/shield-tv/shield-experience-upgrade-8-0/
Adds rooting feature preventing incorrect images from being flashed to SHIELD
Hi
sash11 said:
nVidia did something to protect against rooting. After I flashed stock boot.img and booted into the OS, magisk manager was gone.
Click to expand...
Click to collapse
can't confirm that. Did basically the same, but the manager is still here.
Edit: Wonder if that is the reason Quote from Nvidia:
... once you get to 8.0 and flash to a new release, we'll verify the image being flashed is compatible with the unit being flashed.
Regards
Chaos
hardwarechaos said:
Hi
can't confirm that. Did basically the same, but the manager is still here.
Edit: Wonder if that is the reason Quote from Nvidia:
... once you get to 8.0 and flash to a new release, we'll verify the image being flashed is compatible with the unit being flashed.
Regards
Chaos
Click to expand...
Click to collapse
It is a system application now. That's why I could not find it in the list of regular apps. Very weird. nVidia must classify it as such and put in into that category.
hardwarechaos said:
Hi
Just hit the same problem with my 2015 :-/
Regards
Chaos
Click to expand...
Click to collapse
Same to me, if I boot with magisk_patched, it keeps stuck at nvidia Logo
Guess we have to wait.
Maybe the boot.img of the developer image, once it is released, might work. Or hopefully someone finds a way too root again.
Regards
Chaos
Hi, just a question
Since Nvidia will release an unlocked Full 8.9 developper OTA (hope it'll be soon) , isn't it better to root that than trying on the official "locked" one ?
As for me, since i started rooting my shield, i always did it that way without problems.
Btw i was thinking of trying the same trick as you did but since i hadn't much time ... Anyway you saved my day, thanks
One last thing for those of you who are dev or android enthousiast, i make use of a fantastic Magisk script called xXx No Limits wich i find very neat.
My questions are
* Could such a script be usefull in case of the Shield ?
[Depending, i guess on wich Magisk modules are compatible with the Shield. Is there a list for compatible modules ?
* If worth it Could someone make such a script for the Shield ?
Thanks in advance for giving me clues, have all a great day !
Has anyone, by chance, backed up the 8.0 ota zip file for the shield 2015 16gb version? I updated by accident before saving it.
Hi
TAM1m said:
Has anyone, by chance, backed up the 8.0 ota zip file for the shield 2015 16gb version? I updated by accident before saving it.
Click to expand...
Click to collapse
yes I have it here. Uploading to my gdrive.
Just drop me a PM and i will send you the link.
Regards
Chaos
sash11 said:
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Click to expand...
Click to collapse
nvm.. i found it
yea.. they did something.. no matter what i do i cant get patched boot.img to load.. it just hangs on nvidia logo like others..
i was not able to get the full firmware however and only pulled the ota.zip which has a boot.img and then other patch files
elliwigy said:
yea.. they did something.. no matter what i do i cant get patched boot.img to load.. it just hangs on nvidia logo like others..
i was not able to get the full firmware however and only pulled the ota.zip which has a boot.img and then other patch files
Click to expand...
Click to collapse
The question is if it's the same with boot.img from the dev. rom...that would be bad.
trohn_javolta said:
The question is if it's the same with boot.img from the dev. rom...that would be bad.
Click to expand...
Click to collapse
Compared CRC of both boot img from normal and dev version. It's the same. So better ask topjohnwu for looking into magisk to support this shield tv update.
oldpoem said:
Compared CRC of both boot img from normal and dev version. It's the same. So better ask topjohnwu for looking into magisk to support this shield tv update.
Click to expand...
Click to collapse
Hmm.. yeah. I now think it's because of android pie not necessarily because of changes from nvidia.
Full recovery images are available for download for Shield Experience 8.0.0
https://developer.nvidia.com/gameworksdownload
Would you mind to share the best solution when you succeed?
Hi all using S20,
Samsung have released Android 11 firmware for the S20 series recently.
So has anyone of you here already installed this firmware and got it rooted successfully (with Magisk)?
I've already had the firmware at hand but not installed it on my S20 (SM-G9810, BRI), since I dare not get the firmware rooted.
Thank you guys in advance!
jasonc417 said:
Hi all using S20,
Samsung have released Android 11 firmware for the S20 series recently.
So has anyone of you here already installed this firmware and got it rooted successfully (with Magisk)?
I've already had the firmware at hand but not installed it on my S20 (SM-G9810, BRI), since I dare not get the firmware rooted.
Thank you guys in advance!
Click to expand...
Click to collapse
Had 0 issues. Also have twrp.
Only had a problem hiding magisk but that was probably my fault.
Flash twrp with Odin, install magisk through twrp.
Yep, easily. Follow the guides and read and you should be victorious
Hello everyone. I'm glad i found this topic which is about what I'm exactly trying to solve now. Ive been using Android 10 which was rooted using Magisk. I got a Samsung S20+ (SM-G986B). I was using a method where i had to extract the Android 10's boot image file which i had to patch with Magisk app and then flash it using Odin. Which finally rooted the Android 10. Now i updated my android to the latest 11 build country code (PHN) Netherlands. The same method caused my phone to get stuck at bootloop. The same happens when i just flash Magisk using TWRP right away. My bootloader is unlocked so i'm not sure what is causing the bootloop. Could the problem be that im using the (PHN) firm?. Can you guys maybe share in which country model firm you've successfully be able to flash Magisk right away? Thanks in advance. I'm using many apps which requires root so i need to get the android 11 rooted asap. Or i will have to roll back to Android 10. Thanks in advance for any help
FoxhoundUnit said:
Hello everyone. I'm glad i found this topic which is about what I'm exactly trying to solve now. Ive been using Android 10 which was rooted using Magisk. I got a Samsung S20+ (SM-G986B). I was using a method where i had to extract the Android 10's boot image file which i had to patch with Magisk app and then flash it using Odin. Which finally rooted the Android 10. Now i updated my android to the latest 11 build country code (PHN) Netherlands. The same method caused my phone to get stuck at bootloop. The same happens when i just flash Magisk using TWRP right away. My bootloader is unlocked so i'm not sure what is causing the bootloop. Could the problem be that im using the (PHN) firm?. Can you guys maybe share in which country model firm you've successfully be able to flash Magisk right away? Thanks in advance. I'm using many apps which requires root so i need to get the android 11 rooted asap. Or i will have to roll back to Android 10. Thanks in advance for any help
Click to expand...
Click to collapse
On android 11 you need to copy firmware's AP file to the phone, patch it with latest magisk (canary, in my case), and flash it with Odin (AP slot) instead of original AP file, and you're done.
In case if you prefer to work with a small file on the phone, extract boot.img.lz4 and vbmeta.img.lz4 from AP, pack both extracted files as a single tar file (7zip > tar) - boot_vbmeta.tar - and flash it in the USERDATA slot (remember to flash original AP file in the AP slot).
FoxhoundUnit said:
Hello everyone. I'm glad i found this topic which is about what I'm exactly trying to solve now. Ive been using Android 10 which was rooted using Magisk. I got a Samsung S20+ (SM-G986B). I was using a method where i had to extract the Android 10's boot image file which i had to patch with Magisk app and then flash it using Odin. Which finally rooted the Android 10. Now i updated my android to the latest 11 build country code (PHN) Netherlands. The same method caused my phone to get stuck at bootloop. The same happens when i just flash Magisk using TWRP right away. My bootloader is unlocked so i'm not sure what is causing the bootloop. Could the problem be that im using the (PHN) firm?. Can you guys maybe share in which country model firm you've successfully be able to flash Magisk right away? Thanks in advance. I'm using many apps which requires root so i need to get the android 11 rooted asap. Or i will have to roll back to Android 10. Thanks in advance for any help
Click to expand...
Click to collapse
You have to flash a vbmeta disabled file in the user data section of Odin. You'll find the vbmeta file in the rooting thread on XDA
I patched the whole AP .tar.md5 file using Magisk Manager and it worked!. I'm really thankful to you guys. I do want to note that i could not patch the AP file of the Android 11 firmware version i had. İt ended up giving me a error. What i did is downloading a more recent Android 11 firmware for SM-G986B (PHN). And Magisk thankfully recognized it and i could patch the AP .md5 file and flashed lt alongside with other original components using odin and it worked. Anyways thank you very much for the great help. Now i can continue from where i left off. XDA didn't disappoint me again. Much appreciated
serajr said:
In case if you prefer to work with a small file on the phone, extract boot.img.lz4 and vbmeta.img.lz4 from AP, pack both extracted files as a single tar file (7zip > tar) - boot_vbmeta.tar - and flash it in the USERDATA slot (remember to flash original AP file in the AP slot).
Click to expand...
Click to collapse
What about updating? Can we use this method to install a newer One UI version without losing data? Is this even what the USERDATA slot means?
How to fix sm g530w
Gogu24 said:
What about updating? Can we use this method to install a newer One UI version without losing data? Is this even what the USERDATA slot means?
Click to expand...
Click to collapse
Ofc you can.
This is exactly how I update my S20+ on every new security patch firmware (monthly update) without losing data.