Related
hi everyone
ı' am new in here.
ı want to ask does INTEL BAY TRAIL (z3XXX) support to install linux installing? or not why ? (because bootloader or another thing etc..)
There is some variant of windows tablets on market but can ı install ubuntu, arch linux etc? does it support?
sorry my bad englısh
1a) UEFI/BIOS support. looks like for the Asus T100, Asus only gave a 32-bit UEFI bootloader, so there are hacks to go around it. not sure about other devices like Dell Venue 8 Pro (I don't have that much money to buy so many devices)
1b) Secure Boot option to be disabled. If you can't disable Secure Boot, there are ways to get around it (some distros provide a signed UEFI shim that preloads before grub2, but you'll have to get that shim working with 32-bit bootloaders if you hit the problem above in 1a)
2) SoC support. Intel has submitted the Bay Trail SoC to the linux kernel. However, there are still some parts missing (eg open source video driver xf86-video-intel has it somewhat supported with bugs)
here is my WIP on getting ubuntu working on my Asus T100.... only major thing missing is graphics driver, everything else (besides sound) is working
http://forum.xda-developers.com/showthread.php?t=2500078
Baytrail T100 grub won't boot kernel
paperWastage said:
1a) UEFI/BIOS support. looks like for the Asus T100, Asus only gave a 32-bit UEFI bootloader, so there are hacks to go around it. not sure about other devices like Dell Venue 8 Pro (I don't have that much money to buy so many devices)
1b) Secure Boot option to be disabled. If you can't disable Secure Boot, there are ways to get around it (some distros provide a signed UEFI shim that preloads before grub2, but you'll have to get that shim working with 32-bit bootloaders if you hit the problem above in 1a)
2) SoC support. Intel has submitted the Bay Trail SoC to the linux kernel. However, there are still some parts missing (eg open source video driver xf86-video-intel has it somewhat supported with bugs)
here is my WIP on getting ubuntu working on my Asus T100.... only major thing missing is graphics driver, everything else (besides sound) is working
http://forum.xda-developers.com/showthread.php?t=2500078
Click to expand...
Click to collapse
Having a hell of a time getting ubuntu to get past grub.
Tried both Asus T100, and Dell Venue 8 Pro
Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image)
Tried x86_64: ubuntu 13.04, 13.10, Fedora 20
All 6 Combinations, Boot into Grub, but grub throws the following error message every time, when booting the kernel:
"Can't Terminate EFI Services", and go back to grub.
Tried both boot loader binaries: - bootia32.ubuntu_13.04_x64.zip, and bootia32_normal_configfile.zip
From main thread: http://forum.xda-developers.com/showthread.php?p=46861952#post46861952
After that grub error, USB devices are all disabled.
Not sure how to debug further, seems like a grub EFI issue, but can't confirm.
Tried grub debug, using "set debug=all", and the error occurs right after the EFI map is displayed.
Please advise on how to proceed - how can this happen on both T100 and V8P?
M$ ruined baytrail by requiring 32 bit EFI, on a 64 bit system!
I could be wrong, but I thought I remembered seeing a 32 efi folder in Ubuntu GNOME 14.04. I'm not positive because I used the 64 bit installation on my HP Pavilion x2 2-in-1. It has the bay trail graphics. I stumbled upon this thread because I was looking for improved driver support. Right now the only thing not working on my installation (besides bluetooth) is display brightness control.
BayTrailSucks said:
"Can't Terminate EFI Services", and go back to grub.
Click to expand...
Click to collapse
I saw this log from time to time when I've used binaries you've mentioned.
So I've recompiled grub myself from sources taken from: ftp.gnu.org/gnu/grub
I've used version 2.00
To compile grub I've used commands:
./configure \
--with-platform=efi --target=i386 --disable-nls \
--disable-grub-emu-usb --disable-grub-emu-sdl --disable-grub-emu-pci --disable-grub-mkfont \
--disable-device-mapper --disable-libzfs --disable-werror
sed -i -e '/gets is a/d' grub-core/gnulib/stdio.in.h
make -j 2 MAKEINFO=true
make -j 2 install MAKEINFO=true
and then to prepare bootloader binary I've executed:
i386-grub-mkimage -o bootia32.efi -O i386-efi -p /boot/grub ntfs boot cat efi_gop efi_uga elf fat linux keylayouts \
memdisk minicmd ext2 extcmd part_bsd part_gpt search search_fs_file chain \
loadbios loadenv memrw mmap msdospart scsi loopback
For kernel tests I've used kernel 3.12 from kernel.org and 3.13.0-rc8 from repository: git://people.freedesktop.org/~danvet/drm-intel
Kernel 3.12 booted fine when I've added 'video' parameter as was mentioned in paperWastage thread.
For kernel 3.13.0-rc8 I've to revert one commit, see more info in bug 71977 at bugs.freedesktop.org
After I've updated xf86-video-intel to 2.99.907 and libdrm to 2.4.52 I was able to run X server with acceleration:
# glxinfo | grep ren
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
OpenGL renderer string: Mesa DRI Intel(R) Bay Trail x86/MMX/SSE2
GL_NV_conditional_render, GL_AMD_draw_buffers_blend,
What about hardware accelerated video playback
What about hardware accelerated video playback?
vshalimo said:
What about hardware accelerated video playback?
Click to expand...
Click to collapse
It works. I can use GPU accelerated decoding in vlc compiled with libva support.
-bash-4.2# vainfo
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /kanapi_packages/libva-master/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.34 (libva 1.2.2.pre1)
vainfo: Driver version: Intel i965 driver - 1.2.3.pre1
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
Battery status
Patch for kernel for battery status has been just added to bug 69011 in kernel bugzilla (I can't put link here)
and it works on ASUS T100TA:
cat /sys/class/power_supply/BATC/uevent
POWER_SUPPLY_NAME=BATC
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=8
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3750000
POWER_SUPPLY_VOLTAGE_NOW=4174000
POWER_SUPPLY_CURRENT_NOW=1172000
POWER_SUPPLY_CHARGE_FULL_DESIGN=8180000
POWER_SUPPLY_CHARGE_FULL=9595000
POWER_SUPPLY_CHARGE_NOW=9316000
POWER_SUPPLY_CAPACITY=97
POWER_SUPPLY_MODEL_NAME=SR Real Battery
POWER_SUPPLY_MANUFACTURER=Intel SR 1
POWER_SUPPLY_SERIAL_NUMBER=123456789
Well, for the past few months, I am trying to run Kali Linux on my device. But since it was x86 based android device, but keep getting annoying errors. But, last week after i upgrade my P5220 into 4.4.2 Kitkat, it works like magic. I can run it. With latest linux deploy which support x86 devices i am sure you can run it smoothly.
For those who wondering how to get Kali works on your tab 3 10.1 ( which previously spam a tones of error while installing kali with linux deploy)
This is what i did:
1. Connect to kies and upgrade to kitkat 4.4.2
2. Flash to Philz recovery (you can find it within Xda tab3 section) with odin from stock recovery
3. Root it
4. run linux deploy and follow this https://www.kali.org/how-to/kali-linux-android-linux-deploy/ (but set to i386 instead)
5. Click Install button (it may take a long while to load)
6. download SSH or VNC viewer and connect, default password is changeme
7. done!
JuiceSSH : https://play.google.com/store/apps/details?id=com.sonelli.juicessh&hl=en
Linux Deploy : https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy&hl=en
VncViewer : https://play.google.com/store/apps/details?id=com.realvnc.viewer.android&hl=en
Always remember, tab 3 10.1 are on x86 processors, so there is something different.
Dont forget to check out this if you are on GT-P5210 (wifi Edition) if you wish to use monitor mode on external wifi dongle
http://forum.xda-developers.com/showthread.php?t=2727771
I will release Modded Kernel For GT-P5220(LTE edition) with external wifi dongle support soon....
Jacker31 said:
4. run linux deploy and follow this https://www.kali.org/how-to/kali-lin...-linux-deploy/ (but set to i386 instead)
Click to expand...
Click to collapse
I'm sorry but this link isn't working.
Thank you for the tutorial.
Max4000 said:
I'm sorry but this link isn't working.
Thank you for the tutorial.
Click to expand...
Click to collapse
I fixed up the link Added google play link too
Do I HAVE to have Philz recovery to be able to do this, I got TWRP isnt that enough?
Hello all, I've been trying to root my Droid Maxx 4.4.4 SU6-7 and was working fine until after bricking it, I was unable to run the RUN_Root.bat. I'm running Windows 7 64 bit. This is the error I would get in the command prompt after trying to run RUN_Root.bat .
C:\Python27>python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com9
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device programming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91 ,ca,fd,bb,94,2a,0d,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
C:\Python27>pause
Press any key to continue . . .
I can still use the USB I think. I see Qualcomm HS-USB Loader 9008 (COM9) in the device manager whenever I would plug in the USB and it was manually updated after I selected x64 folder from the windows_drivers_QHSUSB_DLOAD folder(windows would say it was up to date when selecting x64 folder). I tried different ports but the Port otion never shows up for them in the device manager. I'm also not using USB 3.0.
I believe I followed every other instruction as far as I know from this thread http://forum.xda-developers.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609 I'd really appreciate if someone could help me out.
Phoop said:
Hello all, I've been trying to root my Droid Maxx 4.4.4 SU6-7 and was working fine until after bricking it, I was unable to run the RUN_Root.bat. I'm running Windows 7 64 bit. This is the error I would get in the command prompt after trying to run RUN_Root.bat .
C:\Python27>python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com9
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device programming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91 ,ca,fd,bb,94,2a,0d,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
C:\Python27>pause
Press any key to continue . . .
I can still use the USB I think. I see Qualcomm HS-USB Loader 9008 (COM9) in the device manager whenever I would plug in the USB and it was manually updated after I selected x64 folder from the windows_drivers_QHSUSB_DLOAD folder(windows would say it was up to date when selecting x64 folder). I tried different ports but the Port otion never shows up for them in the device manager. I'm also not using USB 3.0.
I believe I followed every other instruction as far as I know from this thread http://forum.xda-developers.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609 I'd really appreciate if someone could help me out.
Click to expand...
Click to collapse
Besides manually update the driver.
First, you have to disable the mandatory use of signed drivers in Windows.
Why? The driver you are trying to install (or update) is not signed and windows by default only allows the use of signed drivers.
Search a tutorial on "how to install an unsigned driver Windows 7"
I send you some, but I am the translator of google lol ..
I had a similar problem for the driver and the solution I gave you, solved my problem.
The best of luck, a big hug!
I managed to fix my problem yeasterday following br0adband advice in this thread http://forum.xda-developers.com/showpost.php?p=62651329&postcount=1159 sorry I forgot to close my thread(if I can figure out how). Thanks for that helpfull tip though, I'll keep that in mind for later driver issues.
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.
A couple of weeks ago my phone crashed out of nowhere and QUALCOLM CRASHDUMP MODE was displayed. I got it fixed but since then my wifi isn't turning on. Bluetooth works just fine. Its only the wifi that is causing problem. a few days later it again crashed which forced me to move to a custom ROM; lineage OS. I thought it might fix the issue, but invain. My phone just wont tun on the wifi. The about section says device wifi mac address unavailable. I used busy box and terminal emulator as suggested in one of the post to know the original MAC address but its value tuned out something like this hwdr 00:00:00:00
Any help guys?
.... test MCDKernel.... fixed my WLAN Problem
Release mcd r16 · mcdachpappe/android_kernel_oneplus_sdm845
Two-in-One kernel image installer: The installer detects your current installed OS (OxygenOS / custom ROM) and flashes the correct image file. Prerequisite: An updated firmware isn't needed anymor...
github.com
lamahgra said:
.... test MCDKernel.... fixed my WLAN Problem
Release mcd r16 · mcdachpappe/android_kernel_oneplus_sdm845
Two-in-One kernel image installer: The installer detects your current installed OS (OxygenOS / custom ROM) and flashes the correct image file. Prerequisite: An updated firmware isn't needed anymor...
github.com
Click to expand...
Click to collapse
Can you please tell me step by step process of how to do it. I seem to be messing up somewhere. Pleasseee *_*
flash mcd kernel zip via twrp
mcd-kernel= https://github.com/mcdachpappe/android_kernel_oneplus_sdm845/releases/tag/r17
lamahgra said:
flash mcd kernel zip via twrp
mcd-kernel= https://github.com/mcdachpappe/android_kernel_oneplus_sdm845/releases/tag/r17
Click to expand...
Click to collapse
please can you tell me step by step process. I don't know much about this. I can follow commands tho *_*
OnePlus 6 (enchilada)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
lamahgra said:
OnePlus 6 (enchilada)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Click to expand...
Click to collapse
update : didnt work. ANy other thing i could try?