[Q] Custom ROM developing - Android Software Development

Hi just asking if anyone knows any links or archives or anything i can read through, im looking to build my own ROM. any help would be much appreciated and dont mind donating to someone that can help me start to learn.
Thanks

Well, first of all you need to be able to compile Android. This is pretty easy and it's explained directly in the developers google website. If you're not running a Nexus One or a Nexus S, you can't actually compile a working android copy for your own phone "as is" from AOSP. Because of this, you firstly need to change / create some dirs and files in order to add the support for your particular device. I'd start searching on CM repositories for this (I've got the Nexus One and thus I don't have such problems).
After you've compiled Android for your device and your changes (for example root), you'll have some disk images (you can find them all under out/target/product/PHONE_MODEL/, they are the .img files). You can directly flash them via fastboot ("fastboot flash boot boot.img" etc.). You can though create an update.zip file, and this can be made extracting the system.img file in a folder. Remember that you'll have to recreate the symlinks (to toolbox and/or busybox if you want to include it in your build) and set permissions, as zip doesn't save the permissions of the files once compressed.
Thus so far, if you succeed making every single step you should have your ROM on your phone

Related

[GUIDE] All you need to know about the ramdisk of the kernel

WHAT'S IN THE RAMDISK
So anyone who has compiled a kernel (for the X8) or is about to step into the world of developing android awesomeness through kernel building, should know that there are 2 (two) parts to the kernel:
The kernel image compiled from source code, and
The ramdisk
Both are equally important and are inter-dependent; without the kernel, the ramdisk is nothing (unless of course the devs come up with any other use) and without the ramdisk, the kernel is incomplete (again, this may change in the near future).
You (XDA-ians as I like to call you guys), especially those in the X8 sub-forums must have read viper001's kernel building guide. If you haven't, and do not want to read just 4 posts because of your laziness, it tells you how to compile your kernel image. Hah, now you are almost dying to read it. Well go ahead, read it.
Done reading. Well if you followed that guide to the letter (which I am sure many of you haven't), you'll have compiled your kernel with the FXP ramdisk. Now you want to build it from another source. It's pretty much the same process. However the FXP ramdisk won't work with this kernel. Not a chance (maybe a little). You need the ramdisk so you unpack the kernel using DooMLorD's tool (and forget to thank him; go thank him right now) and see a folder named kernel.sin-unpacked. You open it and see a bunch of files that you've never even heard of. You drop the kernel-building project.
This guide will hopefully eradicate that fear, or ignorance (maybe), and cover up what's in the ramdisk.
The parent (or root) directory of the ramdisk folder itself contains a bunch of files and folsers, which also contain more files.
Let's look at the contents in the root directory:
1 “modules” folder – This one is pretty easy. It contains the kernel specific modules that are loaded up at boot.
2 “res” folder – This folder contains another folder named “images” which contains images to be used in the recovery (more on that later).
3 “sbin” folder – Inside this folder are about 200 files (may vary), most of which are responsible for basic functioning of the phone.
4 default.prop – This file contains only a few lines of code that allow adb to run (line 4) and also makes the kernel insecure to give us permanent root.
5 init – This program initializes elements of the android OS and looks at the two following files:
6 init.rc – This file contains generic initialization code
7 init.<machine_name>.rc – This file contains device-specific initialization code.
8 initlogo.rle – This is the bootlogo (not the bootanimation which comes with the ROM).
9 pre_hw_config.sh – This file is executed at boot to get settings like cpu freq and governors just right.
10 recovery.fstab – This file specifies how the different partitions and file systems are to be mounted.
11 ueventd.rc – This file sets user or group (or root?) permissions on /dev nodes. (I got this line from the Internet and have no idea myself what the hell this means o_0).
12 ueventd.goldfish.rc – This file is empty in our kernels. Dunno why, though.
Now for the files in the /res/images directory:
1 icon_clockwork.png – This is the background seen in CWM.
2 icon_error.png and icon_firmware_error.png – These images are displayed on the screen when there is an error. Not sure though as I have never encountered any such error before in my life.
3 icon_firmware_install.png and icon_installing.png – These images are displayed when installing anything via CWM.
4 indeterminateX.png (where X is a number from 1 to 6, both inclusive) – This is basically the animation of the progress bar (the grey stripes moving forwards, or backwards, or both).
5 progress_empty.png – This is the progress bar during the initial stages of flashing anything in CWM.
6 progress_fill.png – This is the progress bar fill.
These are the files in the /modules folder:
1 sdio.ko – This is a file related to WiFi.
2 tiwlan_drv.ko – This is the tiwlan WiFi driver module.
3 tiap_drv.ko – This is the tiap WiFi driver module.
4 x8uv.ko – This is the undervolting module.
5 synaptics_i2c_rmi4_no_dt.ko – This disables dual touch in Synaptics.
6 synaptics_i2c_rmi4_dt.ko – This enables dual touch in Synaptics.
NOTE: I am not an expert.
More to come soon. See you and I hope sincerely that I do not get banned for this.
THE DREADED SBIN DIRECTORY
Going into the /sbin directory, we see a lot of files, the names of each sending shivers down your spine. But fear not, for sgt. meow will help you understand the functions of some important ones:
1. adbd – The file that allows you to use the adb shell. “adbd” stands for “Android Debugging Bridge Daemon”.
2. bootlogo – This file starts the kernel bootlogo (according to some user on the androidcentral forum; just saw a snippet on google search, opened the page and there was no thread).
3. bootrec – This file basically tells a kernel how to boot up a recovery
4. busybox – It lets you run LINUX / UNIX based commands (ls, gzip, uname etc.) that are required for root-level tasks.
5. dmesg – It is the Linux kernel's own logging system and is similar to logcat.
6. fix_permissions – This file applies and fixes permissions on the Android data folders.
7. insmod – This file is basically what is executed when you type insmod /..../../../../ xxx.ko (or similar) to load up the modules. An alternative way to do this is to write the line in hw_config.sh of /system folder (I guess) to load up modules at every boot. Or you could place the modules in the /modules directory of the kernel.
8. killrecovery.sh – This file, as the name suggests, kills the recovery when you exit it and boots into Android.
9. nandroid – The file responsible for nandroid backups.
10. nandroid-md5.sh – This file generates MD5 checksums for nandroid backups to verify its integrity.
11. reboot – This file reboots the phone when prompted to.
12. recovery – This is the recovery binary. For our devices, it is CWM recovery. This file can be changed easily (what I did with oxydo ICS) to other recoveries for this device for that version of Android.
Most of the other files are LINUX / UNIX based commands and some are files the functions of which cannot be explained by me.
More to come soon. Hope you enjoyed it so far.
FILES YOU CAN EASILY EDIT IN THE RAMDISK
There are some files in the ramdisk that can be edited pretty easily. There are also other files editing which means you gotta be RD or gotta have similar talent. Let's not go into that for now. The easy ones are:
1. initlogo.rle - The file that is easiest to edit. Basically you can convert any image to .rle format and replace it. make sure it is the right resolution.
2. /sbin/recovery - You can use recovery from another kernel (for the same Android version)and replace it in yours. You can also compile your own recovery binary by issuing the make recovery command after a successful CM build.
3./sbin/bootrec - You may have to change this when you change the recovery. Just a simple copy paste, that's all.
4. /sbin/rec_input - This file may need changing too when you change recovery.
5. /res/images/.. - Every .png file in this directory can be easily changed to any other .png file. Just make sure the resolutions are right, or else you will not be able to navigate properly in recovery.
6. init.rc - This file is easily changeable but you need to know what you are doing, otherwise you may mess up the boot sequence.
You can have a shot at changing other files, too. Lemme know how it goes.
CREDITS:
1. Allah Almighty (yes I'm a Muslim)
2. All XDA-ians, especially those in the X8 sub-forum for help (and for pressing thanks)
3. The Internet (Google, Wikipedia and Github mostly) for info
4. Me, for spending hours behind this guide.
5. My family, for not disturbing me while I was doing this. LOL
thank you
that is what i'm trying to understand :good:
This is for sure a valuable thread. Thanks for this!!
Sent With My Brains To Yours. Duh.
Nice thread , Captain Meow Meow
Sent from my X8 using xda app-developers app
sbin will take some time to cover but i will try my best.
sgt. meow said:
sbin will take some time to cover but i will try my best.
Click to expand...
Click to collapse
Its good to see that you are working hard...
Keep it up
great thread.thanks
sent from my x8™ using gingerzaraki®
THREAD UPDATED WITH SBIN CONTENTS. OMG. :wink:
Dude, you should make an *updated* Kernel Building Guide with new sources (i.e. alfs kernel or nAa kernel). Old one still uses FXP kernel source and outdated toolchain instead of Linaro.
RohinZaraki said:
Dude, you should make an *updated* Kernel Building Guide with new sources (i.e. alfs kernel or nAa kernel). Old one still uses FXP kernel source and outdated toolchain instead of Linaro.
Click to expand...
Click to collapse
And link to your sources as an example for others..
Banned? And why? This is usefull =))
Sent from my E15i using xda premium
@Rohin
yeah I might
@Elmir
that was a joke
@all
THREAD UPDATED WITH FILES THAT CAN BE EDITED AND CREDITS. :BIG GRIN:

TF300TG Voice Calls enabled on 4.1.1 now 4.2.2 also

Hi Guys, I'm super stoked to post that I have just modded my stock ASUS TF300TG 4.1.1 to enable voice calls from the on board sim. Not VOIP, not Groove IP or SIP from the mobile number from the sim!!!
I was one of the unfortunate few who purchased this device in hast when it was on special. I was searching for an all-in-one unit. 7” was too small, single core wasn’t enough, no expandable memory, no thank you. I read that this device had at one stage using Hydro 4.4 firmware which enabled voice. So I knew it was possible. Even though people who reported it working stated that it only truly works via a Bluetooth headset, but that’s what I wanted anyways. Besides, who wants to have a 10” tablet to the side of their face while on the phone, people might think you’re mad.
What I didn’t know in my hast, was the sleepless nights that would follow by simply pressing OK to an ASUS update from 4.0.3 to 4.1.1 would cause.
Here are some facts I have learnt along the way.
NVFLASH is unit specific.
NVFLASH can be install on JB, but because of the above, can’t go back to ICS anyway unless to installed it while you were on ICS and made the files then.
Why go back, once you update to JB, ASUS enables signing which prevents you from installing HYDRO 4.4 or stock ICS anyway.
No one makes ROMS for TF300TG, sad news get over it. I had to. If they do, none enable the phone function, or disabled 3G all together or have reported nothing but issues when it was enabled.
My only option was then clear, make my only rom or mod to do it myself with stock 4.1.1.
This is what I have installed currently, any other variation has not been tested and I will not be held responsible for bricking your device if you wish to test this on your device!!!
I have stock ASUS WW_epad-10.4.3.9 firmware
I have rooted my device via the motochopper method
I have unlocked my bootloader via the official unlocker from ASUS v7
I have installed openrecovery-twrp-2.6.3.0-tf300tg-JB and BACKED UP EVERYTHING BEFORE PROCEEDED!!
I will not bore you will all the different ways I tried, how many soft bricks or hours I spent learning from knowing nothing about Android or cooking as this is my first android device. So here is what worked.
I can’t attach the TWRP update.zip of the end result until I reach 10 posts, but if I give you a fish, you’ll eat for a day, but if I teach you how to fish, you’ll eat for a lifetime.
Hunt down the following tools on your PC (WILL POST SOURCE LOCATIONS ONCE AGAIN WHEN I REACH 10 POSTS) (ALSO I KNOW THIS SHOULD BE IN THE DEV SECTION, CAN’T POST THERE UNTIL 10 POSTS EITHER) Please don’t ask:
FrameworkFlasher-MOD 1.1.4 to generate installable zips to push changes
Apktool to decompile and recompile apk packages
JAVA JDK 1.7
WinRAR
Notepad++ (regular notepad / wordpad might add artifacts to your file and “F” with things)
Install the following on your tablet, FX with the root explorer add-on both free
Using FX on your device copy the following file located under /system/framework/framework-res.apk to a USB device.
Copy into the folder of Apktool on your PC and run the following commands from the command line:
apktool.bat if framework-res.apk
apktool.bat d framework-res.apk
(keep command prompt open)
This will create a folder called "framework-res", navigate to that folder and open "framework-res\res\values\bools.xml”
In here you’ll find a line "config_voice_capable">false
Change false to true
Save file.
Rebuild the apk by running from the command line
apktool.bat b framework-res framework-res-new.apk
Here is a trick I learnt to overcome the countless soft-bricks which followed and disappointment of being stuck on the boot screen.
Open "framework-res-new.apk" with a program such as WinRAR and extract out the file called "resources.arsc".
Once that’s done open the original unmodified framework-res.apk with WinRAR and replace "resources.arsc" with the one you extracted from the last step. (make sure you keep a backup of the original framework-res.apk before modifying it a.k.a framework-res-orig.apk)
Now create the update.zip or push via abd
It is kind of just making the shell zip to copy your mod into as I created this from a previous attempt at enabling phone functionality.
Copy your original framework-res-orig.apk into the FrameworkFlasher-MOD\place-framework-res-here folder
Run the RunMe.bat file and select option 1, then 2, then 3 and then 4. Signing kills the file, but we have to, to create a shell update.zip
Go into the FrameworkFlasher-MOD\final-zip-file
There you’ll find your ~5MB update file. Open this via WinRAR and head to \system\framework.
Override the framework-res.apk file with the file we created with apktools.
Side note: rename the framework-res-orig.apk to framework-res.apk and create another update.zip with your original framework-res.apk file a.k.a framework-res-orig.apk and call it updatefix.zip. This is just in case this doesn't work for you, you can just use this to reinstall your original file back. Saved me time and from having to restore my device repeatedly.
Copy to your Device and install via TWRP.
Note I did a wipe of cache and Dalvik, but for some reason google play had issues. Stating that google play had stopped, and whenever I tried to install would be stuck at installing for what appears to be infinity.
As this device is only a few days old had nothing on it, so I did a factory reset and everything including voice calls started working correctly.
You have been warned!!
Now shop for a bluetooth headset and happy voice calls.
Happy days 10 posts reached. Attached are the update files for 10.6.2.10 stock ASUS rom. I don't have them for 4.1.1. Please backup your framework-res.apk file first and place it in the updatefix.zip file under system/framework just in case. Update via recover install from zip method. Wipe cache and Dalvik.
Updateshell.zip is just an empty zip that you can't then use to install other changes.
Update
NVFLASH appears to require people to update as close to the JB Bootloader as possible before NVFLASH will work correctly. A handful of people have reported issues when not running 10.6 JB bootloader.
Will update to 10.6 JB and create a backup of my device. Will then trail my patch again if not, will run through the NVFLASH process to go back to 10.4 JB.
Moving forward, I will slowly as far as time permits, to add more features to the stock rom for TF300TG enabling the phone and other enhancements. Will keep you all posted.
Upgrading from 10.4.3.9 to 10.6.2.10
For those of you worried about having JB 4.1.1 with TWRP 2.6.3.0 JB installed and wanting to update to 4.2.X but fear that because you have a custom recovery installed not sure how to upgrade. The easiest way is to use fastboot and download the latest firmware from ASUS.
As part of the blob you download from ASUS contains the bootloader, system, recovery and boot partitions. So it doesn't matter what version you are running, all the before mentioned with be updated with stock 4.2.
All you have to now remember is to reflash your TWRP with the 4.2 version.
I will upgrade shortly and then reflash my patch and confirm whether it works with 4.2. If so I with move onto adding some other useful mods.
Flashed to 10.6.2.10 broke everything
Updated to 10.6.2.10 via fastboot to the staging partition. The blue bar filled and the command ended. Issue a fastboot reboot to reboot device.
Flashed TWRP 2.6.3.0 4.2 but this never made it into recovery. Reverted back to TWRP 2.5.0 4.2 and all is well.
Tried to update the framework-res.apk which broke everything. Bootloop
Had to recompile via the same method above, but also failed stating invalid resource directory. Still haven't found a solution to completely recompile back to an APK. Was told to simply remove the affected folder and later add to the APK via WinRAR. Removing the folder allowed me to recompile, however as this is a Value folder which gets complied into resources.arsc so you can't add it later.
Flashed with the newly created 4.2.2 and phone function is enabled, but still am working on completely compiling the APK.
Heard it could also be a aapt.exe issue. Downloading the SDK 17 to recompile again.
It's been a day now and I haven't seen any side effects from deleting the values-mcc454-mnc-1 folder so that I can't compile the apk. Still haven't found a solution to the problem. Framework-res.apk appears to be version specific so you will really have to compile it yourself following the steps in my first post, otherwise you'll get stuck with a bootloop device.
Has anyone come across a: invalid resource directory name when recompiling 10.6.2.10 framework-res.apk? If so could you please post a working aapt.exe and which compiler you used.
Thanks in advance.
Built the frame-res.akp in full
Just an update, was able to fully compile the framework-res.apk file.
Was looking at it all wrong. The build process only failed at one directory. Looked at all other value folders and noticed that it was only this folder that had a mnc-1 where others had a mnc1, mnc7, mnc10 none had a -1 or other number. Corrected the folder to values-mcc454-mnc1 compiled correctly. Must be a glitch when decompiling.
Cooking the TF300TG
Started cooking my first rom, some tips so far.
Followed http://forum.xda-developers.com/showthread.php?t=1801690
To set up the kitchen. Step 1 only
Downloaded 10.6.2.10 from ASUS Extracted both zips, as in the zip within the zip
Used http://forum.xda-developers.com/showthread.php?t=1890912 on the blob file
BlobUnpack.exe blob
This gives you a number of files
blob.HEADER – Header stuff (ignore it)
blob.APP – system.img
blob.LNX – boot.img
blob.SOS – recovery.img (e.g. regular boot.img)
blob.EBT – bootloader.bin (ignore)
Rename each the matching.
Past the renamed files into the kitchen original_update
Setup working directory... TBA
Boy who cried wolf
Hmmm....it appears that I have hit another road block. I finally got my Bluetooth earpiece, paired the two, made a call and no sound....
After another night of trolling the forums found that all I have really done is tell android that this device is voice enabled, which simply allows you to access the phone app and that there could be a lot more I have yet to discover which could be stopping this from working.
Now I love all the comments people have made in regards to the fact that similar devices have been out for a while now and that people much smarter then you have been trying to crack what appears to be the 'Da Vinci code' over this time and that if they can't do it, then essentially it isn't going to happen.
But I also love one comment I came across "Hope dies last"
I have read an interest forum http://forum.xda-developers.com/showthread.php?t=2025377 all 46 pages of what appeared to be a group of very clever people trying to get the Nexus 7 3G to do the same. From my understanding of the forum is that they started out with a device which has what appears to be no telephony beyond data via 3G. AKA no SMS or MMS or voice. They managed to get SMS and MMS but never VOICE.
Why not stop there then? Well from what would appear to be to the more experienced devs here as a simply party trick on my part to change one Boolean value in the framework-res.apk file to true I have learned the following a parts from the fact that SMS and MMS worked out of the box, but also that by putting in my mobile phone sim into my voice capable enable device the following works:
The phone apps loads
I can dial and the call reaches the other mobile and displays my number
I can call my mobile number and my tablet rings
I can answer and hang up
So most of the underlying functionality appears to be active. What doesn't work:
When I answer, there is no sound from the tablet or Bluetooth
The people on the other end can't hear me from the tablet or Bluetooth.
Why did I cry wolf, well with all the functionality appeared to working, with someone claiming to have had this working only via Bluetooth already and another device apparently having it working via a similar method got me over excited.
The road block currently is the follow:
Software
Or hardware AKA the connection between the 3G and sound hardware is not linked, which I thought that having a Bluetooth device would overcome as my thinking was the following. Bluetooth would create it's own software sound device which will send the audio to the 3G via software bypassing the hardware, but I could be wrong in this way of thinking. When I have the Bluetooth paired, when I dial I hear that the Bluetooth device activates and dis-activates when I hang up, so the tablet is communicating and I suspect transmitting sound.
Or the biggest problem, IMEI is black listed by the courier, which I didn't think was the case as why would I be able to dial and connect to another number if I was blacklisted?
So it kind of leaves me to wonder if it's only really software, a link of profile missing in the Bluetooth stack, the my device has my headset listed as "Use for phone audio"
Moving forward I will get NVFLASH and the blob files created as I fear flashing anything I have created myself without a fail-safe way of getting my device back. Play a little with the build.prop file and retrace the step then ended with the forum I read to see if I am about to get any further as as far as I can tell it's more software at this stage.
Anyone could shed some light on this?
It's nice job bro.
I admire you
you try hard to challenge with this issue
I learn many thing from you
tnx
sadly it doesn't work
continue your job I believe on you and I proud to you
freak4916 said:
Hi Guys, I'm super stoked to post that I have just modded my stock ASUS TF300TG 4.1.1 to enable voice calls from the on board sim. Not VOIP, not Groove IP or SIP from the mobile number from the sim!!!
I was one of the unfortunate few who purchased this device in hast when it was on special. I was searching for an all-in-one unit. 7” was too small, single core wasn’t enough, no expandable memory, no thank you. I read that this device had at one stage using Hydro 4.4 firmware which enabled voice. So I knew it was possible. Even though people who reported it working stated that it only truly works via a Bluetooth headset, but that’s what I wanted anyways. Besides, who wants to have a 10” tablet to the side of their face while on the phone, people might think you’re mad.
What I didn’t know in my hast, was the sleepless nights that would follow by simply pressing OK to an ASUS update from 4.0.3 to 4.1.1 would cause.
Here are some facts I have learnt along the way.
NVFLASH is unit specific.
NVFLASH can be install on JB, but because of the above, can’t go back to ICS anyway unless to installed it while you were on ICS and made the files then.
Why go back, once you update to JB, ASUS enables signing which prevents you from installing HYDRO 4.4 or stock ICS anyway.
No one makes ROMS for TF300TG, sad news get over it. I had to. If they do, none enable the phone function, or disabled 3G all together or have reported nothing but issues when it was enabled.
My only option was then clear, make my only rom or mod to do it myself with stock 4.1.1.
This is what I have installed currently, any other variation has not been tested and I will not be held responsible for bricking your device if you wish to test this on your device!!!
I have stock ASUS WW_epad-10.4.3.9 firmware
I have rooted my device via the motochopper method
I have unlocked my bootloader via the official unlocker from ASUS v7
I have installed openrecovery-twrp-2.6.3.0-tf300tg-JB and BACKED UP EVERYTHING BEFORE PROCEEDED!!
I will not bore you will all the different ways I tried, how many soft bricks or hours I spent learning from knowing nothing about Android or cooking as this is my first android device. So here is what worked.
I can’t attach the TWRP update.zip of the end result until I reach 10 posts, but if I give you a fish, you’ll eat for a day, but if I teach you how to fish, you’ll eat for a lifetime.
Hunt down the following tools on your PC (WILL POST SOURCE LOCATIONS ONCE AGAIN WHEN I REACH 10 POSTS) (ALSO I KNOW THIS SHOULD BE IN THE DEV SECTION, CAN’T POST THERE UNTIL 10 POSTS EITHER) Please don’t ask:
FrameworkFlasher-MOD 1.1.4 to generate installable zips to push changes
Apktool to decompile and recompile apk packages
JAVA JDK 1.7
WinRAR
Notepad++ (regular notepad / wordpad might add artifacts to your file and “F” with things)
Install the following on your tablet, FX with the root explorer add-on both free
Using FX on your device copy the following file located under /system/framework/framework-res.apk to a USB device.
Copy into the folder of Apktool on your PC and run the following commands from the command line:
apktool.bat if framework-res.apk
apktool.bat d framework-res.apk
(keep command prompt open)
This will create a folder called "framework-res", navigate to that folder and open "framework-res\res\values\bools.xml”
In here you’ll find a line "config_voice_capable">false
Change false to true
Save file.
Rebuild the apk by running from the command line
apktool.bat b framework-res framework-res-new.apk
Here is a trick I learnt to overcome the countless soft-bricks which followed and disappointment of being stuck on the boot screen.
Open "framework-res-new.apk" with a program such as WinRAR and extract out the file called "resources.arsc".
Once that’s done open the original unmodified framework-res.apk with WinRAR and replace "resources.arsc" with the one you extracted from the last step. (make sure you keep a backup of the original framework-res.apk before modifying it a.k.a framework-res-orig.apk)
Now create the update.zip or push via abd
It is kind of just making the shell zip to copy your mod into as I created this from a previous attempt at enabling phone functionality.
Copy your original framework-res-orig.apk into the FrameworkFlasher-MOD\place-framework-res-here folder
Run the RunMe.bat file and select option 1, then 2, then 3 and then 4. Signing kills the file, but we have to, to create a shell update.zip
Go into the FrameworkFlasher-MOD\final-zip-file
There you’ll find your ~5MB update file. Open this via WinRAR and head to \system\framework.
Override the framework-res.apk file with the file we created with apktools.
Side note: rename the framework-res-orig.apk to framework-res.apk and create another update.zip with your original framework-res.apk file a.k.a framework-res-orig.apk and call it updatefix.zip. This is just in case this doesn't work for you, you can just use this to reinstall your original file back. Saved me time and from having to restore my device repeatedly.
Copy to your Device and install via TWRP.
Note I did a wipe of cache and Dalvik, but for some reason google play had issues. Stating that google play had stopped, and whenever I tried to install would be stuck at installing for what appears to be infinity.
As this device is only a few days old had nothing on it, so I did a factory reset and everything including voice calls started working correctly.
You have been warned!!
Now shop for a bluetooth headset and happy voice calls.
Happy days 10 posts reached. Attached are the update files for 10.6.2.10 stock ASUS rom. I don't have them for 4.1.1. Please backup your framework-res.apk file first and place it in the updatefix.zip file under system/framework just in case. Update via recover install from zip method. Wipe cache and Dalvik.
Updateshell.zip is just an empty zip that you can't then use to install other changes.
Click to expand...
Click to collapse
I was wondering, the update files you uploaded, are they simply run and go?
I installed the update file you provided. I do, indeed, have a dialer. I recieve incomming calls and can make them too. but no audio. I have a bluetooth headset, is there anything else I can try?
how can that mod be for 4.2.2 if the last version asus released was 4.2.1 asus rom 10.2.6.11 ?
edit:
[changes the framework-res.apk and did changes ,got telephone app but i always get connection problem]
edit2:
[phonecalls are working at first i tried a mmi code *100# now i will retry with a bt headset]
edit3:
[get no sound if i get a call or place a call the call connectes fine but i cant hear me even with a bt headset, im going to backup via twrp now and then make a factory reset maybe that will help]
edit4:
[im drunk and i can report that its not working indded you can place a call the call connects but you cant hear one word or speak tried to call to my nexus 4 from tablet and other way around]
Hi, I have tf300tg and I was wondering too if I can make voice calls. I will try it and make you feedback I hope. My tablet is rooted and I have tested android 5.1 (cyanogenmod) but there is no 3G support. I have returned original 4.2 and try voice call. Sorry for bad english.

Flashing Files Without Wiping System

Hey guys! This my first post on XDA, I'm a new member. I'm fluent with scripting and general OS. I hear often the phrase of a dirty flash, which I'm understanding to be flashing a new ROM without wiping the system first. I assume that may include not wiping the data partition as well. It's my understanding that is accomplished by editing the updater script within the ROM to be flashed. I understand that can easily be accomplished by unzipping file, making edits and then zipping back up. It's my understanding that can be accomplished without unzipping the entire ROM, by editing the contents in place using a PC and even with some native Android apps. relative to Android app that does one that does that extremely well, I'd appreciate that feedback is one point of this post. What I'm looking for is a way to zip the existing flash file into a new flashable ROM with a pre-built script that in essence calls the previous lines of the script and executes the code sequentially, while watching for the "delete" entries for partition like system or data and avoid executing those lines of code. My main purpose would be to avoid having to save two copies of a ROM on my sd card, one that wipes and one that doesn't, for purposes of space. Additional info. I'm currently using safestrap on a Samsung, I am not asking about aroma or a kitchen solution as they are not compatible but standard update.zip scripting type code. this seems easy with standard shell commands, but I must move out how that would relate back to the update.zip commands available. it may not be possible, and/or there may be a simpler solution I have not heard of otherwise. What is the standard practice for other people wanting to do a dirty flash on a ROM that they've downloaded that white partitions by default?

New file_contexts.bin format and make_ext4fs

Trying to alter a stock ROM and resign with my own custom key just for myself. This process will allow me to use a device with custom changes (NOT root), but still allow me to use Android Pay.
This process involves using the "make_ext4fs" tool. However, this tool (as far as I can tell) requires using the old plaintext version of "file_contexts". Android 7+ uses a new binary version of this file instead ("file_contexts.bin").
So if anyone can solve either of these questions, I would be very grateful:
1) Is there a tool to convert my device's binary "file_contexts.bin" to the old plaintext "file_contexts"? -OR-
2) Is there a build of "make_ext4fs" that accepts the new binary format "file_contexts.bin"? I tried to build the new nougat version myself from AOSP, but after a successful build of the tool, I can't get the thing to read files on either 64-bit or 32-bit systems. It yields an error "No such file or directory" when trying to point to file_contexts. I am not a great C developer, so I don't know if I built it wrong. For reference, no, I am not missing the lib32stdc++6 libraries. I have attached the binary if you want to see if you can get it to work. -OR-
3) If anyone has the file_contexts text file for the OnePlus 3, ROM version 7.X Nougat, that would work too!​
Any help anyone can offer in any way would be fantastic! Thank you so much for your time to look at this!
A good question
1) yes, see my signature
munjeni said:
1) yes, see my signature
Click to expand...
Click to collapse
I'm trying to do the same with a 7.1.1. rom. I convert the file_contexts.bin to file_contexts, unpack the rom, do the modifications to the rom, repack the rom then replace the original system.new.dat and system.transfer.list with the newly packed ones (original file_contexts.bin is still in the original zip) and when I go to flash it in TWRP it doesn't flash the system and I get a No OS installed Is there something I have to do to the file_contexts.bin after I repack the system.new.dat?
"file_contexts.bin" to the old plaintext "file_contexts" tool: http://blog.cofface.com/archives/2255.html
puargs said:
I tried to build the new nougat version myself from AOSP, but after a successful build of the tool, I can't get the thing to read files on either 64-bit or 32-bit systems. It yields an error "No such file or directory" when trying to point to file_contexts. I am not a great C developer, so I don't know if I built it wrong. For reference, no, I am not missing the lib32stdc++6 libraries.
Click to expand...
Click to collapse
Try building with the pie (Position Independent Executable) flag. Had this exact same problem when trying to compile a CVE for android.
Hopefully this should work for you and sorry for the Necro post

[VK810] Archive of Files (Stock, Programs, Recovery, Root)

This thread is meant to help share programs and older files that have gone missing or have dead links and to collect everything in one place. I came here a long time ago to ask a few questions, but now I would like to return the favor by organizing everything so owners of the VK810 don't have to run around looking for everything.
One of the most common files I see asked for is TWRP 2.7.0.1. I still have my old copy and have uploaded it to Android File Hosts. The link is located below at the very bottom. In that link, I also include a stock rom in case anyone wants to start over along with the tools to do so. Other TWRP versions are also included. I also include some other programs as well, but they are mostly meant to act as a backup in case other links go down. Just to clarify, they are not my own. I just want to make sure everyone gets what they need. If there is anything I forgot to give credit for, I will add it as I remember or let me know so I can properly give the credit.
I don't want to take credit for anything here. I just want to help people have an easy time with setting up their device, but I will give out credit where needed.
For people starting out, roirraW "edor" ehT has made an extensive tutorial for the VK810. His roms work with LTE if you need it.
https://forum.xda-developers.com/lg-g-pad-83/general/vk810-4g-reliable-to-root-install-t3283027
Since his Android File Host page is still working and he is still very active, I won't archive any of his work. Get everything you need from his pages.
For anyone that wants to return to stock, ttn1185 has a very simple guide on return to root along with the stock rom, but the link to the guide doesn't seem to work.
https://forum.xda-developers.com/lg-g-pad-83/general/vk810-verizon-lg-g-pad-8-3-to-stock-t2800857
To save time, I have included the guide I used and the link to the guide for returning to stock below. Credit goes to hyelton for creating it.
https://forum.xda-developers.com/showthread.php?t=2432476
Magendanz has been making new TWRP builds for the VK810. I included one of his older builds in my archive since it helped me out a lot.
https://forum.xda-developers.com/lg-g-pad-83/general/vk810-twrp-3-1-1-0-unofficial-t3691551
One way I managed to install it was to flash my recovery to version 2.8.7.0, run the recovery, flash the image using TWRP, and then restart. There are easier methods, but I used this one since it doesn't rely on using ADB or setting it up if you don't have it already.
Drgravy originally had the important TWRP 2.7.0.1, but his link to it is dead. The instructions for it are still relevant.
https://forum.xda-developers.com/showthread.php?t=2726707
For those that don't want to use ADB, you can copy the contents of the files to a folder you have easy access to, download/run a terminal emulator of your choice on the device, change directory to where the lok and flash files are, and use the cp command in place of push to copy the contents to the specified folders. Other than that, the other commands in the instructions are the same and can be followed verbatim. I believe it is easier or required to have root first to do this, so run Stump to root the device before doing this. It is also included in the link.
For people that do not need LTE, invisiblek has created a rom of Lineage 14.1 to work with the device. It is what I am currently using right now. While invisiblek gets credit for creating the rom, I give credit to thunderbolt128 for introducing it to me. He has simple instructions on how to install it and has a link to download the rom included in the post.
https://forum.xda-developers.com/lg-g-pad-83/general/vk810-invisibleks-lineage-14-1-rom-t3806903
I flashed pico gapps (ARM) when I was flashing the rom in recovery, but use whichever gapps (or none) that you are comfortable with.
Finally, here is my page with all of the files I mentioned before.
https://www.androidfilehost.com/?w=files&flid=278786
Again, I do not take credit for anything in here other than organizing it. I do hope it helps you a lot like it did for me.

Categories

Resources