Database Develop

Need help with Me176c, fastboot.... 123# screen

My Asus memo pad 7 is stuck on fastboot.... 123# screen. I've tried temporary recovery and had success installation with lineage-14.1 but nothing changed. Please help. Thanks.

Did you have Lollipop installed before?
Also, do I understand it correctly that you're able to get into the temp recovery session?

Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.

MJMJ7 said:
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
Click to expand...
Click to collapse
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).

I will try these steps and update you. Thank you very much.

O yes! It worked. Tablet is now back in operation on lineageos. Going and get Gapps now. Thanks a lot lambdadroid

I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

lambdadroid said:
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
Click to expand...
Click to collapse
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

MJMJ7 said:
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
Click to expand...
Click to collapse
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.

lambdadroid said:
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
Click to expand...
Click to collapse
Just thought you wouldn't be notified if I don't quote.
The gapps file is giving an error and failing, the lineageOS just stalls and never complete the installation.
I will try again now.....

patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.

Got the Gapps to install, had to choose x86 version. Still no improvement from lineage.

MJMJ7 said:
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Click to expand...
Click to collapse
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?

lambdadroid said:
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
Click to expand...
Click to collapse
Did it again with another copy and enabled the verification and all came out successfully. Thanks for your help.:good:

Magisk 22.0 update killed phone will only boot into fastboot

Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the Magisk log, said unknown image type and that it failed, rebooted phone, phone will now only reboot into fastboot mode. Not the quality I've been accustomed to and certainly does not belong in the stable branch. Now can someone please tell me what I should do to fix this hot mess?
Edit: Fixed boot with backup boot image. Included log of attempted but allegedly failed update.

Was able to restore boot image from TWRP. Here are what the logs said when I tried to update Magisk boot:
- Target image: /dev/block/sde1
- Device platform: arm64-v8a
- Installing: 22.0 (22000)
Parsing boot image: [/dev/block/sde1
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
Click to expand...
Click to collapse

callihn said:
Was able to restore boot image from TWRP. Here are what the logs said when I tried to update Magisk boot:
Click to expand...
Click to collapse
Hey could you please tell how did you do it? Mine won't boot into recovery at all

Same thing on my OP7,
I can't go to recovery mode, only fastboot, and the phone isn't detected when i type 'adb devices'
Is there any way to get my data back?

fastboot reboot recovery gets itself back in the [email protected] fastboot?
try reflash TWRP and flash magisk uninstaller

abdAlmuqtadir said:
Same thing on my OP7,
I can't go to recovery mode, only fastboot, and the phone isn't detected when i type 'adb devices'
Is there any way to get my data back?
Click to expand...
Click to collapse
you need
fastboot devices

Nothing appears..

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
< waiting for any device >

Cable works huh?

I got same problem. Fix was install again whole factory update zip file which I received during last phone upgrade from vendor. (oneplus 5T)

abdAlmuqtadir said:
Same thing on my OP7,
I can't go to recovery mode, only fastboot, and the phone isn't detected when i type 'adb devices'
Is there any way to get my data back?
Click to expand...
Click to collapse
First: When you're in fastboot-mode then use "fastboot devices".
You don't need the recovery to solve your problem!
1. extract the "boot.img" from an existing original ROM on your PC
2. use fastboot command to flash that original boot.img
3. reboot to system - your phone will work well as before
You can root again, but use Magisk 21.4. There seems to be something buggy in version 22.0.
Version 22.0 worked properly with my Xiaomi Note 10 Pro (Android 10) but it didn't work with my Xiaomi Mi 10 Lite 5G (Android 11).

marulinko said:
I got same problem. Fix was install again whole factory update zip file which I received during last phone upgrade from vendor. (oneplus 5T)
Click to expand...
Click to collapse
You mean a full OTA?

Oliie23 said:
You mean a full OTA?
Click to expand...
Click to collapse
Either you flash a full image of your existing ROM, or you extract the boot.img from the ROM archive (i.e. .zip) and flash it (as boot)

The same happened to me, Lenovo Zuk Z2 Pro. Are Magisk team aware of what is happening?

erOzeOz said:
Either you flash a full image of your existing ROM, or you extract the boot.img from the ROM archive (i.e. .zip) and flash it (as boot)
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.

Oliie23 said:
You mean a full OTA?
Click to expand...
Click to collapse
yes, full OTA. I did not play with restoring it from TWRP and I had no idea which part is affected. But Phone was not wiped, it kept everything.

My pc did recognize the device in fastboot mode
I booted the recovery via fastboot
Install the last update without wyping anything
Install TWRP, Install Magisk 21.4
Everything is working with 21.4 , i will wait for next realease

abdAlmuqtadir said:
My pc did recognize the device in fastboot mode
I booted the recovery via fastboot
Install the last update without wyping anything
Install TWRP, Install Magisk 21.4
Everything is working with 21.4 , i will wait for next realease
Click to expand...
Click to collapse
brick is magisk 22

I downloaded the Magisk-v22.0.apk file and renamed it to Magisk-v22.0.zip I went to recovery and installed from there everything worked

None of this happened to me. Downloaded and installed via wifi through the normal Magisk update. Maybe you guys are doing it over mobile data?

OOS stable boot image and patched magisk boot image both for 11.1.1.1.

Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.

I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​

235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D

sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot

235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well

sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process

sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)

previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later

abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.

I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!

F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.

I got boot loop after updating to 11.1.2.2
Any new boot img?

izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.

The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?

raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes

rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you

Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.​​I uninstalled magisk by mistake and could regain root, quick and painless​

Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?

Bootloop after latest Magisk update

I always keep my Magisk canary updated. So when I saw an update today I did just that. I updated the app first and then flashed the new Magisk. After flashing I clicked on reboot and since then (a few hours ago) I have been trying to fix the bootloop I got stuck into.
Things I've tried:
Fastboot flash original boot.img
Flash the latest (and my current) image with flash-all.bat (minus the -w of course)
Try to boot in safe mode with adb wait-for-device shell magisk --remove-modules
Flash the latest Android 13 through Google browser flash-tool.
But all I get is a loading G, a black screen and reboot. After a while it goes back to Fastboot mode saying "no valid slot to boot"
I've been a long time XDA user and have been able to fix many bootloops and even some bricks in the past. But this is new to me.
Nothing works and I REALLY don't want to wipe my data. My phone has been well crafted with a LOT of apps.
I'm at a loss here...

drdionysius said:
I always keep my Magisk canary updated. So when I saw an update today I did just that. I updated the app first and then flashed the new Magisk. After flashing I clicked on reboot and since then (a few hours ago) I have been trying to fix the bootloop I got stuck into.
Things I've tried:
Fastboot flash original boot.img
Flash the latest (and my current) image with flash-all.bat (minus the -w of course)
Try to boot in safe mode with adb wait-for-device shell magisk --remove-modules
Flash the latest Android 13 through Google browser flash-tool.
But all I get is a loading G, a black screen and reboot. After a while it goes back to Fastboot mode saying "no valid slot to boot"
I've been a long time XDA user and have been able to fix many bootloops and even some bricks in the past. But this is new to me.
Nothing works and I REALLY don't want to wipe my data. My phone has been well crafted with a LOT of apps.
I'm at a loss here...
Click to expand...
Click to collapse
What modules do you have installed? Try using adb wait-for-device shell magisk --remove-modules while the device is booting.
If that doesn't work, see if you can "live boot" the patched image. If not, you can flash the unpatched image and should be able to use your device.

V0latyle said:
What modules do you have installed? Try using adb wait-for-device shell magisk --remove-modules while the device is booting.
If that doesn't work, see if you can "live boot" the patched image. If not, you can flash the unpatched image and should be able to use your device.
Click to expand...
Click to collapse
I've tried all these things without luck. The "no valid slot to boot" doesn't make me feel good about this either.

I've tried all these things without luck. The "no valid slot to boot" doesn't make me feel good about this either.
Click to expand...
Click to collapse
Sorry, I missed that.
You've tried a lot of what I would suggest, although I do think it's worth flashing the factory update to both slots. Use the --slot=all argument.
Try sideloading the OTA if you haven't already.

I just tried sideloading the OTA.
"Install from ADB completed with status 0"
Now it looks like I'm no longer stuck in a bootloop but stuck in boot. The G with loading bar stays on screen (been waiting a couple of minutes now).
Magisk modules I had installed were:
-Addon Features for Pixel Devices Lite
-A module to set DNA to 1.1.1.1
-Universal Safetynet fix
Update: still no luck. I'm close to giving up and wiping my device (feeling nauseous)

I tried sideloading OTA again and in recovery it says: "WARNING: Previous intallation has failed. Your device may fail to boot if you reboot now."
Decided to Wipe

drdionysius said:
I tried sideloading OTA again and in recovery it says: "WARNING: Previous intallation has failed. Your device may fail to boot if you reboot now."
Decided to Wipe
Click to expand...
Click to collapse
F
That sucks. If you're going to wipe, I suggest using the Android Flash Tool with the latest update; check the Wipe device and Force flash all partitions boxes. Just to be safe.
Then, flash the patched boot image.
Alternatively, if you prefer to do it via command line, I believe you can use fastboot flashall -w but you would have to extract all the images from the image-device-buildnumber.zip

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.