search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.4k stars 660 forks source link

Not booting past android logo AOSP 10.0 v204 & v206 & v209[Alldocube M5XS T1001XS] #974

Open codergenius1 opened 4 years ago

codergenius1 commented 4 years ago

Device Alldocube M5XS booted AOSP 10.0 v204 & v205(not booting) to android logo (only) [Not booting fully] ( v204_logs.zip logs attached)

phhusson commented 4 years ago

Issue is that you're using Magisk. If you want to use Magisk, you need to use a phh-ed magisk, like this: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/ Though my recommendation is that you don't use magisk if you can.

codergenius1 commented 4 years ago

followed this with v206 (1. without magisk,

  1. with Magisk-v20.2-11b7076a-phh.zip,
  2. with Magisk-v20.2-11b7076a-phh.zip+ https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip ) but no success. attaching the logs as 1without_magisk.zip, 2with_magisk.zip & 3with_magisk+dm-verity.zip respectively 1without_magisk.zip 2with_magisk.zip 3with_magisk+dm-verity.zip
phhusson commented 4 years ago

Issue in "1without_magisk" is that every single executables gets ENOENT: [ 20.706516] (5)[339:init]init: cannot execve('/system/bin/healthd'): No such file or directory [ 20.687932] (4)[337:init]init: cannot execve('/vendor/bin/fuelgauged'): No such file or directory

Sadly the log is too partial to make assertions. Issue could be apex is broken, or it's an A/B flashed over A-only, or yet other ideas.

For 2with_magisk, log isn't enough either, though in that case, you should have working adb when the device is stuck on Android animation, so you can get a proper adb logcat instead of pstore. So please provide adb logcat with magisk

codergenius1 commented 4 years ago

1 the gsi is A only and the device too is A only

2 i will try to get logcat and update here soon

On Mon 16 Dec, 2019, 4:29 AM Pierre-Hugues HUSSON, notifications@github.com wrote:

Issue in "1without_magisk" is that every single executables gets ENOENT: [ 20.706516] (5)[339:init]init: cannot execve('/system/bin/healthd'): No such file or directory [ 20.687932] (4)[337:init]init: cannot execve('/vendor/bin/fuelgauged'): No such file or directory

Sadly the log is too partial to make assertions. Issue could be apex is broken, or it's an A/B flashed over A-only, or yet other ideas.

For 2with_magisk, log isn't enough either, though in that case, you should have working adb when the device is stuck on Android animation, so you can get a proper adb logcat instead of pstore. So please provide adb logcat with magisk

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/974?email_source=notifications&email_token=AN6WLPSVB3FSTUMN3CMAW7DQY2ZEXA5CNFSM4JVXYJLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG5EPJQ#issuecomment-565856166, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6WLPWWHZVVPDL5KQWOC5LQY2ZEXANCNFSM4JVXYJLA .

codergenius1 commented 4 years ago

for 2, i tried getting logcat, but getting "device unauthorized" in adb devices during boot animation, how to proceed?

phhusson commented 4 years ago

  1. How did you check it's a-only? Please note that System-as-Root counts as A/B.

  2. Yeah well that's a bug in Magisk...

codergenius1 commented 4 years ago

Treble check app shows that the device is a only. Any solution for taking logcat during boot when the device says unauthorized during adb devices?

On Tue, Feb 4, 2020, 02:12 Pierre-Hugues HUSSON notifications@github.com wrote:

1.

How did you check it's a-only? Please note that System-as-Root counts as A/B. 2.

Yeah well that's a bug in Magisk...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/974?email_source=notifications&email_token=AN6WLPUBHUXRLDBQ24HX423RBB6URA5CNFSM4JVXYJLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKVKL4Y#issuecomment-581608947, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6WLPXUYXPSJQP2PI6XRL3RBB6URANCNFSM4JVXYJLA .

phhusson commented 4 years ago

Yeah well you can't trust Treble check app, you can only trust Treble info https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

Did you try gettings logs with adb without magisk?

codergenius1 commented 4 years ago

1) i tried to get logs with adb without magisk, but am getting "device unauthorized" error ( for v210 as informed 13 days ago), pl guide me how to solve this and take logs. 2) Treble info shows the device is A only with Legacy Treble VNDK v 26.0

codergenius1 commented 4 years ago

@phhusson if i get help from someone to boot at least v210 OR how to take full adb logs when the device is "not authorized" in adb devices, it would be of great help

P-Zs commented 4 years ago

I have same device. I checked the latest version (v222) and it is still stuck at boot animation. No Magisk. Bootloader opened.

logcat output is atached.

logcat-Alldocube_M5XS-AOSP_10.0_v222.7z.zip

codergenius1 commented 4 years ago

How did you get the logcat without adb authorized?

On Thu, Sep 17, 2020, 5:38 AM P-Zs notifications@github.com wrote:

I have same device. I checked the latest version (v222) and it is still stuck at boot animation. No Magisk. Bootloader opened.

logcat output is atached.

logcat-Alldocube_M5XS-AOSP_10.0_v222.7z.zip https://github.com/phhusson/treble_experimentations/files/5235494/logcat-Alldocube_M5XS-AOSP_10.0_v222.7z.zip

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/974#issuecomment-693730667, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6WLPVW4GNRPZDD5AVJXTTSGFHRRANCNFSM4JVXYJLA .

P-Zs commented 4 years ago

I get logcat when adb was authorized. I experienced same adb unauthorized issue when first tested GSI builds on this tablet. (don't remember what was the first situation whit this build)

When got adb unauthorized message, I flashed back the stock system image. I wiped the data partition, started andriod and made the minimal configuration. (No google profile) Enabled developer mode, and usb debugging I wired the tablet to PC, and enabled the USB debug permanently for my pc. Then reflashed this GSI image to system, but did not wiped the data partition. When I started the tablet, I was able to connect with adb. I booted to recovery and wiped the data partition. When restarted the tablet, the adb connection was still authorized. (adb root also worked)

Now I don't understand why the adb connection worked second time or why didn't worked earlier...

P-Zs commented 4 years ago

I had some spare time, and flashed the v222 again. Before flashing through fastboot mode I booted into recovery and done a factory reset. After flash adb works out of the box. Don't know why your device is unauthorized. I flashed this file: system-quack-arm64-aonly-gapps.img Still stuck at bootanimation

Just to try GSI I flashed AOSP 9.0 v121 With this image tablet works well.

Maybe You can try to flash back the stock android image with SP Flash Tool and retry the GSI flash process.

P-Zs commented 4 years ago

I found other threads with similar issue, and error in the logcat. (library "libstdc++.so" not found) I flashed v222 again and copied libstdc++.so to vendor partition and the system started sucessfuly.

I used these commands: adb root adb remount adb shell cp /system/lib/vndk-26/libstdc++.so /vendor/lib/

The system is now running, but Bluetooth isn't working. Update: Bluetooth is now working after this command: setprop persist.sys.bt.unsupport.stdfeatures 000001 but I found other problem: Screen Cast is not working to smart TV. It can not find any remote screen (This works with 8.0 stock image)

If you can't adb with AOSP 10, then you can try to copy libstdc++.so from stock image before flashing AOSP.

houhouwei commented 3 years ago

Hello, can AOSP 10 work now?

isaac84 commented 3 years ago

I just got one of these devices. Looking at the latest releases. AOSP 11.0 v300.j looks promising;

Fix boot on some vndk 26 devices (Include libstdc++.so in vndk-sp for mali EGL)

So a 'released' version after that might be worth a try. I still have to create a backup rom etc before I try and flash it myself.

isaac84 commented 3 years ago

I tried the latest version AOSP 11.0 v302 tonight. It boots to the welcome page after the first flash. Then crashes and gets stuck on the Android logo on the reboot. I will attach a logcat file tomorrow.

phhusson commented 3 years ago

This is a known issue (that I hoped was fixed recently but well): you need to setup a lock screen with "secure boot" enabled when you setup the lock screen

Le sam. 13 mars 2021 à 10:31, Isaac Gale @.***> a écrit :

I tried the latest version AOSP 11.0 v302 tonight. It boots to the welcome page after the first flash. Then crashes and gets stuck on the Android logo on the reboot. I will attach a logcat file tomorrow.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/974#issuecomment-798024328, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OXYCL3JTA2CR2DHYFTTDMWGNANCNFSM4JVXYJLA .

isaac84 commented 3 years ago

Thanks for the reply @phhusson. I'll have to do that on the oem system image because it crashes before I even get to create an account and set the device up. Is that what you mean?

isaac84 commented 3 years ago

Here is the logcat file post welcome screen crash, where it's stuck on the 'android' logo m5xs.txt.zip

I'm no Android expert but this doesn't look good.

03-01 01:20:56.757 1976 1976 E Zygote : System zygote died with exception 03-01 01:20:56.757 1976 1976 E Zygote : java.lang.NullPointerException: Attempt to invoke interface method 'void android.os.IInstalld.dexopt(java.lang.String, int, java.lang.String, java.lang.String, int, java.lang.String, int, java.lang.String, java.lang.String, java.lang.String, java.lang.String, boolean, int, java.lang.String, java.lang.String, java.lang.String)' on a null object reference 03-01 01:20:56.757 1976 1976 E Zygote : at com.android.internal.os.ZygoteInit.performSystemServerDexOpt(ZygoteInit.java:669) 03-01 01:20:56.757 1976 1976 E Zygote : at com.android.internal.os.ZygoteInit.handleSystemServerProcess(ZygoteInit.java:511) 03-01 01:20:56.757 1976 1976 E Zygote : at com.android.internal.os.ZygoteInit.forkSystemServer(ZygoteInit.java:799) 03-01 01:20:56.757 1976 1976 E Zygote : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:920)

isaac84 commented 3 years ago

So I enabled 'secure boot' on the oem system image and then dirty flashed v302 over the top. The tablet would boot and I could see a heap of flickering 'app not responding' dialogs popping up. Then the tablet would go into a reboot loop. See new logcat attached if curious. dirtyflashwithsecureboot.txt.zip

isaac84 commented 3 years ago

I wiped the cache, but I am using the stock recovery and there wasn't an option to wipe the dalvik cache.

phhusson commented 3 years ago

Wipe the whole data partition

14 mars 2021 03:42:40 Isaac Gale @.***>:

I wiped the cache, but I am using the stock recovery and there wasn't an option to wipe the dalvik cache.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub[https://github.com/phhusson/treble_experimentations/issues/974#issuecomment-798822698], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAA4OVKQSO4AGUD6WKA56LTDQPCBANCNFSM4JVXYJLA]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADgAAAA4CAYAAACohjseAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAjSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAADApwExOAABR9ZGcwAAAABJRU5ErkJggg==###24x24:true###][Image de pistage][https://github.com/notifications/beacon/AAAA4OXCYXDKT5YVI4OGKQTTDQPCBA5CNFSM4JVXYJLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF6ORCKQ.gif]

isaac84 commented 3 years ago

Wipe the whole data partition 14 mars 2021 03:42:40 Isaac Gale @.***>: … I wiped the cache, but I am using the stock recovery and there wasn't an option to wipe the dalvik cache. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub[#974 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAA4OVKQSO4AGUD6WKA56LTDQPCBANCNFSM4JVXYJLA]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADgAAAA4CAYAAACohjseAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAjSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAADApwExOAABR9ZGcwAAAABJRU5ErkJggg==###24x24:true###][Image de pistage][https://github.com/notifications/beacon/AAAA4OXCYXDKT5YVI4OGKQTTDQPCBA5CNFSM4JVXYJLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF6ORCKQ.gif]

@phhusson thanks, but if I do that on the first clean boot it will reboot loop before I get to create an account and enable secure boot. I'm new to flashing GSIs so excuse me if I am misunderstanding what you are saying.

codergenius1 commented 3 years ago

Did you flashed this stock firmware ? https://www.alldocube.com/en/firmware/alldocube-m5xst1006xsk-firmware-download/

On Mon, Mar 15, 2021 at 2:52 AM Isaac Gale @.***> wrote:

Wipe the whole data partition 14 mars 2021 03:42:40 Isaac Gale @.***>: … <#m9043754449140958122> I wiped the cache, but I am using the stock recovery and there wasn't an option to wipe the dalvik cache. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub[#974 (comment) https://github.com/phhusson/treble_experimentations/issues/974#issuecomment-798822698], or unsubscribe[ https://github.com/notifications/unsubscribe-auth/AAAA4OVKQSO4AGUD6WKA56LTDQPCBANCNFSM4JVXYJLA]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADgAAAA4CAYAAACohjseAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAjSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAADApwExOAABR9ZGcwAAAABJRU5ErkJggg==###24x24:true###][Image de pistage][ https://github.com/notifications/beacon/AAAA4OXCYXDKT5YVI4OGKQTTDQPCBA5CNFSM4JVXYJLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF6ORCKQ.gif ]

@phhusson https://github.com/phhusson thanks, but if I do that on the first clean boot it will reboot loop before I get to create an account and enable secure boot. I'm new to flashing GSIs so excuse me if I am misunderstanding what you are saying.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/974#issuecomment-798982258, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6WLPUUDKFV26IXXKOE7MLTDUSKNANCNFSM4JVXYJLA .

isaac84 commented 3 years ago

@codergenius1 no but my tablet was completely stock until I unlocked the boot loader. So I'm not on the latest firmware you linked above, just what was shipped with the device. I backed up the original system.img using spflash before I tried to flash v302. There is no change log for the above firmware so no idea what they have fixed or broken :D

I'm currently using ASOP 10 v222 and after patching in libstdc++.so and adding setprop persist.sys.bt.unsupport.stdfeatures 000001 to /system/bin/phh-on-boot.sh so its applied every time everything seems to be working great. Including casting to my smart TV.

Are you on ASOP 11 now?

codergenius1 commented 3 years ago

Installed v302 on latest firmware (as per my previous post).

Could not boot past logo. Attached is the logcat.

On Thu, 18 Mar, 2021, 12:28 pm Isaac Gale, @.***> wrote:

@codergenius1 https://github.com/codergenius1 no but my table was completely stock until I unlocked the boot loader. So I'm not on the latest firmware you linked above, just what was shipped with the device. I backed up the original system.img using spflash before I tried to flash v302. There is no change log for the above firmware so no idea what they have fixed or broken :D

I'm currently using ASOP 10 v222 and after patching in libstdc++.so and adding setprop persist.sys.bt.unsupport.stdfeatures 000001 to /system/bin/phh-on-boot.sh so its applied every time everything seems to be working great. Including casting to my smart TV.

Are you on ASOP 11 now?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/974#issuecomment-801680985, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6WLPRILWGM2IGHTBTV5WDTEGQARANCNFSM4JVXYJLA .

C:\Program Files (x86)\Minimal ADB and Fastboot>adb logcat --------- beginning of system 03-23 16:08:03.387 347 347 I vold : Vold 3.0 (the awakening) firing up 03-23 16:08:03.390 347 347 D vold : Detected support for: ext4 vfat

C:\Program Files (x86)\Minimal ADB and Fastboot>adb logcat

C:\Program Files (x86)\Minimal ADB and Fastboot>adb logcat

C:\Program Files (x86)\Minimal ADB and Fastboot>adb logcat