Related
Hi guys,
Is it possible to change the kernel of a nand build at all?
I am an Extended Battery user and find only NAND builds with Hastarins kernel work at all..
Is there a way of mixing and matching Kernels with builds?
Ta
nutmegy said:
Hi guys,
Is it possible to change the kernel of a nand build at all?
I am an Extended Battery user and find only NAND builds with Hastarins kernel work at all..
Is there a way of mixing and matching Kernels with builds?
Ta
Click to expand...
Click to collapse
Yes
Just made something for you, note: haven't tested it:
Kernel Theiving
How to:
- Install Nand version which has the kernel you want.
- Run "extract_kernel.bat"
- Install Nand version you like, and want to keep.
- Run "install_kernel.bat".
- Et voila!
Now, you only have to use "install_kernel.bat" if you flash another rom.
Note: You need adb installed on your PC
Quickie on how to install adb:
Moon2 said:
You need adb:
-Get this installer: http://developer.android.com/sdk/index.html
-Go to Available Packages, Expand Third Party - Google - select USB Driver
-Update adb driver, if not already installed from: C:\Program Files\Android\android-sdk-windows\google-usb_driver
-Copy "adb.exe" and "AdbWinApi.dll" from "C:\Program Files\Android\android-sdk-windows\platform-tools" to "C:\Windows\System32".
-Run the batch file.
Click to expand...
Click to collapse
thank you very much!
I will give this a go!
Moon2 said:
Yes
Just made something for you, note: haven't tested it:
Kernel Theiving
How to:
- Install Nand version which has the kernel you want.
- Run "extract_kernel.bat"
- Install Nand version you like, and want to keep.
- Run "install_kernel.bat".
- Et voila!
Now, you only have to use "install_kernel.bat" if you flash another rom.
Note: You need adb installed on your PC
Quickie on how to install adb:
Click to expand...
Click to collapse
I read the batch file and
you have created a folder called boot under data folder and pasted the zimage
so everytime when we boot out Hd2s it going to replace the zimage with the one in boot folder, so i guess its going to delay the booting process (correct me if im wrong) so is it possible to delete that folder after booting our Leos?
agarp said:
I read the batch file and
you have created a folder called boot under data folder and pasted the zimage
so everytime when we boot out Hd2s it going to replace the zimage with the one in boot folder, so i guess its going to delay the booting process (correct me if im wrong) so is it possible to delete that folder after booting our Leos?
Click to expand...
Click to collapse
No, that's not what it does. it mounts the boot partition temporarily to /data/boot, and after it's mounted, adb copies over the zImage file, and overwrites the preexisting kernel image, after this, the partition is unmounted. So it's not repeated at each boot.
works a treat...
I just used Android commander..
made sure it was connected..
then ran the extract batch file
installed the nand build i wanted...
then ran the install Kernel.bat
and it works a treat!!!!
Moon2 said:
No, that's not what it does. it mounts the boot partition temporarily to /data/boot, and after it's mounted, adb copies over the zImage file, and overwrites the preexisting kernel image, after this, the partition is unmounted. So it's not repeated at each boot.
Click to expand...
Click to collapse
thnxx for the clarification, now i get it
nutmegy said:
works a treat...
I just used Android commander..
made sure it was connected..
then ran the extract batch file
installed the nand build i wanted...
then ran the install Kernel.bat
and it works a treat!!!!
Click to expand...
Click to collapse
Is all that done on the phone? It seems you installed the kernel on the phone somehow. I'm clueless about adb, I tried to use it before but was dumbfounded by it all.
Do I need Eclipse? Downloading the SDK stuff...installing JDA SE and it talks about Eclipse.
Moon2 the links dead it says file has been removed anybody re upload it????
.
This will not be the prettiest post until I have most of the bulk written out. Over time I will refine and improve, but for now I need to get it on paper.
-= READ THIS =-
-= I am not responsible for bricked devices. I know what I am doing when it comes to porting, and am giving you exact details on how to port. These methods have a very small chance of bricking, but if anything happens and you come crying to me, I will laugh at you. Follow this thread carefully and you will have little to no issues. =-
Before we begin, the most important part of android developing is to have Ubuntu (or preferred linux distro) installed on either a separate machine, or dual boot in windows. Most scripts that aid in developing can only be run under linux. A simple installer for dual booting Ubuntu/windows can be found here: http://www.ubuntu.com/download/ubuntu/windows-installer.
You also NEED adb installed, along with necessary Nexus S drivers, and have a basic knowledge of adb commands (I will cover a few). (You will need to install the Android SDK and download the platform-tools addon. This is where adb is located. There are guides online telling how to download these. If you need help, ask and I will include in the OP.) I dual boot Windows and Ubuntu, so I have my adb commands installed on my windows partition. This probably isn't the best way to do it, feel free to install adb under whichever OS you prefer. For this guide, I will be referring to using adb under Windows 7. The most common command needed while porting is simple:
adb logcat
Write this down somewhere if you cannot remember it. I have typed this command over 5000 times, it is used to debug system errors (bootloops, rom not booting, apps not working, etc).
I will also be referring to the "Android Kitchen" throughout this guide, mainly when working with boot.img's. In order to understand it more thoroughly, spend some time reading the first page. Link to Android Kitchen is below.
-= Useful Links =-
Be thankful, I saved you the time of googling
Nexus S adb drivers
Android Kitchen
Android SDK
7zip
Click to expand...
Click to collapse
-= Basics =-
The normal Android ROM consists of 3 main parts;
Boot.img – This is where the kernel and ramdisk are compressed. The ramdisk is what initiates the ROM’s main functions, such as Bluetooth, Wifi, and network connectivity information. The main file to pay attention to while porting is in the ramdisk, called the init.rc. It is a simple text file, and can be editied according to the ROM. A “how to” on unpacking/editing/repacking this file will be later in the guide.
System Folder – This folder contains all of the libs, configuration files, apps, and everything else that is the ROM itself. In this folder is where most of the changes are made, since most libs/framework pieces are device specific. This folder is the main cause of bootloops, and non-booting ports. I will try to explain most of my knowledge on what libs control what part of the phone. Almost all of the fixes for camera, sound, wifi, etc will be made somewhere within this folder. Unzip a ROM and dig around this folder for a bit, understand what folder contains what files, they are somewhat self-explanatory (Apps, framework, libs). This folder will become your best friend, learn to love it.
META-INF Folder – This folder holds all of the initial installer scripts; such as when you flash the ROM in a custom recovery. It is what tells your phone to install the ROM and what files to install. This script controls mount points, important system links, and in some occasions special commands. You can also edit this file to include any custom text you want users to see while flashing your rom. This file is device specific, and should ALWAYS be replaced when porting. Flashing a ROM with the wrong updater-script can either:
a) Corrupt partitions
b) Abort Installation (very frustrating with large ROM’s)
c) Rare occasion, brick your device
Bottom line is, pay very close attention to what exactly is in your custom built ROM before you flash it.
I decided this will be a good preface post. Read here for basic information you need to know BEFORE porting.
Here We GO
In order to port ROM's to the Nexus S, you will need a "base" to pull your files from. In order to port a ROM to the Nexus S, we will need a Nexus S ROM to start with, hence the "base". This base is normally CM7 or Stock Gingerbread, and can also be CM9 - Stock ICS. The base you pull from needs to match with the version of ROM you are porting.
1) Is the ROM I'm porting Ice Cream Sandwhich, or Gingerbread?
-This is very important. Most files are incompatible between versions, so make sure you know for sure, which version your port is going to be.
a) If the ROM you are trying to port is based on Gingerbread, download this ROM as a base to pull from (device specific):
CM7 GSM
CM7 4G
b) If the ROM you are trying to port is based on Ice Cream Sandwhich, Download this ROM as a base to pull from (device specific):
IMM76D GSM
IMM76D 4G
Click to expand...
Click to collapse
2) Download the ROM you are going to port. Place this ROM on your desktop, along with the matching base.
3) Unzip both ROM's (port, and base) using preferred archive utility. Extracted ROM's will be in folders with matching name of the zip, DO NOT mix these up; be very organized with your base and the ROM you are porting.
4) Take a look in your newly unzipped ROM's, they should look exactly as I explained in the first post. We will be starting with the System folder of the ROM you are porting, replacing our needed files.
4a) Click into the System folder; you will see many folders inside. The first one we start with is the lib folder. Click inside; you will now be in the directory /system/lib
4b) In this directory is where all of the libs are located; these are crucial to the ROM. Replacing these without knowing what you are doing will result in a ROM that will not boot.
4c) At the top, you will notice 5 main folders; bluez-plugin, egl, hw, modules, soundfx. The ones that we care about are egl and hw. The egl folder contains the graphics drivers for the specific device, and the hw controls lights, gps, and other hardware features. In the ROM you are porting, delete both of these folders. (egl and hw)
4d) At this point, navigate to your base ROM (Nexus S ROM). Select both the egl and hw folders, and drag them to the lib folder of the current ROM you are porting. Your lib folder will now contain 5 folders again. Moving on.
4e) Navigate to your base ROM folder, into /system/lib again. Select these libs and drag-drop into your current ROM you are porting (this step varies between ICS and GB);
-= Gingerbread =-
-libaudio.so
-libaudiopolicy.so } these libs control audio
-libaudioflinger.so
-libril.so
-libsecril-client.so } these libs control network
-libreference-ril.so
-libs3cjpeg.so
-libFLAC.so } these libs are required for media
-= ICS =-
-libaudioflinger.so (may cause issues with booting in some ports)
-libaudioutils.so } once again, these libs are for audio
-libtinyalsa.so
-libril.so
-libsecril-client.so } these libs control network
-libreference-ril.so
-libs3cjpeg.so
That should be it for the lib folder for now. Exit /system/lib, and return to the main branch of the system folder /system.
Click to expand...
Click to collapse
5) Once we are back into the root of the system folder (/system), observe the two folders towards the bottom; usr and vendor.
usr - contains files that relate to touchscreen, softkeys, keyboard, and other hardware buttons.
vendor - mostly nexus specific, contains additional network libs, graphics, hw, and extra configuration files.
5a) In the ROM you are porting, delete both of these folders. They are of no use, since they are specific to devices.
5b) Copy both the usr and vendor folders from your base ROM, to the current port's system folder. As you can see, there is a lot of copy and paste from our Nexus ROMS to the ports, although we keep the important folders that pertain to the ROM itself.
Click to expand...
Click to collapse
6) Navigate back to the /system folder. You should see a folder named etc. Click into it.
6a) The etc folder is a wonderful place; it is one of the most used folders in the ROM. Observe a few of the folders inside. In our base ROM, you will see a few folders that are pretty self explanatory (wifi, permissions, init.d)
TO BE CONTINUED - I'M TIRED AND HAVE TEST ALL DAY TOMORROW AND WEDENSDAY. I WILL UPDATE WHEN I FIND TIME IN BETWEEN
and also this one. Just in case.
I like this already
Sent from my tweaked aosp Sensation
Swamp spreading your knowledge is 10x more beneficial to the community than releasing a ROM. Thanks man.
Sent from my Nexus S 4G using Tapatalk 2
dreamsforgotten said:
Swamp spreading your knowledge is 10x more beneficial to the community than releasing a ROM. Thanks man.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
+1 on the fishing lessons. Goblin your contribution is appreciated.
You without me is like Harold Melvin without the Blue Notes....
Thanks for this. Will attempt working on some of your ROMs like the Epic Touch one.
Sent from my Nexus S 4G using xda premium
This needs a kick
Sent from my Sensation using XDA
great start, can't wait to read the rest!
I've been super busy this last week, had no time for anything really. I'll finish writing this up, there are so many parts that need to be covered, I guess "simple porting" isn't all that simple to explain
I am just impatient to get this entire guide!! Thanks you
I will take my pain with patience.. haha..
waiting for the second part!!
Looking forward to the rest of the guide! Much appreciated swamp!
I will be following this thread closely. I haven't so much as coded a hello world in years but once this guide is complete, it may serve as the segue to get me started again. Waiting with baited breath.
Does this guide work with any rom port? Or is this Nexus S specific?
sivarticus85 said:
Does this guide work with any rom port? Or is this Nexus S specific?
Click to expand...
Click to collapse
I was actually going to add this to the op. The files I have included are nexus specific, but the actual process should work on tons of other devices.. There are a few areas that are nexus specific, such as build.prop edits and vendor folder, but other than that you should be able to follow this for other devices.
Or do you mean nexus s roms? This guide is kind of general porting; more of the basics. With htc sense and fancy roms like that, there will be more edits that need to be done, etc.
swamp goblin said:
I was actually going to add this to the op. The files I have included are nexus specific, but the actual process should work on tons of other devices.. There are a few areas that are nexus specific, such as build.prop edits and vendor folder, but other than that you should be able to follow this for other devices.
Or do you mean nexus s roms? This guide is kind of general porting; more of the basics. With htc sense and fancy roms like that, there will be more edits that need to be done, etc.
Click to expand...
Click to collapse
Well I own a Photon, another member pointed me here because I wanna learn how to port. My intention is to port HTC Sense to it, and learn something new in the process. I'm using the Photon-specific CM7 as a base, and the Energy Rom from the Sensation as my rom port. Since both run GB and are qHD devices, I figured these would be good starting points.
Thank you very much for your guide.
sivarticus85 said:
Well I own a Photon, another member pointed me here because I wanna learn how to port. My intention is to port HTC Sense to it, and learn something new in the process. I'm using the Photon-specific CM7 as a base, and the Energy Rom from the Sensation as my rom port. Since both run GB and are qHD devices, I figured these would be good starting points.
Click to expand...
Click to collapse
Yeah, you're set up perfectly. I am pretty sure you could follow this guide, although there may be some photon specific libs that have to be added..
swamp goblin said:
Yeah, you're set up perfectly. I am pretty sure you could follow this guide, although there may be some photon specific libs that have to be added..
Click to expand...
Click to collapse
Ok cool. I'm pretty sure it'll be a while before I ever get this port running, so in the meantime I'll be brushing up on what makes my phone tick, and for you to finish your little guide here.
I knew my EVO inside and out almost, so I'm hoping the Photon is easy to learn too. The file system for both is pretty similar, with the exception of Sense-specific files of course.
How to Make Your Own Custom Rom
Click to expand...
Click to collapse
Part 1 : Setting Up Dsixda's Android Kitchen.
So, Do you want to make a custom rom or, mod one that is made already? If your answer to this question is yes then you are at the right place. In this article I will help you get started with setting up an environment to make your own custom roms or edit the ones that are developed already. We are going to take help of dsixda's Android Kitchen Utility to help us in this task and in this article I am going to help you get started by guiding you through the installation process of Android Kitchen on your Personal Computer. So, you might have the question in your mind what exactly is Android Kitchen and what does it do and whom it is for? Continue reading to know all this as well as to get instructions on setting it up on your PC.
What is Dsixda's Android Kitchen?
Who is this kitchen for?
-Those who are brand new to creating custom ROMs and want an easy place to start learning
-Those who just want to modify shipped ROMs or someone else's custom ROMs to their liking
-Those who are confused by all those scripts and complex commands required for building and extracting
Please note:
-The kitchen will not automatically turn you into a developer. A developer is someone who writes code or builds something from the ground up and understands exactly what goes on behind the scenes. The kitchen hides all that and puts a user-friendly interface above it. However, this may be the push that gets you into development in the future.
My goal is to give you the tools to make your life easier and save you lots of time, and at the same time help you learn about the Android OS.
A little bit of prior UNIX command-line knowledge would be useful to get started with the kitchen, but the help guides should be enough for a newbie. Knowledge of command lines is always important if you ever want to get involved in Android or development.
Code:
===========================================================
Android Kitchen - by dsixda (xda-developers.com)
===========================================================
Main Menu
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
x. Exit
How To Install Kitchen?
1. Install latest Java JDK. It's pretty simple just follow the instructions and you are done.
2. Download and Extract Cygwin Packages and Android Kitchen on your desktop or somewhere easy to
access.
3. Once extracted go through kitchen_readme.txt and you will get an overview of how to setup the
kitchen.
4. To begin, install Cygwin first. So, run setup.exe from the extracted files and go through the installation
process.
5. Run Cygwin.exe once and it will create a folder with your username on /home/ directory.
6. Navigate to the folder where you installed Cygwin and go inside .../ home// folder.
7. Copy the extracted kitchen folder to this location.
8. Once copied, rename it to kitchen (type all letters in lower case for Linux is case sensitive).
9. Run Cygwin.exe and navigate to kitchen folder. for that simply type the command cd kitchen and press Enter
10. Once inside kitchen folder, type ./ menu to run android kitchen. Note: if you get a permission denied error then type chmod +x menu or chmod 777 menu in Cygwin command line utility first and then only run the command ./menu .
11. You will be presented with the Android Kitchen menu seen above. Use these options and get started. That's all. You have successfully installed android kitchen on your PC. Though this is originally meant for only HTC based roms some of it's features will come handy for modding Samsung Roms too. Please note that because of the same reason all the functions/features of Android Kitchen may not work for you.
Wow. Why did you copy and create a new thread and paste it? Why? Don't we have enough spam already?
EDIT: I don't see the point of this. Couldn't just share a link to the thread?
Interesting.
Thanks!
Sent from my Xperia™ PLAY using TapatalkHD
Lol. Nah, I think I will just stick with good ol' Linux and good ol' terminal and gedit (the proper way )
Sent from my E15i using XDA
Aha!!!
This is what i need... Great! Thankx
Nice info
Creating Custom ROM For Xperia 2011 Device
SatrioDwiPrabowo said:
Nice info
Click to expand...
Click to collapse
Is there any guide how to make custom rom for 2011 device like : Xperia Ray .. ???
engkozhe said:
Is there any guide how to make custom rom for 2011 device like : Xperia Ray .. ???
Click to expand...
Click to collapse
Use dsixda for basic tools rest you do whatever you want theme it add scripts do whatever you want !
Sent from my HTC Explorer A310e using xda premium
Ok. Tnx
Sent from my ST18i using xda app-developers app
I got stuck on services.odex n i cant get the classes.dex file, how can i deodex. Odex n put it on jar file? Tnx
ST18 with custom kernel
engkozhe said:
I got stuck on services.odex n i cant get the classes.dex file, how can i deodex. Odex n put it on jar file? Tnx
ST18 with custom kernel
Click to expand...
Click to collapse
To deodex ROMs use the option in Kitchen for it!
Sent from my HTC Explorer A310e using xda premium
Oh... One more question, can we put apk directly to system folder on cygwin? And how do you create credit on updater script?? Thank you
Sent from my ST18i using xda app-developers app
engkozhe said:
Oh... One more question, can we put apk directly to system folder on cygwin? And how do you create credit on updater script?? Thank you
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
You can add apps in /system/app or /data/app
But if you add in data you will have to create appropriate lines in updater script!
Sent from my HTC Explorer A310e using xda premium
Interesting.
...
updated
Did you Ever Wanted your Own Custom ROM? Did you don't understand other Guides? Do you don't Like ROM Kitchens? Than this Guide is the right Guide for you! Just Try It and you can create your Own Custom ROM!
General Information
So, Before we start with this Guide, i just want to tell you some General Informations about [highlight]Custom Roms[/highlight]. When you buy your phone, you will have a [highlight]Stock ROM [/highlight]installed. A [highlight]Stock ROM [/highlight] is just that Software, your Company has created, especially for your phone. It's a Software like Android 2.3.4 with Touchwiz 4 or Android 4.0.4 with Sony UI. Those Softwares may be good, but there are many Things to Improve, for the Best Xperience, while using your Phone. A [highlight]Custom ROM [/highlight]can be complete different to [highlight]Stock ROM [/highlight], like [highlight]Cyanogenmod 10 [/highlight], or be just a improved Version of the [highlight]Stock ROM [/highlight]. To Build a [highlight]Custom ROM [/highlight] you need to know a few Words, and have a Phone with Root Acess + S-OFF / Unlocked Bootloader. So in this Guide we will concentrate on the Easy Way, the [highlight]Improved Stock ROM [/highlight]. You Can also Build a [highlight]ROM [/highlight] out of Source from Google, but thats too complicated for beginners. Setting up compile envirment can be quite complicated . So let's take a look at stuff you need to know:
[highlight]Root Acess[/highlight]
Complete Acess to all System Files, like Administrator on Windows. To Root Your Phone, search XDA. Rooting your Phone is done by putting su library to /system and manage acess with SuperSu or Superuser. When you buy your Phone, it doesn't have Root Acess. Root Acess is needed for installing CWM, mount your /system as Read & Writeable ----> You can delete system files, and installing apps to /system/app, by copying them to /system/app. By Rooting your Phone you loose Warranty, but you can reinstall stock software and no one will notice
[highlight]ClockWorkMod Recovery (CWM)[/highlight]
Recovery Mode of your Phone. In Recovery you can install flashable zips and roms, wipe and format your device, mount different partititons and fix permissions... To Get CWM search XDA. There are different Ways for every Device. You can enter recovery before your device is fully booted, and since touchscreen drivers are not yet available you need to use the volume buttons for controlling the recovery. There are different ways of entering cwm for every device.
[highlight]Rom & Kernel[/highlight]
ROM means: [highlight] Read-Only-Memory[/highlight] . The Funny Thing is that we can Read and Write on our Read-Only-Memory. Anyway, its a partition which includes large parts of the OS ----> operating system of your Phone. In a [highlight]ROM[/highlight] for Android Phones are included apps, framework, libs & many more and since android is modular, there is an app for everything (keyboard, launcher, statusbar). Together with a [highlight]Kernel[/highlight] it's the "Life" of your Phone.
The Kernel is needed for a working Phone. You Can Install Stock or Custom Kernel. When you buy a Phone Stock Kernel is preinstalled of course. The kernel includes many drivers, controlls the cpu and does many more... Just rember that word
General Information
1. Install Stock ROM to your Phone - This Can be Done by Flashing via Flashtool or Odin. You Need a Clean Base to Start. Recomnend is a Stable, Official ROM, like Gingerbread, Ice Cream Sandwich or maybe Jelly Bean.
2. Root the ROM. This Can be done with Different Tools, Very Popular is for Example SuperOneClick Tool.
Just search for "my device name root" in xda if your not sure
3. Improve Stock ROM on Your Phone. So, After You Have Installed the Stock ROM and Rooted the ROM You Can Start. Now You Need To Change Some Things, To Make the Stock ROM to a Customized ROM. You Can do a lot Things, Here are a Few Examples:
- Install Latest Superuser SuperUser
- Install Latest BusyBox Auto-Installer
- Supercharge the ROM, enable Zipalign etc.. ----> here
- Remove Bloatware. Use Es File Explorer to remove not longer needed apps in system/app partitition
- Tweak Build.prop by going with ES File Explorer to /system and editing your build.prop. now you can change the Name shown in Settings and do a lot more ----> http://forum.xda-developers.com/showthread.php?t=1227269
- Change the Bootanimation. You can find a lot of them by Going to themes and apps of your own device.
- Add or Change Apps. Check out Themes and Apps Selection of Your Device and Install a few Of Them, If You Are Allowed to use MooDeD Apps created by other Users
3.1 Now Delete/remove all backups in clockworkmod/backup folder
4. Now Make Sure You Have Installed CWM. If You Have Changed a Lot Things and You Think Your ROM is good enough, Boot to CWM, select wipe data/factory reset and Boot up again. If You Are Still able to Boot, Check the ROM for Bugs or Problems. Write them Down. Try to fix them. You can always take a logcat (adb logcat)
Than Boot again to CWM select wipe data / Factory reset ---> yes advanced ---> wipe battery stats ---> yes. Now Select backup & Restore ---> Backup.
5. Connect Your sd card to PC and go to Clockworkmod/backup folder. Now Go to the only 1 backup folder and copy "system.img" to your PC.
6. On PC Open Yaffey and Choose Open ---> system.img and than extract to empty folder called system.
7. Now You Will Get a Folder "system" which contains the System of your Phone. Now Create an Empty .zip file and paste in extracted Meta-inf folder Download and copy folder "system" inside. ROM should be flashable for NOW!
Remeber to mount /system before flashing // replace with mount Script for ur device... You can check this by dowoading any rom 4 ur device
NOTE: This has nothing to do with developmemt or original development in any way. Its theming a stock ROM in the simplest way...
Just Press thanks if this was helpfull in any way...
How to
[[ Placeholder ]]
[[ Placeholder ]]
[!][RESERVED][!]
[[ Placeholder ]]
1 year later:laugh:
Sorry... I will finish this guide later...
And so on...
Sent from my GT-S7500 using xda premium
To infinity and beyond!
saiz136 said:
To infinity and beyond!
Click to expand...
Click to collapse
Beyond Smart xD
Updated Thread and Added a First Guide
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
ruizit0 said:
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
Click to expand...
Click to collapse
There is a guide lol
jader13254 said:
There is a guide lol
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
ahaha sorry .. i was thinking that was a little intro explaining clocklowrk and stuff .. to a coocking tutorial ahaha
maybe you can expecify more in title or something
nice tutorial to create a rom this way .. i read somewhere that the next clockwork will have this feature
Will try..
Sent from my GT-N8000 using Tapatalk 2
kaipro said:
Will try..
Sent from my GT-N8000 using Tapatalk 2
Click to expand...
Click to collapse
You need different commands for wiping on g Note, just search your device forum
Sent from my LT18i using xda app-developers app
Where is the system.img? I didnt have one when i backed up with cwm
very noob-friendly !
CovXX said:
Where is the system.img? I didnt have one when i backed up with cwm
Click to expand...
Click to collapse
check clockworkmod/backup folder... there should be system.xxxx.img
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
antoinejr1111 said:
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
Click to expand...
Click to collapse
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Click to expand...
Click to collapse
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Viva La Android said:
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Click to expand...
Click to collapse
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Click to expand...
Click to collapse
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
angadsg said:
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
At the boot logo connect to adb. Make sure its recognized and issue the following command: adb shell setprop debug.stagefright.ccodec 0
Sent from my SM-G975U1 using XDA Labs
Viva La Android said:
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
Click to expand...
Click to collapse
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
antoinejr1111 said:
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
Click to expand...
Click to collapse
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Viva La Android said:
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Click to expand...
Click to collapse
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
antoinejr1111 said:
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
Click to expand...
Click to collapse
My only dilemma there is that I've got multiple projects going right now for various LG and Motorola devices. However, I fully plan on future development for the Onn series of tablets (primarily the newer Onn Surf series due to Treble support). As soon as my schedule permits, I'm on it. Here's the beauty with Project Treble: if an Android 10 GSI will boot on the Onn Surf 10.1, it is almost certain that it will also boot on the Surf 8. Out of curiosity, what is the allocated /system partition size on the Onn Surf 8? Is it the same as the Surf 10.1? Also, I noticed recently that there are some rather slim GSI builds of Android 10 (Go Edition). Some of these might be worth looking into.