I compiled RR 7.1.2 unofficial successfully, the make completed and the zip flashed without error. When I go to reboot the ROM won't boot, it stays on the Google splash screen.
I had to manually clone device and kernel sources and used The Muppets github for the proprietary vendor files. Any advice here would be appreciated.
Rondeau79 said:
I compiled RR 7.1.2 unofficial successfully, the make completed and the zip flashed without error. When I go to reboot the ROM won't boot, it stays on the Google splash screen.
I had to manually clone device and kernel sources and used The Muppets github for the proprietary vendor files. Any advice here would be appreciated.
Click to expand...
Click to collapse
Are you able to get a log. How big is your final zip?
Are you talking about the build log? The final zip is 318.02 MB.
Rondeau79 said:
Are you talking about the build log? The final zip is 318.02 MB.
Click to expand...
Click to collapse
Log = logcat
The zip seems small there's a possibility you didn't get the vendor files what device tree are you using?
I used CM based make files and the Muppets vendor files. I deleted device sources and cloned from Resurrection GitHub and I am going to build again.
Rondeau79 said:
Are you talking about the build log? The final zip is 318.02 MB.
Click to expand...
Click to collapse
My rebuild was successful! Turns out my vendor files weren't in the right directory.
Related
I've downloaded and built 4.2.1 just fine, so i tried 4.2.2 today and for some reason the quick settings wont work. I press the icon in the notification window and it makes the sound but they never appear.
This is my build process:
Download the source and make a local mirror with --mirror
Make my working copy from the mirror with repo init -u /opt/aosp_master/platform/manifest.git -b android-4.2.2_r1
Grab the three proprietary binary files and extract them. That yields me a vendor folder, which I copy in to the root of my source directory
make -j9 dist
Then I flash the ota .zip. I also tried flashing the system.img (after using flash-all.sh to install the factory jdq39 image)
Everything else works, that I've seen, except the quick settings...
Any ideas? Am I the only one having issues like this?
inh said:
I've downloaded and built 4.2.1 just fine, so i tried 4.2.2 today and for some reason the quick settings wont work. I press the icon in the notification window and it makes the sound but they never appear.
This is my build process:
Download the source and make a local mirror with --mirror
Make my working copy from the mirror with repo init -u /opt/aosp_master/platform/manifest.git -b android-4.2.2_r1
Grab the three proprietary binary files and extract them. That yields me a vendor folder, which I copy in to the root of my source directory
make -j9 dist
Then I flash the ota .zip. I also tried flashing the system.img (after using flash-all.sh to install the factory jdq39 image)
Everything else works, that I've seen, except the quick settings...
Any ideas? Am I the only one having issues like this?
Click to expand...
Click to collapse
Hi I was about to direct you to google groups but it seems you got the anyway going by the content of the post either that or you've got a stalker
https://groups.google.com/forum/?fr...ick/android-building/BaLWXaIiIK0/qUhdrxqG7gUJ
trevd said:
Hi I was about to direct you to google groups but it seems you got the anyway going by the content of the post either that or you've got a stalker
https://groups.google.com/forum/?fr...ick/android-building/BaLWXaIiIK0/qUhdrxqG7gUJ
Click to expand...
Click to collapse
So it would seem
For completeness' sake:
Jean-Baptiste Queru
Known issue, this is believed to be a missing post-boot configuration, fixing this is on my todo list.
JBQ
Click to expand...
Click to collapse
Hi, i'm editing my first custom rom for my device ( http://www.plunk.it/tvbox/pro ). I wnat to build my custom rom and i need to insert some folders in Sdcard/Android/Obb. When i unpack the firmware i have not this folder. I need to insert this when I edit the firmware.
How can i do?
itachar said:
Hi, i'm editing my first custom rom for my device ( http://www.plunk.it/tvbox/pro ). I wnat to build my custom rom and i need to insert some folders in Sdcard/Android/Obb. When i unpack the firmware i have not this folder. I need to insert this when I edit the firmware.
How can i do?
Click to expand...
Click to collapse
Edit your device.mk in the device tree for your phone. Copy the format used in that file with the files you want to copy
Haze028 said:
Edit your device.mk in the device tree for your phone. Copy the format used in that file with the files you want to copy
Click to expand...
Click to collapse
Sorry, where i find device.mk? Sorry but this is my first custom rom. Can you give me more informations?
itachar said:
Sorry, where i find device.mk? Sorry but this is my first custom rom. Can you give me more informations?
Click to expand...
Click to collapse
In the device tree repo for your device. you'll need the vendor kernel and device source for your device in order to build a custom rom.
The device source will contain a device.mk file, this is where you would add files that need to be copied to the device during the build, along with alot of other things.
I put together a guide on how to build here. I know there are alot of guides out there for building roms, and this isn't much different. Though i've tried to make it as noob friendly as possible.
Good morning. I'm trying to build the kernel for the M4 aqua, but although sony didn't include it in the guides for doing so, I can see the files inside the tulip in sony's github repository. Then, I guess that it's possible to build a kernel from sony's sources. If anyone did so, could please post and briefly describe the steps? More concretely, the line with the arguments for mkbootimg (or the necessary tool). Thanks in advance
alguien24 said:
Good morning. I'm trying to build the kernel for the M4 aqua, but although sony didn't include it in the guides for doing so, I can see the files inside the tulip in sony's github repository. Then, I guess that it's possible to build a kernel from sony's sources. If anyone did so, could please post and briefly describe the steps? More concretely, the line with the arguments for mkbootimg (or the necessary tool). Thanks in advance
Click to expand...
Click to collapse
You can use the same instruction as How to build AOSP Marshmallow for unlocked Xperia devices to download the source.
attached is the sony.xml file you can use to limit to download only tulip builds.
then you can use the follow in commands
$# cd android
android $# export CROSS_COMPILE=/android/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
add the full path to the above CROSS_COMPILE=/mnt/../../../android/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
android $# cd kernel/sony/msm/
android/kernel/sony/msm $# make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE aosp_kanuti_tulip_defconfig
android/kernel/sony/msm $# make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j1
if make is successful, copy the kernel from arch\arm64\boot folder and past into device/sony/common-kernel
and build your full aosp or only boot.img with android$# make -j1 bootimage
RohitBopnna said:
You can use the same instruction as How to build AOSP Marshmallow for unlocked Xperia devices to download the source.
attached is the sony.xml file you can use to limit to download only tulip builds.
then you can use the follow in commands
$# cd android
android $# export CROSS_COMPILE=/android/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
add the full path to the above CROSS_COMPILE=/mnt/../../../android/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
android $# cd kernel/sony/msm/
android/kernel/sony/msm $# make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE aosp_kanuti_tulip_defconfig
android/kernel/sony/msm $# make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j1
if make is successful, copy the kernel from arch\arm64\boot folder and past into device/sony/common-kernel
and build your full aosp or only boot.img with android$# make -j1 bootimage
Click to expand...
Click to collapse
Thanks a lot for the answer! Today, I had my computer setup with everything needed, with sony's guide. I've only made one modification. Inside the kanuti folder (~/android/device/sony/kanuti/rootdir) there's a file called fstab.kanuti. I changed the /data mountpoint to the second partition in the sdcard (in order to get more internal space, if I make it work someday I will post it inmediately ).Then, after carefully following the steps you gave me, I finally got the boot.img. Flashed it with fastboot flash boot boot.img, but when I powered the phone on, after half a second it shut down. Tried more than once with the same result. I flashed again the original kernel, and it came back to live with no more problems. Do you (or anyone) know where the problem could be? I also saw that the boot.img file weighs 9 MB, while the original kernel.elf extracted from the ftf takes 20 MB of space. Is this usual?
alguien24 said:
Thanks a lot for the answer! Today, I had my computer setup with everything needed, with sony's guide. I've only made one modification. Inside the kanuti folder (~/android/device/sony/kanuti/rootdir) there's a file called fstab.kanuti. I changed the /data mountpoint to the second partition in the sdcard (in order to get more internal space, if I make it work someday I will post it inmediately ).Then, after carefully following the steps you gave me, I finally got the boot.img. Flashed it with fastboot flash boot boot.img, but when I powered the phone on, after half a second it shut down. Tried more than once with the same result. I flashed again the original kernel, and it came back to live with no more problems. Do you (or anyone) know where the problem could be? I also saw that the boot.img file weighs 9 MB, while the original kernel.elf extracted from the ftf takes 20 MB of space. Is this usual?
Click to expand...
Click to collapse
the latest kernel that sony has implemented image.gz-dtb is a compressed kernel with the DTB combined, and this needs bootloader level gzip feature to unzip the kernel and load, which is not present today in our bootloaders. After building your kernel, Use the uncompressed kernel (image file and dtb) to build your boot image with old way, you may have to make changes in you boot build to indicate uncompressed kernel.
RohitBopnna said:
the latest kernel that sony has implemented image.gz-dtb is a compressed kernel with the DTB combined, and this needs bootloader level gzip feature to unzip the kernel and load, which is not present today in our bootloaders. After building your kernel, Use the uncompressed kernel (image file and dtb) to build your boot image with old way, you may have to make changes in you boot build to indicate uncompressed kernel.
Click to expand...
Click to collapse
I'm not really experienced in building kernels, I'm trying to learn a bit with this stuff I'm doing... And this phone hasn't got a lot of information yet. Could you please tell me what you mean with building it the old way?
LOL
You are in the stock rom, aren't you?
So, why would you try building an aosp kernel (which is f**ked up) in your stock rom?
You have to build from kernel-copyleft
There is also a tutorial from sony developer world
http://developer.sonymobile.com/kno...h-a-linux-kernel-from-sony-copyleft-archives/
I think you have to find the right defconfig and change arm to arm64 and aarch64 when necessary
RohitBopnna said:
the latest kernel that sony has implemented image.gz-dtb is a compressed kernel with the DTB combined, and this needs bootloader level gzip feature to unzip the kernel and load, which is not present today in our bootloaders. After building your kernel, Use the uncompressed kernel (image file and dtb) to build your boot image with old way, you may have to make changes in you boot build to indicate uncompressed kernel.
Click to expand...
Click to collapse
Now I got what you explained me. I've been looking for information, and I thought that after running make, the dtb file should be in the boot folder, but there I can only find the image file. How can I create the dtb file separately from the dts?
dani020110 said:
LOL
You are in the stock rom, aren't you?
So, why would you try building an aosp kernel (which is f**ked up) in your stock rom?
You have to build from kernel-copyleft
There is also a tutorial from sony developer world
http://developer.sonymobile.com/kno...h-a-linux-kernel-from-sony-copyleft-archives/
I think you have to find the right defconfig and change arm to arm64 and aarch64 when necessary
Click to expand...
Click to collapse
Now I'm not in stock, I've flashed the AOSP rom available in this post: http://forum.xda-developers.com/m4-aqua/development/5-0-aosgp-based-stock-t3262330. So that shouldn't be a problem, right?
aosgp?? a stock rom with aosp style dude,,base on stock not a real aosp
Sent from my E2353 using XDA-Developers mobile app
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please
Android 11 Stock Kernel with Magisk.
Based on SEA Firmware Version 59.1.A.0.485.
Download:
MEGA
Thanks! How did you make it? I did this:
* I downloaded XQ-AU52_Customized EU_59.1.A.0.485-R8B with xperifirm
* It was automatically extracted by xperifirm
* I didn't find anything looking like boot.img, but i saw boot_X-FLASH-ALL-E9C8.sin, which i unpacked with unsin
* The resulting .img (about 67.1 MB) i patched with magisk manager, logs looked positive
However, flashing that created a boot loop. I had to restore original firmware from sony's built-in recovery (back to android 10).
I tried extracting the 67.1 MB img with imjtool. Which results in 4 files: devicetree.dtb, kernelimage, kernel and ramdisk. I thought maybe I needed kernel, but that is only 15.4 MB.
cosmo_roel said:
Thanks! How did you make it? I did this:
* I downloaded XQ-AU52_Customized EU_59.1.A.0.485-R8B with xperifirm
* It was automatically extracted by xperifirm
* I didn't find anything looking like boot.img, but i saw boot_X-FLASH-ALL-E9C8.sin, which i unpacked with unsin
* The resulting .img (about 67.1 MB) i patched with magisk manager, logs looked positive
However, flashing that created a boot loop. I had to restore original firmware from sony's built-in recovery (back to android 10).
I tried extracting the 67.1 MB img with imjtool. Which results in 4 files: devicetree.dtb, kernelimage, kernel and ramdisk. I thought maybe I needed kernel, but that is only 15.4 MB.
Click to expand...
Click to collapse
Here:
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
cosmo_roel said:
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
Click to expand...
Click to collapse
Could you describe the complete procedure you did? Does this make possible to have root on stock ROM without unlocking bootloader?
Thanks in advance.
cosmo_roel said:
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
Click to expand...
Click to collapse
hi, i actually got the procedure myself. However, when editing the boot img in Android Kitchen, i can´t find the file "fstab.qcom". I have two fstab files, fstab.default and fstab.emmc.
Any suggestion?
Thanks in advance.
Supercharlie25 said:
hi, i actually got the procedure myself. However, when editing the boot img in Android Kitchen, i can´t find the file "fstab.qcom". I have two fstab files, fstab.default and fstab.emmc.
Any suggestion?
Thanks in advance.
Click to expand...
Click to collapse
Hi,
did you find a fix or a solution?
Thanks
EDIT: The fix is to comment the system_ext line inside the two fstab files
Just for reference there are two updates to this issue:
There is this tool by @entr0pia that automatically removes system_ext from the boot image
Magisk finally fixed the issue and it is now available in the latest canary builds!
Refs: Issue on Magisk repo - Commit that fixes the issue
Note: I haven't tested them yet!
Click to expand...
Click to collapse