Hello, friends who own G2 Mini. I'm trying for the past weeks to build AOSP (Lollipop) to the D618 variant. Even though I was able to build the zip files and flash them, the ROM won't boot. Instead of booting, I get an error in LG logo with fastboot stuff at the corner of the screen. I believe it's kernel related but I have no idea how to fix, that's where you guys participate. Could you guys help me, please?
The sources I'm using for Kernel is LG original sources, I built the zImage from the .TXT in that source.
Here's a picture of the error:
{
"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"
}
Thank you guys.
Hello, I was wondering if I could install a pure Android lollipop on a AT&T Moto X 2014?
Sent from my XT1097 using XDA Free mobile app
mmaslo1124 said:
Hello, I was wondering if I could install a pure Android lollipop on a AT&T Moto X 2014?
Sent from my XT1097 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know because this is G2 Mini forum.
Go to Moto X section.
Same apply to your case
http://forum.xda-developers.com/showthread.php?p=57798377
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Vagelis1608 said:
Same apply to your case
http://forum.xda-developers.com/showthread.php?p=57798377
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Click to expand...
Click to collapse
So you mean that if I make a zImage-dtb it will work? (Sorry for dumb questions =) )
jfpsb said:
So you mean that if I make a zImage-dtb it will work? (Sorry for dumb questions =) )
Click to expand...
Click to collapse
I mean that there is an issue with your compiled dtb.img
http://forum.xda-developers.com/showthread.php?p=57812554
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Vagelis1608 said:
I mean that there is an issue with your compiled dtb.img
Click to expand...
Click to collapse
So, I compiled a .dtb file from msm8226-g2mds_global_com .dts files, made all the changes in the defconfig file to point to this .dtb file to build the prebuilt kernel with it (I was even able to build the dt.img using dtbToolCM, just to see if it would work). Okay, the zImage-dtb was built fine, I used it in my AOSP build but the error was still the same from OP. Do you know what could be wrong? And to be honest, I'm not really sure how to use that mkbootimg.mk to build AOSP, could you help me?
My defconfig looks like this after the changes:
Code:
#
# Boot options
#
CONFIG_USE_OF=y
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE=y
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE_NAMES="msm8226_g2mds"
CONFIG_ZBOOT_ROM_TEXT=0
CONFIG_ZBOOT_ROM_BSS=0
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_CMDLINE="console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x37 androidboot.hardware=g2mds"
# CONFIG_XIP_KERNEL is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
# CONFIG_AUTO_ZRELADDR is not set
Now I really don't know what the heck is wrong here, I hope someone could help me. Thanks.
Extract dtb.img from stock kernel using Android Image Kitchen and put it in your kernel (again, using AIK)
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Worked
Vagelis1608 said:
Extract dtb.img from stock kernel using Android Image Kitchen and put it in your kernel (again, using AIK)
Click to expand...
Click to collapse
So, I did that (unpacked the boot.img and repacked with my prebuilt zImage) and worked fine, no longer kernel errors, but the phone still won't boot. Do you have any ideas? For sure it's not kernel related anymore (I believe). The phone just stay in LG logo, don't go to boot animation, then reboots to recovery. Thank you very much for the AIK tip by the way.
jfpsb said:
So, I did that (unpacked the boot.img and repacked with my prebuilt zImage) and worked fine, no longer kernel errors, but the phone still won't boot. Do you have any ideas? For sure it's not kernel related anymore (I believe). The phone just stay in LG logo, don't go to boot animation, then reboots to recovery. Thank you very much for the AIK tip by the way.
Click to expand...
Click to collapse
Just grab dmesg and logcat from your ROM with adb and see if you can find what goes wrong.
Sent from my D620r [Stock 4.4.2]
Vagelis1608 said:
Just grab dmesg and logcat from your ROM with adb and see if you can find what goes wrong.
Sent from my D620r [Stock 4.4.2]
Click to expand...
Click to collapse
Ok, I'll try. Thanks a lot.
New problem
I have a new problem now, friends. I'm trying to build CM12 now (I put AOSP aside for a moment). I can get it built everytime, the problem is that it never boots and I have no idea why (like always). And I can't take any dmesg or logcats, don't work either. So, down below there's a video showing the problem. Any ideas? Thanks.
MORE INFO: that weird thing in the corners never leave the screen, even in recovery mode. You guys think it's something related to kernel?
http://youtu.be/Z3cnXFfbciY
I tried more stuff but nothing works. I'm about to give up on this. Any help?
Related
Hello, I'm trying to compile my own kernel from sources for this piece of hardware, everything went well and I completed the whole process, but with my kernel device doesn't boot up and stuck on boot screen at bootloader stage (fastboot mode). I'm using CNexus Boot.img tools from here. To obtain
PAGE SIZE: 2048
BASE ADDRESS: 0x00000000
RAMDISK ADDRESS: 0x01000000
I've used arm-eabi-4.6, stock and working kernel with command ./boot_info boot_327680.bin so I think, these parameters are ok.
{
"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"
}
Whole ramdisk image is also taken from stock kernel with command ./split_boot boot_327680.bin. Configuration used ".config" comes from stock kernel too. Even after compilation of pure split image, device won't boot...
This piece of code I'm using to compile kernel image for example:
Code:
./mkbootimg --kernel boot_327680.bin-kernel --ramdisk boot_327680.bin-ramdisk.cpio.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x37 androidboot.hardware=g2m" --base 0x00000000 --pagesize 2048 --ramdiskaddr 0x01000000 -o test_stock.img
It looks like in newly compiled kernel at the end of file a lot of code is missing.
You may open following files with hex or text editor to see what I mean.
Stock kernel:
https://www.dropbox.com/s/0jidfk7jcsopvy7/stock_boot.bin?dl=0
Compiled one:
https://www.dropbox.com/s/ceui3620ief7m5j/test_stock.img?dl=0
Any suggestions?
Really? No one can help me?
What about dt image in boot image?
Zaaap72 said:
What about dt image in boot image?
Click to expand...
Click to collapse
Thank you for that, didn't really know about that, now I have to find out how to build dt.img or extract it from stock image.
Wysłane z mojego LG-D620 przy użyciu Tapatalka
I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.
EDIT: Attached here kernel with broken video and logcat of it.
If someone want to test it and help me to find out the problem, do nandroid boot backup first!
Guys for CM we need CAF kernel. Kernel from me is CAF and need couple of fix but system is boot and working.
Lukiqq said:
I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.
EDIT: Attached here kernel with broken video and logcat of it.
If someone want to test it and help me to find out the problem, do nandroid boot backup first!
Click to expand...
Click to collapse
Which sources did you use?
Garcia98 said:
Which sources did you use?
Click to expand...
Click to collapse
Pure stock sources from LG site.
Lukiqq said:
I managed to build working kernel but something is still wrong with graphics, there is no image, display stays black. I can hear that system boots up and touch is working, adb is working too.
EDIT: Attached here kernel with broken video and logcat of it.
If someone want to test it and help me to find out the problem, do nandroid boot backup first!
Click to expand...
Click to collapse
Can You post a logcat file with that command : logcat *:E
Lukiqq said:
Pure stock sources from LG site.
Click to expand...
Click to collapse
And are you using stock ROM?
Garcia98 said:
And are you using stock ROM?
Click to expand...
Click to collapse
Yes, stock odexed ROM.
PS. Repacked with this method and then compiled stock boot.img is working ok, so I assume something is wrong with zImage instead of ramdisk.
Lukiqq said:
Yes, stock odexed ROM.
PS. Repacked with this method and then compiled stock boot.img is working ok, so I assume something is wrong with zImage instead of ramdisk.
Click to expand...
Click to collapse
Which defconfig did you use?
Garcia98 said:
Which defconfig did you use?
Click to expand...
Click to collapse
I've used extracted config from stock kernel and d620 global, both failed same way...
Lukiqq said:
I've used extracted config from stock kernel and d620 global, both failed same way...
Click to expand...
Click to collapse
If you upload the source that you used to GitHub I vould help you more, because I doubt that you used stock kernel source code plus stock defconfig, as in logcat appears some errors of missing functions that are defined in stock kernel source
partyzant_x said:
Can You post a logcat file with that command : logcat *:E
Click to expand...
Click to collapse
Here you go, kernel compiled from clean LG sources + Garcia98 config file cyanogenmod_g2m_defconfig. Still working system with black screen
I give up... tried one more time with Zaaap72 CM kernel sources and this time I've got bootloop right after first LG logo appear :-/
Still no ideas? C'mon DEVS! Any help would be greatly appreciated!
OT.
Are you THE Lukiqq, who made kernels for spica???
judas1977 said:
OT.
Are you THE Lukiqq, who made kernels for spica???
Click to expand...
Click to collapse
Indeed, now I'm the one who needs help
Hmm.. i think i cannot help you, because i have LG G2 Mini twin brother - L90. But making own kernel from clean LG sources comes trough my mind)
I've got a Samsung Galaxy Alpha (EU) and started to create a recovery. It doesn't fully work yet but we will get there ...
You can get the sources here: http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/
My phone arrived and I got the recovery working. Looks like some features aren't working yet. I need to dive deeper and get the kernel compiled.
hensk said:
Do you have experience to unlock Art in Developer setting coz is kernal related
will be nice to have it
Click to expand...
Click to collapse
you can try by replacing libdvm.so to libart.so in /data/property/persist.sys.dalvik.vm.lib
the adb command for should be: adb shell 'echo libart.so >/data/property/persist.sys.dalvik.vm.lib'
i would like to remind you that ART and exposed are not compatible. i also read that samsung's touch wiz will crash or cause bootloop with ART. you can do a backup and try ART. in case you have bootloop just restore, install another launcher, unistall touch wiz and you should be fine
in case you will try, please report back and let us know how it went.
I was able to fix the kernel to build it with the CM toolchain. Next step is using a built kernel. After that it is time to start with CM.
neofral said:
you can try by replacing libdvm.so to libart.so in /data/property/persist.sys.dalvik.vm.lib
the adb command for should be: adb shell 'echo libart.so >/data/property/persist.sys.dalvik.vm.lib'
i would like to remind you that ART and exposed are not compatible. i also read that samsung's touch wiz will crash or cause bootloop with ART. you can do a backup and try ART. in case you have bootloop just restore, install another launcher, unistall touch wiz and you should be fine
in case you will try, please report back and let us know how it went.
Click to expand...
Click to collapse
Thanks neofral,for scripts info but about
not compatibility ART with Wanam I know this issue i have SGS 4 also
modpunk said:
I was able to fix the kernel to build it with the CM toolchain. Next step is using a built kernel. After that it is time to start with CM.
Click to expand...
Click to collapse
you dude building kernal also,will it work with TW roms or only for CM
The plan is to get it first working with the TWRP recovery. The rooting stuff should be disabled. And I need adb working on the recovery. Currently you can't get a 'adb shell' on the recovery.
I ran into several issues building the kernel. A lot of fixes are needed, especially for a out of source build. The CM toolchain is old which is also an issue. But the biggest problem is that the dts files are missing to build the Device Tree ...
modpunk said:
I ran into several issues building the kernel. A lot of fixes are needed, especially for a out of source build. The CM toolchain is old which is also an issue. But the biggest problem is that the dts files are missing to build the Device Tree ...
Click to expand...
Click to collapse
i think it's a serious issue since CM officially don't support Exynos platform anymore. they say it's about Samsung Knox but i'm sure there are other things in the play.
if your aim is to build a kernel for our devices i think it's much better to have an awesome kernel for stock rom first and leave some time to see how things develop in CM community with regards to Exynos
neofral said:
i think it's a serious issue since CM officially don't support Exynos platform anymore. they say it's about Samsung Knox but i'm sure there are other things in the play.
if your aim is to build a kernel for our devices i think it's much better to have an awesome kernel for stock rom first and leave some time to see how things develop in CM community with regards to Exynos
Click to expand...
Click to collapse
This was just of issues with Exynos 4, see https://plus.google.com/+CyanogenMod/posts/2a8SiSZpxPn
I've sent a mail to the Samsung using their form on the opensource website. Lets see if they will release new Kernel sources.
I finally got the kernel built in the CM tree and it works using the stock dtb file. Now I need to fix adb/mtp.
hensk said:
hi m8
You already have progress in building your recovery & kernal
send it to me if you like tester
Click to expand...
Click to collapse
In the meantime mtp is correctly starting up after fixing the init system. Parsing /proc/cpuinfo failed cause the buffer was to small for a octa core. adb still doesn't start. I will try tomorrow or on the weekend...
{
"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"
}
Yeah, finally a adb shell as root on the recovery! Time to start with CM ...
Mod Edit
Thread cleaned.
Unless you are a developer and contributing to this project , please refrain from posting here.
Thank you
malybru
Forum Moderator
Guys
Official TWRP 2.8.7.0 has just been released for the OnePlus 2. Should work on all variants.
{
"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"
}
Note: you install at your own risk. Do not try to install this on any other devices.
I have worked with Dees_Troy to get a build out for the OnePlus 2. Download available here: https://twrp.me/devices/oneplustwo.html
Please test and let us know if there are any issues. Should work with all three devices. I currently have a2001 64gb.
Current version of TWRP will flash OTA's. I have tested this.
if anybody wants to become a device maintainer let us know. You need required skills to build TWRP from source.
Reserved
Is Device Encryption supportet in this build?
I haven't tested that yet, not something I would normally use.
works on A2003 64gb! thanks!
There's an issue with the device name of recovery. Currently it's "oneplus2" which prohibits OTAs from being installed because it requires device name to be "OnePlus2". (Case sensitive)
ansysic said:
Is Device Encryption supportet in this build?
Click to expand...
Click to collapse
seems to be not :'-(
so i can't update to 2.1 ...
did anyone have the stock recovery ? and will wit work with it ?
Meneco87 said:
works on A2003 64gb! thanks!
Click to expand...
Click to collapse
Confirmed.
Quote:
Originally Posted by Meneco87
works on A2003 64gb! thanks!
Quote:
Originally Posted by Gamm86
Confirmed.
Confirming the confirmation
SpiritBreak3r said:
There's an issue with the device name of recovery. Currently it's "oneplus2" which prohibits OTAs from being installed because it requires device name to be "OnePlus2". (Case sensitive)
Click to expand...
Click to collapse
I'll see if I can get that updated!!
works on A2001 64gb thanks
Stephen said:
if anybody wants to become a device maintainer let us know. You need required skills to build TWRP from source.
Click to expand...
Click to collapse
what skill is require to become a device maintainer?
[email protected] said:
what skill is require to become a device maintainer?
Click to expand...
Click to collapse
You need to be familiar with building twrp from source. Meaning, you're grabbing the device tree from github and merging it with the twrp sources.
@Stephen: As soon as I get a new PC (should be somewhere around next month, maybe November), I could help out once I got my build environment set up.
threre is not a "oneplus 2" device in the App
danilos2k said:
threre is not a "oneplus 2" device in the App
Click to expand...
Click to collapse
Not in the TWRP app, it needs to be updated first I guess. But you can download and flash it using Flashify.
I was just about to ask about encryption support. Looks like only way to update is with an otg cable but my USB c adapter hasn't come yet.
I have this TWRP 2.8.7.0 version, installed on my OP2 64GB A2001 since about a month ago.
So? What is actually new here? Should I install the "new" version over the same
version, that is already installed on my device?
Hi! For some reason i can't get TWRP to stick
i can boot into using fastboot boot twrp.img but using fast boot flash recovery twrp.img doesn't stick ....original recovery always come back.
thanks!
Joao Oliveira said:
Hi! For some reason i can't get TWRP to stick
i can boot into using fastboot boot twrp.img but using fast boot flash recovery twrp.img doesn't stick ....original recovery always come back.
thanks!
Click to expand...
Click to collapse
Try to flash using flashify.
Tapped from my ❶+❷
TeamWin Recovery Project for LG G2 Mini
In case of current twpr versions were built on old kitkat kernel I decided to compile version on last kernel and android 5.1.1 sources.
Fully supported: D618/D610/D620
How to install:
1. You must have root on your device.
2. You must have bootloader unlocked on your device.
3. If you already have any recovery - download attached archive and flash it via your current recovery.
If you still haven't any recovery - download attached archive, unpack it and flash recovery.img through Rashr
Sources:
Device: https://github.com/NikitaProAndroid/android_device_lge_g2m/tree/omni-5.1
Kernel: https://github.com/NikitaProAndroid/android_kernel_lge_msm8x26/tree/cm-12.1
Awesome work bro...
Thanks bro to makes this phone live
What's better than the older version?
Your version of TWRP is buggy. I can't restore nandroid, it show me error "E:extractTarFork() process ended with ERROR=255". Backup works well. Also some zips can't install. TWRP by powermetza work good for me. The only point for You is that vibration works
barqqlsky89 said:
Your version of TWRP is buggy. I can't restore nandroid, it show me error "E:extractTarFork() process ended with ERROR=255". Backup works well. Also some zips can't install. TWRP by powermetza work good for me. The only point for You is that vibration works
Click to expand...
Click to collapse
The same problem here ERROR=255, can't restore now -.-
[quote name="barqqlsky89" post=64393216]Your version of TWRP is buggy. I can't restore nandroid, it show me error "E:extractTarFork() process ended with ERROR=255". Backup works well. Also some zips can't install. TWRP by powermetza work good for me. The only point for You is that vibration works [/QUOTE]
use TWRP by myllo.setya
http://forum.xda-developers.com/showthread.php?t=3147675 . I am using it right now. It's stable.
Отправлено с моего Lenovo A7600-H через Tapatalk
Uploaded build 2 with fixed system restore from backup. Enjoy!
When i try to use Wipe-> Format Data i get a weird encryption error.. when i use Advanced wipe everything is ok!!
Any newer version for our G2 Mini?
@Nikita Pro Android are you planning to port TWRP 3.0.0 for our phone?
thanks
{
"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"
}
@Nikita Pro Android can you adapt it?
Enviado de meu LG-D618 usando Tapatalk
panagiotisden2 said:
@Nikita Pro Android are you planning to port TWRP 3.0.0 for our phone?
thanks
Click to expand...
Click to collapse
To port - never.
Please bring latest version..plzzzz
Nikita Pro Android said:
To port - never.
Click to expand...
Click to collapse
why not?
Gabenoid said:
why not?
Click to expand...
Click to collapse
Because it is open source project.
Nikita Pro Android said:
Because it is open source project.
Click to expand...
Click to collapse
Do u know if there's gonna be an official release for g2m?
Sent from my LG G2 Mini using XDA Labs
Nikita Pro Android said:
Because it is open source project.
Click to expand...
Click to collapse
Mh..i know that the files are on github..this mean that it's possible to build a TWRP for G2 mini in particular?
How to root?
I would like to install Cyanogenmod in my LG Mini D620, but I am missing how to do the first step: rooting. I tried various ways including LG One Click Root and towelroot. But nothing worked.
I can connect with abd, but reboot recovery brings a "recovery mode" where nothing is possible, literally the android robot on the back picture appears and nothing else.
How I am supposed to root the LG Mini D620?
I'm about to root and unlock bootloader to try flashing any (custom) rom I can find for the d625, any chance this recovery will work?
If not, can anyone please point me to the right direction. No need of holding hands, just a url and I'll find my way.
edit: It's my youngest brother phone, he's starting to get into custom roms, kernels, etc. Yet, he's 11 and I don't have much spare time to help him if the phone goes brick (and I don't wanna leave him without his phone for days til I have the time, so i figured it's better to ask beforehand)
caiowilson said:
I'm about to root and unlock bootloader to try flashing any (custom) rom I can find for the d625, any chance this recovery will work?
If not, can anyone please point me to the right direction. No need of holding hands, just a url and I'll find my way.
edit: It's my youngest brother phone, he's starting to get into custom roms, kernels, etc. Yet, he's 11 and I don't have much spare time to help him if the phone goes brick (and I don't wanna leave him without his phone for days til I have the time, so i figured it's better to ask beforehand)
Click to expand...
Click to collapse
No one has unlocked the bootloader of the D625 (yet?)
If you have any knowledge and you want to help, here is a semi-official thread about it: http://forum.xda-developers.com/g2-mini/general/unlocking-bootloader-tegra-version-t2933295
Download:
DOWNLOAD ROM
Kernel source:
Source
DOWNLOAD EAS KERNEL
MAJOR BUGS:
?
other bugs:
Reboot on first recorded fp
If you have FocalTech Panel Keydisabler wont work.
flash on your own risk.
FLASHING
if you are/were encrypted then booting into bootloader and issuing fastboot format userdata is HIGHLY recomended if comming from stock or other roms (this will totaly erase all your userdata).
If you have weird issues follow this guide:
https://forum.xda-developers.com/showthread.php?t=3609786
DOWNLOAD GAPPS
BeansGAPPS
Changelog
Changelog
Build prop editor
recomended for android pay or banking apps. changes userdebug to user in build.prop.
for ota just put it in /sdcard/OpenDelta/flashafterupdate/ folder and it will auto flash after every ota.
Flashable Build Prop Editor/Mod
------------------------------------------------------------
bug reports now open. Please try to include logs.
{
"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"
}
Here he is, best dev ever thank you
Can som1 from the 727 guys do a bootloader getvar all
In 720 there is nothing distinguishable there
Sent from my Nexus 6P using Tapatalk
darkobas said:
Can som1 from the 727 guys do a bootloader getvar all
In 720 there is nothing distinguishable there
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I can do it, but to be honest I do not know how to do it, also I am full stock, locked bootloader and no root. If that works I can get you the information, a little guide will be great :good:
TheDethEgineer said:
I can do it, but to be honest I do not know how to do it, also I am full stock, locked bootloader and no root. If that works I can get you the information, a little guide will be great :good:
Click to expand...
Click to collapse
you have to have adb and fastboot
then>
adb reboot bootloader
fastboot getvar all
fastboot reboot
darkobas said:
you have to have adb and fastboot
then>
adb reboot bootloader
fastboot getvar all
fastboot reboot
Click to expand...
Click to collapse
hope this helps
TheDethEgineer said:
hope this helps
Click to expand...
Click to collapse
Hmm doesn't seem to be any device attached :/
TheDethEgineer said:
hope this helps
View attachment 3974994
Click to expand...
Click to collapse
thanx.... but no luck... this was my hope to create unified 720/727 builds....
Does this mean its strictly a 727 or 720 build?
PeaKay.18 said:
Does this mean its strictly a 727 or 720 build?
Click to expand...
Click to collapse
I think its just a build.prop difference in these two but i cant be sure, i dont have both
but i am pretty sure it wont explode
PeaKay.18 said:
Does this mean its strictly a 727 or 720 build?
Click to expand...
Click to collapse
Insert my screen
darkobas said:
thanx.... but no luck... this was my hope to create unified 720/727 builds....
Click to expand...
Click to collapse
Will a complete boot and system image help? Someone uploaded for the 727 and I saved it. Otherwise I have already flashed the bootloader t unlock . I really want to get the rom going on the 727. Will get the coffee you deserve as well!
zmanfarlee said:
Will a complete boot and system image help? Someone uploaded for the 727 and I saved it. Otherwise I have already flashed the bootloader t unlock . I really want to get the rom going on the 727. Will get the coffee you deserve as well!
Click to expand...
Click to collapse
no, afaik it will work...
darkobas said:
no, afaik it will work...
Click to expand...
Click to collapse
ok well thank you for interest in the phone. Hopefully it keeps building. As far as I know it's just the build prop that makes the difference and then the modem that needs to be flashed for 727 phones (have that if you need also)
zmanfarlee said:
ok well thank you for interest in the phone. Hopefully it keeps building. As far as I know it's just the build prop that makes the difference and then the modem that needs to be flashed for 727 phones (have that if you need also)
Click to expand...
Click to collapse
yeah so, modem u already have and build prop is not mandatory afaik.
edit: Made incorrect assumption
It's been a hassle but I installed on my x727 and flashed the us modem and so far have superior result.
Has been installed on my 720, in addition to the camera you have declared can not work, the other is great. This is a good start! Appreciate your work!
No built-in root program?
I am using the super SU to get permission
I can confirm it works. Still ways to go but impressive. I appreciate the hard work. Wish I could help more