Develop Bugs

Linux without chroot?

Is it possible to run Linux without chroot? I got Archlinux up and running
Code:
[[email protected] ~]# hostname
galaxys
[[email protected] ~]# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 663.76
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : aries
Revision : 0030
Serial : 313423849c8b00ec
[[email protected] ~]# uname -a
Linux galaxys 3.1.10_IcyGlitch_V14-B6_I9K-T959D #1 PREEMPT Sat Mar 24 18:00:37 CET 2012 armv7l ARMv7 Processor rev 2 (v7l) aries GNU/Linux
[[email protected] ~]# pacman -Qs pacman
local/pacman 4.0.2-1.1 (base)
A library-based package manager with dependency support
local/pacman-mirrorlist 20120204-1 (base)
Arch Linux ARM mirror list for use by pacman
[[email protected] ~]# cat /proc/cmdline
console=ttySAC2,115200 loglevel=4 androidboot.serialno=313423849C8B00EC bootmode=0
[[email protected] ~]#
... but it would be nice to boot into Archlinux instead of ICS. I haven't compiled kernels for the phone before - is the root filesystem path hardcoded in the compile? The only thing I can find is this:
Code:
[[email protected] ~]# zcat /proc/config.gz |grep -i cmdline
CONFIG_CMDLINE="console=ttyFIQ0,115200 init=/init"
Of course, I would probably have to repartition whatever is the root partition. Perhaps I could repartition the internal SD card, give the partition a label and use that for root.
Any pointers? Thanks,
Edit: http://forum.xda-developers.com/showthread.php?t=999097#12206727
Aha. This might be difficult.

Galaxy Trend GT-S7560M Latin America WiFi on CustomROM

So it seems that the LA version of the GT-S7560M has a different WiFi module than other GT-S7560M editions (or is it just South America?).
I wonder if there is a way to the developers of this device out there know what exactly is the WiFi module in our devices so they can figure out what to include in their builds to make this work.
Personally I have no idea about Android Hacking, so I wouldn't know what to do, but I know my way around the commandline in OS X and Linux and at work I have access to Windows 7 too, so I could feed you with the specs of my device.
I'm currently running StockROM with Sadman's Kernel (3.0.8 [email protected]) ) #5 PREEMPT Tue Mar 11.....
I tried to run CyanogenMod with Sadman's Kernel, but that just won't boot.
So how could we users post what exactly, to help you developers to figure out what is different with our devices, so maybe together we could make our devices work with your ROMs?
Personally I have a Samsung Trend GT-S7560M from Tigo Bolivia.
Thanks

I support
In america central not working wifi and tried diferents options to make it work the wifi and not working. And it's good that we do see that here ay people around the world and we should look for ways to solve our problems.
Saludos desde Costa Rica.

hhpss said:
So it seems that the LA version of the GT-S7560M has a different WiFi module than other GT-S7560M editions (or is it just South America?).
I wonder if there is a way to the developers of this device out there know what exactly is the WiFi module in our devices so they can figure out what to include in their builds to make this work.
Personally I have no idea about Android Hacking, so I wouldn't know what to do, but I know my way around the commandline in OS X and Linux and at work I have access to Windows 7 too, so I could feed you with the specs of my device.
I'm currently running StockROM with Sadman's Kernel (3.0.8 [email protected]) ) #5 PREEMPT Tue Mar 11.....
I tried to run CyanogenMod with Sadman's Kernel, but that just won't boot.
So how could we users post what exactly, to help you developers to figure out what is different with our devices, so maybe together we could make our devices work with your ROMs?
Personally I have a Samsung Trend GT-S7560M from Tigo Bolivia.
Thanks
Click to expand...
Click to collapse
Youre very lucky that you didn't hard-brick your phone
sadmans kernels are for STOCK and seriously not meant for cm
Sent from my GT-S7560M using XDA Premium 4 mobile app
---------- Post added at 01:57 AM ---------- Previous post was at 01:52 AM ----------
hhpss said:
So it seems that the LA version of the GT-S7560M has a different WiFi module than other GT-S7560M editions (or is it just South America?).
I wonder if there is a way to the developers of this device out there know what exactly is the WiFi module in our devices so they can figure out what to include in their builds to make this work.
Personally I have no idea about Android Hacking, so I wouldn't know what to do, but I know my way around the commandline in OS X and Linux and at work I have access to Windows 7 too, so I could feed you with the specs of my device.
I'm currently running StockROM with Sadman's Kernel (3.0.8 [email protected]) ) #5 PREEMPT Tue Mar 11.....
I tried to run CyanogenMod with Sadman's Kernel, but that just won't boot.
So how could we users post what exactly, to help you developers to figure out what is different with our devices, so maybe together we could make our devices work with your ROMs?
Personally I have a Samsung Trend GT-S7560M from Tigo Bolivia.
Thanks
Click to expand...
Click to collapse
If the wifi problem hardware related is why is the wifi working on my Galaxy Trend (and also some other users).
thats not logic
i have a (maybe) a fix:
my wifi is working, so i can make (after vacation) a nandroid backup (twrp 2.7) of cm10.2, cm11 and PAC 4.4.4 and upload them i hope that it would fix it
Sent from my GT-S7560M using XDA Premium 4 mobile app

Anas Karbila said:
If the wifi problem hardware related is why is the wifi working on my Galaxy Trend (and also some other users).
thats not logic
i have a (maybe) a fix:
my wifi is working, so i can make (after vacation) a nandroid backup (twrp 2.7) of cm10.2, cm11 and PAC 4.4.4 and upload them i hope that it would fix it
Click to expand...
Click to collapse
my question:
How could we read the poper hardware specs of the WiFi module to compare it?
I found this on StackExchange to get NIC id with dmesg, but I can't figure out what could be my wifi module maybe you can:
Code:
[email protected]:/ # dmesg | grep -i lan
<4>[ 2.160213] wlan_status entered
<4>[ 2.160226] (wlan_status) entered GPIO_RESET_VAL=0
<4>[ 2.160678] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095620>] (wlan_suspend_gpio_config+0x34/0x7c)
<4>[ 2.160713] [<c0095620>] (wlan_suspend_gpio_config+0x34/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.160748] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.161354] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c009562c>] (wlan_suspend_gpio_config+0x40/0x7c)
<4>[ 2.161388] [<c009562c>] (wlan_suspend_gpio_config+0x40/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.161421] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.161971] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095638>] (wlan_suspend_gpio_config+0x4c/0x7c)
<4>[ 2.162004] [<c0095638>] (wlan_suspend_gpio_config+0x4c/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.162036] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.162588] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095644>] (wlan_suspend_gpio_config+0x58/0x7c)
<4>[ 2.162621] [<c0095644>] (wlan_suspend_gpio_config+0x58/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.162653] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.163204] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095650>] (wlan_suspend_gpio_config+0x64/0x7c)
<4>[ 2.163238] [<c0095650>] (wlan_suspend_gpio_config+0x64/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.163271] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.163819] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.163851] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.164188] register_wlan_status_notify --enter<4>[ 5.785766] ebi_grp_3d_clk is unbalanced
<6>[ 7.709036] SDCC CH 2 : msmsdcc_runtime_suspend WLAN SKIP Suspend
<6>[ 26.796343] wlan_setup_ldo_33v - set by BT : on<6>[ 26.796349] wlan_setup_ldo_33v - old wlan_33v_flag : 0
<6>[ 26.796356] wlan_setup_ldo_33v - new wlan_33v_flag : 2
<4>[ 26.796364] wlan_set_gpio - 109 : on
<6>[ 26.796376] wlan_set_gpio: before (1) :: gpio_get_value = 0
<6>[ 26.796393] wlan_set_gpio: after (1) :: gpio_get_value = 1
<6>[ 28.849579] wlan_setup_ldo_33v - set by BT : off
<6>[ 28.849588] wlan_setup_ldo_33v - old wlan_33v_flag : 2
<6>[ 28.849594] wlan_setup_ldo_33v - new wlan_33v_flag : 0
<4>[ 28.849603] wlan_set_gpio - 109 : off
<6>[ 28.849614] wlan_set_gpio: before (0) :: gpio_get_value = 1
<6>[ 28.849631] wlan_set_gpio: after (0) :: gpio_get_value = 0
<4>[ 34.540856] ath6kl_pm_probe()wlan_setup_power on --enter
<6>[ 34.540869] wlan_setup_ldo_33v - set by Wifi : on
<6>[ 34.540876] wlan_setup_ldo_33v - old wlan_33v_flag : 0
<6>[ 34.540883] wlan_setup_ldo_33v - new wlan_33v_flag : 1
<4>[ 34.540891] wlan_set_gpio - 109 : on
<6>[ 34.540904] wlan_set_gpio: before (1) :: gpio_get_value = 0
<6>[ 34.540919] wlan_set_gpio: after (1) :: gpio_get_value = 1wlan_set_gpio - 33 : on
<6>[ 34.541169] wlan_set_gpio: before (1) :: gpio_get_value = 0
<6>[ 34.541181] wlan_set_gpio: after (1) :: gpio_get_value = 1
<6>[ 34.541273] WLAN: wake lock timeout 0.5 sec...
<4>[ 34.669293] wlan_status entered
<4>[ 34.669314] (wlan_status) entered GPIO_RESET_VAL=1
<6>[ 34.669366] SDCC CH 2 : msmsdcc_runtime_resume WLAN SKIP Resume
<7>[ 34.856439] ath6kl: ath6kl_core_init: name=wlan0 dev=0xd0c35000, ar=0xca0c8ae0
<7>[ 35.600853] ath6kl: ath6kl_target_config_wlan_params() vif_index=1 is not yet added
<3>[ 35.768514] init: cannot find '/system/bin/wlan_tool', disabling 'wlan_tool'
<6>[ 36.329033] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<6>[ 37.606724] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<7>[ 47.724691] wlan0: no IPv6 routers present
hhpss

[Kernel] Has anyone got 3.4 kernel working? Kernel hackes are welcome.

I'm trying to get "soho" kernel (from 4..5.5) update to work on the device. With a bunch of fixes I compiled android_jem_defconfig, but as far as I got is
Code:
Uncompressing Linux... done, booting the kernel.
<6>Booting Linux on physical CPU 0
<6>Initializing cgroup subsys cpu
<5>Linux version 3.4.83-g237457e-dirty ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #17 SMP PREEMPT Sun Dec 20 16:15:48 EET 2015
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP4 JEM board
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.83-g237457e-dirty ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #17 SMP PREEMPT Sun Dec 20 16:15:48 EET 2015
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: OMAP4 JEM board
<6>bootconsole [earlycon0] enabled
[ 0.000000] bootconsole [earlycon0] enabled
<6>Initialized persistent memory from a0000000-a01fffff
[ 0.000000] Initialized persistent memory from a0000000-a01fffff
<6>android_display: setting lcd resolution to 1920*1200, bpp=4
[ 0.000000] android_display: setting lcd resolution to 1920*1200, bpp=4
<6>android_display: tiler1d 50331648
[ 0.000000] android_display: tiler1d 50331648
<6>android_display: setting vram to 33554432
[ 0.000000] android_display: setting vram to 33554432
<3>Cannot detect omap type!
[ 0.000000] Cannot detect omap type!
<6>Reserving 33554432 bytes SDRAM for VRAM
[ 0.000000] Reserving 33554432 bytes SDRAM for VRAM
<6>cma: CMA: reserved 16 MiB at ab800000
[ 0.000000] cma: CMA: reserved 16 MiB at ab800000
Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
Then it hangs. For some reason it fails to detect omap4470es1.0. I'm not an advanced kernel hacker so I seek for suggestions in what direction to move to research the problem. I've also tried "bowser" and "soho" configs, still hangs at the same point. Could it be somehow related with the toolchain version? Should I try another one? Mainline 4.3.3 kernel with dts for pandaboard-es built with gcc 5.2 proceed's to boot much further, but I suppose it'll take too much time to get mainline kernel fully functional on the device, if it is even possible (because of blobs, firmwares etc.).
BTW, it may help if someone post "dmesg" output of succesfull boot of "soho" with stock kernel.

Nope not toolchain. GCC 5.2 result is still the same.

Well, it was quite trivial, I traced that it hangs while mapping lowmem. I have no idea why, but changing `vmalloc` to 496M resolves the issue.
Still need to find out why LCD panel does not work, and we'll have a fully functional 3.4 kernel!

Remember kid's, kernel and modules built with significantly different toolchains may be incompatible!
Have it working now. Fire OS 4.5.5 boots up .
Now I have to get touch in put working.
UPD: adding "idc" file for touchscreen and setting SELinux to "permissive" helped, still needs calibration, Woohoo working FireOS 4.5.5

Any progress on porting Fire OS after a semi-working touchscreen?

Compiling a custom kernel for Samsung S9+

Hi, I've downloaded the kernel source based on my device's PDA and compiled it according to the instructions provided by Samsung. I haven't made any changes to the source and I'm using the default exynos config for my devices. I then extracted the original boot.img (using AIK) and replaced zImage & repacked it. After flashing the new boot.img the device gets stuck on "Samsung S9+ .. Secured by Knox" screen. It's not rebooting just hangs on that screen. I've tried clearing my data / cache partitions but that didn't help. I also thought that might be related to dm-verity and disabled it in the kernel / recompiled / rebuilt boot.img but that didn't work either.
Wondering if anyone had this issue? I'm just trying to build the kernel image from the original source code and boot it on my device. Any advice on how to debug this would be appreciated!

just fyi I've pulled the kernel log via twrp and it looks like the device is actually stuck in the boot loop. I can see the S-BOOT bootup printouts and then it gets to actually booting the kernel "Starting kernel..." and restarts right away. There's no ouput from the kernel. Appreciate any help here

it looks like the samsung signature (after SEANDROIDENFORCE) is getting checked :/ Even if I just unpack and then repack the same kernel with AIK (without any modifications) the device won't boot. This signature is the only difference between original and repacked boot.img. The console output is
Code:
SM-G965F androidboot.em.status=0x0 androidboot.verifiedbootstate=orange bcm_setup=0xffffff80f8e00000 reserve-fimc=0xffffff80fa000000 firmware_class.path=/vendor/firmware ecd_setup=disable region1=EUR region2=OPEN'
[0: 2517] ATAG_NONE: 0 0
param logs: (2018-01-10-05-43)N(2018-01-10-05-43)N(2018-01-10-05-44)N(2018-01-10-05-44)N(2018-01-10-05-44)N(2018-01-10-05-44)N(2018-01-10-05-47)N(2018-01-10-06-16)N(2018-01-10-06-17)N(2018-01-10-15-19)R(2018-01-10-15-24)N(2018-01-10-15-24)R(2018-01-10-15-25)N(2018-01-10-15-25)N(2018-01-10-15-27)N(2018-01-10-15-27)N(2018-01-10-15-28)N(2018-01-10-15-32)R(2018-01-10-15-42)N(2018-01-10-15-43)R(2018-01-10-15-46)N(2018-01-10-15-46)N(2018-01-10-16-08)R(2018-01-10-16-09)N(2018-01-10-16-09)N(2018-01-10-16-11)
[0: 2517] [CM] block verified boot commands: start
[0: 2517] [CM] block verified boot commands: success
[0: 2517] [OTP] OTP_SW_BLOCK enable start
[0: 2517] [OTP] OTP_SW_BLOCK enable success
[0: 2517] cal_hash_lock: cal_hash locked
[0: 2517] challenge_size is 0 0
[0: 2517] secure info base: 0x90d20000 and SMC Num = 0x83000013
[0: 2517] secure smc success!!!
[0: 2589] pack_atags: ramdisk size start 0x89000000, size 0x5e2eeb
[0: 3480] max77705_adc_read_temp temp = 33, temp_adc = 1659
[0: 3480] max_freq_update: Current temp: 33
[0: 3511] Updating device tree @0x8a000000: done
[0: 3512] [VIB] max77705_vibtonz_en 1
[0: 3512] PWM PCLK = 26000000
[0: 3512] [PWM : 1] prescaler : 25, div : 1
[0: 3512] [PWM]tcnt : 52, tcmp : 2
[0: 3515] [VIB] max77705_vibtonz_en MCONFIG: [0x82] -> [0xc2]
[0: 3615] [VIB] max77705_vibtonz_en 0
[0: 3619] [VIB] max77705_vibtonz_en MCONFIG: [0xc2] -> [0x82]
[0: 3619]
[0: 3619] Starting kernel...
and the device reboots and gets stuck in this loop. @osm0sis is this because of that samsung signature? does that mean I can't boot any custom ROMs?

mmsub88 said:
it looks like the samsung signature (after SEANDROIDENFORCE) is getting checked :/ Even if I just unpack and then repack the same kernel with AIK (without any modifications) the device won't boot. This signature is the only difference between original and repacked boot.img. The console output is
Code:
SM-G965F androidboot.em.status=0x0 androidboot.verifiedbootstate=orange bcm_setup=0xffffff80f8e00000 reserve-fimc=0xffffff80fa000000 firmware_class.path=/vendor/firmware ecd_setup=disable region1=EUR region2=OPEN'
[0: 2517] ATAG_NONE: 0 0
param logs: (2018-01-10-05-43)N(2018-01-10-05-43)N(2018-01-10-05-44)N(2018-01-10-05-44)N(2018-01-10-05-44)N(2018-01-10-05-44)N(2018-01-10-05-47)N(2018-01-10-06-16)N(2018-01-10-06-17)N(2018-01-10-15-19)R(2018-01-10-15-24)N(2018-01-10-15-24)R(2018-01-10-15-25)N(2018-01-10-15-25)N(2018-01-10-15-27)N(2018-01-10-15-27)N(2018-01-10-15-28)N(2018-01-10-15-32)R(2018-01-10-15-42)N(2018-01-10-15-43)R(2018-01-10-15-46)N(2018-01-10-15-46)N(2018-01-10-16-08)R(2018-01-10-16-09)N(2018-01-10-16-09)N(2018-01-10-16-11)
[0: 2517] [CM] block verified boot commands: start
[0: 2517] [CM] block verified boot commands: success
[0: 2517] [OTP] OTP_SW_BLOCK enable start
[0: 2517] [OTP] OTP_SW_BLOCK enable success
[0: 2517] cal_hash_lock: cal_hash locked
[0: 2517] challenge_size is 0 0
[0: 2517] secure info base: 0x90d20000 and SMC Num = 0x83000013
[0: 2517] secure smc success!!!
[0: 2589] pack_atags: ramdisk size start 0x89000000, size 0x5e2eeb
[0: 3480] max77705_adc_read_temp temp = 33, temp_adc = 1659
[0: 3480] max_freq_update: Current temp: 33
[0: 3511] Updating device tree @0x8a000000: done
[0: 3512] [VIB] max77705_vibtonz_en 1
[0: 3512] PWM PCLK = 26000000
[0: 3512] [PWM : 1] prescaler : 25, div : 1
[0: 3512] [PWM]tcnt : 52, tcmp : 2
[0: 3515] [VIB] max77705_vibtonz_en MCONFIG: [0x82] -> [0xc2]
[0: 3615] [VIB] max77705_vibtonz_en 0
[0: 3619] [VIB] max77705_vibtonz_en MCONFIG: [0xc2] -> [0x82]
[0: 3619]
[0: 3619] Starting kernel...
and the device reboots and gets stuck in this loop. @osm0sis is this because of that samsung signature? does that mean I can't boot any custom ROMs?
Click to expand...
Click to collapse
If that's literally the only difference in the images then yeah, probably. Only other thing you could try is disabling verity and checks by patching it with Magisk Manager first, in case that makes a difference.

osm0sis said:
If that's literally the only difference in the images then yeah, probably. Only other thing you could try is disabling verity and checks by patching it with Magisk Manager first, in case that makes a difference.
Click to expand...
Click to collapse
ah sorry it looks like the device is booting the original boot.img with the samsung signature removed. It must be my kernel then. All I've done is got the kernel source code from opensource.samsung.com corresponding to my PDA. Then I did a default compile without making any changes to the source code or kernel config. (compiled with this toolchain https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 which is the same version as the original samsung kernel in boot.img)
Code:
$ export ANDROID_MAJOR_VERSION=o
$ make ARCH=arm64 exynos9810-star2lte_defconfig
$ make ARCH=arm64
Do you know if there's anything I'm missing that might stop the kernel from booting?

Not my area, sorry. Check with other developers for your device or similar devices.

osm0sis said:
Not my area, sorry. Check with other developers for your device or similar devices.
Click to expand...
Click to collapse
thanks for your answers!

mmsub88 said:
ah sorry it looks like the device is booting the original boot.img with the samsung signature removed. It must be my kernel then. All I've done is got the kernel source code from opensource.samsung.com corresponding to my PDA. Then I did a default compile without making any changes to the source code or kernel config. (compiled with this toolchain https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 which is the same version as the original samsung kernel in boot.img)
Code:
$ export ANDROID_MAJOR_VERSION=o
$ make ARCH=arm64 exynos9810-star2lte_defconfig
$ make ARCH=arm64
Do you know if there's anything I'm missing that might stop the kernel from booting?
Click to expand...
Click to collapse
@djb77 any tips here? Do I need to disable any mitigations to make it boot? I don't think it's related to verity because it's not even getting to the first kernel console printk "Booting Linux ...". Just resets right away when it gets to loading the kernel. I'm using the original dtb image but I also tried compiling my own dtb using the patches from your TGP kernel.

Bootloop issue ....

I have suddenly poweroff device and go to bootloop. When MIUI bootanimation start .
I try all Guide available here and there but still not work.
I can access Recovery and internal Storage but when try to boot rom it goes bootloop .
I try Miui and aosp rom but still .
My kernel log have this :
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.117-perf+ ([email protected]) (clang version 8.0.12 for Android NDK) #1 SMP PREEMPT Wed Dec 9 11:21:40 CST 2020
[ 0.000000] Boot CPU: AArch64 Processor [51af8014]
[ 0.000000] Powerup reason=0x80081
[ 0.000000] Machine: Qualcomm Technologies, Inc. trinket pm6125 + pmi632 IDP
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] OF: reserved mem: OVERLAP DETECTED!
Click to expand...
Click to collapse
Please Help me and thanks alot .

THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Kindly use the existing thread for continuing discussion: https://forum.xda-developers.com/t/help-in-bootloop.4333531/
Regards,
shadowstep
Forum Moderator