Develop Bugs

[SOLVED] 4.0.3 AOSP build stuck at google logo. Kernel problem?

Hey guys,
i have a problem when building 4.0.3 from source. When i flash the fresh compiled
OTA package to my device, the device ends in a bootloop stuck at the google logo.
Logcat says:
Code:
I/SystemServer( 238): Power Manager
I/SystemServer( 238): Activity Manager
I/ActivityManager( 238): Memory class: 64
I/SurfaceFlinger( 251): SurfaceFlinger is starting
I/SurfaceFlinger( 251): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/IMGSRV ( 251): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086860 (Bad address).
E/IMGSRV ( 251): :0: OpenServices: PVRSRVBridgeCall failed.
E/IMGSRV ( 251): :0: PVRSRVConnect: Unable to open connection.
E/IMGSRV ( 251): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 251): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open framebuffer HAL (Not a typewriter)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 251): Display subsystem failed to initialize. check logs. exiting...
I/ServiceManager( 109): service 'sensorservice' died
I/ServiceManager( 109): service 'power' died
I/ServiceManager( 109): service 'entropy' died
D/AndroidRuntime( 259):
D/AndroidRuntime( 259): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 259): CheckJNI is OFF
I don't know whats going wrong. Can it be a kernel problem? I have tried different 4.0.3 kernels from the dev section, but the result is the same.
The device is a GSM device with PRIMEKK15 unlocked bootloader and I9250XXKK6 baseband.
After pulling the latest 4.0.3 sources with repo and setting up the proprietary files i'have compiled the system without errors:
Code:
~/android/4.0.3$ . build/envsetup.sh
~/android/4.0.3$ lunch full_maguro-userdebug
~/android/4.0.3$ make -j4 otapackage
I really don't understand what i am doing wrong ...
Thanks for any suggestions or answers.

i got this problem when I updated my phone using fastboot.
for me, it was an application installed from market. after wipe everything and redo the flash procedure, everything was fine.
don't know if it is the same problem here.

Did you pull in the proprietary files needed for the build?

At least you've got to the boot animation, my ROM fails at the flashing with a status 7 error mentioning the boot.img

PaulW21781 said:
Did you pull in the proprietary files needed for the build?
Click to expand...
Click to collapse
with ./extract-files.sh .correct?

PaulW21781 said:
Did you pull in the proprietary files needed for the build?
Click to expand...
Click to collapse
Yes, the files are pulled from the device ( if you mean the extract_files.sh from the device folder), compilation finishes without errors.
No boot animation, nothing...
Sent from my Galaxy Nexus using XDA App

Now at this point too, bootloops all the time. I think the code is ****ed

Ok, dmesg gave me this:
Code:
<6>[ 5.367248] PVR: Installing MISR with cookie c0833f74
<6>[ 5.367828] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c79f5700
<6>[ 5.368255] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from c8be0000
<6>[ 5.368469] PVR: SysFinalise: Version string: SGX revision = 1.2.0
<6>[ 5.369171] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision (785978)/device DDK revision (780209).
<6>[ 5.369537] PVR_K:(Error): PVRSRVFinaliseSystem: Failed PVRSRVDevInitCompatCheck call (device index: 0) [449, drivers/gpu/pvr/pvrsrv.c]
<6>[ 5.370025] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
<6>[ 5.552337] max17040 4-0036: online = 1 vcell = 4007500 soc = 77 status = 1 health = 1 temp = 340 charger status = 0
<3>[ 5.643005] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns1
<3>[ 5.643737] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns2
<3>[ 5.644287] init: sys_prop: permission denied uid:1001 name:net.rmnet1.gw
<3>[ 5.645263] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns1
<3>[ 5.645812] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns2
<3>[ 5.646484] init: sys_prop: permission denied uid:1001 name:net.rmnet2.gw
<6>[ 5.707031] [MODEM_IF] misc_open : umts_boot0
<6>[ 5.707153] omap_hsi omap_hsi.0: HSI clock is now 96000000
<6>[ 5.723510] omap_hsi omap_hsi.0: Entering RX wakeup in 3 wires mode (no CAWAKE)
<6>[ 5.723602] [MODEM_IF] xmm6260_off()
<6>[ 5.723724] [MODEM_IF] xmm6260_on()
<6>[ 5.724456] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 5.724548] [MODEM_IF] umts_ipc0 state changed: OFFLINE
<6>[ 5.835540] [MODEM_IF] PA EVENT : reset =1, pa=0
<6>[ 5.979125] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx addr 0x3c
<6>[ 5.980194] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
<6>[ 6.087188] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
<3>[ 6.094604] init: untracked pid 118 exited
Anyone knows how to fix this issue?

Try reflashing the boot.img created by your build..

Did you also install the binaries from the google http://code.google.com/android/nexus/drivers.html#maguro into your AOSP source before building?
I built my own AOSP rom too, but haven't tried it yet.
also
Cleaning up when adding proprietary binaries
In order to make sure that the newly installed binaries are properly taken into account after being extracted, the existing output of any previous build needs to be deleted with
$ make clobber
Click to expand...
Click to collapse
http://source.android.com/source/building-devices.html
sorry if you did all this - I'm a noob to ASOP building

Did you wipe the device before installing the rom and kernel?

Luxferro said:
Did you also install the binaries from the google http://code.google.com/android/nexus/drivers.html#maguro into your AOSP source before building?
Click to expand...
Click to collapse
Hey man, that was the problem! Thank you very much... I didn't knew that such libraries exist for 4.0.3.
After installing the binaries and recompiling the phone boots up. Thanks again, also to all the people who tried to help me.

m0rph3us said:
Hey man, that was the problem! Thank you very much... I didn't knew that such libraries exist for 4.0.3.
After installing the binaries and recompiling the phone boots up. Thanks again, also to all the people who tried to help me.
Click to expand...
Click to collapse
No problem. Glad I can help
I guess that hopefully means my build would work too if I ever tried it. Was hoping official 4.0.3 OTA would be out by now. I might just have to try my build too.
Sent from my Galaxy Nexus using Tapatalk

I ran the script under /device/samsung/toro/
is that the correct place to run it, or should I be running it somewhere else?
Nevermind, I'm dumb. I read the post and got it now lol

I'm having the same issue, except for the toro (CDMA/LTE) galaxy nexus. Are these steps in the right order?
step 0: make clobber, step 1: run the extract-imgtec-toro.sh and make clobber, step 2: extract-files.sh, step 3: build/envsetup.sh, step 4: make?

jab416171 said:
I'm having the same issue, except for the toro (CDMA/LTE) galaxy nexus. Are these steps in the right order?
step 0: make clobber, step 1: run the extract-imgtec-toro.sh and make clobber, step 2: extract-files.sh, step 3: build/envsetup.sh, step 4: make?
Click to expand...
Click to collapse
you don't need to excessively run make clobber. all it really does is delete the out/ directory.
Here's how I was able to get a fully functional build ($ANDROID_SOURCE is your build dir):
0) make clobber; # just for the initial cleansing
1) cd $ANDROID_SOURCE/device/samsung/toro && ./extract-files.sh
2) run extract-imgtec-toro.sh OUTSIDE of your build directory (in a temporary location)
3) copy the contents of $TEMPDIR/vendor/imgtec/toro/proprietary/* into $ANDROID_SOURCE/vendor/samsung/toro/proprietary/
4) cd $ANDROID_SOURCE; . build/envsetup.sh
5) lunch #pick your desired toro build. Probably full_toro-userdebug
6) make
The reality is that extract-files.sh does everything well, except it doesn't include the gpu drivers (so we copy them manually). The make files that extract-files.sh creates DOES reference the gpu drivers, they're just not extracted by the script.
Messing with extract-imgtec-toro.sh will give you make files that don't reference any of the other binaries. Your image will boot, but won't have much else working.
Good luck!

Thanks for the quick reply. Here's my script, let me know if you see any errors.
The reason I did make clobber after the extract-imgtec-toro was because the documentation on google's site recommended doing that.
export TOP=/home/jab416171/android/dev/aosp
export GNEXTEMP=/home/jab416171/gnexproprietaryfiles
cd $TOP
repo sync
make clobber
adb wait-for-device
cd $TOP/device/samsung/toro && ./extract-files.sh
cd $GNEXTEMP && ./extract-imgtec-toro.sh
cp $GNEXTEMP/vendor/imgtec/toro/proprietary $TOP/vendor/samsung/toro/proprietary/
cd $TOP
source build/envsetup.sh
lunch full_toro-userdebug
make -j5

jab416171 said:
Thanks for the quick reply. Here's my script, let me know if you see any errors.
The reason I did make clobber after the extract-imgtec-toro was because the documentation on google's site recommended doing that.
export TOP=/home/jab416171/android/dev/aosp
export GNEXTEMP=/home/jab416171/gnexproprietaryfiles
cd $TOP
repo sync
make clobber
adb wait-for-device
cd $TOP/device/samsung/toro && ./extract-files.sh
cd $GNEXTEMP && ./extract-imgtec-toro.sh
cp $GNEXTEMP/vendor/imgtec/toro/proprietary $TOP/vendor/samsung/toro/proprietary/
cd $TOP
source build/envsetup.sh
lunch full_toro-userdebug
make -j5
Click to expand...
Click to collapse
I think your cp needs a '/*' after the first proprietary. The object is to copy the contents of one proprietary directory into the proprietary directory of another. Unless I'm mistaken, your cp will copy the proprietary source folder into the proprietary destination folder resulting in a $TOP/vendor/samsung/toro/proprietary/proprietary. Either that or error out because you specified to cp a dir without a -R.
You should certainly run a make clobber after extracting new binaries if you have files from a previous build still lying around. if you've already cleaned it out, then its just redundant (and not hurting anything).
Otherwise it looks good to me! Good luck!

Makes sense on the cp command. I haven't actually run the script yet, and thanks for taking your time to overlook it.
And do I need to run extract-files and extract-imgtec-toro *every time* I want to do a build, or can I just extract them once, and copy them from another location on my drive, or will the files they extract just stay in the repository?

jab416171 said:
Makes sense on the cp command. I haven't actually run the script yet, and thanks for taking your time to overlook it.
And do I need to run extract-files and extract-imgtec-toro *every time* I want to do a build, or can I just extract them once, and copy them from another location on my drive, or will the files they extract just stay in the repository?
Click to expand...
Click to collapse
Just once. I usually just tar up my vendor/samsung/toro directory and keep the tar in a safe location. No more extractions once you have it.

how to fix errors in flyme6 patchrom

I'm trying to build a flyme6 ROM based on JUI, but there are some errors i can't fix. It seems that register v1 has a wrong type according to log. but i dont know where the method forEachRemaining locate. i tried $grep -r forEachRemaining but find nothing. what can i do to fix the errors?
device: http://www.github.com/jmxl/flyme_patchrom_device_cp_ares
here are the logs:
Code:
01-01 16:03:30.898 908 908 W dex2oat : Verification error in void java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.forEachRemaining(java.util.function.DoubleConsumer)
01-01 16:03:30.898 908 908 W dex2oat : void java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.forEachRemaining(java.util.function.DoubleConsumer) failed to verify: void java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.forEachRemaining(java.util.function.DoubleConsumer): [0x1A] invalid argument count (5) exceeds outsSize (3)
01-01 16:03:30.898 908 908 W dex2oat :
01-01 16:03:30.898 908 908 W dex2oat : Verification error in boolean java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.tryAdvance(java.util.function.DoubleConsumer)
01-01 16:03:30.898 908 908 W dex2oat : boolean java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.tryAdvance(java.util.function.DoubleConsumer) failed to verify: boolean java.util.concurrent.ThreadLocalRandom$RandomDoublesSpliterator.tryAdvance(java.util.function.DoubleConsumer): [0x18] invalid argument count (5) exceeds outsSize (3)
01-01 16:03:30.898 908 908 W dex2oat :
01-01 16:03:30.899 908 908 W dex2oat : Verification error in void java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.forEachRemaining(java.util.function.IntConsumer)
01-01 16:03:30.899 908 908 W dex2oat : void java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.forEachRemaining(java.util.function.IntConsumer) failed to verify: void java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.forEachRemaining(java.util.function.IntConsumer): [0x1A] register v1 has type Integer but expected Double (Low Half)
01-01 16:03:30.899 908 908 W dex2oat :
01-01 16:03:30.899 908 908 W dex2oat : Verification error in boolean java.util.concurrent.ThreadLocalRandom$RandomIntsSpliterator.tryAdvance(java.util.function.IntConsumer)

With all due respect, flyme_LEX720_rogue_6.7.6.30R-beta.zip already exist. Why not just use it?
You probably have a non-printable character in there somewhere which is breaking it. Retype the code manually

Unable to boot any GSI, i get bootloop

Hi,
i have unlocked bootloader and flashed official twrp, everything works, but i wanted to try some GSI so flashed havoc os 2.0 pie and got a bootloop with this error:
Code:
--------- beginning of system
04-16 11:44:38.751 596 596 I vold : Vold 3.0 (the awakening) firing up
04-16 11:44:38.752 596 596 V vold : Detected support for: exfat ext4 ntfs vfat
04-16 11:44:38.757 596 596 D vold : Tearing down stale mount /mnt/phh
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop3: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop0: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop7: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop1: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop6: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop4: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop5: No such device or address
04-16 11:44:38.759 596 596 I vold : [libfs_mgr]dt_fstab: Skip disabled entry for partition system
04-16 11:44:38.762 596 596 D vold : VoldNativeService::start() completed OK
04-16 11:44:38.763 596 600 D vold : e4crypt_init_user0
04-16 11:44:38.764 596 600 D vold : e4crypt_prepare_user_storage for volume null, user 0, serial 0, flags 1
04-16 11:44:38.764 596 600 D vold : Preparing: /data/vendor_de
04-16 11:44:38.764 596 600 E cutils : Failed to mkdir(/data/vendor_de): Read-only file system
04-16 11:44:38.764 596 600 E vold : Failed to prepare /data/vendor_de: Read-only file system
04-16 11:44:38.764 596 600 D vold : Preparing: /data/system/users/0
04-16 11:44:38.764 596 600 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
04-16 11:44:38.764 596 600 E vold : Failed to prepare /data/system/users/0: No such file or directory
04-16 11:44:38.764 596 600 E vold : Failed to prepare user 0 storage
04-16 11:44:38.780 601 601 I /system/bin/tzdatacheck: timezone distro dir /data/misc/zoneinfo/current does not exist. No action required.
04-16 11:44:38.784 596 599 I vold : Found disk at /devices/soc/7864900.sdhci/mmc_host/mmc1/mmc1:aaaa/block/mmcblk1 but delaying scan due to secure keyguard
04-16 11:44:38.985 610 610 I BOOT : MSM target '', SoC 'QRD', HwID '293', SoC ver '65536'
04-16 11:44:38.998 611 611 W DRM_BOOT: file: '/sys/module/drm/parameters/vblankoffdelay' or perms doesn't exist
04-16 11:44:39.542 675 675 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
--------- beginning of crash
04-16 11:44:39.630 701 701 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
04-16 11:44:39.631 714 714 E getcolorid: tp info = 31373201d1533101
04-16 11:44:39.631 714 714 E getcolorid:
04-16 11:44:39.631 714 714 E getcolorid: colorid = 32
04-16 11:44:39.644 676 676 I [email protected]/: [email protected]/backup: Hal starting main loop...
04-16 11:44:39.645 676 676 I [email protected]/: [email protected]/backup Hal is starting up...
04-16 11:44:39.647 717 717 I lowmemorykiller: Using in-kernel low memory killer interface
04-16 11:44:39.652 676 676 W ServiceManagement: Can't efficiently wait for [email protected]::IHealth/default, because we are called from the only binder thread in this process.
04-16 11:44:39.659 707 707 I irsc_util: Starting irsc tool
04-16 11:44:39.660 708 708 I rmt_storage: Shared memory initialised successfully.
04-16 11:44:39.660 708 708 I rmt_storage: Registering modemst1: 0x4a /boot/modem_fs1
04-16 11:44:39.660 708 708 I rmt_storage: Registering modemst2: 0x4b /boot/modem_fs2
04-16 11:44:39.660 708 708 I rmt_storage: Registering fsc: 0xff /boot/modem_fsc
04-16 11:44:39.660 708 708 I rmt_storage: Registering fsg: 0x58 /boot/modem_fsg
04-16 11:44:39.660 708 708 I rmt_storage: 4 GPT partitions found
04-16 11:44:39.661 708 708 I rmt_storage: Capset success!
04-16 11:44:39.666 707 707 I irsc_util: Num of entries:292
04-16 11:44:39.668 676 676 I ServiceManagement: getService: Trying again for [email protected]::IHealth/default...
04-16 11:44:39.668 707 707 I irsc_util: Ending irsc tool
04-16 11:44:39.669 676 676 W ServiceManagement: Waiting one second for [email protected]::IHealth/default
04-16 11:44:39.676 712 712 D PcbaConfigSet: Before, get, [ro.boot.hwversion=], [ro.boot.hwc=], [ro.boot.hwlevel=], [ro.product.cert=], [ro.product.name=treble_arm64_bvN]
Patched boot din't worked.
So, i reflashed with ./flash_all and tried again, flashing also magisk, this time asked me for password, hitted cancel and then selected factory reset.. stuck in twrp
Tried other combos with always flashing stock rom but nothing worked, every time i got bootscreen i get bootloop with the error above(tried also pixel experience, same issue).
This is my first device with treble so maybe i'm a bit noob, someone could help me?

Have you tried the GSI ROM posted in this forum? Also try to flash the stock ROM and see if you didn't broke something.
Does havok has A/B partition support?

SnoopDoggyStyleDogg said:
Have you tried the GSI ROM posted in this forum?
Click to expand...
Click to collapse
Yes, ive tried also pixel experience P because a thread said it's totally compatible.
SnoopDoggyStyleDogg said:
Also try to flash the stock ROM and see if you didn't broke something.
Click to expand...
Click to collapse
After doing exactly the same operation?
I've tried to switch slot(to the one that contain stock) but I got bootloop, so yes, I think the process I've done broke something.
SnoopDoggyStyleDogg said:
Does havok has A/B partition support?
Click to expand...
Click to collapse
Yes, I've downloaded arm64 a/b

Ok, i've managed to install havoc waiting some minutes and ignoring the error, these are the issues i've found:
-camera don't work(even with magisk mi a2 camera)
-torch don't work
-notch not recognised
-internal storage showed as 8 gb
These are common to all GSI or only to havoc?

mac12m99 said:
Ok, i've managed to install havoc waiting some minutes and ignoring the error, these are the issues i've found:
-camera don't work(even with magisk mi a2 camera)
-torch don't work
-notch not recognised
These are common to all GSI or only to havoc?
Click to expand...
Click to collapse
try and enable all permision for the camera app from settings if the error says can't connect to camera
yes notch is an issue on all GSI I've been trying so far, I've been unable to find a way to add a padding to the statusbar so the icon gets cut on the corner,

Jordan~Kurniawan said:
try and enable all permision for the camera app from settings if the error says can't connect to camera
Click to expand...
Click to collapse
Tried but nothing, i have black screen btw, no error is displayed
Jordan~Kurniawan said:
yes notch is an issue on all GSI I've been trying so far, I've been unable to find a way to add a padding to the statusbar so the icon gets cut on the corner,
Click to expand...
Click to collapse
As i've read, notch info is inside build.prop, so maybe copying notch info from stock do the trick
Do you know some 9.0 gsi that are mostly working?

mac12m99 said:
Tried but nothing, i have black screen btw, no error is displayed
As i've read, notch info is inside build.prop, so maybe copying notch info from stock do the trick
Do you know some 9.0 gsi that are mostly working?
Click to expand...
Click to collapse
maybe, for what I've understand we need to manually edit the system ui apk
I'm only trying the 8.1 GSI because i think that what would work the most
I'll try to look into that notch thing and ask some devs
because i haven't read anyone talk about it

Jordan~Kurniawan said:
maybe, for what I've understand we need to manually edit the system ui apk
Click to expand...
Click to collapse
ah ok
Jordan~Kurniawan said:
I'm only trying the 8.1 GSI because i think that what would work the most
Click to expand...
Click to collapse
trying RR Oreo..
Jordan~Kurniawan said:
I'll try to look into that notch thing and ask some devs
because i haven't read anyone talk about it
Click to expand...
Click to collapse
Ok thanks:good:
What about internal storage space issue?
PS
i've found that wiping data from twrp or fastboot cause always a bootloop, the right way is to flash userdata.img from stock rom.

After trying some roms i've understood that:
-only P roms support notch correctly, but all P roms have camera and torch not working(and probably wrong storage space)
-O roms work perfectly but notch is not recognised at all, it's like to have a fullscreen device
I don't know how, but 1 time i managed to get havoc os camera working, unfortunally i wanted to flash twrp to get gapps but i've messed up...
Maybe security patch matter when installing gsi? I'm not sure but i think i was on september update.

mac12m99 said:
After trying some roms i've understood that:
-only P roms support notch correctly, but all P roms have camera and torch not working(and probably wrong storage space)
-O roms work perfectly but notch is not recognised at all, it's like to have a fullscreen device
I don't know how, but 1 time i managed to get havoc os camera working, unfortunally i wanted to flash twrp to get gapps but i've messed up...
Maybe security patch matter when installing gsi? I'm not sure but i think i was on september update.
Click to expand...
Click to collapse
i read somewhere that we need to set SElinux to permissive to make the camera work (idk why) gonna try this soon, you can test this if you have the time

Jordan~Kurniawan said:
i read somewhere that we need to set SElinux to permissive to make the camera work (idk why) gonna try this soon, you can test this if you have the time
Click to expand...
Click to collapse
In fact i Remember to have launched "setenforce 0"
I Will try in the weekend because in these days i dont have much time.
Please tell me if you Will try first

mac12m99 said:
In fact i Remember to have launched "setenforce 0"
I Will try in the weekend because in these days i dont have much time.
Please tell me if you Will try first
Click to expand...
Click to collapse
do you have any idea about vendor partition?
because some say that not every vendor put everything in there, something crucial like camera lib can still be put on system by the vendor (in this case its Xiaomi) thats why when we flash gsi somethings may not work
because the vendor partition (sometimes) does not contain everything we need
edit:
I've been reading few articles about treble and gsi.
apparently, we won't be able to use camera and maybe other things on android 9.0 if we don't have the source for it. it would take a serious hacking involved to make android 9.0 work with 8.1 vendor image.
so our only option is to wait for a developer to work on 9.0 gsi and patch for our device
but it's maybe a waste of time because our device are promised to have at least 2 major android updates
android 9 and 10 and devs probably would be better off using the official firmware and extract blobs from it rather than hacking an oreo libs to work with android 9

Jordan~Kurniawan said:
do you have any idea about vendor partition?
because some say that not every vendor put everything in there, something crucial like camera lib can still be put on system by the vendor (in this case its Xiaomi) thats why when we flash gsi somethings may not work
because the vendor partition (sometimes) does not contain everything we need
Click to expand...
Click to collapse
Can be, i will look into this weekend, but oreo gsi works so i don't think.
Jordan~Kurniawan said:
I've been reading few articles about treble and gsi.
apparently, we won't be able to use camera and maybe other things on android 9.0 if we don't have the source for it. it would take a serious hacking involved to make android 9.0 work with 8.1 vendor image.
so our only option is to wait for a developer to work on 9.0 gsi and patch for our device
but it's maybe a waste of time because our device are promised to have at least 2 major android updates
android 9 and 10 and devs probably would be better off using the official firmware and extract blobs from it rather than hacking an oreo libs to work with android 9
Click to expand...
Click to collapse
Consider that in this thread a lot of people reported that camera work(and someone that don't).
I think all depends on phh patches version that the build use, but thats the first treble device i own so i don't know much about treble, sorry .

[ROM][UNOFFICIAL] LineageOS 14.1 for SM-T113NU

This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Offline charging
Prerequisites:
TWRP version 3.0.2 (https://drive.google.com/file/d/1Hcc1T1-iUEo1ATpPf_Kcu3vXqGR3Boq_/view)
Galaxy Tab E SM-T113NU (reported by some users that works on T116 models, but this is not guaranteed)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Latest Image build:
https://drive.google.com/file/d/1xEq9lttRw752KqIwXnk5ccUFmLJe4BSJ/view
Source links:
# Local manifest
https://github.com/pstglia/local_manifests/tree/T113NU_COM_A_MAO_NO_BOLSO
# Framework-native
https://github.com/pstglia/frameworks-native/tree/T113NU_COM_A_MAO_NO_BOLSO
# Kernel
https://github.com/pstglia/linux/tree/T113NU_COM_A_MAO_NO_BOLSO
# device/vendor
https://github.com/pstglia/android_device_samsung_scx35-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_vendor_samsung_scx30g-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_device_samsung_scx30g-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_vendor_samsung_core33g/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_device_samsung_core33g/tree/T113NU_COM_A_MAO_NO_BOLSO
# frameworks/base (the commit that hacks camera count return to 0 is here)
https://github.com/pstglia/platform_frameworks_base/tree/T113NU_COM_A_MAO_NO_BOLSO
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
(My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note 1:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Note 2:
If you face a bootloop, you can try formatting your efs partition as described bellow (AT YOUR OWN RISK!)
https://forum.xda-developers.com/showpost.php?p=79995765&postcount=42
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17

What do you need to get a working camera? I have an actual Samsung SM-T113NU
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse

MrLinDowsMac said:
What do you need to get a working camera? I have an actual Samsung SM-T113NU
Click to expand...
Click to collapse
Hi,
1) I'd need spare time to find a way to make it work.
2) more knowledge would be needed. To build this image, I had basically to adapt Samsung kernel to met 7.1 requirements (I basically cherry-picked commits from remilia15 - SM-G360H) and some other minor changes.
Camera probably requires advanced coding, which is a bit far from my current skills. Enabling it causes crashes during components startup (see bellow):
Code:
04-19 22:37:01.036 227 769 I SprdCameraHardware: getPropertyAtv:0
04-19 22:37:01.036 227 769 I SprdCameraHardware: getNumberOfCameras:2
04-19 22:37:01.036 227 769 I CameraService: disconnect: Disconnected client for camera 0 for PID 227
04-19 22:37:01.036 227 769 E CameraService: initializeShimMetadata: Error initializing shim metadata: Status(-8): '3: connectHelper:928: Illegal argument to HAL module for camera "0"'
04-19 22:37:01.038 585 585 E System : ******************************************
04-19 22:37:01.038 227 909 E isp-video: ISP_RAW: id:0x00, 00927 line, ispserver_thread : ISP_TOOL:isp-video server version 1.0
04-19 22:37:01.039 227 909 E isp-video: ISP_RAW: id:0x00, 00965 line, ispserver_thread : ISP_TOOL:log server waiting client dail in...
04-19 22:37:01.040 585 585 E System : ************ Failure starting system services
04-19 22:37:01.040 585 585 E System : java.lang.RuntimeException: Failed to boot service com.android.server.retaildemo.RetailDemoModeService: onBootPhase threw an exception during phase 600
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:145)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer$2.run(SystemServer.java:1538)
04-19 22:37:01.040 585 585 E System : at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:13591)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1466)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.run(SystemServer.java:368)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.main(SystemServer.java:237)
04-19 22:37:01.040 585 585 E System : at java.lang.reflect.Method.invoke(Native Method)
04-19 22:37:01.040 585 585 E System : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
04-19 22:37:01.040 585 585 E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
04-19 22:37:01.040 585 585 E System : Caused by: java.lang.IllegalArgumentException: connectHelper:928: Illegal argument to HAL module for camera "0"
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:694)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:778)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:140)
04-19 22:37:01.040 585 585 E System : at com.android.server.retaildemo.RetailDemoModeService.getCameraIdsWithFlash(RetailDemoModeService.java:492)
04-19 22:37:01.040 585 585 E System : at com.android.server.retaildemo.RetailDemoModeService.onBootPhase(RetailDemoModeService.java:569)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:143)
04-19 22:37:01.040 585 585 E System : ... 8 more
04-19 22:37:01.040 585 585 E System : Caused by: android.os.ServiceSpecificException: connectHelper:928: Illegal argument to HAL module for camera "0"
04-19 22:37:01.040 585 585 E System : at android.os.Parcel.readException(Parcel.java:1706)
04-19 22:37:01.040 585 585 E System : at android.os.Parcel.readException(Parcel.java:1645)
04-19 22:37:01.040 585 585 E System : at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:404)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:765)
Maybe sources under hardware/sprd/libcamera should be changed in order to make it work...
3) A device to test. The one I was using was borrowed from a friend, but already returned.
In any case, all source code I changed is available on github (check for pstglia on github - repository "local_manifests" maps all the changes (except platform_frameworks_base, which requires the last 2 commits from branch "T113NU_COM_A_MAO_NO_BOLSO".

Muito obrigado pela ROM
Falei com vc lá pelo YouTube e agradeço novamente pela rom. O tablet ficou novo em folha. Continue com seu ótimo trabalho ?

Heyyy, how you've made this custom rom?
I'm trying to build that for my sm-t280, and all instructions doesn't ever exist. if you gimme instructions to build, you'll doing a huge help.
email: [email protected]
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse

YggH said:
I'm trying to build that for my sm-t280, and all instructions doesn't ever exist. if you gimme instructions to build, you'll doing a huge help.
email: [email protected]
Click to expand...
Click to collapse
Hi,
Tried to write a simplified procedure to compile the custom ROM for T113NU. See the 8 steps bellow:
I) Assuming you already have a build environment set up (see [1] as reference), download lineage sources using repo commands (repo init, repo sync)
Note: Use branch cm-14.1 (nougat)
II) After syncing, download core33g.xml from my github ( repo local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO) and copy to .repo/local_manifests (create it if doesn't exists)
III) execute "repo sync" again. The files/sources I modified will be downloaded and updated on source tree
IV) Edit vendor/cm/vendorsetup.sh and add this lunch combo:
Code:
add_lunch_combo lineage_core33g-userdebug
This will allow you to select a target compatible with T113NU when running "brunch"
V) As pointed previous posts, camera was avoiding Android to start. To allow booting, cameras were disabled (forced returned number of cameras to 0).
So, for T113NU, commit "0acc7879a9794aacdff85ef1563807d051114917 - frameworks/base - HACK - Disable cameras" will be needed. This commit is on my github, repository platform_frameworks_base, branch T113NU_COM_A_MAO_NO_BOLSO)
VI) Before compiling, export these environment variables:
Code:
export USE_CCACHE=1
ccache -M 50G
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export LC_ALL=C
I suggest you to include these on a file in your home dir (ex: ~/.android_profile) and include it every time you want to create a new build:
Code:
source ~/.android_profile
VII) Include build/envsetup.sh to config Android environment
Code:
source build/envsetup.sh
VIII) Compile the ISO using brunch (select lineage_core33g-userdebug option)
This should do it.
For your device (T280) you'll probably want to replace kernel by the one provided by samsung opensource.
Download it from Samsung Opensource Release Center (see [2]) and unpack it to kernel/samsung/core33g (clean previous files first)
Also:
A) After unpacking, cd to kernel/samsung/core33g and execute a "make mrproper" to remove any temp files under the source tree;
B) cd to kernel/samsung/core33g/arch/arm/configs and rename/copy one of the config files there to "cyanogen_core33g_defconfig" (select one that matches your device - in my case was goyavewifi-dt_hw04_defconfig)
C) You'll probably will need commits to make your kernel compatible with Android 7.1. Try cherry-picking the commits I used, starting from 8c97f3624701f53843b7b2da40185cdcd1c7a422
Play around with config/fw files and have lots of pacience. Creating a working image is not always a funny (consumes lots of time and requires much pacience, logging/debugging )
Good luck!
[1] - https wiki DOT lineageos DOT org/devices /bacon/buildcon/build
[2] - opensource DOT samsung DOT com
ps: Does your device uses Spreadtrum SOC, right?
ps2: Except for kernel, most of changes were minor. Most of this commits were based on remilia15 work. Kudos for who really deserve it!

@sasi2006166 @dhruvpatel_9880 Also works with T116!!

MegaStormBR said:
@[email protected]_9880 Also works with T116!!
Click to expand...
Click to collapse
I will try it today ?

@pstglia Thank you soo much For This ROM..I will try this ROM Today on my SM-T116NY.

Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166

pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse
Bro I installed twrp 3.0.2 and Wiped Data, Chache,Dalvik and system..And I flashed the ROM.. It showed "Unknown Command [log]" BUT FLASHING WAS SUCCESSFUL..So I Botted the tab and now it's showing the Lineage OS boot animation from 15 mins..Ik it takes a hell lot of time for the first boot but 15 mins?!??
I'll update if something happens..

Shreyas.ĒXĒ said:
Bro I installed twrp 3.0.2 and Wiped Data, Chache,Dalvik and system..And I flashed the ROM.. It showed "Unknown Command [log]" BUT FLASHING WAS SUCCESSFUL..So I Botted the tab and now it's showing the Lineage OS boot animation from 15 mins..Ik it takes a hell lot of time for the first boot but 15 mins?!
I'll update if something happens..
Click to expand...
Click to collapse
Hi
5 minutes is the maximum time. 15 minutes can be threated as a bootloop.
Some users reported this on youtube (for T113NU models).
Try pluging USB and check if you have adb connection. If so, check logcat/dmesg

sasi2006166 said:
Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166
Click to expand...
Click to collapse
Hi, this manifest has all the repositories changed (except framework-native, which also can be pushed from my github, branch T113NU_COM_A_MAO_NO_BOLSO)
# Local manifest
https://github.com/pstglia/local_manifests/tree/T113NU_COM_A_MAO_NO_BOLSO
# Framework-Native
https://github.com/pstglia/frameworks-native/tree/T113NU_COM_A_MAO_NO_BOLSO

pstglia said:
Hi
5 minutes is the maximum time. 15 minutes can be threated as a bootloop.
Some users reported this on youtube (for T113NU models).
Try pluging USB and check if you have adb connection. If so, check logcat/dmesg
Click to expand...
Click to collapse
I took a Logcat file.But I am not able to attach it to this post it's showing"Bad Request"I think you are right my Tab is Bootlooped..Any solutions??
Edit: I have uploaded a Google drive link for the logcat.log file..pls see it..
https://drive.google.com/file/d/15491N45mEhIb-MZU72ef83VESCEK_WGi/view?usp=drivesdk

Thanks for the rom! I am using this ROM whit gapps pico and works everything so good! !!
Enviado desde mi Nexus 5X mediante Tapatalk

dhruvpatel_9880 said:
I will try it today
Click to expand...
Click to collapse
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
dhruvpatel_9880 said:
I will try it today
Click to expand...
Click to collapse
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!

Shreyas.ĒXĒ said:
I took a Logcat file.But I am not able to attach it to this post it's showing"Bad Request"I think you are right my Tab is Bootlooped..Any solutions?
Edit: I have uploaded a Google drive link for the logcat.log file..pls see it..
https://drive.google.com/file/d/15491N45mEhIb-MZU72ef83VESCEK_WGi/view?usp=drivesdk
Click to expand...
Click to collapse
Hi,
Unfortunatelly couldn't get any clue by logcat output. Can you post dmesg as well?
@All
Anyone with experience in LineageOS ROMS could give a clue?
Some user with identical device models I had in hand (T113NU) reported the same issue. In these cases, logcat stops logging at the beginning and I couldn't figure out any related message on dmesg?
I'm discarding hw failure because stock ROM works in these cases (based on reports from users)
Regards
pstglia

This rom technically should work if the device code name is " goyave ".mine was sm-t116 and code name is "goyave3g".And working perfectly .

pstglia said:
Hi,
Unfortunatelly couldn't get any clue by logcat output. Can you post dmesg as well?
@All
Anyone with experience in LineageOS ROMS could give a clue?
Some user with identical device models I had in hand (T113NU) reported the same issue. In these cases, logcat stops logging at the beginning and I couldn't figure out any related message on dmesg?
I'm discarding hw failure because stock ROM works in these cases (based on reports from users)
Regards
pstglia
Click to expand...
Click to collapse
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
MegaStormBR said:
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!
Click to expand...
Click to collapse
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..

Shreyas.ĒXĒ said:
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..
Click to expand...
Click to collapse
Huh, thats weird. T116BU working.

Is there any Lineage OS for Lenovo Tab 11 Pro ? [TB-J716F]

Hello,
I was wondering if there is a Lineage OS distribution for Lenovo Tab 11 Pro with the reference TB-J716F. If not, is it possible for me to build one? I'm a noob in custom ROMs, but I'm willing to learn

LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too

Ungeskriptet said:
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Click to expand...
Click to collapse
Thanks, I'll check all of that once I managed to get my tab working.........

Ungeskriptet said:
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Click to expand...
Click to collapse
I managed to install LineageOS. But I cannot install twrp using your image.
These are my logs:
Code:
01-01 08:33:29.842 0 0 I init : starting service 'recovery'...
01-01 08:33:29.847 756 756 F linker : CANNOT LINK EXECUTABLE "/system/bin/vendor.qti.hardware.vibrator.service": library "android.hardware.vibrator-V1-ndk_platform.so" not found: needed by main executable
01-01 08:33:29.847 0 0 I init : Service 'vendor.qti.vibrator' (pid 756) exited with status 1
01-01 08:33:29.847 0 0 I init : Sending signal 9 to service 'vendor.qti.vibrator' (pid 756) process group...
01-01 08:33:29.847 0 0 I libprocessgroup: Successfully killed process cgroup uid 0 pid 756 in 0ms
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.version" to "3.6.1_11-0": error code: 0xb
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.boot' from uid:0 gid:0 pid:755: Read-only property was already set
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.version' from uid:0 gid:0 pid:755: Read-only property was already setunsupported, phys idx 0
01-01 08:33:29.900 755 755 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 755 (recovery), pid 755 (recovery)
01-01 08:33:29.902 758 758 F libc : failed to exec crash_dump helper: No such file or directory
01-01 08:33:29.903 755 755 F libc : crash_dump helper failed to exec
01-01 08:33:29.908 0 0 I init : Service 'recovery' (pid 755) received signal 11

redblood252 said:
I managed to install LineageOS. But I cannot install twrp using your image.
These are my logs:
Code:
01-01 08:33:29.842 0 0 I init : starting service 'recovery'...
01-01 08:33:29.847 756 756 F linker : CANNOT LINK EXECUTABLE "/system/bin/vendor.qti.hardware.vibrator.service": library "android.hardware.vibrator-V1-ndk_platform.so" not found: needed by main executable
01-01 08:33:29.847 0 0 I init : Service 'vendor.qti.vibrator' (pid 756) exited with status 1
01-01 08:33:29.847 0 0 I init : Sending signal 9 to service 'vendor.qti.vibrator' (pid 756) process group...
01-01 08:33:29.847 0 0 I libprocessgroup: Successfully killed process cgroup uid 0 pid 756 in 0ms
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.version" to "3.6.1_11-0": error code: 0xb
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.boot' from uid:0 gid:0 pid:755: Read-only property was already set
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.version' from uid:0 gid:0 pid:755: Read-only property was already setunsupported, phys idx 0
01-01 08:33:29.900 755 755 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 755 (recovery), pid 755 (recovery)
01-01 08:33:29.902 758 758 F libc : failed to exec crash_dump helper: No such file or directory
01-01 08:33:29.903 755 755 F libc : crash_dump helper failed to exec
01-01 08:33:29.908 0 0 I init : Service 'recovery' (pid 755) received signal 11
Click to expand...
Click to collapse
You shouldn't need TWRP.

mikefnz said:
You shouldn't need TWRP.
Click to expand...
Click to collapse
Why not? All I have is stock rom recovery....

redblood252 said:
Why not? All I have is stock rom recovery....
Click to expand...
Click to collapse
Just need adb & fastboot
For example:
Download vbmeta.img from google
Reboot to fastboot
Open an cmd:
fastboot flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot flash system XYZ.img
fastboot reboot recovery
Make an factory reset
Reboot