[Q] Deodexerant binary for 4.4.2 - Android Q&A, Help & Troubleshooting

Good day fellow XDA citizens.
I'm in dire need of a usable deodexerant 4.4.2 binary for my device. I'm in the process of deodexing framework files but some files (namely core.odex, framework.odex, and framework2.odex) just refuse to deodex. Apparently my device has a non standard inline table (whatever that is) and some files will not deodex unless this non standard inline table has been extracted from my device using this deodexerant binary. I would like to give this a shot but with avaricious internet providers here it will take at least three weeks nonstop to download the full AOSP source. No kidding.
My phone is a MT6592 device running on Android 4.4.2. I hope someone will assist me regarding this matter, as the development for this specific device is just plain dry and I have to do the things I like to have in my phone all by myself.
If some sort of workaround is available or if there is someone I can PM to ask for assistance or if there is anything of help at all please feel free to reply in this thread.
P.S. Here is the README file I used as reference https://cells-source.cs.columbia.ed...759ef422e9f7cf4a08c80ac87f/deodexerant/README
Best regards
Ocenyx

After fooling around in Google for some more I found something peculiar and such is the case of my device. Classes.dex are already included in the apk and jar files I intended to deodex. It seems like the odex files present are duds.
As this dilemma seems to be not present in the first place, I'll leave this thread open as deodexerant binary might come in handy for future use.

Related

[Q] how to port ics (serious learner)

Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte

[HELP] Working on a patch for Tablet UI on Nexus10

There is currently a patch for true Tablet UI on the Nexus7 Development that has worked successfully. Link is here. The following is a quote from the original thread:
Intro
Goal of thread is to share details around how the trigger for Phone UI/Phablet UI/Tablet UI works, and provide a dpi independent patch for tablet ui. Hopefully this also eliminates the misinformation that changing lcd density is the only way to get Tablet UI.
What's "true" tablet UI vs what is called tablet UI in many roms? The Tablet UI actually defines how some apps work (e.g. dual-paned settings like in the screenshots below) vs the other solutions that simply draw the standard Nexus UI with tablet navigation/system bars.
The 'Triggers'
In 4.1.x, there are two files that need to be modified:
PhoneWindowManager.java, located in frameworks/base/policy/src/com/android/internal/policy/impl contains the code that determines which UI to present. During compile this is a part of android.policy.jar
WindowManagerService.java, located in frameworks/base/services/java/com/android/server/wm contains code that specifies the lowest DP settings and has the system select from either sw600 or sw720 presentations. It is a part of services.jar
Click to expand...
Click to collapse
Basically, I'd like to modify this to work on a 4.2.1 AOSP ROM on the Nexus10 (flashing the Nexus7 patch on the Nexus 10 leads to a bootloop). The OP shows what modifications can be made in his thread so I'm wondering how I can port this to a Nexus10 ROM. I've used APKTool to break down the "android.policy.jar" file and looked through the smali files hoping to simply edit the corresponding lines but I was unable to locate it. Apparently there's more to it than that. Any thoughts on how to create a flashable zip to patch these files?
brGabriel said:
There is currently a patch for true Tablet UI on the Nexus7 Development that has worked successfully. Link is here. The following is a quote from the original thread:
Basically, I'd like to modify this to work on a 4.2.1 AOSP ROM on the Nexus10 (flashing the Nexus7 patch on the Nexus 10 leads to a bootloop). The OP shows what modifications can be made in his thread so I'm wondering how I can port this to a Nexus10 ROM. I've used APKTool to break down the "android.policy.jar" file and looked through the smali files hoping to simply edit the corresponding lines but I was unable to locate it. Apparently there's more to it than that. Any thoughts on how to create a flashable zip to patch these files?
Click to expand...
Click to collapse
haha i saw your post to my rom thread and this is exactly what i tried to do!
the thing is when you decompile precompiled java code you get the assembly and actually have to edit the opcodes. i tried doing that and failed (bootloop). I was so frustrated because i spent like 6 hours for nothing and decided to learn how to build AOSP from scratch. When i succeeded i posted my rom
schnip said:
haha i saw your post to my rom thread and this is exactly what i tried to do!
the thing is when you decompile precompiled java code you get the assembly and actually have to edit the opcodes. i tried doing that and failed (bootloop). I was so frustrated because i spent like 6 hours for nothing and decided to learn how to build AOSP from scratch. When i succeeded i posted my rom
Click to expand...
Click to collapse
Haha, well it was a noob "shot in the dark" attempt on my part. Going to start looking into building from scratch so I can take care of business on my own instead of having to rely on others. I don't mean that in a negative sense, I'd like to be able to contribute to the community one day.
Anyway, thanks for your work, schnip!

Porting htc one roms to the max?

hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
+1
Sent from my SM-N900V using Tapatalk
hectorz321 said:
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
Click to expand...
Click to collapse
Permission failure? Noob here too
I am guessing the ROM you tried to port checks for the Model number of the phone before flashing. What ROM did you try to port to and if you could post the instructions here we will make this the porting thread
Given that HTC One has all the custom ROM's and kernels we need devs or someone like us who can follow instructions to start doing it. I am sure we will get help from one another and end up with custom ROM's for the MAX.
I was also thinking of doing this but just to start with i don't want to look at the fingerprint scanner and may be later we could get it working.
I am certain most people would be willing to not have a working fingerprint scanner, as a trade off for a few custom roms/kernels...
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Murrda said:
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Click to expand...
Click to collapse
this was exciting to read, best of luck
I am going to get Ubuntu installed today and then Android Kitchen here i come!
pradeepvizz said:
I am going to get Ubuntu installed today and then Android Kitchen here i come!
Click to expand...
Click to collapse
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
DeadPhoenix said:
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
Click to expand...
Click to collapse
Thanks, i just installed it via virtual box without disturbing my system.
Just got android kitchen up and running, on prting sides of things got further this time, into aroma installes but error 7 which suggested earlyer is to do with mount points, if anyone could happen to help with theese it would be fab ))
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Click to expand...
Click to collapse
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
pradeepvizz said:
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
Click to expand...
Click to collapse
Murrda said:
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
Click to expand...
Click to collapse
heyy i could use some help doing this part in android kitchen. straight from android kitchens page but i can't seem to get the recovery.fstab out anyway! im on t6ul verson of the max by the way thanks
/HIDE (sorry dont know how to get this to work (forum noob here too)
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
hectorz321 said:
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
Click to expand...
Click to collapse
Good start mate! awesome!
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
hectorz321 said:
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
Click to expand...
Click to collapse
Which guide are you following? i just cooked a ROM today first time. I made the stock ROM for the T6UL.
---------- Post added at 08:34 PM ---------- Previous post was at 08:34 PM ----------
ooo, Merry Christmas everyone
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
HolyAngel said:
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
hectorz321 said:
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
Click to expand...
Click to collapse
Yeah, i know for the kernel, without being able to mess with the zimage, the sense max kernel lacks the init.environ.rc from gpe, the fstab file is different(at least file extension), and there's a few things that point to sense files or folders that don't exist on gpe. Currently there is no released source for the max yet :'( so unless someone knows how to do it manually and hasn't shared HOW to do so, I just have to wait.. Hopefully it won't be too long.
Sent from my HTC One using XDA Premium 4 mobile app

Odds, Ends, Tests - Update-August 12 2014

Okay so,
A there isn't much going on with tab 3 10.1 [p5210-specific] meaning extra-ROMular activity
I'm going to add this thread in the hopes it will spark some further creativity/participation.
As a scolding to the gimme gimme crowd - instead of demanding/expecting, try inquiring/learning/contributing.
This is my current boot/kernel image. Modified as follows;
Contains busybox [x86] in /sbin and set to --install -s /system/xbin via /sbin/antwerp.sh
This is NOT a flashable zip for a reason. dd is an incredibly kick-ass tool provided you respect it's authoritah.
I've been making changes by way of .rc,.prop files to make my experimenting easier, meaning less remount,rw
Read the info in zip for better description. I'm not certain I will actually be able to answer intensive questions.
I wiil do my best. When i succeed with a new test I will post. The ramdisk.gz is included.
Link DevHost - http://d-h.st/users/moonbutt74/?fld_id=37381#files
GT-P5210 stock recovery
Link DevHost - http://d-h.st/SLp
---------------------------
This is a transparented Modification of MultiWindowSidebar_v1.3_060614.apk from Thread by @zst123
Note- this modded apk must be dropped into /system/app perm-644
Thread http://forum.xda-developers.com/showthread.php?t=2729450
Link to modded apk DevHost - http://d-h.st/users/moonbutt74/?fld_id=37382#files
When I have more I will add.
note - i am attempting to sort out issues with cwm as it was abandoned by a very rude person.
as far as i can figure the problems seem to be maybe in init binary which is out of my league BUT,
i did manage to reduce my back up time to about 45 min on a moderately heavy rom by swapping
zImage with stock and striking kernel cmdline. any meaningful help/direction would be of benefit
to everyone.
m
----------------------------------------------------------------------
Update-Succeded building stock kernel
Will be posting useful device info for quick reference as I encounter need for it/them.
---------------------------------------------------------------------
UPDATE jULY 10 2014: this is what i hope to be a mostly correct device tree for
the samsung galaxy tab 3 10.1 GT-P5210 santos10wifi CM11
github - https://github.com/moonbutt74?tab=repositories
Thanks to @Angel_666 for his device tree for santos103g
---------------------------------------------------------------------
Useful Reading;
http://www.linux.org/threads/the-linux-kernel-android.5459/
Kernel Source KK 4.4.2
Kernel Source KK 4..4.2
Kernel source is up GT-P5210_EUR_KK_Opensource.zip
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=gt-p5210
UPDATE jULY 10 2014
hey,
so i've posted what i hope is a mostly correct device tree for samsung galaxy tab 3 10.1 GT-P5210 santos10wifi http://forum.xda-developers.com/showthread.php?t=2787136
as I encounter errors or omissions i wil attempt to resolve them in as timely a fashion as permissible.
any updates will be posted as extract and overwrite .tar.gz or .zip files unless there is a reason to diff/patch something.
either way, the updates if any will be labled clearly and contain readme.
thank you to @Angel_666 for his santos103g device tree which was my guide.
thank you for reading
m
NOTE- conversation/q&a related content have been relocated to split thread in q&a
http://forum.xda-developers.com/showthread.php?t=2812791
as to keep this thread focused. i apologize for any inconvenience and intend no slight
in anyway. thank you for your patience and understanding.
m
On booting Android 4.4
This comes by way of @Angel_666,
To boot Android 4.4
enable selinux in your kernel source - make menuconfig, goto security options, yes @ app-armor, yes @ nsa selinux, and set
Default Security Module to- Unix Discretionary Access Controls
Use modules that accompany this build.
adjust your init.*.rc's in accordance with Android 4.4, and at that basic level, you should be good.
add salt to taste.:good:
Something to play with GT-P5210
okay so here is a moderately succesful build through of cm11
i am just posting it for play value. there is no support or requests being accepted.
issues- no sound, no wifi, no video playback, some games will work - [gltron from fdroid is fun], external storage does not register, no bluetooth, you must move terminal.apk from system to sdcard and install as normal app. get a copy of total commander on your sdcard as well, trust me, much more manageable file manager. To poweroff or reboot you must type in terminal;
poweroff -f
or
reboot -f
make backup first. DUH.
will flash no problems with my philz recovery build.
Do not hassle me because of your user error. [no noobs]
Remember this is just to play with. However, a note to experienced people, if you resolve any of the issues
please share the solution with the community.
devhost link - http://d-h.st/01Q
please do not post questions in this thread. Goto q&a and post in the odds & ends thread there.
http://forum.xda-developers.com/showthread.php?t=2812791
have fun
m
and p5200 no hope ?
5200
khaledreno said:
and p5200 no hope ?
Click to expand...
Click to collapse
hi,
it's a variant so yes, hope, just work. :good:
m
Hey guys, anybody doing anything on this device at all? I would love to pick up development if someone can point me in the right direction as far as device tree and any needed files go, please let me know asap as I'm a decent Dev and just picked this device up
soupysoup said:
Hey guys, anybody doing anything on this device at all? I would love to pick up development if someone can point me in the right direction as far as device tree and any needed files go, please let me know asap as I'm a decent Dev and just picked this device up
Click to expand...
Click to collapse
soupy,
meant in the best way.
dude, search, read, especially the OP for this [my] thread.
c'mon.
m
We are closing this at the OP's request, and may be reopened when ready.

[PORT] [Q] Regarding ports, Base ROMs and whatnot

Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
b0taSs said:
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
Click to expand...
Click to collapse
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Ruben Craveiro said:
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Click to expand...
Click to collapse
And here I thought porting would be easier, but yeah, now that you mention that.. :silly:
Aw well, thanks mate :good:

Categories

Resources