Database Develop

[RECOVERY][ROOT]TWRP 3.0.2.1 Galaxy SM-A700FD - MARSHMALLOW

Unofficial release -TWRP recovery for the Galaxy A7 - SM-A700FD - Qualcomm msm8939
UPDATE 4/8/2016:
TWRP 3.0.2-1 MM build.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
MARSHMALLOW:
twrp_3.0.2-1_sm-a700fd_mm_4816
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
https://download.chainfire.eu/969/SuperSU/
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1/6.0.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.

Reserved

Will it work with Lollypop? On my SM-a7100 (also Qualcomm msm8939) it installs file with odyn, but when i try to reboot in TWRP - sams bootscreeen + error
P.s. Really like your work!

@ashyx
Thankss ! :good:

mur4ello said:
Will it work with Lollypop? On my SM-a7100 (also Qualcomm msm8939) it installs file with odyn, but when i try to reboot in TWRP - sams bootscreeen + error
P.s. Really like your work!
Click to expand...
Click to collapse
Marshmallow only I'm afraid.

having No OS installed / device isn't rooted and error error executing updater binary in zip when trying to install custom rom in twrp.
Tried to re-flash CF auto root and TWRP but yet it only boot loops. Also tried to flash the firmware from sammobile but failing.. any help? :/ TIA

Set Warranty Bit: kernel
Bootscreen shows "Set Warranty Bit: kernel" in yellow font and booting into recovery shows the Seandroid warning. This happened after flashing twrp and rooting the phone. That's the only problem though because twrp and supersu are working properly. How to fix this? tia!

nieohl said:
having No OS installed / device isn't rooted and error error executing updater binary in zip when trying to install custom rom in twrp.
Tried to re-flash CF auto root and TWRP but yet it only boot loops. Also tried to flash the firmware from sammobile but failing.. any help? :/ TIA
Click to expand...
Click to collapse
Sorry for this. It was my unlocked device in my pocket. Please delete

OEM issue
Im using this sm a700fd device but in my developer mode i dont have OEM option thats the reason my 4 is not getting root not installing Twrp not even cf auto root working plz help .......

thnk u vry mchhhhhhhhhhhh.........................

TWRP & LineageOS 16 installed in T5

I have been able to install LineageOS, it is working but with bugs, for example the 5GHz Wifi is not working & It have been hard to make it connect to the 2.4 GHz, once connected for first time it worked fine (2.4 only)
Here is how to do:
You need fastboot, connect T5 to computer.
Download TWRP for Huawei P20 Lite, I used this one:
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
Copy downloaded file to adb&fastboot folder
Open a DOS box or command line, use:
adb reboot bootloader
fastboot flash recovery_ramdisk TWRP.img
fastboot reboot
Press volume+ & diconnnect USB, TWRP will start.
From the main menu of TWRP, tap Wipe, and then tap Format Data.
Follow TWRP’s instructions.
Tap on Advanced Wipe.
Check the boxes: Dalvik/ART Cache, System, and Cache. Leave all the others unchecked.
Swipe from left to right on the slider marked Swipe.
Download LineageOS 16 from:
https://openkirin.net/download/
go down to EMUI 8-based Builds
Copy downloaded file to adb&fastboot folder
Extract the compressed .XZ file
Go to command line & enter:
adb reboot bootloader
fastboot flash system lineage16.img
fastboot reboot
Disconnect USB, LineageOS will start.

stuck on recovery
Hi,
I followed the tuto and flashed a GSI rom following this tuto, and I ended up stuck on the recovery boot page, I can't access fastboot anymore, even if I flash it from the PotatoNV tool, it blink on the fastboot an then reboot on the recovery.
Does anyone know how to clean flash the fastboot. I think that way I could flash the recovery and the system...
Please help me

fixed my mistake
EtienneHD said:
Hi,
I followed the tuto and flashed a GSI rom following this tuto, and I ended up stuck on the recovery boot page, I can't access fastboot anymore, even if I flash it from the PotatoNV tool, it blink on the fastboot an then reboot on the recovery.
Does anyone know how to clean flash the fastboot. I think that way I could flash the recovery and the system...
Please help me
Click to expand...
Click to collapse
I fixed it by rebooting using vol+, vol-, power to reboot in the special mode from huawei. it allowed me to download and flash the firmware from here.
I will try again later, I hope it will work better next time :silly:

Kgonla said:
I have been able to install LineageOS, it is working but with bugs, for example the 5GHz Wifi is not working & It have been hard to make it connect to the 2.4 GHz, once connected for first time it worked fine (2.4 only)
Here is how to do:
You need fastboot, connect T5 to computer.
Download TWRP for Huawei P20 Lite, I used this one:
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
Copy downloaded file to adb&fastboot folder
Open a DOS box or command line, use:
adb reboot bootloader
fastboot flash recovery_ramdisk TWRP.img
fastboot reboot
Press volume+ & diconnnect USB, TWRP will start.
From the main menu of TWRP, tap Wipe, and then tap Format Data.
Follow TWRP’s instructions.
Tap on Advanced Wipe.
Check the boxes: Dalvik/ART Cache, System, and Cache. Leave all the others unchecked.
Swipe from left to right on the slider marked Swipe.
Download LineageOS 16 from:
https://openkirin.net/download/
go down to EMUI 8-based Builds
Copy downloaded file to adb&fastboot folder
Extract the compressed .XZ file
Go to command line & enter:
adb reboot bootloader
fastboot flash system lineage16.img
fastboot reboot
Disconnect USB, LineageOS will start.
Click to expand...
Click to collapse
Have any screenshots ?

OpenKirin doesn't support TWRP.
Read the point 4:
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
I installed twrp and then flashed LineageOS it just stuck at TWRP recovery splash screen. I could access adb commands, nothing else.
Fortunately I managed to boot into stock recovery by pressing Vol + and start button, it allowed me to download the stock firmware and flash it back to original firmware.
I don't know how to remove TWRP completely and I am scared to flash lineage os 16 again.

gunpal5 said:
OpenKirin doesn't support TWRP.
Read the point 4:
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
I installed twrp and then flashed LineageOS it just stuck at TWRP recovery splash screen. I could access adb commands, nothing else.
Fortunately I managed to boot into stock recovery by pressing Vol + and start button, it allowed me to download the stock firmware and flash it back to original firmware.
I don't know how to remove TWRP completely and I am scared to flash lineage os 16 again.
Click to expand...
Click to collapse
TWRP do not work when LineageOS is installed.
When LineageOS is deleted or replaced by the Huawei firmware TWRP will work again.
If you want to delete the firmware you can do it via fastboot:
fastboot erase system
To delete TWRP I think this is the command (not 100% sure):
fastboot erase recovery_ramdisk

Hi, did you trie to install ROM without TWRP ?

Hi guys, I have successfully installed LineageOS 16 on my Mediapad T5 LTE. So far everything seems to work fine including wifi and LTE and i haven't had any problems with it. I followed this: https://forum.xda-developers.com/mediapad-t5/how-to/how-to-unlock-bootloader-t4141705 to unlock the bootloader. I then followed the instructions on OpenKirin website to flash LineageOS 16. I have also successfully installed magisk on LOS16 by patching the ramdisk from ags-l09. Hope it works for you guys as well. Here are screenshots.

wesmat95 said:
Hi guys, I have successfully installed LineageOS 16 on my Mediapad T5 LTE. So far everything seems to work fine including wifi and LTE and i haven't had any problems with it. I followed this: https://forum.xda-developers.com/mediapad-t5/how-to/how-to-unlock-bootloader-t4141705 to unlock the bootloader. I then followed the instructions on OpenKirin website to flash LineageOS 16. I have also successfully installed magisk on LOS16 by patching the ramdisk from ags-l09. Hope it works for you guys as well. Here are screenshots.
Click to expand...
Click to collapse
Netflix and Prime is working?
Sent from my ELE-AL00 using Tapatalk

sheenswizner said:
Netflix and Prime is working?
Sent from my ELE-AL00 using Tapatalk
Click to expand...
Click to collapse
Just tested it. Netflix needs the old app but prime works fine

So have any way to install magisk on this system

Got my mediapad t5 working with the latest lineageOS 16 and magisk 21.1!
Took a while but finally figured it out.
TWRP will get stuck on the boot screen after you fastboot flash lineageOS so either erase the recovery partition or leave it if you want to take the risk (I never got stuck on it, just press and hold the power button, plug in cable + volume down when it restarts to go into fastboot mode).
Follow the instructions here: https://openkirin.net/user_guide/how-to-install-magisk/ for magisk install without TWRP. You'll need to find the closest firmware download to your device model #. Mine was AGS2-L03 but I could only find AGS2-L09 to be the closest here: https://pro-teammt.ru/en/online-firmware-database/?firmware_model=ags2&firmware_page=0.
You'll need to extract the update.APP, and then extract the ramdisk using the Huawei recovery tool. Then patch with magisk manager (and flash the patched boot.img with fastboot).

I lately tried to flash my mediapad t5 with lineage but after several tries and searches I couldnt for the live of me get the pad unlocked to flash. i followed the instructions but it will always say 'phone - locked' on the dev screen.
some searchresults suggested that huawei had a service website where you could request an unlock code for your t5 but the site was shut a while ago. how do i unlock MY mediapad?!
Edit: Is the only option to open the case and short the testpoint?

Trying to install LineageOS 16 but I see FRP is Locked. Is it safe to continue? If not, how do I unlock FRP?

Has anyone here heard of the hcu repair tool? has anyone used it before and does it work to unlock the ags2-w09 mediapad t5 completely?
mine says 'phone locked' and the only option i seem to have atm is to short the testpoint. that seems to be a last resort for me. any suggestions?

Unlocked the bootloader without any problems and flashed LineageOs 16.0 B6 on ags2-l09.
Sound and wifi works fine, the cam works with androin.camera2.
Compared to the stock rom it runs a lot better.
As been mention small quirk with the blured text can be fixed by disable HW overlays.
Is it posible to set this option permanently? It gets reseted after reboot.
There is one bigger inconiniane.
When i plug the tablet to a pc(windows) it does not show in the explorer(file transfer is enabled). In the devce menager it gets mounted as composite device.
Under linux i also cannot mount it.
Has anyone the same issue? Any fix?
Luckily adb/fastboot works.

Can someone send me the lineageOs image? I went through all the trouble unblocking the bootloader and now the website is down. Thanks!

geist_patrick said:
Can someone send me the lineageOs image? I went through all the trouble unblocking the bootloader and now the website is down. Thanks!
Click to expand...
Click to collapse
Here it is, version 16.0 with gapps. This is the only one I have:
File on MEGA
mega.nz

borja113 said:
Here it is, version 16.0 with gapps. This is the only one I have:
File on MEGA
mega.nz
Click to expand...
Click to collapse
Thank you very much! Finally I'll have lineageOS on my device!
I didn't know there is a version with gapps. Actually I was searching for the version without them to improve speed but I can just remove them.

I see that Openkirin site is back again. You can pick a more recent build there, and without gapps if it's you preference.

How To Guide Rooted my Pixel 7

Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, enter bootloader do a "fastboot flash init_boot magskpatchedfile.img.
9, reboot and test,
I have removed the _a in the cmd line as it appears its not needed
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum.
Ok,, this how I flashed ,and will flash, the new updates coming out so as not to lose data ,this will NOT do a wipe plus it's faster ,,,,, I know there are multiple other ways but for now I choose this,, hth
1. Download the correct ota file here
https://developers.google.com/android/ota and copy to adb folder
2. Place phone in factory recovery and toggle to apply update from adb,,
3. Open cmd prompt in adb folder type adb sideload factoryota.zip ,,,takes 5-10 minutes to complete, reboot ,,
if rooted,
1 download correct full image zip here
https://developers.google.com/android/images. That matches ota you just flashed,
2 extract the ini.boot.img , patch with magisk and reflash in adb for root

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
Does the screen come on at all? In your other post you said it was black. If there's nothing at all on the screen, your phone is probably bricked.

JimJamer8 said:
it doesnt turn on at all
Click to expand...
Click to collapse
Have you tried a hard reset - hold the power button down for 10 seconds or so until the phone vibrates?

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You didn't try the steps I listed as I never said to flash a rooted bootloader

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You may need to disable Verity and Verification. I flashed my stock image back to the phone using the tool here: https://flash.android.com/ and checked the boxes to disable verity and verification, then followed the steps above. Important to note that booting to Bootloader tells you which slot is active, and running the command fastboot flash init_boot magisk_patched_25205_GUID.img automatically patches the active boot slot. From there you just need to run the Universal Safety net fix from KDrag0n and the latest MagiskHide and you should be good to go

hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Thank you for the help, turned out the _a was screwing me over, works great now!

mnemonical said:
Thank you for the help, turned out the _a was screwing me over, works great now!
Click to expand...
Click to collapse
I know ,,that was messing me up too, it did not work untill I put that part in,, don't ask me why! Lol

Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.

googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.

atom_jack said:
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
Click to expand...
Click to collapse
I'll give it a try

googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
Use the non replace version of revanced and disable stock YT

Hitman478™ said:
Use the non replace version of revanced and disable stock YT
Click to expand...
Click to collapse
Revanced Manager app is just going to black screen after install

hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?

AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik

googletermsofservice said:
Revanced Manager app is just going to black screen after install
Click to expand...
Click to collapse
I've it installed and it's working without any issue

AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
Use fastboot flash init_boot "image.img" without quotes and without specific the partition, it will goes on the active one, for me it has working at first try

hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
THX, in fact the "fastboot boot" command was used a lot with OnePlus devices because it is safer to boot in the rooted os and when there is an error you can just reboot without the command...and when you install it afterwards with magisk you know it will work

Does Universal Safetynet Fix work?

Just wanted to thank OP. My Pixel 7 arrived about an hour ago, got the bootloader unlocked no problem, then actually I flashed the latest System Image first, then had Magisk patch init_boot.img, flashed that, easy peasy.

hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
It's usually used to temporarily boot a patched boot image and then you can do direct install in magisk manager

Question stuck at bootlogo after installing gsi

Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation

WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.

starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible

kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing

I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?

stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.

lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.

kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.

stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.

stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?

Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.

mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.

No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).

mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully

The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?

mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.

General Patched recovery with fastboot

This works on my device, but use at your own risk, as if used wrong this could cause you to brick your device.
Test was conducted on XAR_X200XXS2CWD2
Requires Unlocked BootLoader (OEM UNLOCKING ENABLED in developer settings)
Unlock bootloader by holding the volume up and volume down buttons while the device is powered down, after connecting to a USB ota cable.
If you unlock your bootloader, your warrenty is void.
not much detail needed here really, just Flash the recovery.tar to AP file in Odin and you can use fastboot

MrFluffyOven said:
This works on my device, but use at your own risk, as if used wrong this could cause you to brick your device.
Test was conducted on XAR_X200XXS2CWD2
Requires Unlocked BootLoader (OEM UNLOCKING ENABLED in developer settings)
Unlock bootloader by holding the volume up and volume down buttons while the device is powered down, after connecting to a USB ota cable.
If you unlock your bootloader, your warrenty is void.
not much detail needed here really, just Flash the recovery.tar to AP file in Odin and you can use fastboot
Click to expand...
Click to collapse
I have TWRP right now. I can still flash this to AP and it will replace it?

kevinco1 said:
I have TWRP right now. I can still flash this to AP and it will replace it?
Click to expand...
Click to collapse
yeah, this is the stock recovery patched so you can use fastboot, the reason i made this is because some people were having trouble with the touchscreen on twrp, as a general rule twrp is better

MrFluffyOven said:
yeah, this is the stock recovery patched so you can use fastboot, the reason i made this is because some people were having trouble with the touchscreen on twrp, as a general rule twrp is better
Click to expand...
Click to collapse
Ok cool, but with switching over to the patched recovery you are unable to flash Magisk?

kevinco1 said:
Ok cool, but with switching over to the patched recovery you are unable to flash Magisk?
Click to expand...
Click to collapse
will need to test adb sideload and get back to you

kevinco1 said:
Ok cool, but with switching over to the patched recovery you are unable to flash Magisk?
Click to expand...
Click to collapse
i need to perform some checks to make sure my adb drivers are all functional before giving you a full answer, but assuming that your device is pre rooted with magisk and you want to flash zips try this
Magic ToolFlash lets you flash ZIP packages directly from your Android device
Magic ToolFlash is a unique Magisk module that allows you to install flashable ZIP files from a terminal emulator app on your phone.
www.xda-developers.com