We all want Gpe KitKat, don't we?
I'm not a professional developer, so I'm just trying to replicate everything that DooMLoRD did for Z1 with respect to difference between our devices
Steps I imagine should be taken and results:
Find GPe kernel sources
Sony sources
Diff them with DooMLoRD's and upload to Github
Only small changes and buildscripts
My Github repo kernel tree
Diff changes to configs
No changes
Get the toolchain
The same as DoomLoRD's
change buildscripts
Don't know why but DoomLoRD uses strip from other toolchain. Will do the same
Compile kernel
Got compiled, but don't have the files from buildscript:
arch/arm/mach-msm/qdsp6v2/adsp-loader.ko
net/wireless/cfg80211.ko
./drivers/coresight/coresight-event.ko
./block/test-iosched.ko
./arch/arm/mach-msm/qdsp6v2/adsp-loader.ko
Should be ok because they don't have to be modules according to config. Maybe there is a reason I don't know why they are still in build_it
Compiled kernel can be downloaded here
Get a ramdisk
Currently here
On most devices I used before one could create a new ramdisk from scratch. Where should I get one?
Ran a lot of diffs, I belive I should use ramdisk from DooMLoRD's advanced GPe kernel for ZUGPe...
Pack in a boot.img
more steps to come to create a flashable zip
run KitKat and have fun
Help me, do it with me and all that
Don't have much time until the holidays are over and I have to study so we have to do it quickly :fingers-crossed:
We'll hello there sir we do want gpe on our zu and will help you in any way possible if you need a beta tester.
Thumbs up! I can't really support you but I really appreciate the work you're doing!
Sent with my Xiaomi MI2 with Tapatalk Pro
wooki said:
Thumbs up! I can't really support you but I really appreciate the work you're doing!
Sent with my Xiaomi MI2 with Tapatalk Pro
Click to expand...
Click to collapse
Now that my Z Ultra accidentally hard bricked after ordinary flashing .290 ftf I have a problem with moving on xD And have no more warranty because bootloader unlocked. Waiting for full discharge, maybe it will come back to life after that
thermatk said:
Now that my Z Ultra accidentally hard bricked after ordinary flashing .290 ftf I have a problem with moving on xD And have no more warranty because bootloader unlocked. Waiting for full discharge, maybe it will come back to life after that
Click to expand...
Click to collapse
I'm hoping we get progress. I can get fastboot to load an .img, and TWRP/CWM but no other screens on display if I had a .ZIP, otherwise I'm SOL. Worst case I return and pay for both but that would be a horrific scenario.
I'm trying to do pretty much what you're trying to do but I can't for the life of me get any kernels I build to boot. Did you have any luck even getting as far as the Sony/Google logo? I know I'm not very likely to get this working properly but it would be nice to learn a little.
I've got the zImage, dt.img and then I've used the ramdisk.cpio.gz that I've extracted from the GPe boot.img with the custom recoveries. Packaged it all up in a boot.img using the following command:
./mkbootimg --base 0x00000000 --kernel zImage --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --ramdisk ramdisk.cpio.gz --dt dt.img -o boot.img
All i get after flashing it to my device is the led flashing red. If someone can give me some pointers I'd really appreciate it.
Thanks
datty said:
I'm trying to do pretty much what you're trying to do but I can't for the life of me get any kernels I build to boot. Did you have any luck even getting as far as the Sony/Google logo? I know I'm not very likely to get this working properly but it would be nice to learn a little.
I've got the zImage, dt.img and then I've used the ramdisk.cpio.gz that I've extracted from the GPe boot.img with the custom recoveries. Packaged it all up in a boot.img using the following command:
./mkbootimg --base 0x00000000 --kernel zImage --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --ramdisk ramdisk.cpio.gz --dt dt.img -o boot.img
All i get after flashing it to my device is the led flashing red. If someone can give me some pointers I'd really appreciate it.
Thanks
Click to expand...
Click to collapse
Make sure the you're on 4.3 (.290) on your firmware. Easiest way to do this is to FTF 290 but exclude system and kernel.
That should get it booting, but then a lot of FC's. As long as you have debugging enabled in your ramdisk, you can check the logcat for the errors and debug from there.
Sent from my Nexus 5 using Tapatalk
datty said:
I'm trying to do pretty much what you're trying to do but I can't for the life of me get any kernels I build to boot. Did you have any luck even getting as far as the Sony/Google logo? I know I'm not very likely to get this working properly but it would be nice to learn a little.
Click to expand...
Click to collapse
I do get Sony or Google before lights out depending on the img I have loaded. I'm lost after that.
Make sure the you're on 4.3 (.290) on your firmware. Easiest way to do this is to FTF 290 but exclude system and kernel.
Click to expand...
Click to collapse
bigxie, I am also lost on the build details, but I think moving to 4.3 (290) is the main reason I'm SOL on the GPe device. Is it cool to go back to go forward?
Any news of gpe rom port to c6833 ?
Sent from my C6833 using xda app-developers app
We are still here and following you, Thermatk, so don't lose your motivation just yet. How's the project going?
LordManhattan said:
We are still here and following you, Thermatk, so don't lose your motivation just yet. How's the project going?
Click to expand...
Click to collapse
It seems that thermatk has joined the .290 FTF bricked XZ1+XZU club:
http://forum.xda-developers.com/showthread.php?p=49055487#post49055487
has taken down a few XZU's - including mine.
n0bleINtP said:
It seems that he has joined the .290 FTF bricked XZ1+XZU club:
http://forum.xda-developers.com/showthread.php?p=49055487#post49055487
has taken down a few XZU's - including mine.
Click to expand...
Click to collapse
I'm glad that there aren't the no of bricked ZU as there are Z1, it is disturbing the no. of dead Z1's
blueether said:
I'm glad that there aren't the no of bricked ZU as there are Z1, it is disturbing the no. of dead Z1's
Click to expand...
Click to collapse
there aren't as many zu as z1 around as a whole
Sent from my Xperia Z Ultra using Tapatalk
I will get a replacement motherboard for 150$ later this month
Anyway I like Z Ultra
thermatk said:
I will get a replacement motherboard for 150$ later this month
Anyway I like Z Ultra
Click to expand...
Click to collapse
Ouch.. that sucks.
thermatk said:
I will get a replacement motherboard for 150$ later this month
Anyway I like Z Ultra
Click to expand...
Click to collapse
will you replace it yourself?
Sent from my Xperia Z Ultra using Tapatalk
gbohm said:
will you replace it yourself?
Sent from my Xperia Z Ultra using Tapatalk
Click to expand...
Click to collapse
That's what I'm very afraid of. I mean it's easy to disassemble but to get it back being waterproof again is kind of impossible
Anyway :fingers-crossed:
You honestly don't need to do all this
Wait I will share link of the ZU GPe port to ZU that I was working on a while back...
Sent from my C6603 using xda app-developers app
thermatk said:
That's what I'm very afraid of. I mean it's easy to disassemble but to get it back being waterproof again is kind of impossible
Anyway :fingers-crossed:
Click to expand...
Click to collapse
http://feedly.com/k/1eL5fJy
Sent from my Xperia Z Ultra using Tapatalk
DooMLoRD said:
You honestly don't need to do all this
Wait I will share link of the ZU GPe port to ZU that I was working on a while back...
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Is a lot of fun and experience
Can you share what I did wrong if i did it wrong(couldn't test anything because hard-brick got me during update the same day)? Or just links to github, buildscripts and all that?
Related
Building a sweet treat for you guys, will post it in dev section assuming all goes well
Can you post link here as well when its ready?
jontr said:
Can you post link here as well when its ready?
Click to expand...
Click to collapse
sure
Wow! Excited to breathe some new life into the old manta.
Has it been two hours yet??!?!?!
I guess all didn't go too well...
how to farm upvotes this isn't reddit guys
wturner859 said:
I guess all didn't go too well...
Click to expand...
Click to collapse
Had some java issues, will be def ready tomorrow :good:
sooti said:
Had some java issues, will be def ready tomorrow :good:
Click to expand...
Click to collapse
Bad news... buillt fine, flashed it, no boot, i think our device needs a new bootloader, unless someone else has an idea? tried both otapackage and img files
sooti said:
Bad news... buillt fine, flashed it, no boot, i think our device needs a new bootloader, unless someone else has an idea? tried both otapackage and img files
Click to expand...
Click to collapse
What are you trying to build? I built Lollipop from the r2 repo a few days ago, available here: http://d-h.st/Ryr
stiggy2012 said:
What are you trying to build? I built Lollipop from the r2 repo a few days ago, available here: http://d-h.st/Ryr
Click to expand...
Click to collapse
Same here, but my device doesn't boot, is it working for you???
sooti said:
Same here, but my device doesn't boot, is it working for you???
Click to expand...
Click to collapse
Yep, works fine. Build with the latest "preview binaries". Literally all I did was repo init/sync, load the variables, run the binary scripts, chose manta with lunch and then finally run make.
stiggy2012 said:
Yep, works fine. Build with the latest "preview binaries". Literally all I did was repo init/sync, load the variables, run the binary scripts, chose manta with lunch and then finally run make.
Click to expand...
Click to collapse
Preview binaries? that must be what I am missing... anyway if you already built one no point in duplicating work, good job, ill get back to building for my G3-D855
sooti said:
Preview binaries? that must be what I am missing... anyway if you already built one no point in duplicating work, good job, ill get back to building for my G3-D855
Click to expand...
Click to collapse
Yep, these: https://developers.google.com/android/nexus/blobs-preview
I suspect that will be much, MUCH more difficult than a Manta build! Tell you what though: If you do manage to get it going well I may well buy a G3 myself as the hardware is gorgeous and they are quite cheap nowadays... Only thing that puts me off is LG's update record and (until recently) the locked bootloader
stiggy2012 said:
Yep, these: https://developers.google.com/android/nexus/blobs-preview
I suspect that will be much, MUCH more difficult than a Manta build! Tell you what though: If you do manage to get it going well I may well buy a G3 myself as the hardware is gorgeous and they are quite cheap nowadays... Only thing that puts me off is LG's update record and (until recently) the locked bootloader
Click to expand...
Click to collapse
Got mine booting pac-rom with everything working just fine, some minor issues like camera getting stuck in background sometimes but nothing major
stiggy2012 said:
Yep, works fine. Build with the latest "preview binaries". Literally all I did was repo init/sync, load the variables, run the binary scripts, chose manta with lunch and then finally run make.
Click to expand...
Click to collapse
Hi, how is it to load the variables? I tried to build lollipop for manta and I did all that you said but I don't remember that step.
tavocabe said:
Hi, how is it to load the variables? I tried to build lollipop for manta and I did all that you said but I don't remember that step.
Click to expand...
Click to collapse
"source build/envsetup.sh" from build directory.
https://source.android.com/source/building-running.html
stiggy2012 said:
"source build/envsetup.sh" from build directory.
https://source.android.com/source/building-running.html
Click to expand...
Click to collapse
OH, yeah I remember that. Didn't know the initialization/setup of the environment was actually loading the variables. Thanks!
Oh so this is the show off thread?
Well I built mine with transparent bars via linaro toolchain
Seriously though this isn't reddit...
Is anyone trying to work on the Honor 7? I've got the the point now where I can't continue.
Things I know:
Kernel source compiles with no issues
Boot image has secure boot for first 4095 bytes
Kernel and ramdisk can be extracted easily
Bootloader is crap! Doesn't allow fastboot boot
Things I can't do:
Repack a stock boot image! Tried countless ideas. Various unmkbootimg give differing offset values for kernel and ramdisk, tried all those, tried zeroing off the secureboot section. I either get hang on Honor or bootloader error
Superr's kitchen doesn't even recognise it as a valid boot.img, I thought that was my lifeline..
Can't create flashable zip, various update-binary's have been tried - including Huawei's own pulled from the 140 OTA, can't get any edify zip to run (I know shell scripts will work, that's how SU installs.)
It's either something I'm doing wrong (very likely), or this handset is so non-standard, we as a community are screwed! (less likely but possible)
Just to note - I'm not a dev, I'm a Linux admin by day...
Any sensible ideas welcomed :silly:
Hey there,
for differing Offset u tried this:
http://forum.xda-developers.com/showpost.php?p=61956115&postcount=54
For a flashable zip-file u should have a look at anykernel2 ... maybe u can find a solution here!
The secure boot shouldn't be a problem as ur bootloader is unlocked
Sent from my PLK-L01 using XDA Premium HD app
thanks @c0llal0 , some interesting things to look at there that I haven't tried :good:
Ur welcome! We all benefit from ur efforts.
In case i find some free time in the next days, i will try to help more...
Sent from my PLK-L01 using XDA Premium HD app
AnyKernel2 seems to be working :victory: - don't understand, as it's using still using umkbootimg and mkbootimg (arm) - need to put some debug in there to get the values it's using!
...but i've had to use use some force. I've had to disable the device check, which I'm not happy about (you know, some people may flash another device by "mistake")
Can u tell me where u disabled it? Maybe u could link to some code? Will have a look at those lines.
Sent from my PLK-L01 using XDA Premium HD app
in anykernel.sh
Code:
do.devicecheck=1
using
Code:
device.name1=HWPLK
device.name2=hi3635
as that's what is in build.prop
this is used in META-INF/com/google/android/update-binary
Code:
if [ "$(file_getprop /tmp/anykernel/anykernel.sh do.devicecheck)" == 1 ]; then
ui_print "Checking device...";
for i in 1 2 3 4 5; do
testname="$(file_getprop /tmp/anykernel/anykernel.sh device.name$i)";
if [ "$(getprop ro.product.device)" == "$testname" -o "$(getprop ro.build.product)" == "$testname" ]; then
ui_print "$testname";
match=1;
fi;
done;
ui_print " ";
if [ "$match" != 1 ]; then
abort "Unsupported device. Aborting...";
fi;
fi;
Always get unsupported device
I am on B170! Rooted.
My build.prop only shows HWPLK
No second device id here!
Sent from my PLK-L01 using XDA Premium HD app
added some extra ui_print - it's getting the value "HWGRA" ! that's not in build.prop :silly:
I had a look via TWRP and things get a little revealing
Code:
adb shell
~ # getprop
[ro.build.product]: [HWGRA]
[ro.product.device]: [HWGRA]
so, it looks as though this recovery is for the Huawei P8 / GRACE !
So now we have another job to do!
here's what Anykernel2 returns from unpackbootimg (also posting here for my own reference )
values here are yet again different from other unpackbootimg builds!
Code:
BOARD_KERNEL_CMDLINE mem=3072M mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p6(modemnvm_factory),p9(splash),p10(modemnvm_backup),p11(modemnvm_img),p12(modemnvm_system),p14(3rdmodemnvm),p15(3rdmodemnvmback),p17(modem_om),p20(modemnvm_update),p30(modem),p31(modem_dsp),p32(dfx),p33(3rdmodem) androidboot.selinux=enforcing
BOARD_KERNEL_BASE 00678000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 07588000
BOARD_TAGS_OFFSET ffb88000
something else to try...
EDIT:
YESSSS! :victory: :victory: :victory:
that's the one!
Code:
mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline \
'mem=3072M mcparts=mmcblk0:p1(vrl),p2(vrl_backup),p6(modemnvm_factory),p9(splash),p10(modemnvm_backup),p11(modemnvm_img),p12(modemnvm_system),p14(3rdmodemnvm),p15(3rdmodemnvmback),p17(modem_om),p20(modemnvm_update),p30(modem),p31(modem_dsp),p32(dfx),p33(3rdmodem) androidboot.selinux=enforcing' \
--base 0x678000 --pagesize 2048 --ramdisk_offset 0x7588000 \
-o new_boot.img
Yep! There u go
Now we have a good base to start, at least, kernel development!
Great work!!!
Sent from my PLK-L01 using XDA Premium HD app
c0llal0 said:
Yep! There u go
Now we have a good base to start, at least, kernel development!
Great work!!!
Click to expand...
Click to collapse
thanks can you do one thing for me, as you're on 170
can you tell me what the kernel version is?
cheers :highfive:
Here we go
Sent from my PLK-L01 using XDA Premium HD app
c0llal0 said:
Here we go
Click to expand...
Click to collapse
3.10.61, cool thanks!
As u have a bootin' kernel, what comes out of those logfiles? U looked after drivers for sensors and stuff?
Is the phone behaviour like it should be?
Sent from my PLK-L01 using XDA Premium HD app
c0llal0 said:
As u have a bootin' kernel, what comes out of those logfiles? U looked after drivers for sensors and stuff?
Is the phone behaviour like it should be?
Sent from my PLK-L01 using XDA Premium HD app
Click to expand...
Click to collapse
phone is working fine, as it's the same kernel version, the module for sensors etc. are all loading and working normally
Hi guys,
I've been following these posts for a few weeks now als also the kernel development. Massive shout out to Sminki and the ON-OR kernel!!
But I'm really new to the development of kernels and ROMs and new to xda so I have some questions if you don't mind.
I guess you guys are working on the kernel, how long should this take since it's kind of safe to use? And can I help testing (pls keep in mind I'm not an expert, just used to flash roms and kernels on nexus 4, that's all my knowlege.)?
When you get the kernel up and running, does it take much to make roms? Like making them from scratch or just a few changes to existing roms?
And again, can I help testing those ROMs?
My buildnr is PLK-L01c432B121, as far as I understand, L01 means I have the European version and B121 stands for the firmware version (an old one i guess). What does C432 mean?
You're working on an L01 kernel, is this compatible for other versions? In other words, when there are other kernels available, should I keep in mind that I can use only L01 based kernels?
Thank you to all the people that are spending their free time and all your hard work!!!!
Sorry this is a long reply, i got carried away, but you did ask a lot!
Anderjax said:
Hi guys,
Massive shout out to Sminki and the ON-OR kernel!!
Click to expand...
Click to collapse
thanks
But I'm really new to the development of kernels and ROMs
Click to expand...
Click to collapse
Me too, although I have been using linux for about 13 years so I do have some understanding of the underlying system, compiling, kernel modules, etc.. However some bits of this post may be incorrect!
I guess you guys are working on the kernel, how long should this take since it's kind of safe to use?
Click to expand...
Click to collapse
It is safe, i added the experimental tag as mine went into un-wakeable sleep with bluactiv cpu governor, but it's current uptime is 85hrs using ondemand instead. i built it because i wanted to see if it would actually compile, i posted it because it worked (and no one else had, haha!)
When you get the kernel up and running, does it take much to make roms? Like making them from scratch or just a few changes to existing roms?
Click to expand...
Click to collapse
this is where it gets difficult. right now there is nothing, no AOSP, no CM, etc.. to port to
So to start from scratch you need a device tree, which is essentially a collection of files that give the rom the bits of info it needs to build for your device, roms are a little easier to build if you have a "sibling" or "ancestor" (similar/older) device with a custom ROM, one that is similar enough to use some of the device tree that custom ROM was built from.
As the CPU is Huawei's own HiSilicon Kirin, there really is nothing similar with the exception of codeworkx CM for the Honor 6, the P8 is a "sibling" (but no custom roms) and the mediapad x2, which is Kirin, but not a phone, but someone may be able to do something with the custom roms available (?)
I'm currently playing around with this when i have spare time
What does C432 mean?
Click to expand...
Click to collapse
no idea!
You're working on an L01 kernel, is this compatible for other versions? In other words, when there are other kernels available, should I keep in mind that I can use only L01 based kernels?
Click to expand...
Click to collapse
the Chinese PLK-AL10 is the PLK-L01 with more RAM - with the MarshMallow beta "blackbox" partitions flashed i was able to run the AL10 kernel and system (android 5.1.1) on the L01
The PLK-(UL/TL/CL) are all essentially the same (rom) in a smaller system partition (as I tried that too!) I've not looked into the Indian variant yet..
"blackbox" are things like "radio" that you can flash directly from fastboot on a nexus, but not on this device, this is where the problems would lie. So yes, kernel per device, unless the dev has considered the above, but there is only one kernel right now :silly:
sminki said:
Sorry this is a long reply, i got carried away, but you did ask a lot!
Nice one,
Thank you, this explaines a lot really. Have you ever made a tree like that?
Is there someway to help you by installing the kernel en sending you feedback errors and stuff?
Click to expand...
Click to collapse
Anderjax said:
Nice one,
Thank you, this explaines a lot really. Have you ever made a tree like that?
Is there someway to help you by installing the kernel en sending you feedback errors and stuff?
Click to expand...
Click to collapse
Never made a tree before, but I have something which might work, will find out soon
As for the kernel, you can try and install it but it may not work because:
a) your're on B121
b) you may have the chinese twrp
c) other
I'll post the B121 boot.img later (at work now) on the main kernel post should you need to go back to it.
However - I don't know how much I'll be able to debug as i'm not a dev, or that good at C, also the huawei source seems to be really non-standard! :silly:
Hello there.
Here is device tree:
DOWNLOAD from My github.
It is in Alpha (developers) release as probably You will need to fix few errors by hand....but, anyway, someone must to start with something....
Kernel is in this moment not released by HTC, but We can do some things with prebuilt kernel.
PREPARATION:
Please, after You pull it inside cm-13 source, GET VENDOR FILES by cd into device/htc/htc_a51ul and
Code:
./extract-files.sh
(with connected phone in adb enabled mode)
Second, please comment out in BoardConfig.mk following line:
Code:
TW_THEME := pure4
and uncomment:
Code:
TW_THEME := portrait_hdpi
as I wasn't release yet pure4 design skin to github.
Third, if You cannot handle "BSP" (and it's about 99% that You can't ) comment out:
Code:
TARGET_USES_QCOM_BSP := true
and remove flag
Code:
-DQCOM_BSP
from COMMON_GLOBAL_CFLAGS
Then You are ready to build (until first error come)
PLEASE, don't take advantage with this if You really don't know how to handle errors as I will NOT help or respond on PM's regarding help about building this.
When something come up, will make post/and/or attach possible working image.
Cheers
EDIT1: dts is attached, so if someone like to play with kernel... Check it out. I will put changes to 64bit kernel on My github soon with this device tree.
EDIT2: kernel is updated. You can grab it on MY GITHUB
EDIT3: BoardConfig.mk is changed, so no need to change twrp skin and BSP (steps second and third).
Thank you, btw. great job!
Great beginning!
So, things changed... Kernel updated, device tree updated, read.me updated.
Please be free to pull Kernel and make changes so We can got it working. I was made first steps and don't have so much time to make all this together work but if few of dev's come aboard and take work, We can make it work soon.
So i am quite interested in this device, don't own it yet so @fergy would appriciate it, if you could push vendor (too much work to do it all manually, especially the makefile ).
Thanks.
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename
fergy said:
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename
Click to expand...
Click to collapse
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push
btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul
Thanks.
Thecrazyskull said:
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push
btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul
Thanks.
Click to expand...
Click to collapse
https://github.com/Skorupa123/vendor_htc_htc_a51ul
Recently I uploaded it, so, enjoy!
Skorupa123 said:
https://github.com/Skorupa123/vendor_htc_htc_a51ul
Recently I uploaded it, so, enjoy!
Click to expand...
Click to collapse
Thanks a damn lot!!!
@Thecrazyskull Do you make cyanogenmod?
@Thecrazyskull
I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
Dragonfail said:
@Thecrazyskull
I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
Click to expand...
Click to collapse
I pretty much lost interest, especially since i dont want to develop without owning the device.
Thecrazyskull said:
I pretty much lost interest, especially since i dont want to develop without owning the device.
Click to expand...
Click to collapse
I can help you.. please.. continue...
Sent from my HTC Desire 820 using XDA Free mobile app
Dragonfail said:
I can help you.. please.. continue...
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
Its a pain for myself, and i don't wanna go through that so i won't be developing for this device anymore unless i can get my hands on one (very unlikely)
What is thts device tree not understanding
chitranjn_k said:
What is thts device tree not understanding
Click to expand...
Click to collapse
This is not really the place to ask...
chitranjn_k said:
What is thts device tree not understanding
Click to expand...
Click to collapse
If you don't understand it you don't need it.
Wysłano z Tapatalk / Sent with Tapatalk
Any idea about htc desire 826 dual sim i.e. a52_dtul device tree ?
Hi,
Some of you all (who are reading this thread) might have seen me somewhere on subforums (either this subforum and/or other devices' subforum). I was previously maintained kernels for some devices (which I discontinued them later due to limited free time and I was no longer have them under my control).
Why I make this public?
I want to collect as many information as possible regarding building arm64 kernels (which I never do it before today), not limited to a developer, but as many as possible (if can)
I want to make my comeback on development by making an attempt to build a custom kernel for Redmi 3. So, I have these prepared:
Configured my netbook as building machine with LXLE.
Downloaded the required kernel source (I'm building for CM-14.1 based ROMs)
Grabbed UBERTC 4.9.4 aarch64
To make things easier without need to edit Makefile everytime I change toolchain, I created a script:
Code:
#!/bin/bash
# Placeholder - my system puts warnings everywhere about locale
export LC_ALL=en_US.UTF-8
# Environment variables
export ARCH=arm64
export CROSS_COMPILE=../../toolchains/aarch64-linux-android-4.9-kernel/bin/aarch64-linux-android-
# Actual command
make -s distclean
make -s cyanogenmod_ido_defconfig
make -s -j4
No problems during compilation process. All forbidden warnings triggered could be bypassed safely. Then, I tested my own build by creating a flashable zip. The process did flawlessly. However, it stucks forever on Mi logo.
Oh ya, I use -O3 optimizations on compilation.
Is there something I should do regarding the unbootable kernel?
I don't want to test every single toolchain out there due to my limited internet quota and my expectations on the same result.
Or... maybe suggestions?
Any help, suggestions, and comments are greatly appreciated. Thank you!
Regards.
Bump.
Seems like nothing noticed this thread. Should I mention every kernel developers here? I'm out of nowhere.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Bump.
Seems like nothing noticed this thread. Should I mention every kernel developers here? I'm out of nowhere.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Hey,
well, your way of doing it looks good. Do you get a last_kmsg probably? Also did you use the correct ramdisk, etc?
Excuse me sir, i want ask for help for my battery issue. Why my battery drop to 98% after unplug just a few second?_ I am on mokee and RR rom before and now i already flash it to MIUI but still got like that. Please help me if any solution for that ? sorry for my bad english
BlueFlame4 said:
Hey,
well, your way of doing it looks good. Do you get a last_kmsg probably? Also did you use the correct ramdisk, etc?
Click to expand...
Click to collapse
Nope. It stuck all way at Mi logo. No sign of life at all. Tested on official CM-14.1 and MoKee 7.1.1.
I use the modified AnyKernel2 template (removed Busybox requirement and points to Image.gz instead).
I also tried to download other kernel and use the zip as the base and the output is same.
Sent from my ASUS_Z00A using XDA Labs
ghal17 said:
Excuse me sir, i want ask for help for my battery issue. Why my battery drop to 98% after unplug just a few second?_ I am on mokee and RR rom before and now i already flash it to MIUI but still got like that. Please help me if any solution for that ? sorry for my bad english
Click to expand...
Click to collapse
Hi,
It's better to stay on topic.
You may create your own separate thread so people could assist you better and won't mix up with this one.
Regards.
Sent from my ASUS_Z00A using XDA Labs
So you get a last_kmsg?
Problem solved.
The culprit is the missing DTB!
When I look into the source once again, there's something missing: DTB file.
The file doesn't exist on arch/arm64/boot/dts, but instead on arch/arm/boot/dts. So, I created a link:
Code:
$ ln -s ../../../arm/boot/dts/msm8939-qrd-wt88509_64.dtb ./arch/arm64/boot/dts/msm8939-qrd-wt88509_64.dtb
Then I enabled CONFIG_BUILD_ARM64_APPENDED_DTB and re-compile kernel (using Google's GCC). Re-test it again (but with a boot.img extracted from MoKee zip unpacked with AIK and finally it booted!
Thank you very much, anyway.
Thread marked as Solved for now.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Problem solved.
The culprit is the missing DTB!
When I look into the source once again, there's something missing: DTB file.
The file doesn't exist on arch/arm64/boot/dts, but instead on arch/arm/boot/dts. So, I created a link:
Code:
$ ln -s ../../../arm/boot/dts/msm8939-qrd-wt88509_64.dtb ./arch/arm64/boot/dts/msm8939-qrd-wt88509_64.dtb
Then I enabled CONFIG_BUILD_ARM64_APPENDED_DTB and re-compile kernel (using Google's GCC). Re-test it again (but with a boot.img extracted from MoKee zip unpacked with AIK and finally it booted!
Thank you very much, anyway.
Thread marked as Solved for now.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Hey what did you change from original kernel? New features like hotplug? Is it easy to compile an booting kernel?
Sent from my Redmi 3 using XDA-Developers mobile app
rikusuicide said:
Hey what did you change from original kernel? New features like hotplug? Is it easy to compile an booting kernel?
Click to expand...
Click to collapse
For now, kernel patching.
Unless you have ever compiled one.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
For now, kernel patching.
Unless you have ever compiled one.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Will you release an costume kernel? CM 13, CM 14.1 or miui 8? Ya need testers?
Sent from my Redmi 3 using XDA-Developers mobile app
rikusuicide said:
Will you release an costume kernel? CM 13, CM 14.1 or miui 8? Ya need testers?
Click to expand...
Click to collapse
Maybe next year, as things go unpredictable.
EDIT: MIUI won't be supported due to lack of resources required.
I'll ask moderators to close this thread to prevent other type of nonsense discussions.
Sent from my ASUS_Z00A using XDA Labs
Thread closed at OPs request
It's almost done...
D!OS is rolling out the next Days. It's pretty basic for now. Based on latest Android 12.1/12L with Google Apps.
If You want to be one of the first who uses this new Xperia exclusive OS, leave a Comment and become a Tester!
Need Testers for XQBC52 Xperia 1 MK3
What about the twrp, any progression in that for A12 ?
Pandemic said:
What about the twrp, any progression in that for A12 ?
Click to expand...
Click to collapse
I gave up on this after to much trouble. I don't think ill try again since i enabled Recoveries on AOSXP for us. It allows Wipes, Updates and Tests like it should ootb. There are People working on TWRP but i would guess they have the same trouble as i had...
Finally got more options
Will it have the ability to change the physical display size/aspect ratio (not just resolution)?
SmashMan4 said:
Will it have the ability to change the physical display size/aspect ratio (not just resolution)?
Click to expand...
Click to collapse
Of course. Its an native Android Feature available on any OS...
Changing Resolutions eg isn't included yet but it will come soon.
How to become a tester, I want to try
I'd love to try it out, been looking for a good rom
ld41233 said:
How to become a tester, I want to try
Click to expand...
Click to collapse
Firebuster said:
I'd love to try it out, been looking for a good rom
Click to expand...
Click to collapse
AOSXP-XQBC52.zip
drive.google.com
I mean, strictly for testers only.
XQ BC72 can flash？
fairyshacker said:
AOSXP-XQBC52.zip
drive.google.com
I mean, strictly for testers only.
Click to expand...
Click to collapse
If that's the same one from OP's site then I already tried to flash it and got a boot loop
Firebuster said:
If that's the same one from OP's site then I already tried to flash it and got a boot loop
Click to expand...
Click to collapse
yup!
Sign in - Google Accounts
New Builds on the Way...
#D!OS
Miustone said:
New Builds on the Way...
#D!OS
Click to expand...
Click to collapse
What base version should I be on? I used xperifirm and newflash to return to stock android 12 firmware and then ran the bat file and everything flashed fine but it just sticks on the Sony logo.
Edit: Tried using both the latest firmware from Sony (61.1.A.4.78) and Android 11 firmware (61.0.A.23.20) both result in just sitting on the Sony logo.
Firebuster said:
What base version should I be on? I used xperifirm and newflash to return to stock android 12 firmware and then ran the bat file and everything flashed fine but it just sticks on the Sony logo.
Edit: Tried using both the latest firmware from Sony (61.1.A.4.78) and Android 11 firmware (61.0.A.23.20) both result in just sitting on the Sony logo.
Click to expand...
Click to collapse
Sorry to hear that. Android 12 will be the right base for latest Android Builds. But since i only have an Xperia 5 can i not test the Xperia 1 III Builds. I'm moving to Ubuntu 22.04 right now and will start from Scratch again. Think ill also need an Server for further Development... I will keep You Updated! Think ill also start using Twitter again so You can follow Me there and on My Discord Server which will also push Git Updates...
Miustone said:
Sorry to hear that. Android 12 will be the right base for latest Android Builds. But since i only have an Xperia 5 can i not test the Xperia 1 III Builds. I'm moving to Ubuntu 22.04 right now and will start from Scratch again. Think ill also need an Server for further Development... I will keep You Updated! Think ill also start using Twitter again so You can follow Me there and on My Discord Server which will also push Git Updates...
Click to expand...
Click to collapse
I appreciate the work you're putting into it. I don't use Twitter but I'll join your discord. The link on your linktree seems to be invalid however
Firebuster said:
I appreciate the work you're putting into it. I don't use Twitter but I'll join your discord. The link on your linktree seems to be invalid however
Click to expand...
Click to collapse
Thanks for making me aware! Link should be fixed now!
New Testversion is up. Fingers crossed that it works for You Folks...
Miustone said:
Thanks for making me aware! Link should be fixed now!
Click to expand...
Click to collapse
I tried to join, the link still does not work. At least for me
Awesome Things are going on. I need to create an own Repo with some Xperia Stock Files. Is someone willed to pull Me everything out of /vendor/etc/acdbdata from the Xperia Lineup from 2019+? Namely:
-Xperia 1 MK1
-Xperia 5 MK1
-Xperia 1 MK2
-Xperia 5 MK2
-Xperia 1 MK3
-Xperia 5 MK3
I would really appreciate the Help!