Yes, I know and always did a clean flash when trying a different image. However, I have the feeling that the "format data" function in TWRP does not work as intended with the latest kernel. Did you format your data partition from TWRP or via different means when installing the 2030507 build?
-
We are moving to xdaforums.com.
Until then, this forum is in read-only mode.
You will be automatically redirected once the migration is complete.
Question stuck at bootlogo after installing gsi
- Thread starter WolfHRB
- Start date
Here is some more detailed info on what happens: I formatted data in TWRP and wiped cache etc. Then I installed lineage-20.0-20230507-UNOFFICIAL-arm64_bgN.img via fastboot. No errors so far. After rebooting the device, it runs into a bootloop. Just before the next iteration of the boot loop, it displays an error message on screen, which I captured a video of and tried to transcribe below (sorry for typos and misreadings, the video quality was poor). It says (excerpt):
Sysdumping now, keep power on.
Reset mode: kernel crash
exception_file_info:
not-bugon
exception_panic_reason:
dmv corrupt
exception_stack_info:
[...]
APSS INFO
Panic caller : verity_handle_err_hex_debug+0x3dc/0x3e0
Panic msg: dmv corrupt
Thread: kworker/u16:1:66
Anyone able to make sense out of this? Should I disable verity verification anyway?
Sysdumping now, keep power on.
Reset mode: kernel crash
exception_file_info:
not-bugon
exception_panic_reason:
dmv corrupt
exception_stack_info:
[...]
APSS INFO
Panic caller : verity_handle_err_hex_debug+0x3dc/0x3e0
Panic msg: dmv corrupt
Thread: kworker/u16:1:66
Anyone able to make sense out of this? Should I disable verity verification anyway?
kevinco1
Senior Member
For the third time, you cannot do that with the SM-X200. Do not flash any image related to this meant for another device
I'd recommend you to flash stock again through Odin and start over. Something is messed up big time and this may be the only way to get you out of this hole
Thank you, but I am aware that flashing empty vbmeta.img is dangerous on the SM-X200 and did not really mention that before. I also saw the other threads where people mistakenly flashed an empty vbmeta.img.
I am just curious whether I get these kernel errors related to verity. I actually reverted to stock via Odin twice (first to X200XXS2CWD2, then to X200XXS2CWD1), re-installed TWRP afterwards, wiped and formatted, flashed the LOS image via fastboot and so on. The result is always the same: bootloop. I am out of ideas.
You must be doing something wrong because I just did this on my X200. I have had LOS 20 running for a while but when so many people were having problems rooting with the latest stock ROM, I decided to start from scratch with CWD2 to see if it worked. You can see from my post in the "SM-X200 root failed" thread that I succeeded rooting stock and the steps I took to do it. After that, I again flashed TWRP, used it to format data and factory reset wipe. Then I re-booted to fastboot mode and used that to flash the LOS 20 GSI. It is up and working. Of course bluetooth is still not working but hopefully someone will find a fix for that soon. The GSI I used was the 0507 LOS 20 bgN.
Last edited:
Thank you for your patience. Finally I made some progress. I installed a new set of adb/fastboot (Android SDK Platform-tools 34.0.3) and said "fastboot -erase system" before flashing the system.img file. Now LineageOS is booting up. Not sure whether it was the missing "fastboot -erase", the old fastboot command or the combination of both that caused the kernel panic.
However, I am still fighting with random reboots of LOS (as mentioned in another thread here). This happens with both the 0507 LOS and the one from February that is said to have a working bluetooth. The tablet just reboots after a few minutes, possibly because some watchdog triggers it.
However, I am still fighting with random reboots of LOS (as mentioned in another thread here). This happens with both the 0507 LOS and the one from February that is said to have a working bluetooth. The tablet just reboots after a few minutes, possibly because some watchdog triggers it.
I didn't use "fastboot -erase system" and mine works. The TWRP /Wipe and swipe for factory reset, should have already erased the system. Watchdog will cause the reboot problem, but why it happens on your tablet and not anyone else's, is beyond me.
Just to follow up on the random crashes: I had these with two LOS 20 builds (Andy Yan bgN from March and May) and was not able to fix this issue. Even after writing 'V' to /dev/watchdog, /dev/watchdog0 and /dev/watchdog1 (from a root shell), the system sporadically rebooted. With LOS 19 (bgN May build) there are no random reboots. This could hint at an imcompatibility between LOS 20 and the X200XXS2CWD2 firmware. For the time being, I stay at LOS 19.
That sounds logical except for the fact I'm running LOS 20 WITHOUT random reboots. And Watchdog doesn't cause "random" reboots. It causes a TIMED reboot so many seconds after startup. If you have random reboots, it sounds more likely that you are running out of memory. How much RAM do you have? 20 does require more than 19.
Last edited:
kevinco1
Senior Member
Same here, for any LOS 20 build that flashed successfully none of them rebooted randomly for me at all
Have you installed anything other than the ROM itself? Is it possible you have a corrupt system.img file?
Last edited:
No, clean flash. I tried 3 different AndyYan LOS 20 images bgN (without vndklite) from February, March and May with the same result, i. e. sporadic reboots. The LOS 19 images from the same author (tried February and May) work flawlessly.
Similar threads
