Related
Hi everyone,
I've successfully built OmniRom from source for my Nexus 5 using this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-how-to-build-fav-kk-rom-cm-aokp-t2617919
The ROM builds fine and the omni-4.4.2-xxx-hammerhead-homemade.zip is created in /out/target/product/hammerhead.
However, when I flash that zip file, my phone is stuck on the Google logo and it won't boot into the system.
Is there anything I am missing?
A Google search didn't reveal anything.
Thanks in advance!
I'm assuming you've already downloaded and extracted the proprietary blobs, yes?
---
Posted from whatever phone booted today
I knew I was missing something. Can you point me to the right direction how to do it?
edit:// Nevermind, found it and building as we speak! Thanks!
edit2:// The missing proprietary blobs were the issue indeed. My phone just booted into my first self-built ROM. Cheers!
For anyone having the same issue: Here's a good guide for getting and extracting the missing files.
Hi guys,
So am back to making Custom kernels for Lollipop, in an attempt to help some friends and was able to successfully provide a Custom kernel for Samsung S4 : 9506 (Lollipop). The kernel worked well, without a major hiccup. :good:
But, when I tried to make a custom kernel for Samsung S5 Plus : SM-G901F (Lollipop), the source code provided by Samsung fails to boot properly. His device is stuck in a boot loop, though I tried two source codes from the site (to check, I did not modify the source code, just tried to compile and flash). If I "repack" the Stock boot.img, that is working fine, so I assume there is no issue with Ramdisk and the packing method am using (mkbootimg_tools by Xiaolu). I tried two build versions : B0C4 and B0CA, both have same problem
Can someone suggest something, or tell me how I can collect kernel logs? (since am stuck with a bootloop, /proc is not accessible)
-Roc
roc_vader said:
Hi guys,
So am back to making Custom kernels for Lollipop, in an attempt to help some friends and was able to successfully provide a Custom kernel for Samsung S4 : 9506 (Lollipop). The kernel worked well, without a major hiccup. :good:
But, when I tried to make a custom kernel for Samsung S5 Plus : SM-G901F (Lollipop), the source code provided by Samsung fails to boot properly. His device is stuck in a boot loop, though I tried two source codes from the site (to check, I did not modify the source code, just tried to compile and flash). If I "repack" the Stock boot.img, that is working fine, so I assume there is no issue with Ramdisk and the packing method am using (mkbootimg_tools by Xiaolu). I tried two build versions : B0C4 and B0CA, both have same problem
Can someone suggest something, or tell me how I can collect kernel logs? (since am stuck with a bootloop, /proc is not accessible)
-Roc
Click to expand...
Click to collapse
probably u r using old mkbootimg that does not pack dt.img or even not recognizes it.
i have different problem, when i compile stock kernel (not a single modification) and repack it to boot.img with stock dt.img and stock ramdisk (maybe this is the cause?) i get reboot right after phone boots to password.
Somewhere i saw somone had similar issue but he didnt get the answer so i dont know too .
im reading forums and google for a week now, i never used linux longer than a few days or at school so i had really hard start even to compile stock kernel
Most guides or tutorials are written by guys who know linux very well, they often forget that not every person have same setup, i as example failed to compile because i didnt have lzop installed - after reading logs i found that its te cause it wont compile at te end (couldnt compress kernel to zBoot).
Its very big pain for newbie like me to do this work but i need custom kernel, pure stock, without singlemodification except lower voltages on cpu - no one will do it for me so i try really hard
i had the same problems after i successfully compiled kernel, it wouldnt boot because of old mkbootimg i was using.
Hi
How is the status on development of LineageOS for manta? Is anyone working on this?
Would be great LineageOS on Nexus 10....nougat flavour please!!!
To get LOS on our beloved Nexus 10 would be awesome. :victory:
Apparently, Manta is on the list of devices that will be getting Lineage. However, the initial release is likely to be Marshmallow based still.
I'm fine with mm since there is no Xposed for nougat so far.
I've bee trying to build for three days now. My last attempt ended right before making the zip after six hours on my old Acer laptop (because it has Ubuntu) with the error:
Code:
TypeError: argument of type 'nonetype' is not iterable android
AgentOrange96 said:
I've bee trying to build for three days now. My last attempt ended right before making the zip after six hours on my old Acer laptop (because it has Ubuntu) with the error:
Code:
TypeError: argument of type 'nonetype' is not iterable android
Click to expand...
Click to collapse
I managed to get a nougat build but, it will not go past the google logo.
I am using bbqlinux.
Kernel source from binkybear for nethunter support.
The kernel works I just cant get it to go further
Got a working LineageOS 13 build for manta without too much of a hitch.
The build guide ///wiki.lineageos.org/manta_build.html#extract-proprietary-blobs) is missing the required package libxml2-utils. If you install that and follow the guide closely it should run fine.
Remember to activate caching really helps speed up build times. I'm down to 15 minutes on consecutive builds on a ubuntu headless server on virtualbox with 4 cores & 8G RAM.
Getting the build installed was a bit trickier. TWRP flash over the last CM13 build didn't work.
I needed to flash the official ROM first, then install the latest TWRP version (//twrp.me/devices/samsungnexus10.html)
It's been running reasonably stable for two days with the 6.0 micro opengapps package apart from some PlayStore installation issues, but I haven't tested extensively.
Cheers
Your VM has twice the cores and twice the RAM as my laptop. I wish I could run this on my desktop, but the Linux subsystem is nearly impossible to build on >.<
I'll see if I didn't have that package installed and give it another go I suppose.
Build success! And in an hour fifteen minutes this time! (Last time it failed after six hours) I already had libxml2-utils installed. I did use distcc with another computer, but I'm not sure if it was even used. I suspect the majority of the speedup was due to caching from my last attempt.
Edit: I can't for the life of me get the home button to work...
I'm having the exact issue described here, but no solutions will work.
Hmm, home button works fine for me.
I've only got one bug that I had infrequently on the official CM builds, too: I can only install one app from the play store at a time.
Have to close the playstore and reopen it. That's probably related to GAPPS, though.
If you want, you can try out the build I'm currently running. Not absolutely fresh, but haven't had any problems except the one above:
Code:
//androidfilehost.com/?fid=745425885120704233
I compiled lineage os yesterday in 1,5h. I will try to install it this evening. I could upload it for everyone until there are official builds.
My build doesnt boot. I don't know if the file size of the zip is right. Mine is 283 mb . @zerebruin
@XxM4tzexX not sure, if build size is a good indicator. My build from Jan 27 build was 278.4 MB (291,889,838 Bytes).
Just built again with a fresh repo sync and that was 278.4 MB (291,885,568 Bytes). So not much of a difference.
Your installation works, just not the system bootup? which bootloader are you using?
zerebruin said:
@XxM4tzexX not sure, if build size is a good indicator. My build from Jan 27 build was 278.4 MB (291,889,838 Bytes).
Just built again with a fresh repo sync and that was 278.4 MB (291,885,568 Bytes). So not much of a difference.
Your installation works, just not the system bootup? which bootloader are you using?
Click to expand...
Click to collapse
Installation is fine although the install process is quite fast compared to a installation of cm. What do you mean by 'which bootloader'?
sorry, I meant the recovery, of course. still getting mixed up with terms here sometimes :|
Are you using the stock recovery or a custom one like TWRP or CWM?
They might give more/better feedback on installation errors.
zerebruin said:
sorry, I meant the recovery, of course. still getting mixed up with terms here sometimes :|
Are you using the stock recovery or a custom one like TWRP or CWM?
They might give more/better feedback on installation errors.
Click to expand...
Click to collapse
i'm using TWRP.
Are you using repo sync or repo sync -c (to downoad only the current brunch, should not make any difference)?
I've been using the full repo sync...
I'm using TWRP 3.02 and If I remember correctly, I needed to do a full wipe for the first install to work. Then again, after the installation went through it all worked fine.
I guess the next step would be to go through the build log...
I finally got it working now.
Congrats!
Out of interest: What was the fix?
hi,
this was the first time compiling a kernel from android source. I'm actually a java and app dev, so this was actually new to me.
I wanted to have full ntfs support and maybe some other features on my shield so i thought i'll give it a try.
the first thing i tried was pulling the whole android source code from the nvidia git server. Then I followed the instructions except i changed "mp dev" to "mp bootimage -j5" to just build the kernel. (I also did no modifications to the kernel). All went well and I got the boot image.
I used this repo: rel-24-uda-r1-partner.
I flashed the boot image with fastboot, but when it boots up, the nvidia sign comes and after some time I get a message with a red exclamation mark, which says that the partitions are corrupted or something like that. Then I get a black screen.
I also dont want to open up the device to access the uart to read out the kernel messages.
I dont know what else to do. Am I missing something? Does the open source kernel even work on stock android rom?
have u tried wiping the data partition?
yes i have
Take a look at the last few posts on this thread https://forum.xda-developers.com/sh...ecovery-twrp-shield-android-tv-t3510456/page4
so do you mean i have to use a another toolchain?
Jahusa said:
so do you mean i have to use a another toolchain?
Click to expand...
Click to collapse
I believe so
It works now. I copied the kernel from the repo into a another folder, set the env variables for the cross compilers and compiled it.
With the help of some threads in the nvidia forum and google, i got everything compiled.
The kernel boots now. But there's still the red sign at boot. I have to figure it out later.
Edit: OK, i think I got it now. To remove the annoying sign, I have to somehow disable the boot verification.
@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image
That warning pops up once you unlock bootloader.
Jahusa said:
@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image
Click to expand...
Click to collapse
This thread is presently about the development of a TWRP port to these devices.
The build is not yet working!
I am in the process of porting TWRP to my 3562 mostly out of pure spite for this stupid device. This thread is mostly for collecting my development process, for anyone who is interested, or wants to help.
Presently, TWRP will boot properly, and does function apart from UI issues and generally not being able to mount partitions correctly.
The UI draws in portrait mode (USB port at the top), but the touch interface responds in landscape mode (USB port on the right). This is very annoying, but it is still usable, so I haven't looked too far into it.
It seems to mount boot and userdata partitions okay, /sdcard is full of garbage data (encrypted? bad mount flags?), /system will not mount at all.
First order of business is to get /system mounted. It looks like this is related to vbmeta, so I have to sort out how to properly wipe the vbmeta on this device.
Here is my current image, if anyone is interested in trying it out: https://drive.google.com/file/d/1kMvKvocKY6AWRR-xkXIwisv27TmF6xcP/view?usp=sharing
I'll keep this updated as I keep working. As always, any input is greatly appreciated.
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
rolenthedeep said:
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
Click to expand...
Click to collapse
Thanks for moving, we were a bit OT in other thread. Yes the boardconfig.mk is for building from source. Does no good when using kitchen, I was just showing you an example of where and how rotation was handled. I still haven't followed up on changing rotation and touch input using kitchen, just got home from another heart catheterization. The only way to get a fully working fully functional twrp is to build from source, but without source code AIK is an awesome alternative. I just can't remember if we can change rotation and touch input in de-compiled img. We can ask @osm0sis if it is possible to edit recovery rotation via AIK. If you've not done so already, check out his work here on XDA. There are a lot of useful tools and scripts authored by him and a wealth of android knowledge that you can only benefit from reading.
Haven't ever messed with TWRP rotation myself, sorry. I'm sure it's something you can Google and find out though.
@rolenthedeep look at this may be helpful with rotation
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
mpalpha said:
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
Click to expand...
Click to collapse
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
tek3195 said:
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
Click to expand...
Click to collapse
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
mpalpha said:
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
Click to expand...
Click to collapse
I thought I was replying to someone else, but same applies. You're wanting to port one using kitchen the best place to start is here:
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
Where it gives the different screen resolutions go with largest, if it calls for a file not present in your device just skip it and don't add extras. There are a lot of guides but that one I know works rather well, I've used it on 3 diff devices. Cooking custom recovery in kitchen works but not always correctly. By that I mean that you may not have the ability to backup or restore or install. You may not be able to control brightness or some other setting or it could be that usb does not work. It can be a combination of any of those things and more. It can also be that you never notice something not working because it does everything you want it to. Just letting you know what to expect and saying that building from source is always best, even when it's unavailable.
If you ever get the time can you port TWRP to the 100015685-E?
@rolenthedeep here is a WIP fstab. I have commented out the partitions that were not first_stage_mount If you try it as is to try to get an idea of which parts are needed for recovery there is no sd card in it as it too is commented out for now. Got caught up in some other issues and stopped looking at it for a while. Maybe it will help a little.
Any updates on this? I have the 10.1 3562 version