Hi All,
Whether the LG G2's Knock On (Double tap to wake) feature can be incorporated in Redmi 1S. I am ok with a good launcher which support this feature as I cant root the device as its enabled for official mails
Thanks in Advance
It can be implemented only through kernel. Unless xiaomi releases kernel sources, nothing can be done!
Gh0sT.RPG said:
It can be implemented only through kernel. Unless xiaomi releases kernel sources, nothing can be done!
Click to expand...
Click to collapse
Yes , all mokee , aosp , cm11 ,carbon, pac etc are using the stock kernels , though there were talks of using some other devices kernel which was next-to-almost-compatible with Redmi.
on cm11 i tried flashing their kernel with update v45, even that failed and gave me bootloops.
kapil.git said:
Yes , all mokee , aosp , cm11 ,carbon, pac etc are using the stock kernels , though there were talks of using some other devices kernel which was next-to-almost-compatible with Redmi.
on cm11 i tried flashing their kernel with update v45, even that failed and gave me bootloops.
Click to expand...
Click to collapse
you changed the ramdisk?
saurabhrck said:
you changed the ramdisk?
Click to expand...
Click to collapse
I just changed bootanimation and init.qcom.post.boot.sh for mpdecision tweak and max/min freq ..
before the kernel flash I have booted phone 20+ times in last weeks, never bootlooped.
kapil.git said:
I just changed bootanimation and init.qcom.post.boot.sh for mpdecision tweak and max/min freq ..
before the kernel flash I have booted phone 20+ times in last weeks, never bootlooped.
Click to expand...
Click to collapse
I just tried to repack latest cm11 kernel for mokee as mokee is using old kernel. I changed the ramdisk, the device boots up but wifi is not working. but the thing is I can't find any wifi module in those kernel to swap. do you have any suggestion regarding thsi wifi module
can we use mokee wlan.ko ?
saurabhrck said:
I just tried to repack latest cm11 kernel for mokee as mokee is using old kernel. I changed the ramdisk, the device boots up but wifi is not working. but the thing is I can't find any wifi module in those kernel to swap. do you have any suggestion regarding thsi wifi module
Click to expand...
Click to collapse
It could be because mokee old kernel has this wlan.ko as loadable module
Can you try replacing the cm11's ko with the one attached ?
Code:
[email protected]:# find /system -name wlan.ko
/system/lib/modules/wlan.ko
[email protected]:# ls -l /system/lib/modules/wlan.ko
lrwxrwxrwx root root 2014-11-12 07:20 wlan.ko -> /system/lib/modules/pronto/pronto_wlan.ko
[email protected]:# md5sum pronto_wlan.ko
8f99e1923e2a25f0f7cc57ff62e5683d pronto_wlan.ko
when I enable Wifi
# lsmod
wlan 3616884 0 - Live 0x00000000 (O)
relevant console logs in mokee startup
<6>[ 1.414962] wcnss_wlan probed in built-in mode
<6>[ 11.033752] wcnss_wlan triggered by userspace
<6>[ 12.138179] wcnss_wlan_ctrl_probe: SMD ctrl channel up
<6>[ 555.845568] wlan: loading driver v3.2.3.172
<3>[ 555.964780] wlan: WCNSS WLAN Version 1.5.1.2, Host expected 1.4.1.2
<6>[ 555.964799] wlan: WCNSS software version 120418
<6>[ 555.964811] wlan: WCNSS hardware version WCN v2.0 RadioPhy vUnknown with 19.2MHz XO
<6>[ 556.014001] wlan: driver loaded
kapil.git said:
It could be because mokee old kernel has this wlan.ko as loadable module
Can you try replacing the cm11's ko with the one attached ?
Code:
[email protected]:# find /system -name wlan.ko
/system/lib/modules/wlan.ko
[email protected]:# ls -l /system/lib/modules/wlan.ko
lrwxrwxrwx root root 2014-11-12 07:20 wlan.ko -> /system/lib/modules/pronto/pronto_wlan.ko
[email protected]:# md5sum pronto_wlan.ko
8f99e1923e2a25f0f7cc57ff62e5683d pronto_wlan.ko
when I enable Wifi
# lsmod
wlan 3616884 0 - Live 0x00000000 (O)
relevant console logs in mokee startup
<6>[ 1.414962] wcnss_wlan probed in built-in mode
<6>[ 11.033752] wcnss_wlan triggered by userspace
<6>[ 12.138179] wcnss_wlan_ctrl_probe: SMD ctrl channel up
<6>[ 555.845568] wlan: loading driver v3.2.3.172
<3>[ 555.964780] wlan: WCNSS WLAN Version 1.5.1.2, Host expected 1.4.1.2
<6>[ 555.964799] wlan: WCNSS software version 120418
<6>[ 555.964811] wlan: WCNSS hardware version WCN v2.0 RadioPhy vUnknown with 19.2MHz XO
<6>[ 556.014001] wlan: driver loaded
Click to expand...
Click to collapse
which rom's is it? If I wanna repack cm11's kernel to mokee I will need the cm11's .ko file. right? so which rom's is it?
saurabhrck said:
which rom's is it? If I wanna repack cm11's kernel to mokee I will need the cm11's .ko file. right? so which rom's is it?
Click to expand...
Click to collapse
I am on mokee which has wlan as loadable module and may be thus shipped in ROM.
if CM has this inbuilt , you may have to disable the wifi and then insmod this ko.
pac also has this loadable
# cd /armani/ROMS/pac_armani_4.4.4.RC-2_20141026-175447/system/lib/modules/pronto
# md5 pronto_wlan.ko
MD5 (pronto_wlan.ko) = 6fc7aba9195e29702dac09dd384bdb00
it worked! all modules are working now. had to copy cm11's pronto_wlan.ko to mokee after kernel flash. and reboot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
saurabhrck said:
it worked! all modules are working now. had to copy cm11's pronto_wlan.ko to mokee after kernel flash. and reboot!
Click to expand...
Click to collapse
Glad , it helped.
Can you please make a small writeup about how to use a newer stock kernel with mokee/CM
( I think this is what you achieved , right ? )
saurabhrck said:
it worked! all modules are working now. had to copy cm11's pronto_wlan.ko to mokee after kernel flash. and reboot!
Click to expand...
Click to collapse
Can you make a flashable image of the new kernel for mokee? THX
LE I found latter the post you've made on developer...
kapil.git said:
Glad , it helped.
Can you please make a small writeup about how to use a newer stock kernel with mokee/CM
( I think this is what you achieved , right ? )
Click to expand...
Click to collapse
I already made s thread in dev subforum.
Gh0sT.RPG said:
It can be implemented only through kernel. Unless xiaomi releases kernel sources, nothing can be done!
Click to expand...
Click to collapse
kernel source has already been released. are you try to compile the kernel with dttw or s2w?
Related
Hello guys,
Some of you guys will recognise me, I was trying to make progress on Sultan's 3.10 kernel on his topic. After a while I've wanted to do that from scratch, in new base, and now I can say it's done.
This kernel is the one all recent flagships' use. Also 3.10 kernels' support will end in Oct. 2017, while 3.4 ones will end in Apr. 2017.
In theory it should have better memory management, less battery consumption etc. It took me about 7-8 months to come to this point.
Currently everything works.
Extra features
* KCAL
* 6 new governors
* Touchscreen driver has been updated and optimized - also S2W added, you can find it in Kernel Aduitor
* Works with pelya's USB Keyboard app.
* New charger driver features:
They're placed in: /sys/devices/qpnp-charger-ed443000
You need to reach them from some terminal app or adb shell.
threea_charge
Making it 1 will activate experimental 2.5A charge. It's triggered if AICL mA is 2000(if you're not sure about AICL mA, simply disable AICL by below parameter), temperature is appropriate and screen is off.
Only use if you have 2.5A or above charger. Don't use QC's Quick Charge adapters.
Untested, but can't damage your phone.
disable_aicl
Making it 1 will disable AICL and charger driver will always try to take 2A from your AC/wall charger (there's no problem if you charger isn't 2A)
You need to replug adapter to see the effect.
max_aicl_rate
Max. charge current. (Not exactly if it's below 0 Celsius)
It should be one of those: 100,150,500,900,1200,1500,2000. Other values will be rounded. Values below then 100 and higher then 2000 won't be accepted.
Has no effect if AICL is disabled via above parameter.
If threea_charge is enabled and this parameter is 2000, max current will be 2.5A.
You need to replug adapter to see the effect.
fast_usb_charge Can also be found in Kernel Aduitor
Making it 1 will charge your phone through 900 mA if it's charging via USB port.
You need to replug adapter to see the effect.
charge_limit
It only accepts values between 0-100. Charger driver will cap charge percent to entered value. It's known that capping it to 50-60 percent increases battery life.
Making it 100 will revert the effect.
soft_aicl_vol
It must be between 4350 and 5000.
Default is OP2 value (4465 - but algorithm is different from LinOS and you shouldn't directly enter Sultan's or LinOS's value).
Don't change that if you don't know what it is.
Ramdisk changes
Last update: 17-02-2017
in fstab.bacon:
* F2FS filesystems must be mounted without noatime option.
* "/devices/platform/xhci-hcd" --> "/devices/*/xhci-hcd.0.auto/usb";
* "voldmanaged=usbdisk:auto" --> "voldmanaged=usb:auto";
in init.bacon.rc:
* qcom_oncrpc must be removed from loc_launcher (this is CM's mistake)
* netmgrd must also have system group
* qmuxd's user must be changed to root
in init.qcom.power.rc/init.recovery.bacon.rc:
* cpubw.40 must be changed to cpubw.47
Click to expand...
Click to collapse
These are only things different than CM ramdisk right now.
in anykernel patch format (all credits goes to @idprophecy)
## 3.10 ramdisk fixes
# fstab
if [ -f fstab.bacon ]; then
fstab="fstab.bacon";
backup_file $fstab;
elif [ -f fstab.qcom ]; then
fstab="fstab.qcom";
backup_file $fstab;
fi;
if [ -n $fstab ]; then
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid";
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid";
replace_string $fstab "/devices/*/xhci-hcd.0.auto/usb" "/devices/platform/xhci-hcd" "/devices/*/xhci-hcd.0.auto/usb";
replace_string $fstab "voldmanaged=usb:auto" "voldmanaged=usbdisk:auto" "voldmanaged=usb:auto";
fi;
# init.recovery.bacon.rc
if [ -f init.recovery.bacon.rc ]; then
qcomrecovery="init.recovery.bacon.rc";
backup_file $qcomrecovery;
fi;
if [ -n $qcomrecovery ]; then
replace_string $qcomrecovery "cpubw.47" "cpubw.40" "cpubw.47";
fi;
# init.qcom.power.rc
if [ -f init.qcom.power.rc ]; then
qcompower="init.qcom.power.rc";
backup_file $qcompower;
fi;
if [ -n $qcompower ]; then
replace_string $qcompower "cpubw.47" "cpubw.40" "cpubw.47";
fi;
# init.bacon.rc
if [ -f init.bacon.rc ]; then
qcomdevice="init.bacon.rc";
backup_file $qcomdevice;
elif [ -f init.oppo.common.rc ]; then
qcomdevice="init.oppo.common.rc";
backup_file $qcomdevice;
fi;
if [ -n $qcomdevice ]; then
replace_string $qcomdevice "# loc_launcher qcom_oncrps not needed" " group gps qcom_oncrpc inet" " # loc_launcher qcom_oncrps not neededn group gps inet";
replace_string_multiline $qcomdevice "# fix netmgrd service" "service netmgrd /system/bin/netmgrdn class mainn user rootn group radio" "service netmgrd /system/bin/netmgrdn class mainn user rootn # fix netmgrd servicen group radio system";
replace_string_multiline $qcomdevice "# fix qmuxd service" "service qmuxd /system/bin/qmuxdn class mainn user radio" "service qmuxd /system/bin/qmuxdn class mainn # fix qmuxd servicen user root";
fi;
## 3.10 ramdisk fixes
Downloads
Code:
Nobody knows is your warrant is still valid.
Also it's suspicious is there any warranty for OPO.
After you started to use this kernel, I'm not resposible for anything happened to your device.
* Encryption works but I cannot guarantee that it won't cause any data loss.
* They're all AnyKernel.
* There will be two types of build after 19/05, one with CM camera driver, one with CAF/Sultan camera driver.
27-05-2017:
With CM camera: https://www.mediafire.com/?7z672wl1y6xy275
With CAF/Sultan camera: https://www.mediafire.com/?sts35t5hd5ca3xr
19-05-2017:
With CM camera driver: https://www.mediafire.com/?4pkk3co7290lx1l
With CAF/Sultan camera driver: https://www.mediafire.com/?hohbwk9l805nrn0
09-04-2017: http://www.mediafire.com/file/h2k3moy0s6mxiht/09042017kernel.zip
A little nostalgia (It's too buggy, you have been warned)
26-08-2016: http://www.mediafire.com/file/6j5xw1j1lel1tra/260816kernel310.zip
Source code link is available bottom of this post.
Technical side
* It is based on LA.BF.2.1.2
* You can use both LA.BF and LA.BR prima, I'm using LA.BF one with some LA.BR commits.
* Tspp driver was causing bootloop, so i've disabled it. And I don't know is it used at all, it's disabled in apq8084 devices (like nexus 6) even.
* I'm compiling it with GCC 4.8. I've switched to Uber 6.0 after 09-01 build.
* KGSL drivers is pretty messed up after 30-08 build. It's my fault.
* And compiled DT is in in arch/arm/boot, it was different in 3.4 I think.
Pull requests are welcome.
You can use use/fork/develop this but you should give credit for 3.10 kernel on your releases.
Did you like my work?
I appreciate all the donations, it will keep me motivated, also I'm a student so it will help me in my life
Addendum: PayPal has been banned from my country, if PayPal denies your transaction and if you want to donate, I can give you my IBAN.
Credits
Sultan - this kernel would be impossible without his helps & his first 3.10 kernel attempt.
Ra1nst0rm - for helping me to upload repo - releasing this would be impossible due to creeping internet in here.
Mecca UL & idprophecy - for their insane effort to test and improve this kernel =)
XDA:DevDB Information
OnePlus One 3.10 kernel, Kernel for the OnePlus One
Contributors
erorcun, Sultanxda
Source Code: https://github.com/erorcun/android_kernel_oneplus_msm8974-3.10
Kernel Special Features: 3.10 kernel - better memory management and battery consumption in theory
Version Information
Status: Beta
Current Beta Version: 1.0
Created 2016-05-14
Last Updated 2017-05-27
Reserved
GREAT!
NICE!!!!
Proud cuz a turkish dude managed to do it
---------- Post added at 09:33 PM ---------- Previous post was at 09:28 PM ----------
This might be the biggest revolution to the OPO since the Sultan's CAF Rom and camera HAL.
Tested on f2fs Sultans stable Rom. Bootlooping on cm logo.
Sent from my A0001 using XDA-Developers mobile app
@DerRomtester
It's only for CM nightlies, i'm writing it to OP.
It could be related with f2fs too, I don't know.
erorcun said:
@DerRomtester
It's only for CM nightlies, i'm writing it to OP.
It could be related with f2fs too, I don't know.
Click to expand...
Click to collapse
Why don't you use anykernel so it also works on sultans rom but stock CAF camera drivers will be needed to work with oxygen blobs
nikhil18 said:
Why don't you use anykernel so it also works on sultans rom but stock CAF camera drivers will be needed to work with oxygen blobs
Click to expand...
Click to collapse
I can't make big changes anymore. It was freakin' hard to come to this point.
Maybe if I know diffs between sultan and cm kernel.
Testing
My country is famous with creeping internet, so I gave a chance to github import tool to import it from caf first, but it has been almost 1 day and progress bar still seems full, I think it got stuck.
I will be grateful to anyone who gives me LA.BF.2.1.2_rb1.5 kernel imported repo :silly: Ofcourse I can do it myself but I don't know when I can.
And I will add credits to one who upload it.
Nice to see someone continue 3.10 for bacon!
I'm going to try it soon.
Works beautifully with CM Nightly 15-05 on a secondary Multirom installation. GPS worked well for me, but during calls the other party couldnt hear my voice. So reluctantly removed for now. Hope you fix the issues and continue developing the kernel for our beloved OPO.
mucinch said:
Works beautifully with CM Nightly 15-05 on a secondary Multirom installation. GPS worked well for me, but during calls the other party couldnt hear my voice. So reluctantly removed for now. Hope you fix the issues and continue developing the kernel for our beloved OPO.
Click to expand...
Click to collapse
Yeah, GPS works well actually but it shouldn't be perfect since part of it crashes.
Thanks!
Source is up now, thanks to Ra1nst0rm.
Enjoy =)
@erorcun you are welcome
Will test it soon
erorcun said:
Source is up now, thanks to Ra1nst0rm.
Enjoy =)
Click to expand...
Click to collapse
Great work. Just checked your source.
Thats big step ahead :good:
Bluetooth works fine, GPS too, only f2fs doesnt.
Tested on nightly and RR
CraZY_BoY^ said:
Thats big step ahead :good:
Bluetooth works fine, GPS too, only f2fs doesnt.
Tested on nightly and RR
Click to expand...
Click to collapse
Thanks for testing bluetooth.
Nice development! Thanks for this!
Edit: Working nicely on a test install of Vanilla Unicorn (CM based)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
*/
About GlazeOS:
Glaze OS is a free, open-source, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. It offers features not found in the official Android based firmwares of vendors.
AOSP
Based on Android Open Source Project.
Linaro Optimized
Linaro’s GCC improvements have been producing measurable performance advantages over Google’s stock Android environment and build toolchain, delivering an improvement of 30 to 100 percent in various benchmarks.
Enablement for Qualcomm MSM
The Android for MSM project allows users to build an Android based platform containing additional enhancements for Qualcomm chipsets. The platform uses Google's Android Linux implementation and tools.
Substratum Theme Engine
Based on Sony's Overlay Manager Service (OMS). This is similar to Layers in terms of stability and customization as it runs off an upgraded version of the Resource Runtime Overlay system, with the added benefit of running up-to-date Sony code on a customized ROM.
Customization
Soon :laugh:
BUGS
Camera
Wi-Fi
You tell me more bugs :3
Downloads:
GlazeOS for e610
Gapps ARM->7.1->PICO Recommended
Flashing Instructions:
Download GlazeOS-v1.0-EXPERIMENTAL-e610-2017XXXX-XXXX.zip
Copy to SD-CARD
Wipe dalvik, cache and system.
Install ROM and GAPPS
Reboot system
Screenshots:
Credits:
Team Subtratum
Team Linaro
AOSP
Team LineageOS
Team GlazeOS
And More People :3
XDA:DevDB Information
GlazeOS, ROM for the LG Optimus L5
Contributors
ROM-PacMe, ROM-PacMe
Source Code: https://github.com/GlazeOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP-CAF
Version Information
Status: Testing
Created 2017-04-02
Last Updated 2017-04-02
L7? u.u
Hugo Salce said:
L7? u.u
Click to expand...
Click to collapse
Can you be a tester?
Thanks for the ROM
create for e615? Pls
ROM-PacMe said:
BUGS
Camera
Wi-Fi
You tell me more bugs :3
Click to expand...
Click to collapse
As I can see from screenshots, another bug is RIL and as far as I remember audio doesn't work as well.
SlimShady's said:
As I can see from screenshots, another bug is RIL and as far as I remember audio doesn't work as well.
Click to expand...
Click to collapse
Hehe ... since I did not have a SIM inserted in the pone x3
I finished compiling GlazeOS (android 7.1.2_r8) for LG L7 II (Vee7).
https://www.androidfilehost.com/?fid=745425885120732876 Anyone want to try?!
NOTE: Do not flash recovery from this ROM, it will not work and maybe damage /recovery partition!
My main job is to make nougat rom for Huawei Y300/G510 since there is none till today, but first to made working rom for LG L7 II, because of more resources and because of similar specifications (same CPU, GPU, RAM).
adeii said:
I finished compiling GlazeOS (android 7.1.2_r8) for LG L7 II (Vee7).
https://www.androidfilehost.com/?fid=745425885120732876 Anyone want to try?!
NOTE: Do not flash recovery from this ROM, it will not work and maybe damage /recovery partition!
My main job is to make nougat rom for Huawei Y300/G510 since there is none till today, but first to made working rom for LG L7 II, because of more resources and because of similar specifications (same CPU, GPU, RAM).
Click to expand...
Click to collapse
Hi. I am not able to flash the rom. I am getting 'signal 4 error' right at the start.
It failed even after removing assert() functions and otasigcheck. Maybe the updater-script is corrupted.
Kindly fix this issue.
Can't wait to try this one.
@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
XDA-00 said:
@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
Click to expand...
Click to collapse
Thank you for trying. I do not know why is not booting.
Device tree is from: https://github.com/LegacyLG
I also got flashing error 4, on TWRP 3.1.0.0, on Y300, use update-binaries fro 6.0.1 rom to finish installing.
Also do not boot, keeps restarting on Huawei logo screen.
In your log, there are errors like:
0.000000] smem_find(137, 80): wrong size 64
0.000000] smem_find(137, 72): wrong size 64
0.094871] vddx_c2: 750 <--> 1500 mV at 1150 mV normal
0.094999] Error-Bad Function Input
0.187663] CRASH LOG START ADDR : 0x1ff3e000
0.187854] CRASH LOG END ADDR : 0x1ff3efff
0.225056] qup_i2c qup_i2c.1: I2C slave addr:0x3e not connected
0.225269] sx150x 1-003e: i2c write fail: can't write 01 to 1f: -107
0.225624] sx150x: probe of 1-003e failed with error -107
0.447166] get_nand_partitions: no flash partition table in shared memory
0.456164] rpcrouter: Server create rejected, version = 0, program = 3000003b
Do you know what could make them?
adeii said:
Thank you for trying. I do not know why is not booting.
Device tree is from: https://github.com/LegacyLG
I also got flashing error 4, on TWRP 3.1.0.0, on Y300, use update-binaries fro 6.0.1 rom to finish installing.
Also do not boot, keeps restarting on Huawei logo screen.
In your log, there are errors like:
0.000000] smem_find(137, 80): wrong size 64
0.000000] smem_find(137, 72): wrong size 64
0.094871] vddx_c2: 750 <--> 1500 mV at 1150 mV normal
0.094999] Error-Bad Function Input
0.187663] CRASH LOG START ADDR : 0x1ff3e000
0.187854] CRASH LOG END ADDR : 0x1ff3efff
0.225056] qup_i2c qup_i2c.1: I2C slave addr:0x3e not connected
0.225269] sx150x 1-003e: i2c write fail: can't write 01 to 1f: -107
0.225624] sx150x: probe of 1-003e failed with error -107
0.447166] get_nand_partitions: no flash partition table in shared memory
0.456164] rpcrouter: Server create rejected, version = 0, program = 3000003b
Do you know what could make them?
Click to expand...
Click to collapse
https://github.com/search?utf8=✓&q=vee7&type=
Some of the links are from nicknitewolf. Just Saying.
I tried TWRP 3.1.1-0 made by him and it did not work. Wasn't able to boot into recovery.
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7
OR THIS :- https://github.com/TeamHackLG/android_device_lge_msm7x27a-common
I really can't help much, but you can ask neutrondev or weritos for help, they might solve the issue and if you recompile the rom, just change the value of ro.secure to 0 (in default.prop of kernel)
OR Maybe you can ask for help at modaco too.
Do you know what could make them?
Click to expand...
Click to collapse
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Thats all I can say.
Lets hope someone fixes the issue and we'll have nougat for our devices.
Edit :- just realized that the fork should be from msm7x27 not msm7x30 (see attachment)
and re-check fstab.vee7, there might be some error regarding partitions/blocks.
@adeii
Try this boot.img (see attachments)
XDA-00 said:
https://github.com/search?utf8=✓&q=vee7&type=
Some of the links are from nicknitewolf. Just Saying.
I tried TWRP 3.1.1-0 made by him and it did not work. Wasn't able to boot into recovery.
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7
OR THIS :- https://github.com/TeamHackLG/android_device_lge_msm7x27a-common
I really can't help much, but you can ask neutrondev or weritos for help, they might solve the issue and if you recompile the rom, just change the value of ro.secure to 0 (in default.prop of kernel)
OR Maybe you can ask for help at modaco too.
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Thats all I can say.
Lets hope someone fixes the issue and we'll have nougat for our devices.
Edit :- just realized that the fork should be from msm7x27 not msm7x30 (see attachment)
and re-check fstab.vee7, there might be some error regarding partitions/blocks.
Click to expand...
Click to collapse
Thanks a lot for reply. I hope I'll find errors. Have you tried to boot with newboot.img ? Somewhere is written that TWRP 3.0.3.0 should be enough to boot 7.1.1...but this is 7.1.2.
adeii said:
Thanks a lot for reply. I hope I'll find errors. Have you tried to boot with newboot.img ? Somewhere is written that TWRP 3.0.3.0 should be enough to boot 7.1.1...but this is 7.1.2.
Click to expand...
Click to collapse
You're welcome. And no I did not try, I'm done.. for now.
I have TWRP 3.0.2-0. Its the only working recovery.
Try contacting weritos or neutrondev.
XDA-00 said:
@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
Click to expand...
Click to collapse
How did you manage to make logs while booting the device?I cant figure out how to do that.
I set persist.sys.usb=adb and ro secure=0 but adb says device unauthorized.
Thanks.
Gent' said:
How did you manage to make logs while booting the device?I cant figure out how to do that.
I set persist.sys.usb=adb and ro secure=0 but adb says device unauthorized.
Thanks.
Click to expand...
Click to collapse
After kernel crash/bootloop, goto twrp > advanced > terminal and type :
For kernel log :-
cat /proc/last_kmsg > /sdcard/last_kmsg.text
For dmesg :-
dmesg > /sdcard/dmesg.txt
Edit :- set persist.adb.debugging to 1 if not done already.
XDA-00 said:
https://github.com/search?utf8=✓&q=vee7&type=
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Click to expand...
Click to collapse
Kernel is changed to weritos' Vee7.
https://www.androidfilehost.com/?fid=817550096634773143 try this kernel.
From 7.0 it is changed to file_contexts.bin, no more textual file contexts.
Newer kernel, with updated fstub.qcom and ro.secure and ro.adb.secure=0 at https://www.androidfilehost.com/?fid=961840155545568953
adeii said:
Kernel is changed to weritos' Vee7.
https://www.androidfilehost.com/?fid=817550096634773143 try this kernel.
From 7.0 it is changed to file_contexts.bin, no more textual file contexts.
Newer kernel, with updated fstub.qcom and ro.secure and ro.adb.secure=0 at https://www.androidfilehost.com/?fid=961840155545568953
Click to expand...
Click to collapse
Did not boot man. I tried both kernels but did not succeed.
See logcat.
KMSG :- https://pastebin.com/dvDjz6S6
DMESG :- https://pastebin.com/ppNiHVFX
Try changing SELINUX to permissive default and upload fixed rom zip.
Are you sure that the file inside is fstAb.qcom and NOT fstUb.qcom
Don't lose hope.:fingers-crossed:
Good work man !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TripNDroid Mobile Engineering is proud to hereby announce the release of the TripNDroid rom for the Cheeseburger also known as the OnePlus5
Android 7.1.2 Nougat
Working:
- As far as i know everything
Not working:
- Please let me know..
So here we are, after a few years of absense TripNDroid is back with finally a brand new ROM, all the TripNDroid mods are completely rebuilded in Android 7.1.2.
Please report anything you find! The things you like but also the ones you don't
ROM has its very own style, looks and features including source built natively TripNDroid Dolby sound processing and various TripNDroid modifications just like the old days. And last but not least.. i'm welcoming you to the TripNDroid experience.
Features:
- Latest firmware included
- TripNDroid Dolby Sound Processing
- Up to 7.1 surround sound decoding
- Dolby DTS decoder
- OptiSound™
- TripNDroid look and feel
- Native root built-in
- Custom ringtones
- Custom messaging tones
- TripNDroid I/O scheduler
- Custom apps
- Basic gapps included
Supported A/V Formats
- AC3, Dolby DTS, Dolby DTS-HD, MKV, WMV, WMA, MOV, REAL and more!
Installation instructions:
- Go into recovery
- Full wipe when coming from any other rom
- Format /system if you're upgrading from earlier version
- Flash the rom
- Reboot
- Enjoy the TripNDroid experience
Changelog 1.2:
- Added TDF (TripNDroid Framework)
- 32bit audio support
- TripNDroid CPU governor
- TDF CPU hotplug
- 230mhz min. frequency
- 364mhz max. frequency in suspend
- Max. 2 cores online in suspend
- Small rom bugfixes
Changelog 1.1:
- Multi-sim fixup (didnt test it, but should work)
- Upgraded TripNDroid I/O scheduler
- Improved speed
- Tried to make it unified to work on encrypted/decrypted (test it and report back)
If you are encrypted and rom doesnt boot you can try flashing this boot.img within recovery.
Download rom:
https://mega.nz/#!iZ5WjAoC!O3bySKZl5vUWugeDTqF3_NUIJ4At0PxfZYcmSTF3DcQ
https://www.androidfilehost.com/?fid=745849072291690051
Enjoy another fine TripNDroid release!
Keep in touch!
You can follow TripNDroid Mobile Engineering on Twitter. Feel free to hit me up there if you have anything to share or just to follow.
Sources:
https://github.com/TripNDroid
https://github.com/TripNRaVeR
Do it yourself!
The complete tutorial how to build a TripNDroid rom
On ubuntu from the command line execute the following:
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
REBOOT
Code:
cd ~/android/system/
repo init -u git://github.com/TripNRaVeR/android.git -b master-44
. build/envsetup.sh
lunch
choose tripndroid-cheeseburger-userdebug
Code:
make -j8 otapackage
Replace 8 with the number of CPU's in youre system
Credits:
Lineage OS
CAF
James Fung for the base EQ
TeamAmaze for the FileManager base
Reserved!
Tnx fot this! Will flash it asap!It will be the last N build before Oreo?Thanks!
P.s: @TripNRaVeR sorry buddy, do we need to flash also magisk or is already included? Tnx!
Awesome to see you here !! Will try it asap
Flamehell said:
Tnx fot this! Will flash it asap!It will be the last N build before Oreo?Thanks!
P.s: @TripNRaVeR sorry buddy, do we need to flash also magisk or is already included? Tnx!
Click to expand...
Click to collapse
It is natively rooted. :good: (i forgot to add that info to the OP)
TripNRaVeR said:
It is natively rooted. :good: (i forgot to add that info to the OP)
Click to expand...
Click to collapse
I flashed the rom(i was on oos,i m encrypted)boot animation is working,but it stay on that,is it normal or first boot take long time before start?Thanks!
Flamehell said:
I flashed the rom(i was on oos,i m encrypted)boot animation is working,but it stay on that,is it normal or first boot take long time before start?Thanks!
Click to expand...
Click to collapse
I'm uncrypted myself so i dont really know. I will make a bootimage for encypted phones. Just a minute.
TripNRaVeR said:
I'm uncrypted myself so i dont really know. I will make a bootimage for encypted phones. Just a minute.
Click to expand...
Click to collapse
Thanks buddy,really apreciate
Flamehell said:
Thanks buddy,really apreciate
Click to expand...
Click to collapse
Download the bootimage here:
https://mega.nz/#!6RRRlDCA!vv0B2HAhVkRZ_cAcnsG8xHX5x4buDHNvsJ33qhn2F2M
- Reboot to fastboot
- "fastboot flash boot boot.img"
- "fastboot reboot"
TripNRaVeR said:
Download the bootimage here:
https://mega.nz/#!6RRRlDCA!vv0B2HAhVkRZ_cAcnsG8xHX5x4buDHNvsJ33qhn2F2M
- Reboot to fastboot
- "fastboot flash boot boot.img"
- "fastboot reboot"
Click to expand...
Click to collapse
Will report in a few sec :good:
Thanks for this rom for me the same don't boot
PS:
Ok thanks for the boot img
I'm not on a computer can I flash this in recovery like a recover img?
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
TripNRaVeR said:
Download the bootimage here:
https://mega.nz/#!6RRRlDCA!vv0B2HAhVkRZ_cAcnsG8xHX5x4buDHNvsJ33qhn2F2M
- Reboot to fastboot
- "fastboot flash boot boot.img"
- "fastboot reboot"
Click to expand...
Click to collapse
Same issue also after flashing the boot img..... do you think that the issue is because i am encrypted?
Flamehell said:
Same issue also after flashing the boot img..... do you think that the issue is because i am encrypted?
Click to expand...
Click to collapse
I don't think it has something to do with Encrypted. Did you format the Data beforehand? I flashed the original rom on an encrypted phone and booted good just that it takes a while to boot. Few secs you'll just see the Android Mascot and then the boot animation.
Try flashing this in recovery.
https://mega.nz/#!uZB3AJZL!8CujRfKAtLupMr1EXpw90MGeNUgVQsVk4B3A5Q3OG-w
Or this:
https://mega.nz/#!GFoBXQKJ!-Ysb4QETiMMdeQULa39EnrSyc8zeFStEN1GexDtztO4
TripNRaVeR said:
Reserved!
Click to expand...
Click to collapse
As I understand, this Rom is for good sound lovers?
Has it 32bit audio processing? (default is 24)...
Alex Tian8800 said:
As I understand, this Rom is for good sound lovers?
Has it 32bit audio processing? (default is 24)...
Click to expand...
Click to collapse
Not yet...
TripNRaVeR said:
Not yet...
Click to expand...
Click to collapse
OK, hope, this Rom will make OP 5 a real Music player. SD 835 has a lot of improvements for this... :cyclops:
---------- Post added at 05:30 AM ---------- Previous post was at 05:28 AM ----------
Also, what about custom kernels? As I understood, your Rom has your own Kernel?
Alex Tian8800 said:
OK, hope, this Rom will make OP 5 a real Music player. SD 835 has a lot of improvements for this... :cyclops:
---------- Post added at 05:30 AM ---------- Previous post was at 05:28 AM ----------
Also, what about custom kernels? As I understood, your Rom has your own Kernel?
Click to expand...
Click to collapse
This rom will always include a custom TripNDroid kernel that matches this rom.
You are obviously free to flash and try a custom kernel but there will be no support for using them. :good:
TripNRaVeR said:
This rom will always include a custom TripNDroid kernel that matches this rom.
You are obviously free to flash and try a custom kernel but there will be no support for using them. :good:
Click to expand...
Click to collapse
OOS or LOS Kernel?
Does it include Oos cam with Portrait Mode and volte wrking?
And also since it's pre rooted, which u have included magisk or supersu?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
TheRagingBeast Kernel for X00TD, a kernel entirely battery oriented and optimized for balanced use laced with unique features never seen before in other custom kernels.
Features
latest Linux version - 4.4.163
Overclocked And undervolted
Power and battery efficient
Fast charge ( screen on- 1.5A screen off- 2-1.8A )
No Stock stepping charge
Minimum frequency set to 300 including deep sleep
Sound Gain (Headphone gain and mic gain)
KCal Control
WireGuard
TouchBooster (OPTIONAL)
U can check more on Telegram channel
MOD EDIT: LINKS REMOVED
Small fix for dt2w if its not working :
1.Get any root explorer
2. Open sys/kernel/touchpanel
3.change dclicknode value to 1
Or
Feeling lazy:
See in channel varun made one magisk module for that purpose
For Stepping charge issue :
Root is mandatory along with kernel aduitor (u can get it from play store)
In kernel aduitor turn on "Intellithermal" and select apply on boot
Reboot to recovery
Mount system and vendor
Remove these mentioned files using twrp file manager :
a) vendor/etc/thermal-engine.conf
b) system/bin/thermalserviced
Reboot
Turn on/off usb fast charge in battery section of kernel aduitor check whichever mode gives you better speeds
Installation
Reboot to recovery
Flash latest kernel zip.
Downloads:
MOD EDIT: LINK REMOVED
For HOMEMADE-CLANG MOD EDIT: LINKS REMOVED
Credits:
Asus for device and sources
[email protected] #DérpGang™ #$tayRaged™ (TheHardGamer) - making this kernel possible
DérpGang for helping
@osm0sis for AnyKernel2
kanishk and @joshi1 for testing
May be others too .....
Source code:
https://github.com/joshi3/android_kernel_asus_sdm660
Version
Stable
Finally on xda, thanks
Please add d2tw support
thekrishna said:
Please add d2tw support
Click to expand...
Click to collapse
Already there ... Didn't mention because they are common
joshi1 said:
Already there ... Didn't mention because they are common
Click to expand...
Click to collapse
DT2W is not working! Currently on Havoc OS
Dt2w not working on stock 334 build
thekrishna said:
Dt2w not working on stock 334 build
Click to expand...
Click to collapse
Flash magisk module for dt2w..
D2w not working bro
very slow charging..
-D2w not working by default im on msm extended letest
-charging is very fast compared ko previous other kernels i used
-giving best battery backup
-please add feature to make small cores and big cores controller for turning cores on/off in hotplug ,Alucard hotplug doesn't turn cores off properly(because i want to turn all big cores off as i used to do with my previous different device)
-please add hotplug boost
-I like many features in this kernel and im hoping for updates further.
-can i use intellithermal and alucard at same time?
-thanks dev
Dt2s working? I'm on pixel experience
Paresh18shah said:
Flash magisk module for dt2w..
Click to expand...
Click to collapse
What is module's name?
X_Blade said:
What is module's name?
Click to expand...
Click to collapse
Try this one..
The idle battery drain is too much... 4% in just 3.5 hrs?, without internet or wifi or any apps in the background.
Harsh Maroo said:
The idle battery drain is too much... 4% in just 3.5 hrs, without internet or wifi or any apps in the background.
Click to expand...
Click to collapse
Tweak cpu frequency ... And drain depends on many factors like wifi network rom etc etc
Bro , DT2W not work in stock rom. Try install magisk module too. Kernel is very good
thekrishna said:
Bro , DT2W not work in stock rom. Try install magisk module too. Kernel is very good
Click to expand...
Click to collapse
See post #1
thanks for the kernel, i really enjoy with this kernel,
i really waiting for next update
Ok , now working DT2W. THANKS BRO.
Source is private...lol
This Kernel is for EA Android Q version. If you're using TM or ATT, please cross flash to EA.
This Kernel Does not Support for L51A(JP version[DOCOMO])
(I have committed the TM20k change in rebase but not merge in EA version)
NOTE:
1. Your Phone must be unlocked bootloader and have magisk root
2. Your Phone's ANDROID VERSION must be 11/12
KERNEL FEATURE:
01. Merge CAF version into LA.UM.9.12.r1-14000-SMxx50.0
02. Merge DTS version into LA.UM.9.12.r1-14000-SMxx50.0
03. Update Kernel version to 4.19.225
04. Move to PELT
05. Use Sultan Kernel Toast's CPU/Devfreq input boost
06. Use SIMPLE LMK (Sultan Kernel Toast's)
06. GPU overclock to 855Mhz (I've broke the TM varient while oc to 870MHZ)
07. KCAL support
08. Import Juhyung Park arter97's exfat to support LGE's texfat
09. Use Proton Clang 13 for kernel compiling
10. Disable blocking touch while reboot to recovery (TESTING) -> author: SGCMARKUS
HOW TO FLASH:
1. The flashable zip is support Magisk, Flash it just like flashing a module.
DOWNLOADLINK:
MEGA LINK
KERNELSOURCE:
GITHUB LINK
Special Thanks:
* SGCMarkus
* Sultan (kernel toast)
* Arter97
* Ayrton990
* TingyiChen
* LibXZR
* EmanuelCN
* spakkkk
AND Many Other Great Developers!
Final: Sorry about my English
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChangeLog
Android 12:
V6:
1. Merge ACK (Kernel version: 4.19.267)
2. Update exfat source from namjaejeon
3. Merge latest f2fs-stable
4. Fix LGE wifi private command error
V5:
1. Merge ACK (Kernel version: 4.19.261)
2. Update exfat source from namjaejeon
V4:
1. Merge ACK (Kernel version: 4.19.255)
2. Merge caf tag to LA.UM.9.12.r1-14700-SMxx50.0
3. Merge latest f2fs-stable
4. Update crypto.
Android 11:
V13 (Reupload):
WALT only:
1. Merge ACK (Kernel version: 4.19.255)
2. Merge caf tag to LA.UM.9.12.r1-14500-SMxx50.0
3. Merge latest f2fs-stable
4. Tweak little cpu freq to reduce animation lags
5. Clang 16 support
6. Use LRNG random
V12:
WALT only:
1. Merge ACK (Kernel version: 4.19.251)
2. Merge caf tag to LA.UM.9.12.r1-14300-SMxx50.0
3. Android 12 support And FIX com.android.phone crashed
4. Android 11 final (no longer update)
V11:
WALT/PELT:
1. Merge ACK (Kernel version: 4.19.240)
2. MPTCP update to 0.95.2
3. ZRAM update to 5.15 (Arter97)
BUG:
1. HIGHER CPU JITTER DURATION AND I CAN'T SOLVE IT ANYMORE
2. DON'T KNOW ABOUT WIFI ISSUE
Really fast kernel. It works fine on my V600Ea
If im on the att 60 A10, can i still crossdflash?
FC06 said:
If im on the att 60 A10, can i still crossdflash?
Click to expand...
Click to collapse
It's necessary, but i don't have a guide to crossflash to EA ver
staljin said:
Really fast kernel. It works fine on my V600Ea
Click to expand...
Click to collapse
The v2 version has been rebuilt, details are on the changelog.
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
crimsonrommer said:
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
Click to expand...
Click to collapse
I came to ask this question for the exact same reason.
crimsonrommer said:
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
Click to expand...
Click to collapse
mnt/product/op -> the configs of volte are in this folder
ErickG233 said:
mnt/product/op -> the configs of volte are in this folder
Click to expand...
Click to collapse
Right and what do I do with that info lol?
crimsonrommer said:
Right and what do I do with that info lol?
Click to expand...
Click to collapse
back up your preset folder, and backup your ftm(dev/block/bootdevice/by-name/ftm) block, refurbish to ea 20j, then use hex to open ftm binary file, search "FFF" with asicII(not hex), then change the end number(ea is 11), flash it,then replace all the files in /mnt/product/OP/OPEN_EU/etc and /mnt/product/OP/OPEN_EU/cust.prop then reboot.
maybe one day i will post a thread about OP mod....
ErickG233 said:
back up your preset folder, and backup your ftm(dev/block/bootdevice/by-name/ftm) block, refurbish to ea 20j, then use hex to open ftm binary file, search "FFF" with asicII(not hex), then change the end number(ea is 11), flash it,then replace all the files in /mnt/product/OP/OPEN_EU/etc and /mnt/product/OP/OPEN_EU/cust.prop then reboot.
maybe one day i will post a thread about OP mod....
Click to expand...
Click to collapse
To replace the files in the OPEN_EU folder, where do I get the new files from?
I believe a thread on changing the OP is much needed and appreciated since there are a lot att devices crossflashed to EU FW.
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
Hi, I live in Europe and I have v600tm, I like to put my company's software, i looked everywhere on this site to understand how to cross flash, can you please link me a place to understand how cross flash works, thanks and sorry for my English
MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
V6 has been released.
Any plans in releasing a kernel that doesn't require crossflash?
crimsonrommer said:
Any plans in releasing a kernel that doesn't require crossflash?
Click to expand...
Click to collapse
Well you can flash anyway, it can boot but not sure NO BUG.
Bootable variant (A11): TM ver.
MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
How did u crossflashed your V600TM to EA firmware?
Hi, just wanna ask which EA firm should i crossflash? Tried on mine Crossflashed but i got kernel panic
Kratos574 said:
Hi, just wanna ask which EA firm should i crossflash? Tried on mine Crossflashed but i got kernel panic
Click to expand...
Click to collapse
you need to recover the abl from kdzs NOT the factory ABL