Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
dblackburn965 said:
Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
Click to expand...
Click to collapse
Good luck, did WiFi work out for you?
ok. i am most likely asking this in the wrong back alley for this particular set of questions, if so please inform me to stfu, n ask <insert correct forum here> and ill then be on my way.
so, i have three of the same fairly dated, samsung galaxy s (4g) / us.cellular [not hooked up] not the point.. up until this post, many attempts to create a custom recovery for this has proven useless.. my question is this, if samsung has provided the "source code" for this particular model, shouldnt the i guess, particular informaton required for building of a custom recovery should be avalible, correct?
hell, i am most likely wrong but i am curious to know..
-deadseth
"i die alot"
Follow this thread from the post I linked to, I explained to another forum member how to compile a custom boot image, which will in turn allow you to edit the recovery before you compile. This will compile a KitKat kernel, which should technically work with other KitKat ROMs but will not work with anything older.
http://forum.xda-developers.com/showthread.php?p=57558013#post57558013
well
the phone is working off gingerbread.
deadseth said:
the phone is working off gingerbread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1828171
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Good luck.
this phone has no current custom recovery yet for it, that is what i am trying to work on here.
here is samsung's open source release of the phone's os
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=r930
These are the forums for the SGH-T959V and SGH-T959W. The link to the open source release you posted is for the SCH-930.
If you really ARE looking for SGH-T959V information read on.
We have several versions of CWM available, as well as a few TWRP versions. They are all integrated into a bootimage. They aren't built for a separate recovery partition.
Anyway in this commit, bhundven imported the samsung open source kernel files.
https://github.com/bhundven/blastof...mmit/03b6581e79545d2e40e41d0f4bedf165bb39b183
Then several people added more commits to the kernel samsung. You can read the commit history yourself:
https://github.com/bhundven/blastoff_kernel_samsung_galaxys4g/commits/gingerbread
BAD NEWS:
My Development Laptop's Hard Drive crashed, so I no longer have the projects I was working on (this one included). Due to the amount of time and effort Android development takes, and how little time I have to spare, I am going to hand this project over to the community. I have given the most active member I have seen so far (@AutumQueen92) contributor status, so that they can manage the thread. I can help here and there, but I will no longer be actively trying to develop CyanogenMod for the C3. I don't want to give this project up, but I just don't have the time for it any more. If you want to help with the ROM, you can find the device configs either at my GitHub or @wwwhana's GitHub. CyanogenMod Sources can be found on the CyanogenMod GitHub. Build instructions, amongst other things, can be found at the CyanogenMod Learning Center. If you need anything, please don't hesitate to contact me at [email protected].
Original Post:
THIS ROM IS STILL IN ALPHA. PLEASE DO NOT INSTALL IF YOU DON'T KNOW WHAT THIS ENTAILS!
Code:
******DISCLAIMER:*****
*You are installing this software at your own risk.
*I accept no responsibility for any bricked,
*dead, damaged, exploding, imploding,
*existentially challenged, time-travelling,
*zombified, or otherwise abnormal phones.
*
BUG REPORTS SHOULD GO IN THE "Bug Reports" TAB. REMEMBER, NO LOGCAT, NO FIX
Download Links in 2nd Post
ROM
Today, I bring great news: CM12.1 for the Xperia C3!
This is a port of CyanogenMod, a free, open-source, community-made ROM based on the Android Open Source Project. This ROM is still in Alpha Stage, but I have posted the flashable zip in the 2nd post so that I can get user bug reports. Please report any unlisted bugs in the Bug Reports Tab.
Note: This ROM shouldn't damage your phone, but if it does, don't point the finger at me. I will laugh at you. Only after I am finished laughing, will I attempt to fix the ROM.
Note #2: I am currently studying IT at university, and do not have much time to spare for this project. If I do have time, I will try to contribute, but I will also have to rely on other developers to contribute to this ROM via GitHub. You can find the source at either my GitHub or @wwwhana's GitHub. CyanogenMod Sources can be found on the CyanogenMod GitHub. Build instructions, amongst other things, can be found at the CyanogenMod Learning Center.
Working
Boot
Audio
Bluetooth
Cellular Signal
RIL
WiFi (Should be fixed as of ALPHA2)
Not Working
Mobile Data (Untested as of ALPHA2)
Mobile Hotspot
Brightness
Assorted Sensors (Rotation, etc.)
Camera (Also Flash, so no Torch) (Untested as of ALPHA2)
Instructions
Copy zip to /sdcard
Reboot to Recovery
[OPTIONAL] Make NANDROID Backup
[IF COMING FROM STOCK SONY] Wipe Data/Factory Reset
Install zip
[OPTIONAL] Install GApps (OpenGApps is preferred)
Reboot to System
[IMPORTANT] ENJOY!
First Boot will take a while, Sit back and relax for a bit.
Extras
To flash nut's XZDR TWRP for C3, follow the guide here.
To download OpenGapps, please use the Android 5.1 arm version here.
Edit from AutumQueen92: Sorry guys, I'm abandoning this phone entirely for a non-Sony. There are better phones out there and it's extremely difficult to find help from other devs. I'm leaving this up in case some crazy guy wants to make this work.
XDA:DevDB Information
CyanogenMod 12.1 for Xperia C3 D2533, ROM for the Sony Xperia C
Contributors
Riccorbypro, wwwhana
Source Code: https://github.com/Riccorbypro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2015-08-14
Last Updated 2017-11-10
Download & Changelog
DOWNLOADS PROVIDED FOR COMMUNITY DEVELOPERS - POST NO LONGER UPDATED
Original Post:
Download
Alpha 2:
Failed to boot in tests, not posting.
Alpha 1:
cm_wukong-UNOFFICIAL-ALPHA1.zip
Changelog
Alpha 2
WiFi should work now.
Mobile Data might work (Untested)
Camera binaries included in build (Untested)
Alpha 1
Original Release
Dude if u are successful in this I'll be the biggest fan of yours
Cause I'm waiting like hell for this rom
And a big big thanks in advance :good:
Good news!
I would like to be a tester for this ROM!
ADD OIL!
is this for xperia c (c2305) becouse it requires unlocked bootloader and i dont think you can do it on xperia C
If OP found a way to unlock this, I'm not sure if the different models would present a problem. The D2533 model 2014 and after has combined storage, meaning the phone memory and sd memory are now combined into 8gb. You can install more apps, but that's all there is to it.
masterismos said:
is this for xperia c (c2305) becouse it requires unlocked bootloader and i dont think you can do it on xperia C
Click to expand...
Click to collapse
This is for C3
Unlocking C3 Bootloader uses the same unlock code as Xperia Z3 Compact. I'm working on getting sources for yukon device tree and wukong device now.
It sucks that sony end support for the C2035 TT^TT, I was excited for the 4.3 update and after the news, i felt like I lost my faith in Sony.
I'm not trying to start a flame war here
Lel, it's a good thing I only unlocked the bootloader to get full root. I downloaded the kernel provided but not sure if I wanted to flash it just yet >.>
Which kernel "provided"? I haven't posted a kernel yet, I'm just having trouble booting with the universal msm8226 kernel. Making my own changes to it, then I'll try compile it again.
ROM source is still downloading... (South African internet...)
But I have found the right configs, and have a semi-complete device tree. Hoping I'll finish the download tonight...
Sent from my D2533 using Tapatalk
Riccorbypro said:
Which kernel "provided"? I haven't posted a kernel yet, I'm just having trouble booting with the universal msm8226 kernel. Making my own changes to it, then I'll try compile it again.
ROM source is still downloading... (South African internet...)
But I have found the right configs, and have a semi-complete device tree. Hoping I'll finish the download tonight...
Sent from my D2533 using Tapatalk
Click to expand...
Click to collapse
That's good news!!!!! Can't wait for that!!!
I meant the one in nut's xperia files. Not really confident in building one so I'm still reading up stuff >.>
No, the nut one works, I mean that I'm having trouble with the one I'm building from source.
Sent via Carrier Pigeon
While you wait...
OK, so I had nothing to do last night while the sources were downloading, so i decided to cook up a custom bootanimation.zip for the ROM. It is a mix of the traditional BIOS bootanimation and the CM12 bootanimation, so, here you go.
Preview and download attached.
Hey umm, just wanna confirm. The recovery from nut.xperia is for 5.0 and not KitKat right? And how do you flash it with flashtool?
Flashing TWRP
To install TWRP, please make sure that you are running the 19.4.A.0.182 ROM. The old 19.3.A.0.472 ROM's TWRP can still be built using the instructions in the hidden section.
Here is a file that can be used to install TWRP to 19.4.A.0.182, just download it and run the .bat file.
AutumQueen92 said:
Hey umm, just wanna confirm. The recovery from nut.xperia is for 5.0 and not KitKat right? And how do you flash it with flashtool?
Click to expand...
Click to collapse
Yes, the nut recovery is for 5.0.2 (19.3.A.0.472).
Download and extract the flashable zip, from http://nut.xperia-files.com/ -> XZDualRecovery -> Kernel Builder -> Check Box -> T2 Ultra D5303 -> D2533 -> DOWNLOAD.
Also copy the original zip to your phone's SD card (NOT INTERNAL STORAGE).
Install using:
Code:
fastboot flash boot <path to nut's boot.img>
Replace the <path to nut's boot.img> with the real path that you extracted from the flashable zip. (I would recommend just putting the boot.img in C:\adb\ for easy reference. This way, the command would be fastboot flash boot C:\adb\boot.img)
then type:
Code:
fastboot reboot
As soon as your device reboots, BUTTON-MASH BOTH the volume buttons (I'm still not sure if it's VOLUP or VOLDOWN to enter recovery!!!). If you've done it correctly, a green LED will light up, and then turn to purple. ONLY STOP PRESSING THE BUTTONS WHEN IT IS PURPLE.
You should now be in TWRP.
Then install the flashable zip from your SD card to your device, this will make sure that all the correct tweaks are in place for the recovery to have full functionality.
Aaaaaaaaaaand......... YOU'RE DONE!
P.S. This tutorial assumes your bootloader is UNLOCKED. If it is LOCKED, just use the installer from http://nut.xperia-files.com/ -> XZDualRecovery -> 2.8.21 -> T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip
P.P.S I HIGHLY RECOMMEND UNLOCKING THE BOOTLOADER.
Status update
Okay, so I have good news and bad news.
Good news
The ROM source is almost done downloading and I have finally managed to compile a kernel.
Bad news
The kernel didn't work, well, boot at least. I managed to get into recovery from it, but that was the limit of it's functionality. And the touchscreen didn't work in recovery anyway, so I gave that "release" up as a bad job.
I am currently exploring different ways of tackling the kernel problem, and will report back soon. The ROM should, hopefully, at least have basic functionality on the stock 5.0.2 kernel, once it has been built, and I'm hoping to get a build out within the next week.
For now, back to the kernel...
You can always ask ROM devs from other forums, especially those in the Xperia and similar device threads for ideas and advice. There was one guy who worked on a CM12.1 variant for the Note 1, he really souped the phone up.
AutumQueen92 said:
You can always ask ROM devs from other forums, especially those in the Xperia and similar device threads for ideas and advice. There was one guy who worked on a CM12.1 variant for the Note 1, he really souped the phone up.
Click to expand...
Click to collapse
I've actually been asking around, but they all say that I need to build before I can debug. And it's quite hard to debug a kernel when it won't even boot enough time to initialise adb. But the source is at 97%, so I'll hopefully have it by the time I go to bed. I can always start a build at that time...
Sent via Carrier Pigeon
I'm interested in building an updated, de-googled, de-bloated, ROM for a TCL A30 , model TCL5102D, mt6762/6765. First off was whether to post in tha Alcatel Section. My understanding is that Alcaltel is no more and those phones are now marketed as TCL. Prior Alcaltel posts may be helpful - perhaps the moderators could rename the section "Alcaltel/TCL" rather than adding a New TCL section.
I fouund mtkclient in the forum and it works on my device. I have not TWRP rooted it yet but have pulled boot.img, vbmeta.img and the entire system image. I have also found the TCL source code site, downloaded an earlier device with Mediatek Helio 22P chips and adb pulled /proc/config.gz. GPL source for my specific device has yet to be published by TCL.
I've yet to pull the vendor blobs and have only found guides in the Lineagos documentaion. It's pulling from a zip'd image rather than a device and TCL does not have images for any of their current phone. Also could not find a dump for this particular phone.
My first challenge is trying to build the kernel. The TCL source code, kernel 4.19.127, is not structured like the AOSP kernel source and aarch64, gcc builds hang up on the lcdscreen driver. The screen driver was backported in later 4.19.x versions which built with the config.gz and upstream kernel.org source.
What I'd like to do is to do is update the TCL source to the latest stable 4.19 code base but my web searches have not come up with any examples on how to do this. Could also build with the AOSP 4.19-stable source with the pulled config.gz - chances that it would work?
If I can prebuild the kernel, then make a decision in regards to a LineageOS build vs a GSI build. Maybe even build within GrapheneOS (uses prebuild kernels).
Where, in the forum, should I start the line of questions? Can anybody point me to a guide on howto build an kernel with an up-to-date source?
hi, your best place to go would be here and here
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
danvep5014 said:
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
Click to expand...
Click to collapse
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
971shep said:
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm working on how to get the device to be recognized in mtkclient. Regardless of what button combination I use, the device fails to be recognized. Any specific way it needs to be done on the TCL A30?
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
danvep5014 said:
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
Click to expand...
Click to collapse
I start mtkclient with the phone connected via usb but powered off. Mtkclient messages that it is trying to establish a connection. Then just power up with the power key only. You should get messages that you connected in brom mode.
I was finally able to get it. Had to use adb reboot edl. Did the trick. Now I'm trying to build a rom with oxygen os but i keep getting stuck in a boot loop.
Boot loops can have many causes.. In the case of a custom rom, it is often that boot verification of the file systems fails, ie a file system checksum is different. In the thread I linked above, the way around this was to overwrite the three different vbmeta.* files with a blank file..
Hello there!
I know this thread is going to annoy some of you, but it’s my last attempt before giving up.
I’ve got a Zenfone 4 (Z01KDA) lying around and this phone is nice. But no one ever developed or ported any ROM to it, even if the bootloader is unlockable and there is an official version of TWRP. The source code is also available on the official Asus website.
So, here’s my question: is there any way for someone here to port a Z4 Max ROM to the Z4? I’m no developer, I just know how to tinker a bit with phones but not much.
Thanks in advance for any help!
Dunno if this answer could help (even i am no dev myself), but it seems even this device got it's development abandoned tbh.
I remember the latest actual development for both X00ID and X00HD fell during late 2021 (at this point 1yr ago) with PBRP (apparently TWRP got deprecated and retired by, i assume, issues with the code- i think) and LOS suddenly got vaporized on the download links.
The source codes are around (i have like a post into this device's forum that collects such), and the already compiled LOS for the X00HD doesn't seem to work at all.
I assume that before effectively porting it for the Z4, it is needed to fix something with the partitions firsthand (i tried to flash it with PBRP on my X00HD, via getting the ROM on webarchive, and got terrible results- even by disabling DM Verity on install and signature verification).
Got stuck over the boot animation and wasted my time trying to figure things out-
turns out the reason why it refuses to boot is mainly one reason:
the /cache partition gets formatted as SquashFS, making the OS stuck on boot. If i format the same partition as Ext4, just to make it work, Lineage refuses as a whole to boot and redirects me to recovery or fastboot.
Nowadays i'm unsure if the fault falls on PBRP or i lack the Lineage Recovery .img file to make that function proper (since the original post mentions about having both- but the X00HD has no source code for it either and only the X00ID has it: both compiled as an .img and source on GH).
Upon further inspection and comparing the .zip files to an official Asus update.zip file, it seems the dev hasn't setup a cache.img file at all into the flashable zip last time it got touched.
Just sharing my slice of experience since now i'm getting why (presumably) the Lineage DL links got nuked. Maybe too many defects went around and the dev abandoned things as a whole.
I hope someday this device will get taken back to development, since sources are still available (sadly, i couldn't contribute compiling because of a proper lack of resources to do so) and unsure if the Z4 can get a Custom ROM by either reverse engineering the X00ID or X00HD's codes.
Nowadays i'm practically stuck to the Pie Beta ROM with root perms, still waiting for someone to come and resume where the previous dev left things out at.