hi
been trying to download repo for cynogenmod but have failed with numerous attempt. it is a huge file. is it possible to download just the required files to make cwm recovery 11 ? for kitkat? if possible how ?
Regrettably, no. You will need to repo sync the entire source code
shoey63 said:
Regrettably, no. You will need to repo sync the entire source code
Click to expand...
Click to collapse
alrite,
Code:
:git fetch aosp --tags tag android-4.4.4_2 +refs/tags/android-4.4.4_r2:refs/tags/android-4.4.4_r2
getting error on this one, can i download it manually from ?
https://android.googlesource.com/platform/prebuilts/sdk/+refs
Before going through the pain of doing that, does your device have Cm11 device tree?
shoey63 said:
Before going through the pain of doing that, does your device have Cm11 device tree?
Click to expand...
Click to collapse
no. as per my knowledge . My device is Lg g3 f460 k (snapdragon 805 variant). on kitkat 4.4.2. i searched far and wide but nothing related to it.
I only have 2 options now,
sync cm 12 (not sure if i could build a recovery here that will work in kitkat)
download individual files and put it the respective folders.
It would be better to start with cm11, which is known to be compatible with your device, as you have kitkat. But Cm12 has, at least in the later revisions, his own Recovery, which only offers a part of the options.
Spartaner25 said:
It would be better to start with cm11, which is known to be compatible with your device, as you have kitkat. But Cm12 has, at least in the later revisions, his own Recovery, which only offers a part of the options.
Click to expand...
Click to collapse
okay got everything but there is sdk folder missing in prebuilts.. help me download it manually perhaps ? my version of android is 4.4.2
Related
I've been trying to get a working build over the past week or two for the GS4 and I wanted to clarify.
My UT repo is up to date, yet when using the lunch cm_jfltetmo-userdebug command tells me that it's PLATFORM_VERSION=4.2.1. Shouldn't this be 4.2.2 or have the sources just not been updated to 4.2.2 yet? If it's just that the phablet sources are still on version 4.2.1, is there any way I could at least update my local Ubuntu repo to match 4.2.2? For reference, my CM build tells me the correct version number...
lordcheeto03 said:
I've been trying to get a working build over the past week or two for the GS4 and I wanted to clarify.
My UT repo is up to date, yet when using the lunch cm_jfltetmo-userdebug command tells me that it's PLATFORM_VERSION=4.2.1. Shouldn't this be 4.2.2 or have the sources just not been updated to 4.2.2 yet? If it's just that the phablet sources are still on version 4.2.1, is there any way I could at least update my local Ubuntu repo to match 4.2.2? For reference, my CM build tells me the correct version number...
Click to expand...
Click to collapse
If you look at http://phablet.ubuntu.com/gitweb you will see branches named phablet-saucy, amorng others things (like working with flipped images only) it updates on top of cm-10.1.2 which is based out of 4.2.2
You can probably extra officially use it, but it still needs some testing and hasn't been announced.
Is there any way I can build for my device without the kernel and either inject the kernel after the build completes or make it a separate flashable unit?
Bump
lordcheeto03 said:
Is there any way I can build for my device without the kernel and either inject the kernel after the build completes or make it a separate flashable unit?
Click to expand...
Click to collapse
You can just put in the boot IMG in the zip after it builds, or you can put a prebuilt boot.IMG in the device repo.
Sent from my LG-LS970 using Tapatalk 4 Beta
The reason I post my ROM here is because I'm soon starting with a new rom, broodROM KitKat which will also be available for the Note 3, So I figured why not test it on my current AOSP ROM (to see if there is any trouble on compiling, but no!). This AOSP is based on the real Google AOSP, no real further modifications (only thing is that it includes DeviceSettings from the S4 currently), and AppOps is exposed. that's all.
It includes the stock CM11 kernel (which is kinda crappy). but I don't have the device so cannot make decent kernel myself without testing. Also the ROM is 100% untested. but it compiled without any error with my sources (www.github.com/AOSP-S4-KK) so I think it's alright.
Working List
- You tell me I have no idea :silly:
Download Alpha 1
www.broodplank.net/files/AOSP-442-N9005-Alpha-1.zip
on alpha 01 you need to flash a custom kernel
SEND ME LOGCAT! BECAUSE CURRENTLY IT SEEM TO BOOTLOOP
The device name is listed as hlte in settings / build.prop, don't worry this is actually hltexx
Download Gapps Lite + SuperSU (yes it's not rooted by default, I recommend installing this package)
http://broodplank.net/files/gapps-4.4.2-lite-with-supersu-1.86.zip
Sources
- https://github.com/aosp-s4-kk
Download:
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u git://github.com/AOSP-S4-KK/platform_manifest -b kk-4.4
repo sync
Building:
Code:
. build/envsetup.sh
lunch
make otapackage
reserved1
Sweet man!! Thanks always looking for something new to flash lol downloading now
Sent from my iPad using Tapatalk
Downloading!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thankyou OP
anybody that has tried this, can you let me know if the temp/humidity sensors are still working after a few hours? as with other cm roms they stop working for me
Awesome Broodplank! Just switched from the Galaxy S Plus to the Note 3, always enjoyed your roms on there. Will try out this one! Keep up the good work
Sent from my SM-N9005 using xda app-developers app
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
radicalisto said:
Flashed and it went straight into Odin mode and said "Could not do normal boot" - I'm on the new Kitkat bootloader.
Click to expand...
Click to collapse
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
broodplank1337 said:
Lol what the hell, that's almost impossible that my rom triggered download mode XD.
But it could be true, I have no clue since I do not have the device. what you could try is using the boot.img & /system/lib/modules from CM11 nightly.
btw, just downloaded CM11 and noticed there are NO modules in the kernel of hltexx. this means the kernel I added will not boot most likely.
So please install this zip after installing the rom:
www.broodplank.net/files/aosp-442-hltexx-kernel.zip
Click to expand...
Click to collapse
OK - will try again now and let you know :good:
and new bootloader ?
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
radicalisto said:
Just bootloops with that .zip you added.
I did however change your kernel zip after the bootloop and used - temasek's HLTE custom kernel - I am now on the Android start up screen you have added but it is stuck on there.
Click to expand...
Click to collapse
ok good, could you open up adb shell, and send me the logcat, since I have no idea what actually could be the cause atm.
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
radicalisto said:
Yup will do it shortly, just heading home now
Sent from my CM11 Kitkat powered N9005
Click to expand...
Click to collapse
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
broodplank1337 said:
Ok thank you very much, without some proper logcat I cannot fix anything since I don't have the device :silly:
Anyways, I think the problem won't be a serious one, since the rom has msm8974 support
www.broodplank.net/logcat for uploading logcats pls
Click to expand...
Click to collapse
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
radicalisto said:
Sorry I couldn't manage to get a logcat via ADB due to some kernel issues with connecting to the PC - I'll try again today. - Is It possible you are using the old CM sources rather than the unified build sources? - device changed from HLTEXX to HLTE
Click to expand...
Click to collapse
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
gianton said:
This ROM is built from pure AOSP sources not CM.
Hope a working build comes up soon, really like pure AOSP ROMs!
Click to expand...
Click to collapse
Ah I dropped the herp a derp then hahah, Nah reason I thought that was because of the CM kernel used to boot it up. Thanks for correcting :good:
---------- Post added at 08:56 AM ---------- Previous post was at 08:55 AM ----------
@gianton it'll boot into splash screen with temasek's kernel, if you wanna try and grab an ADB Logcat? - I'm having issues getting one :crying:
Sorry for not providing a good kernel, the thing is I cannot compile it decently with the ROM. it says I have to add module support and recontinue, thing is, the note 3 does not use it. but my build forces it.. Anyone have experience on CM with compiling the kernel? (the kernel is from CM after all)
You could try temasek or Yank555 or wootever for help with kernels as they're pretty decent at them - civato knows his stuff also, however I believe he has only worked with Stock samsung kernels and not CM stuff.
Still cannot get ADB logcat, phone won't recognise in PC
So, after destroying a tremendous amount of data and a whole lot of wait, I finally synced the whole OmniROM 6.0 source code via repo. Now I want to compile it for my device XOLO BLACK (Codename: BLACK) so, can somebody tell me how I can and what am I gonna need (I mean files, like vendor files, kernel etc.)?
Also, how can I extract its device tree? Because it's not available online.
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
zelendel said:
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
Click to expand...
Click to collapse
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
NutVolt said:
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
Click to expand...
Click to collapse
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
zelendel said:
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
Click to expand...
Click to collapse
I know it's gonna take long but if I can't even start then I'll feel very bad, all the hard work I've done to just fetch the source.
Anyway, how can I make a device tree? Can you teach me?
I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know
I'm looking possibility to make custom image to Lenovo Tab 2 A10-30F/L but i have stuck.
system.img is divided to system_*.unsparse files.
one user has done unsparse file joiner application but it doesn't work and no sources available from it. https://forum.xda-developers.com/showthread.php?t=2647429
I have also looked different custom rom kitchens but those doesn't have any file joining solution for joining unsparse files.
Not sure if this is a common method for qualcomm products to have system.img divided to unsparse files.
Any help would be much appreciated.
Jugehuge said:
I'm looking possibility to make custom image to Lenovo Tab 2 A10-30F/L but i have stuck.
system.img is divided to system_*.unsparse files.
one user has done unsparse file joiner application but it doesn't work and no sources available from it. https://forum.xda-developers.com/showthread.php?t=2647429
I have also looked different custom rom kitchens but those doesn't have any file joining solution for joining unsparse files.
Not sure if this is a common method for qualcomm products to have system.img divided to unsparse files.
Any help would be much appreciated.
Click to expand...
Click to collapse
Would it be possible to unpack system.new.dat and repack it as system.img?
https://forum.hovatek.com/thread-15855.html
I unzipped the TB2-X30F_S113_160816_ROW_FULLOTA rom and can only see system.new.dat, not system.img. Where did you get the system.img from?
kreator83701 said:
Would it be possible to unpack system.new.dat and repack it as system.img?
https://forum.hovatek.com/thread-15855.html
I unzipped the TB2-X30F_S113_160816_ROW_FULLOTA rom and can only see system.new.dat, not system.img. Where did you get the system.img from?
Click to expand...
Click to collapse
Isn't that FULLOTA image for updating sw from SDcard??
I have downloaded SW from here. https://cloud.mail.ru/public/3Kcw/Mm9WDWTWH
I have unzipped TB2-X30F_S000113_160816_ROW_qpst.7z and it has system.img divide to Unsparse images.
Jugehuge said:
Isn't that FULLOTA image for updating sw from SDcard??
I have downloaded SW from here. https://cloud.mail.ru/public/3Kcw/Mm9WDWTWH
I have unzipped TB2-X30F_S000113_160816_ROW_qpst.7z and it has system.img divide to Unsparse images.
Click to expand...
Click to collapse
Pardon my lack of knowledge on roms but what would be the issue if using the OTA Rom?
kreator83701 said:
Pardon my lack of knowledge on roms but what would be the issue if using the OTA Rom?
Click to expand...
Click to collapse
Probably not an issue. If i remember some other forum correctly that FULLOTA update fails if you have rooted your tablet.
Also same problem that i have with those unsparse files but it seems that for system.new.dat there seems to be solution.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Jugehuge said:
Probably not an issue. If i remember some other foorum correctly that FULLOTA update fails if you have rooted your tablet.
Also same problem that i have with those unsparse files but it seems that for system.new.dat there seems to be solution.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Click to expand...
Click to collapse
So can use the ota Rom?
kreator83701 said:
So can use the ota Rom?
Click to expand...
Click to collapse
I don't see reason why not.
Look forward to seeing a CM based ROM!
Have you had much luck getting the source code for the Mediatek chip? Appears to not be readily available
chibot75 said:
Have you had much luck getting the source code for the Mediatek chip? Appears to not be readily available
Click to expand...
Click to collapse
Lenovo Tab 2 A10-30 doesn't have Mediatek chip.
It's using Qualcomm 1.3 GHz quad-core Snapdragon 212 (APQ8009) processor with a Adreno 304 GPU
Would it be possible to build lineage OS for this device using this guide?
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
chibot75 said:
Would it be possible to build lineage OS for this device using this guide?
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
Click to expand...
Click to collapse
I haven't much experience of LineageOS so can't say sure. Could be.
Jugehuge said:
I haven't much experience of LineageOS so can't say sure. Could be.
Click to expand...
Click to collapse
I'm following the above guide in order to build Lineage 14.1 for my Lenovo Tab A10-30F. The guide is intended for Lineage 13.0, so a few minor tweaks are needed. Will keep you updated here, but it's the first time I try to build Lineage from scratch, I only do it because I softbricked my tablet, and I don't manage to find a build for it, so I'm not very optimistic
EDIT: I gave up, it does not look too difficult, but unfortunately I underestimated the amount of time and disk space needed, I need to switch to a better machine... Could someone try?
I found this thread, but I think the device it refers to is different.
It looks strange that nobody built lineage for this tablet though... it's a good piece of hardware, cheap and functional... Did I search in the wrong places?
Up
News anybody?
Up <.<
On the Russian forum http://lenovo-forums.ru/topic/23256-lenovo-tab-2-a10-30-achilles-lineageos-141 someone reports having installed LineageOS 14.1 on the Lenovo Tab 2 A10-30.
Fraxel said:
On the Russian forum ... reports having installed LineageOS 14.1 on the Lenovo Tab 2 A10-30.
Click to expand...
Click to collapse
I have installed this rom today on my TB2-X30L and succesfully tested Wifi, mobile data (LTE/4G), camera (photos only - video does not work) and even FM radio.
I tried to make a phone call what of course did not work.
It´s an unofficial build from July 31st, 2019 (meaning only 5 months old). Security patches from July 5th, 2019.
14.1-20190731-UNOFFICIAL-achilles
Does anybody use this ROM?
Or any other ROM with current security patches?
I actually gave up with Lineage on this device but just because I turned it into a kind-of ebook reader: I removed all the crapware and set it to bare minimal functionality for reading scanned color pdf (D&D manuals mostly) and with the original firmware this yields a monstruous battery life. Like, I can forget it for weeks in my closet and pull it out still half battery
Guys for that tablet the latest custom ROM is lineages 16.0 and the latest twrp is 3.1.1
ROM: https://androidfilehost.com/?fid=7161016148664803115 (tested working fine , RIL not working)
TWRP: https://drive.google.com/file/d/1Z5g-AJXypO0b-_pvJR8TMk7I9cAyREa9/view (tested evrythink working)