Database Develop

VOLTE & IMEI Recover Solution after move back to Stock / Custom ROMs

As i have come to know or you can say i have faced this issues after moving back to stock rom via fastboot, i have lost IMEI and VOLTE.
By doing various things and search for the solutions on google and Moto G5sPlus XDA Community thread, i did'nt got VOLTE.
so, finally one of the Moto G5s Plus Dev found the Solution and i applied the trick too, get the VOLTE & IMEI back.
Note: Im not blaming and mentioning anyone who finds a various way to get back IMEI & VOLTE.
Huge Thanks to @premaca - Ground Zero Roms DEV
Here is the simple and easiest way, which i prefers everyone who lost their VOLTE & IMEI.
1. Please download the lastest stock rom -NPSS26.116-61-2 http://androidfilehost.com/?fid=962187416754460903 or NPSS26.116-61 https://androidfilehost.com/?fid=889964283620776326
2.After Flashing via Fastboot setup the device and once again reboot to bootloader.
3.Flash Multirom TWRP Recovery via Fastboot eg: fastboot flash recovery TWRP_multirom_sanders_20171221-01.img
TWRP Recovery 21.12.2017 -https://androidfilehost.com/?fid=889964283620773492
4.Reboot to recovery -> Flash this Multirom.zip File on TWRP, Which works for 32/64 bit recoveries.
MR Zip -https://androidfilehost.com/?fid=889964283620765983
5.After Done the above two method (3 & 4) then flash Validus ROM on Secondary along with gapps (GZR/unofficial Open gapps 8.1 version), I will be sharing only validus Rom build in below.
Validus ROM 28.01.2017 - https://androidfilehost.com/?fid=818070582850488560
6.Setup the device then again goto back to bootloader
7.On bootloader just flash those 3 fastboot commands on cmd window.
fastboot erase modemst1
fastboot erase modemst2
then
fastboot reboot
Then restarted by chossing Validus OS for to boot up the device. "LTE is Restored"..
Just try this method if anyone still not yet restored LTE..
Thanks to @premaca for TWRP MR Recovery, Zip and Validus OS build.
Thanks to @CheckYourScreen "Nimit" for Sanders Stock Zip Files.

im getting error while flashing mr zip
---------- Post added at 12:20 PM ---------- Previous post was at 12:05 PM ----------
Sri Datta said:
im getting error while flashing mr zip
Click to expand...
Click to collapse
wiping internal storage solved it does it restore volte

Would this work to enable volte of custom roms?
That is the only reason I am still on the stock ROM. All custom ROMs I try, volte does not work. I think it just might be my carrier is unsupported (MetroPCS)

Sri Datta said:
im getting error while flashing mr zip
---------- Post added at 12:20 PM ---------- Previous post was at 12:05 PM ----------
wiping internal storage solved it does it restore volte
Click to expand...
Click to collapse
Did you use above twrp recovery image and multirom zip files only..

Recrux said:
Would this work to enable volte of custom roms?
That is the only reason I am still on the stock ROM. All custom ROMs I try, volte does not work. I think it just might be my carrier is unsupported (MetroPCS)
Click to expand...
Click to collapse
Yes, of course it enable volte in custom or stock ROM..

syed sajid said:
Yes, of course it enable volte in custom or stock ROM..
Click to expand...
Click to collapse
Well it ain't able to enable volte on stock rom one of friends lost his volte & is unable to get his volte bavk even with this

s.k.rajput said:
Well it ain't able to enable volte on stock rom one of friends lost his volte & is unable to get his volte bavk even with this
Click to expand...
Click to collapse
He has done all the steps.. Tell him to contact me via telegram @iSyedsajid

syed sajid said:
He has done all the steps.. Tell him to contact me via telegram @iSyedSajid
Click to expand...
Click to collapse
Wrong tag, bro.
Sent from my SM-G925I using Tapatalk

Thank you very much, thank you

juniorhonorato1986 said:
Thank you very much, thank you
Click to expand...
Click to collapse
Did it restore volte on stock??

syed sajid said:
As i have come to know or you can say i have faced this issues after moving back to stock rom via fastboot, i have lost IMEI and VOLTE.
By doing various things and search for the solutions on google and Moto G5sPlus XDA Community thread, i did'nt got VOLTE.
so, finally one of the Moto G5s Plus Dev found the Solution and i applied the trick too, get the VOLTE & IMEI back.
Note: Im not blaming and mentioning anyone who finds a various way to get back IMEI & VOLTE.
Huge Thanks to @premaca - Ground Zero Roms DEV
Here is the simple and easiest way, which i prefers everyone who lost their VOLTE & IMEI.
1. Please download the lastest stock rom -NPSS26.116-61-2 http://androidfilehost.com/?fid=962187416754460903 or NPSS26.116-61 https://androidfilehost.com/?fid=889964283620776326
2.After Flashing via Fastboot setup the device and once again reboot to bootloader.
3.Flash Multirom TWRP Recovery via Fastboot eg: fastboot flash recovery TWRP_multirom_sanders_20171221-01.img
TWRP Recovery 21.12.2017 -https://androidfilehost.com/?fid=889964283620773492
4.Reboot to recovery -> Flash this Multirom.zip File on TWRP, Which works for 32/64 bit recoveries.
MR Zip -https://androidfilehost.com/?fid=889964283620765983
5.After Done the above two method (3 & 4) then flash Validus ROM on Secondary along with gapps (GZR/unofficial Open gapps 8.1 version), I will be sharing only validus Rom build in below.
Validus ROM 28.01.2017 - https://androidfilehost.com/?fid=818070582850488560
6.Setup the device then again goto back to bootloader
7.On bootloader just flash those 3 fastboot commands on cmd window.
fastboot erase modemst1
fastboot erase modemst2
then
fastboot reboot
Then restarted by chossing Validus OS for to boot up the device. "LTE is Restored"..
Just try this method if anyone still not yet restored LTE..
Thanks to @premaca for TWRP MR Recovery, Zip and Validus OS build.
Thanks to @CheckYourScreen "Nimit" for Sanders Stock Zip Files.
Click to expand...
Click to collapse
Only lte working not Volte

Kdemwa said:
Only lte working not Volte
Click to expand...
Click to collapse
Same here

Does volte work in your device .? @syed sajid

akshu2697 said:
Does volte work in your device .? @syed sajid
Click to expand...
Click to collapse
I asked him he said yes

Sri Datta said:
I asked him he said yes
Click to expand...
Click to collapse
Does your volte works.?

akshu2697 said:
Does your volte works.?
Click to expand...
Click to collapse
No

I want u to add some thing for users who want to lock bootloader just ignore erase modemst1 and modemst2 while flashing stock rom

syed sajid said:
As i have come to know or you can say i have faced this issues after moving back to stock rom via fastboot, i have lost IMEI and VOLTE.
By doing various things and search for the solutions on google and Moto G5sPlus XDA Community thread, i did'nt got VOLTE.
so, finally one of the Moto G5s Plus Dev found the Solution and i applied the trick too, get the VOLTE & IMEI back.
Note: Im not blaming and mentioning anyone who finds a various way to get back IMEI & VOLTE.
Huge Thanks to @premaca - Ground Zero Roms DEV
Here is the simple and easiest way, which i prefers everyone who lost their VOLTE & IMEI.
1. Please download the lastest stock rom -NPSS26.116-61-2 http://androidfilehost.com/?fid=962187416754460903 or NPSS26.116-61 https://androidfilehost.com/?fid=889964283620776326
2.After Flashing via Fastboot setup the device and once again reboot to bootloader.
3.Flash Multirom TWRP Recovery via Fastboot eg: fastboot flash recovery TWRP_multirom_sanders_20171221-01.img
TWRP Recovery 21.12.2017 -https://androidfilehost.com/?fid=889964283620773492
4.Reboot to recovery -> Flash this Multirom.zip File on TWRP, Which works for 32/64 bit recoveries.
MR Zip -https://androidfilehost.com/?fid=889964283620765983
5.After Done the above two method (3 & 4) then flash Validus ROM on Secondary along with gapps (GZR/unofficial Open gapps 8.1 version), I will be sharing only validus Rom build in below.
Validus ROM 28.01.2017 - https://androidfilehost.com/?fid=818070582850488560
6.Setup the device then again goto back to bootloader
7.On bootloader just flash those 3 fastboot commands on cmd window.
fastboot erase modemst1
fastboot erase modemst2
then
fastboot reboot
Then restarted by chossing Validus OS for to boot up the device. "LTE is Restored"..
Just try this method if anyone still not yet restored LTE..
Thanks to @premaca for TWRP MR Recovery, Zip and Validus OS build.
Thanks to @CheckYourScreen "Nimit" for Sanders Stock Zip Files.
Click to expand...
Click to collapse
Does this work on G5 Plus as well (XT1686) ?

iSyed said:
Wrong tag, bro.
Click to expand...
Click to collapse
Well try roms for ur device or u will end Messing it up permanently

Shonilchi said:
Does this work on G5 Plus as well (XT1686) ?
Click to expand...
Click to collapse
U just flash fsg.mbn, adspso.bin & non hlos.bin files of ur stock rom .. ur imei will be restored not sure abt volte... If volte lost u will get after u recieve any ota update for it

K20 Pro popup camera problem

So after trying Xiaomi EU, MiGlobe Rom and Android Q Beta
I decided to flash back to MIUI 10.3.8 via fastboot
Somehow my front camera won't open properly, it kept saying "Can't open front camera, please calibrate".
And when I press Calibrate, popup cam goes up and down 3 times in a row and says "Can't calibrate".
Any idea how to fix this?
EDIT: Must be the fastboot rom I downloaded. Other rom's front cam worked fine...

I am having same issue. Initially I thought it was hardware problem.
But I noticed it seem to be related to software.
Took few restart of camera app and sometime phone restart, for it to work

same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?

LogicalMaverick said:
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
Click to expand...
Click to collapse
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.

Robbo.5000 said:
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Click to expand...
Click to collapse
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly

I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
What's LR?

degeaba1981 said:
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
What's LR?
Click to expand...
Click to collapse
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325

Robbo.5000 said:
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Click to expand...
Click to collapse
Problem solved! I flashed via miflash the Chinese rom, in fastboot and the front camera was working. Then I've put the Indian global version and front camera is working fine now.

LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh

Ekalous said:
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Click to expand...
Click to collapse
I have the same problem. I'm trying to solve it but nothing for now!

LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html

topaloglu321 said:
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
Click to expand...
Click to collapse
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!

thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer

znsvs123 said:
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
Click to expand...
Click to collapse
You can't show them up. The only way is to change TWRP, hoping that is supported

thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
I'll try this thank you.

thelegoboy said:
You can't show them up. The only way is to change TWRP, hoping that is supported
Click to expand...
Click to collapse
thanks, not all of twrps are built equally. :good::good::good:

Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.

i fixed that problem just flashing chinese.rom via miflash and.camera pop up working again

sagar.anits said:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
Click to expand...
Click to collapse
Same problem here

RAJIB AHMED0077 said:
Same problem here
Click to expand...
Click to collapse
try flashing 10.3.16 chinese rom via fastboot yesterday i flash that rom and it fix that problem in my k20 Pro

Question [Solved] Unable to install EU ROM :/

Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?

did you format data after flashing 12.5.20.0

marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)

Only fastboot Version available right now bro. Already using it.

If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only

marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password

why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line

marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved

General Unofficial TWRP Image Leak

I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
Directly download it here
As said below, this should be flashable within magisk to install
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com

It should be able to flash into magisk, but there is no guarantee that flashing into rom can enter the system

PlasmaTornado said:
I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com
Click to expand...
Click to collapse
we need testers

TrajanoX3 said:
we need testers
Click to expand...
Click to collapse
Agreed. I'm sure there are some people willing to give it a shot.
I haven't flashed an image since split partitions has existed, which is a fairly long time now
Even with the OP10, I am still unrooted. TWRP provides just that extra bit of security to me

I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.

Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
Fantastic! Can you confirm that it can decrypt without any issues?

Its working good

Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
we donate screenshot

heres recovery log from TWRP

Canuck Knarf said:
heres recovery log from TWRP
Click to expand...
Click to collapse
Are you using twrp right now?

TrajanoX3 said:
Are you using twrp right now?
Click to expand...
Click to collapse
Yes

Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Can you send us a screenshot of twrp?

Canuck Knarf said:
Sim
Click to expand...
Click to collapse
Thanks for the screenshots, did you flash magisk through twrp?

Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Magisk installation working probably by twrp?

just installed Magisk

TrajanoX3 said:
we donate screenshot
Click to expand...
Click to collapse
then install and flash partition A and then partition B and relapse to recovery?

Yes
fastboot flash recovery_a then fastboot flash recovery_b then reboot to recovery from fastboot . then change language ...cause its in Chinese

Oh and Twrp works with screen password lock so no need to disable it

Canuck Knarf said:
Oh and Twrp works with screen password lock so no need to disable it
Click to expand...
Click to collapse
how do you operate

Beware, this twrp.img is not bootable. Command fastboot boot twrp.img won't work, you will get bootloop into OP logo. Rebooting into fastboot mode and doing fastboot boot stockboot.img will help.
So it means you can only flash it directly. Confirmed by me and three others.

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.