search

TrebleDroid / treble_experimentations

Scripts to automatically build/CI/Release TrebleDroid GSI
Other
203 stars 26 forks source link

bootloop on SM-T510 (Galaxy Tab A 10.1) only with android 13.x #38

Open eldersixpack13 opened 1 year ago

eldersixpack13 commented 1 year ago

Current Behavior:

directly installing android_13.x on the device via TWRP with format data leads to a bootloop. installing AOSP 12.1 v416 doesn't show this behavour.

installing ASOP 12.1 and directly installing Android_13.x afterwards without (!!!) formating data works !

Expected behavior

able to directly installing Android 13.x with formating data

Smartphone (please complete the following information):

phhusson commented 1 year ago 
What people call a "bootloop" usually can be:
- The device turns around itself at every boot
- Device shows OEM logo, vibrates, show black screen, shows OEM logo, shows
recovery
- Device shows OEM logo, then reboots to weird debug screen and remains
there
- The camera turns around at every boot
- Device shows OEM logo, vibrates, show black screen, shows OEM logo, shows
black screen, etc in loop
- Device shows OEM logo, and remains on OEM logo forever
- Device shows OEM logo, then reboots to black screen, and remains there
(look at USB for flash mode)
- Device dances around the nearest pole at every boot (also called
boot-tease)
- Device shows OEM logo, shows OEM logo, then remain on black screen
forever.
- Device shows OEM logo, shows OEM logo, then shows Android bootanimation
forever
- .... I'm sure there can be other possibilities

So stop saying "bootloop", and say what ACTUALLY HAPPEN.
Also, always check what is the state of ADB. It could be working while
doing boot loops

Also please try with stock unmodified oem recovery

eldersixpack13 commented 1 year ago

sorry for having been so inaccurate. I'm no developer ! the ROM show the logo and stays there.

will try the next days to provide more info and your suggestions, but (I'm unsure) stock recovery does not have "format data", what you suggested in another thread.

Thanks for lightning fast support and - of course - your encouragement to have such a ROM at all

eldersixpack13 commented 1 year ago

so, today I did the following:

  1. flashed last stock (what is Android 11)
  2. boot device with stock
  3. connect wlan
  4. let device do google updates (NO google account) and the initial setup
  5. setup "developer options" (tapping on "Buildnumber") and USB Debug
  6. connect via usb

in an terminal:

  1. adb reboot recovery
  2. in stock recovery: factory reset
  3. in (see [1]) stock recovery: reboot to bootloader

=>

=================== [1] because "adb reboot bootloader" gives:

error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.

================ [2] https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

================= so the only way to get (but not successfull install) GSI ROM on my device seems -so far- to be via TWRP, so

  1. I install TWRP via ODIN
  2. boot to recovery
  3. format data
  4. install system-td-arm32_binder64-ab-vanilla.img to system (and tested vndklite variant too)
  5. reboot
  6. GSI logo "android" appears and it stuck there (now since ~45 minutes)
  7. got a log via "adb logcat -G 16M && adb logcat > log.txt" for some minutes with a crashdump (?)

log file for vanilla variant is attached (vndklite looks similar)

vanilla_log.txt

any advise to help to nail this bug down ?

phhusson commented 1 year ago

you can flash samsung's recovery with https://github.com/phhusson/samsung-galaxy-a51-gsi-boot/ to enabled fastbootd in it. But first of all, in TWRP, are you using "format data" or "Wipe data"? I think you're supposed to use "format data" (the one is big warnings)

Le ven. 2 juin 2023 à 18:14, eldersixpack13 @.***> a écrit :

so, today I did the following:

  1. flashed last stock (what is Android 11)
  2. boot device with stock
  3. connect wlan
  4. let device do google updates (NO google account) and the initial setup
  5. setup "developer options" (tapping on "Buildnumber") and USB Debug
  6. connect via usb

in an terminal:

  1. adb reboot recovery
  2. in stock recovery: factory reset
  3. in (see [1]) stock recovery: reboot to bootloader

=>

  • boots to download mode and device is gone for adb/fastboot afterwards !
  • no adb devices, no fastboot devices
  • and therefore no further commands working to install GSI Rom as described in [2]

=================== [1] because "adb reboot bootloader" gives:

error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.

================ [2]

https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

================= so the only way to get (but not successfull install) GSI ROM on my device seems -so far- to be via TWRP, so

  1. I install TWRP via ODIN
  2. boot to recovery
  3. format data
  4. install system-td-arm32_binder64-ab-vanilla.img to system (and tested vndklite variant too)
  5. reboot
  6. GSI logo "android" appears and it stuck there (now since ~45 minutes)
  7. got a log via "adb logcat -G 16M && adb logcat > log.txt" for some minutes with a crashdump (?)

log file for vanilla variant is attached (vndklite looks similar)

vanilla_log.txt https://github.com/TrebleDroid/treble_experimentations/files/11636918/vanilla_log.txt

— Reply to this email directly, view it on GitHub https://github.com/TrebleDroid/treble_experimentations/issues/38#issuecomment-1573987371, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OVOKPHPBJC2AGEE7M3XJIGNVANCNFSM6AAAAAAYW7OZOM . You are receiving this because you commented.Message ID: @.***>

eldersixpack13 commented 1 year ago

thanks for fast response.

in TWRP I used "format data", what has been working for your android 12.x GSI, too. was that wrong ?

P.S. I currently do not have a Samsung recovery for my Tab, only FW files for BL, AP, CSC BL unzipped gets me: cm.bin.lz4, param.bin.lz4, sboot.bin.lz4, vbmeta.img.lz4 will try to find a stock recovery ...

eldersixpack13 commented 1 year ago

Okay, now I have the modified {r,b}.img

How do I flash this ?

even when reading: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

and there => "Important Notes" cit.: "... Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, ..."