Let's get some custom ROM tweaking going on for our 7s!
As well as my own MoDaCo Custom ROM for the 5X, I've created a custom ROM starter template for anyone who wants to have a go. It's a bit different.
Basically, this ROM template will let you create your own custom ROM VERY easily. Easier than ever before. All you have to do is...
download my ROM template zip
make the changes to the system of your phone just as you'd like them for your custom ROM
run some commands on your device via ADB
add the resulting files to the template zip
That's it! No messaging around with install scripts, no rebuilding anything complex, just mod - and go!
Preparation
ONLY if you are completing the process for the first time, you need to set up a file on your microSD card - so launch and ADB shell and type the following commands...
Code:
touch /sdcard/exclude
echo app > /sdcard/exclude
echo priv-app >> /sdcard/exclude
echo delapp >> /sdcard/exclude
ROM build
Once you have your system up and running how you want it, and you're ready to distribute it (just the system and cust dirs mind, it won't pull the data dir, so your personal data is safe), reboot to recovery, launch an ADB shell and type the following commands:
Code:
mount /system
tar -X /sdcard/exclude -zcvpf /sdcard/system.therest.tar.gz /system/
tar -zcvpf /sdcard/system.apps.tar.gz /system/app /system/priv-app /system/delapp
mount /cust
tar -zcvpf /sdcard/cust.tar.gz /cust
You'll then end up with 3 new files on your SD card - system.apps.tar.gz (which is apps and priv-apps from system), system.therest.tar.gz (which, as the name suggests, is the rest of the system partition!) and cust.tar.gz with is the cust partition contents.
Update the template zip with these 3 files and that's it. It's ready to distribute for people to flash via TWRP! If you have updated the boot image, you'll need to replace that too, the easiest way is to do a TWRP backup then pull that file from the SD card and drop it into the template zip as boot.img. That's really it!
I hope this inspires a few people to start playing around with custom ROMs for the 57.. more cool things coming soon!
Oh and the all important template file...
DOWNLOAD - customromtemplate-7-plk01-b370-r4.zip [ROMRAID] MD5: c1ffe2bccd622a1a8a88f96be0a31f70
P
Changelog
r4:
Updated to B370
r3:
Updated to B330
r2:
Boot flash fix
r1:
Initial release
custom rom for the honor 7 coming soon you say?
music to my ears kind sir. anything is an improvement to emui
Good news!
paulobrien said:
Let's get some custom ROM tweaking going on for our 7s!
Ahead of my own MoDaCo Custom ROM for the 7, which is coming soon, I've created a custom ROM starter template for anyone who wants to have a go. It's a bit different.
Basically, this ROM template will let you create your own custom ROM VERY easily. Easier than ever before. All you have to do is...
download my ROM template zip
make the changes to the system of your phone just as you'd like them for your custom ROM
run some commands on your device via ADB
add the resulting files to the template zip
That's it! No messaging around with install scripts, no rebuilding anything complex, just mod - and go!
Click to expand...
Click to collapse
We tried to compile a tree from the files extracted from the device, and adding vendor blobs, but was not successful, if you have a tree by which we can get a working ROM, then can you please share it with us?
Thank you for the template though.
Great News!
We have been trying to compile the tree for so many weeks without reaching any positive results.
Thank you for your work and contribution. We will be tuned for your updates.
Note: It would be kind if you can share your feedback on this post -> http://forum.xda-developers.com/honor-7/development/tree-help-creating-honor-7-device-tree-t3310970
I haven't looked at the device tree yet, it's on my list of things to do!
I'm creating a stock-based ROM first then moving on to that.
P
paulobrien said:
I haven't looked at the device tree yet, it's on my list of things to do!
I'm creating a stock-based ROM first then moving on to that.
Click to expand...
Click to collapse
Thank you for your fast reply and contribution in all that. We will wait patiently for your updates.
I just want to say I love you
Template updated to r3 based on B330.
P
Thank you very much, Sir.
Long time no cooking. Maybe I give this a shot.
Hey,
I'm wondering if your method is applyable to other ROMs ?
Greetings from Germany
Is it possible to make such a template for B180 (LP)? I am fed up with MM but wish to have slightly modified stock LP rom.
morganmf said:
Is it possible to make such a template for B180 (LP)? I am fed up with MM but wish to have slightly modified stock LP rom.
Click to expand...
Click to collapse
Why would the dev create a pack like that based on an outdated software version? B330 runs as good as any previous builds. Here and there a tiny bug as every build has. No need for such nonsense as creating a B180 build now.
Sent from my PLK-L01 using XDA-Developers mobile app
t-ryder said:
Why would the dev create a pack like that based on an outdated software version? B330 runs as good as any previous builds. Here and there a tiny bug as every build has. No need for such nonsense as creating a B180 build now.
Sent from my PLK-L01 using XDA-Developers mobile app
Click to expand...
Click to collapse
With all the respect, it is not as much outdated as you say. B330 isn't as good as LP's B180. In manmy cases MM can be pain in the ass. It is not only my opinion. I understand you are happy with it but not everyone has to be you.
I had no problems with LP, neither do I have problems with MM. I don't get what all this is about... I call it nonsense.
Sent from my PLK-L01 using XDA-Developers mobile app
Our world seems to be big enough to give space for all kind of users!
Stay calm!
Why stay calm? I was just giving my point of view. If I consider it nonsense, I feel free to say so.
morganmf said:
Is it possible to make such a template for B180 (LP)? I am fed up with MM but wish to have slightly modified stock LP rom.
Click to expand...
Click to collapse
You can do it with the instructions in the first post.
P
Sent from my VIE-L09 using Tapatalk
No intention of being rude though, guys.
@paulobrien Do you plan to update MCR to B370 or are you too busy these days?
Related
Welcome to COFFEE SHOP v2.x; Your favorite KITCHEN for HD2 Android
COFFEE SHOP - creating your own HD2|ANDROID roms (2.1 only)
HTC SENSE supported
Desire base
Froyo base
ECLAIR base
Evo base ( but is very unstable )
If your base is not listed above, that does not mean that it is not compatible with your ROM. While I have not tested other roms, I suspect that most roms are similar enough that they should all be compatible (to some degree).[ Some features MIGHT be restricted such as Camera. Test it out, and report back for the convenience.
How do I use it?
Read the second post
Your Android system image (system.img) should go to '/root/of/coffee/shop/bin/environment/image/system.img' < You should create the folder if it doesn't already exist
COFFEE SHOP 2.1 is here!
If you have no clue what I said above, there really is no point of attempting, unless of course you want to learn
Download: v2.1
COFFEE SHOP -Tips:
Before starting, you will need any supported Android Image. Download it, and save it to the root of your COFFEE SHOP directory. Extract the "system.img" to 'bin/environment/image', which is located inside of the rom ZIP. (Only zip is explained in this guide. However, if you know how to extract from .EXE, by all means, go ahead).
Coffee Shop will do the following
EXTRACT SYSTEM IMG CONTENTS
INSTALL MODULES/APPS/ETC
REPACK SYSTEM+HOUSEKEEPING
You will need one separate dependency
Code:
genext2fs
#in terminal, use the following to install
apt-get install genext2fs
My rom won't work?
Make sure that you have adequate permissions on all coffee shop files!
Use the following command before your first time running COFFEE SHOP!
Code:
chmod 777 -R /path/of/coffee/shop/*
HOW-TO-USE?(2.1 only)
Using COFFEE SHOP 2.1 is simple as ever!
1. Move your 'system.img' to 'bin/environment/image'
2. Click "Build Android" button
--Your image contents will be extracted
3. Click "Export Android"
--Your system.ext2 will be built and ported to 'bin/environment/port/'
You have the option to install Modules, Apps, HTC-SENSE support ( does not install HTC-SENSE ), or root your rom! Check the boxes according to your preference. More options coming soon!
Where do I get my roms from?
http://shipped-roms.com/index.php?category=android
ROMS SUCCESSFULLY BUILT VIA COFFEE SHOP
XTarantula v1.x
DEVELOPERS LOG:
v1.0: Build System Images + Root
v1.1: Adding Media to System Image now suppported
v1.2: Custom shell commands now supported.
v1.3 Fixes "(" unexpected, unyaffs, genext2fs not found issues. Media is now accessible
v1.4 Adds dhdutil, e2fsck, scp, sqlite3 support (= Also, the COFFEE SHOP is more stable, and less bloating
v1.5 Fixes compatibility issues on x86-32bit systems Now everyone should be able to run COFFEE SHOP . Also, libs+modules are now installable!
v1.6 Fixes genext2fs issue. Make sure to apt-get install genext2fs
v1.7 Fixes a few glitches. You now also have the option to download a rom from a select list. Check ROM features for more information....
v2.0 has been rebuilt from scratch, and implements a bunch of new rom building functionality! Refer to documentation.
v2.1 Adds support for most Android images! Also, a GUI is included for the most simple ROM porting! *Supports HTC-SENSE
SUPPORTED ENVIRONMENT(S):
LINUX: Such as Ubuntu, OpenSUSE, Debian and most other Linux distributions
Great initiative. Looking forward to trying it once I get my HDD figured out.
montraydavis said:
Welcome to COFFEE SHOP v1; Your favorite KITCHEN for HD2 Android
COFFEE SHOP
Allows you to build roms based off most STOCK ECLAIR/FROYO builds
Allows you to build roms based off SOME STOCK HERO builds
How do I use it?
First, make sure you are on Linux (cygwin MIGHT be supported, but is untested. Anyone who wants to test, and report back, feel free to do so).
All you do is simply put your "system.img" file into the COFFEE SHOP root directory, and run the following via terminal
Code:
cd /root/directory/of/coffee/shop
./start.sh
==SETTINGS==
FILE : settings/settings
Code:
#allow root access on rom
root=1
settings are read per line
[variable]=[value], otherwise, it will NOT work. Currently, the only option though is allowing root access. More customization will come later
THIS IS A BETA RELEASE; NO DOCUMENTATION, OR FURTHER HELP UNTIL OFFICIAL COFFEE SHOP HAS BEEN RELEASED.
-THIS BUILDS ONLY THE "system" image
If you have no clue what I said above, there really is no point of attempting, unless of course you want to learn
Download: http://www.megaupload.com/?d=O23ENSB9
Click to expand...
Click to collapse
Awesome, soon some cooks will put all ingredients in the pot and get a nice flashing ROM out of their stove for many people to enjoy some tasty Froyo on their beloved HD2...
Soooo looking forward !
Therefore NAND have to work.. I think people shouldn't call it ROM, until it is something you can flash to NAND..
COFFEE SHOP v1.1 released;
Great work
montraydavis said:
COFFEE SHOP v1.1 released;
Click to expand...
Click to collapse
Im not a chef, but i can make something ^^
Big Thanks
yimb0 said:
Im not a chef, but i can make something ^^
Big Thanks
Click to expand...
Click to collapse
You can become one [=
Good luck ; Make sure you add some creame to the frappacino
This is very interesting and cool. I think I might have to play around with this and learn once there is a little more documentation.
so can i take for instance the .img from a Cyanogen build and cook a build based on that?
looks fun going to play now
palosjr said:
so can i take for instance the .img from a Cyanogen build and cook a build based on that?
Click to expand...
Click to collapse
Cyanogen has NOT been tested, but, why not give it a shot, and let me know ?
Demon_man said:
looks fun going to play now
Click to expand...
Click to collapse
Have fun, good luck, and let me know how it goes.
so, you are running this from terminal via the phone, or via terminal from a linux machine?
palosjr said:
so, you are running this from terminal via the phone, or via terminal from a linux machine?
Click to expand...
Click to collapse
Linux machine.
montraydavis said:
Linux machine.
Click to expand...
Click to collapse
gotcha. alright, getting my dual boot going again and then its off to the races!! so glad im off tomorrow!!!
palosjr said:
gotcha. alright, getting my dual boot going again and then its off to the races!! so glad im off tomorrow!!!
Click to expand...
Click to collapse
Someone is pretty excited [=
Good luck; Remember, this is a BETA release, so, it's not the BEST rom porting method, but, it's hell of a lot easier than any other one at this moment in time
Let me know how it goes;
--On the contrary, folks, feel free to report issues and or make suggestions
Im reinstalling ubuntu now so ill try this right after
montraydavis said:
Someone is pretty excited [=
Good luck; Remember, this is a BETA release, so, it's not the BEST rom porting method, but, it's hell of a lot easier than any other one at this moment in time
Let me know how it goes;
--On the contrary, folks, feel free to report issues and or make suggestions
Click to expand...
Click to collapse
definitely excited, this sounds like a great idea/tool and I am anxious to try it.
BETA or not, its better than what we have now (next to nothing!!!)
JJbdoggg said:
Im reinstalling ubuntu now so ill try this right after
Click to expand...
Click to collapse
likewise... man oh man, i wish i hadnt deleted my ubuntu.iso file a few weeks ago *_*
This is simply AOSP compiled from source. I am using the binaries provided by Google and the stock kernel provided by Google.
Instructions.
1. Download ROM- https://www.androidfilehost.com/?fid=95784891001615065
2. Downloas gapps- http://d-h.st/jzr
3. Reboot recovery
4. Wipe data and cache.
5. Flash ROM and gapps
6. Reboot
source for device tree
Github.com/papi92/android_device_moto_shamu
Issues
Video playback
Recovery is overwritten (I know the fix)
Feel free to submit fixes or just compile with your fixes.
Thanks!
papi92 said:
This is simply AOSP compiled from source. I am using the binaries provided by Google and the stock kernel provided by Google.
Instructions.
1. Download ROM- https://docs.google.com/a/droid-hive.com/file/d/0B0yE3jDMsld7dWZPck5sRXU1T28/edit?usp=docslist_api
2. Downloas gapps- http://d-h.st/jzr
3. Reboot recovery
4. Wipe data and cache.
5. Flash ROM and gapps
6. Reboot
source for device tree
Github.com/papi92/android_device_moto_shamu
Issues
Video playback
Recovery is overwritten (I know the fix)
Feel free to submit fixes or just compile with your fixes.
Click to expand...
Click to collapse
Your download is permission-only, FYI.
Let me change it
https://www.androidfilehost.com/?fid=95784891001615065
Added to Dropbox. I'm mobile so its hard to upload. Mirrors would help. I think I'm missing binaries (not on googles site) I'll look later. Would love to make this a community effort. AOSP is a lot faster then stock.
I ran a build myself. Haven't had the chance to see what may be missing. Would you mind sharing the fix for recovery being overwritten?
papi92 said:
Added to Dropbox. I'm mobile so its hard to upload. Mirrors would help. I think I'm missing binaries (not on googles site) I'll look later. Would love to make this a community effort. AOSP is a lot faster then stock.
Click to expand...
Click to collapse
Encryption enabled by default?
Yes. And Milly7 its in BoardConfig.mk I can do it later today.
Added an androidfilehost link.
This may be a dumb question but how different is this from the stock lolipop on the Nexus 6? I've used AOSP before but it's been a while.
You'll lose all the proprietary google apps as the default options. But you can download them from the play store. I am noticing a huge difference in performance tho. I'm hoping to fix the video playback soon. I want to just add a battery percentage option tho then I'll just optimize without touching hardware or kernel.
Would someone mind uploading the gallery.apk from this build? Currently using an older one which force closes on the editor screen and don't want to backup->flash->pull apk->restore.
Thanks for this papi92. I compared the vendor folder from the stock image to aosp and it appears quite a few files are missing. I really don't know how to add them and have always relied on devs such as yourself. Can upload the stock vendor folder if you need it.
That'd help a lot but those won't be the only ones missing. Some go in weird spots. I just need the missing ones.
Here is my vendor file for anyone who can help https://github.com/papi92/android_vendor
...and it begins. Thanks OP!
Here are the vendor files from the stock image. http://d-h.st/XV7
I was looking at them on 2 different computers so it was hard to tell which were different, but there are quite a few missing.
Ya I'll try to figure it when I have time. My daughter was born on the 21st so I was just trying to help people get started. I'm hoping the community helps with this. It'd be nice to get a solid base for the Nexus 6
papi92 said:
Ya I'll try to figure it when I have time. My daughter was born on the 21st so I was just trying to help people get started. I'm hoping the community helps with this. It'd be nice to get a solid base for the Nexus 6
Click to expand...
Click to collapse
Congrats on your newly born and thanks for your work.
I pooped my pants once, it's a long story....
Update 04-24-15.
Please scroll down to post #27 as a starting point for this ROM development. @tx_dbs_tx has picked up the efforts and has it breathing. Please thank him for his efforts.
/////////////////////////////////////////////////
Update 1: 04-14-15 2121 hrs PDT. The update script doesn't work. The flash fails. I just tried it. I need to figure out where the problem is with the kitchen. I will take down the link for now.... Sorry guys.
Update 2: 04-15-15 0741 hrs PDT. In trying to figure out the issue with the kitchen, I broke the Ubuntu VM. I am in the process of rebuilding it, but that will take some time.
--------------------------------------
IF IT SEEMS LIKE I'M YELLING, IT IS BECAUSE I AM. THIS IS A PRE-PRE BETA BUILD. I AM NOT A DEV. I USED A KITCHEN THAT DOES NOT DIRECTLY SUPPORT THIS ROM. THIS IS BUILD WITH MY VERY LIMITED KNOWLEDGE. ANYTHING YOU DO WITH MY PRODUCT IS ALL ON YOU--YOU CAN BRICK YOUR PHONE AND/OR BECOME STERILE. I JUST DON'T KNOW. IF YOU'RE NOT WILLING TO JACK UP YOUR PHONE AND STAY UP ALL NIGHT TO FIX YOUR PHONE, DON'T TRY THIS.
THIS BUILD MAY BE DOA. I HAVE NOT HAD TIME TO FLASH OR TEST THIS, I JUST WANTED TO GET IT TO YOU GUYS ASAP. IT MAY NOT WORK AT ALL.
--This is a recovery flashable ROM
--[Should be] deodexed, if you see .odex files, they should be safe to delete
--zip aligned
--rooted (you will need to update SuperSU or maybe reapply CF Autoroot, update binary too)
--busybox and init.d support
--startup sound disabled
--includes modem/baseband
Step 1) Make nandroid/backup, backup your data again, and have a backup for your backup
A) If you're on my KK ROM
--download and flash via recovery
--wipe cache/dalvik
--reboot and pray
--if all works, phone will start w/ Lollipop and all your apps, you should have the OC8 baseband too, the only thing you don't have is the latest bootloader, which is okay most of the time. If you want that too, flash the stock package (see below).
B) If you OTA'd or odin'd the stock package
--root and install recovery
--go to A)
C) If you're on KK and want the LP bootloader
--odin the stock package (from my other thread)
--odin recovery
--go to A)
Let me know how it works out. Like I said, I just wanted to get this out ASAP. I have done exactly zero testing. No idea how it will work out. The instructions above are based on memory and off of the top of my head. If this doesn't work, restore from your backup and let me know, and I'll deodex using my old tried-and-true methods (which is much more time consuming).
Again, I want to manage your expectations. I have no confidence that this will work. If it does, it's a miracle! Good luck to us all....
Oh yea, the link [taken down for now]
Check MD5....
If I didn't NEED my phone for work tomorrow I would be a guinnea pig.
VenpaCasa said:
If I didn't NEED my phone for work tomorrow I would be a guinnea pig.
Click to expand...
Click to collapse
Well it's alright. At the dismay and protest of my gf, I will flash this shortly and see how it works. Can't believe I'm taking the phone over [possible] sex.
Downloading to test
Thank you.
I just tested it. The updater script fails to execute. I'm looking into it.
I requested our firmware and kernel but they responded with this:[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
Dear Sir or Madam,
Thanks for your continuous interest in our products.
We received your request on OSRC.
We will provide the response ASAP, if your request is related to FOSS.
(This site is just for providing source code of FOSS Software we have used in our product.
You could contact with other types - ex. firmware - on your local Samsung support homepage.)
Thank you.
Sincerely yours,
What does this mean?
dinaps86 said:
I requested our firmware and kernel but they responded with this:[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
Dear Sir or Madam,
Thanks for your continuous interest in our products.
We received your request on OSRC.
We will provide the response ASAP, if your request is related to FOSS.
(This site is just for providing source code of FOSS Software we have used in our product.
You could contact with other types - ex. firmware - on your local Samsung support homepage.)
Thank you.
Sincerely yours,
What does this mean?
Click to expand...
Click to collapse
FOSS = Free and Open-Source Software
It looks like they will only provide you with FOSS used in Samsung products, which makes sense.
snovvman said:
FOSS = Free and Open-Source Software
It looks like they will only provide you with FOSS used in Samsung products, which makes sense.
Click to expand...
Click to collapse
........do we want this lol I'm still confused ?
Should I
Allow Super SU to update the binary?
Thanks
Charles
I haven't flashed snovvman's stock rooted rom
ceabbott2 said:
Allow Super SU to update the binary?
Thanks
Charles
I haven't flashed snovvman's stock rooted rom
Click to expand...
Click to collapse
Yes. But not in recovery. I haven't flashed it either
Another thank you to Snovvman for all of the hard work
If it matters please don't give up your stock rooted Roms have been a godsend.
Sent from my Nexus 7 using XDA Free mobile app
Thanks for the encouragement guys. I have been working on fixing the kitchen when I have time. If that doesn't work, I'll do it the traditional way, which is to extract the ROM manually, and deodex, etc. I don't do this often, so I have to figure things out each time. This will get done because I can't live without root and I can't live without Xposed customization. I am off to a business trip tomorrow, so I won't pick this up again until next Thursday or Friday. Thanks for your patience.
After a few hours of work, I got the VM and kitchen running again. I have also resolved the symlink issue. Instead of doing the work on a shared folder with the host, I expanded the VM Linux partition and do all the work there.
The updater script generated by the kitchen does not work. I suspect this is because of the unsupported kitchen.. I will try to use the script from the NK1 ROM. That should work fine.
I've run into something that I don't quite understand. I expect to see the \system\app and \system\priv-app to be full of apks and odex files. When I extracted the ROM, these two folders contain one sub-folder for each of the apk, containing the app apk and other folders. For example, for Maps:
system\app\maps\maps.apk
system\app\maps\arm\maps.odex.art.xz and maps.odex.xz
system\app\maps\lib\arm\*.so files
During odin or OTA, I believe a script would properly install these files. The traditional kitchen extraction doesn't provide for that. Because of this, I think I will need to first odin the stock package, run a nandroid, and use that as the basis for making the deodexed/rooted ROM.
At this time, if anyone can shed some light on what I am seeing, it would be helpful.
It would also be helpful if someone who has already OTA'ed or odin'd the Lollipop package, and have installed TWRP/CWM, can nandroid the /system and boot, and send those files to me. (It does not matter if it is rooted or not). I am off to a business trip later today, so I won't be able to do anything until I get back next Thursday. If no one sends me the files, I'll odin to Lollipop and extract the files myself when I return.
Thanks.
Well, this partially explains the folders I see:
http://www.dorylabs.com/how-to-deodex-android-5-0-lollipop-applications/
How
snovvman said:
Well, this partially explains the folders I see:
http://www.dorylabs.com/how-to-deodex-android-5-0-lollipop-applications/
Click to expand...
Click to collapse
Can I help. If you can explain I will give it a shot. I have flashed the ext sd card and the sound modification. Will that matter?
Sincerely,
Charles
ceabbott2 said:
Can I help. If you can explain I will give it a shot. I have flashed the ext sd card and the sound modification. Will that matter?
Sincerely,
Charles
Click to expand...
Click to collapse
What sound mods did you use
Sent from my SM-N915P using XDA Premium HD app
thatruth132 said:
What sound mods did you use
Sent from my SM-N915P using XDA Premium HD app
Click to expand...
Click to collapse
The medium one from this thread.
http://forum.xda-developers.com/showthread.php?t=2955648
@snovvman
I think you mentioned being away for business...but if you need anything for assistance, let me know , I will be happy to send you files to get this moving along.
I am on rooted stock KK right now.
SuperR's Kitchen has moved to a dedicated subforum found at the link below.
SuperR Kitchen
forum.xda-developers.com
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
SuperR. said:
If you want to build a flashable boot.img, you should build boot flashable. If you want to build a full rom, you should build a full rom. If you want to build a flashable zip with deodexed files you should choose build custom and choose the option you want.
Click to expand...
Click to collapse
I took the first option (build full rom zip) after deodexing.
Is it good enough or do I still need to select specific custom zip to build?
ferbulous said:
I took the first option (build full rom zip) after deodexing.
Is it good enough or do I still need to select specific custom zip to build?
Click to expand...
Click to collapse
It depends on what you want to end up with. If you only want the full rom zip then full rom is good. If you want more zips with different contents, make more
SuperR. said:
Sounds like your build.prop either reports the rom as less than Lollipop or the build.prop line is different than all others I have ever seen. Please post it so I can take a look.
Did you install the package I linked above?
Click to expand...
Click to collapse
Edit: The prop says it is 5.1.1
https://mega.nz/#!GURQQADK!ujhHvu1XJ7F9BNz8cgBSclKMGilcP6fYLetub82zLzU
nghia0423 said:
Edit: The prop says it is 5.1.1
https://mega.nz/#!GURQQADK!ujhHvu1XJ7F9BNz8cgBSclKMGilcP6fYLetub82zLzU
Click to expand...
Click to collapse
This is the line we are looking for:
ro.build.version.sdk=22
and it says it is Lollipop for sure. I am not sure why it is telling you that. Are you sure you are working on the correct project?
not-i said:
So with my Moto X files I have successfully unpacked, deodexed, done some minor mods and its repacked system_new.img and its the same size as original system/img so looks promising.
I'm guessing now I "created rom zip" and thats when system.new.dat is created?
Click to expand...
Click to collapse
How did you unpack the moto x system image with this kitchen?
I just tested the moto x vzw 5.1 system image with no luck.
Many moto firmwares use an encrypted sparse format (MOTO.W›.MOT_PIV256).
I am able to use imgextractor (windows) to dump the image and list of symlinks, as well as get image info, but I haven't found any linux utilities that can handle this format.
At one point I got to plug-in my device - so far, so clear, but what if I make a rom for a device I don't have
Androidwizzard said:
At one point I got to plug-in my device - so far, so clear, but what if I make a rom for a device I don't have
Click to expand...
Click to collapse
You only need to plug in your device if you are ripping the img's from it. Normally you can get the by-name info from a boot.img. If the device does not use by-name you will need to create an mmc file and still don't need to plug in the device.
fyi
nghia0423 said:
Well this program is made for linux
Click to expand...
Click to collapse
ok well then, for the record....
the program does not like functioning with a linux emulator
v0.9.0.2
Changes:
When entering Boot/Recovery Tools, recovery no longer takes precedence. You will be presented with a choice of which to work on if boot.img and recovery.img both exist in the project directory.
Looks very nice. I guess I'm going to have to dust off my Linux install and give it a go.
SuperR. said:
Are you on the newest kitchen? I ask because it now checks to make sure you have all the other dependencies met. If you are running the newest kitchen and you are on 32-bit Ubuntu, I have no idea what is going on. Are there any errors in the terminal if you scroll up after building the zip?
Click to expand...
Click to collapse
I changed to 64 bit ubuntu and I'm able to install lib32.
Now I can generate he zip file without any issues. Looks like I'm definitely ditching the 32bit system now.
Been considering that, myself. BUT.. I deodexed ur ROM with a 32 bit Linux Mint system.. 64 bit processor tho, you?
Sent from my N9510 using Tapatalk
SuperR. said:
Try it and let us know. If you have trouble, post links to all the img files so I can have a look.
Click to expand...
Click to collapse
I am trying to create a custom rom for “Huawei Mediapad T1 8.0”. I just need a flashable rom from the stock system.img and boot.img.
I am using “dell Inspiron 15r n5010” model computer with 4gb ram and 500 gb harddisk, dual booting windows 7 with linux mint rafaela.
Version of super kitchen is 0.9.0.4. version of android 4.3 (emui 1.6)
I extracted system, boot, recovery from device using the super kitchen by options 1 and 4.
After the extraction i checked out the options and at some point kitchen wanted me to choose from set_meta or set_perm, i chose set_meta but it said that my kernel doesnt support the set_meta type and chose set_perm by default.
Using the kitchen, I debloated the firmware.
Then built the fullrom zip.
I tried to flash using TWRP recovery, but it doesnot allow me and said , “This rom is for 'msm8610' devices, This is a 'mediapadt1'”. I thought to delete that line from updater script. But didnot delete because, that may need some changes in other files too.
I think that buildprop product name is differing from recovery product name.
I have attached files i was using,, I am new to linux and also android rom building..
Help me..
Update to latest version and try again..? I'm running same dualboot system you are (diff PC) He's made many changes since earlier this week to encompass more devices
Sent from my N9510 using Tapatalk
Huawei is little complicated to build roms, can you upload the firmware?
Gesendet von meinem D6503 mit Tapatalk
stamilselvan said:
I am trying to create a custom rom for “Huawei Mediapad T1 8.0”. I just need a flashable rom from the stock system.img and boot.img.
I am using “dell Inspiron 15r n5010” model computer with 4gb ram and 500 gb harddisk, dual booting windows 7 with linux mint rafaela.
Version of super kitchen is 0.9.0.4. version of android 4.3 (emui 1.6)
I extracted system, boot, recovery from device using the super kitchen by options 1 and 4.
After the extraction i checked out the options and at some point kitchen wanted me to choose from set_meta or set_perm, i chose set_meta but it said that my kernel doesnt support the set_meta type and chose set_perm by default.
Using the kitchen, I debloated the firmware.
Then built the fullrom zip.
I tried to flash using TWRP recovery, but it doesnot allow me and said , “This rom is for 'msm8610' devices, This is a 'mediapadt1'”. I thought to delete that line from updater script. But didnot delete because, that may need some changes in other files too.
I think that buildprop product name is differing from recovery product name.
I have attached files i was using,, I am new to linux and also android rom building..
Help me..
Click to expand...
Click to collapse
Take a look at this post
http://forum.xda-developers.com/showpost.php?p=63088636&postcount=234
I try build for s3 i9300 with system.img boot.img and zip file
always I have
executing updater binary in zip
any help please
Sent from my GT-I9300 using XDA Free mobile app
Parse dat is out of date, whats your recovery version?
Gesendet von meinem D6503 mit Tapatalk
This rom is built directly from the stock MRA58R Google image.
PSA
For pin to work you will need a permissive kernel, Rom is currently running enforcing so flash a permissive kernel if you want pin. No issues if your using cataclysm. I'm working on figuring out the fix thanks.
It is basically just the system folder extracted from the MRA58R Google update and repackaged as a flashable zip with a stock kernel with added features by @gerar_f.
I packaged this together for people that want a Stock Bloated Google experience. Or a fully stock rom to customize to the users liking.
Any mod made for the stock google rom should work 100% here.
Cataclysm mod is recommended if your looking for a more custom rom experience and I fully support flashing it over this rom.
http://forum.xda-developers.com/nexus-6/orig-development/rom-cataclysm-nexus-6-t3219121
Cataclysm flashes a kernel so if you like the added features of gerar_f's kernel then you will want to flash it after cataclysm. Link below
Rom Features
Odexed
None really. This is as stock Google as it gets, you will find all the gapps that will possibly fit in the system partition just like a stock google image.
Root is not included. Flash SuperSu 2.5.2 if you want. You can run this rom un-rooted with cataclysm mod flashed over top and have a custom unrooted rom with working android pay.
(Theoretically) I haven't been able to test pay around me
Busybox is also not installed so grab that from the playstore if you want/need it.
Included Kernel by @gerar_f
Included kernel is Custom "Stock" v4 created by @gerar_f big thanks to him and go over to his thread and drop a like.
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
Kernel is stock in behavior with a few features. First it is without forced encryption, It is Seandroid Enforcing and includes several features, Root with rw if rooted, Disabled boot verification warning, Color control, Headphone and mic gain control, Vibration control, Wake gestures, Multirom support.
TIPS
There is only 33mb free in the system partition due to google including so many gapps. In my testing ive found that this is enough for installing 1 layers theme and Cataclysm Mod.
Some gapps may need removed to install things like Xposed modules, and other apps to the system(TBO apps, better battery stats etc) or anything that takes up more than a few megs going into the system.
I personally remove Fit, Sheets, and Slides which gives you around 100mb free in system which is enough for my use. I recommend this app for removing system apps you dont want. Root Required.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
Thanks
@gerar_f for great custom stock kernel. (I couldn't even begin to figure out how to customize a kernel)
@tupac4u for the updater-binary and update-script to flash the zip properly. (my attempts at making the script were futile)
@atl4ntis for making Cataclysm and inspiring me to create a stock rom for said mod to be flashed over.
Google
@magnamentis @dhruvmalik for testing. @Chainfire for ROOTS!
Download
Rom
https://www.androidfilehost.com/?fid=24269982087001131
MD5
52526f45a3ffafd6d9b6bdd0b7f8836c
Install instructions
In TWRP, factory rest, wipe cache, dalvik, data, and system.
Flash Rom
If wanted flash additional stuff (supersu, cataclysm, and/or kernel)
Profit
Reserved for possibly more
Hi,
Thank you for this as this is very useful!
Droidphilev said:
Hi,
Thank you for this as this is very useful!
Click to expand...
Click to collapse
Thanks!
I was surprised that there was not a unmodified flashable Google rom out so I put one together.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Thanks!
I was surprised that there was not a unmodified flashable Google rom out so I put one together.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried myself too but gave up
I wonder: this is a one time project? I mean if there's a new factory image can i just extract the system.img and put it into your zip and never ever bother you again?
(I'm not able to download today hence the question)
EDIT: please don't mind the kernel in this question
Droidphilev said:
I tried myself too but gave up
I wonder: this is a one time project? I mean if there's a new factory image can i just extract the system.img and put it into your zip and never ever bother you again?
(I'm not able to download today hence the question)
EDIT: please don't mind the kernel in this question
Click to expand...
Click to collapse
I'm planning on releasing more versions as Google releases it's monthly updates.
To answer your other question it's not as simple as just extracting the system.img but isnt too hard. Basically you extract the actual system.img from the Google update. Then use ext4 unpacker to unpack it into an ext4 file. Then you use ext2 explore to unpack the ext4 file which gives you the system folder with all the files within. Then just take the system folder a compatible boot.img and a working meta-inf folder and zip them up. Then you have your Rom.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
I'm planning on releasing more versions as Google releases it's monthly updates.
To answer your other question it's not as simple as just extracting the system.img but isnt too hard. Basically you extract the actual system.img from the Google update. Then use ext4 unpacker to unpack it into an ext4 file. Then you use ext2 explore to unpack the ext4 file which gives you the system folder with all the files within. Then just take the system folder a compatible boot.img and a working meta-inf folder and zip them up. Then you have your Rom.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you for this info and explanation but after reading this i think i will just download your releases if you don't mind
Droidphilev said:
Thank you for this info and explanation but after reading this i think i will just download your releases if you don't mind
Click to expand...
Click to collapse
Lol that's fine with me.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Lol that's fine with me.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah, thanks for the explanation, its nice to learn about stuff that has bewildered you for ages.
arifqur said:
Yeah, thanks for the explanation, its nice to learn about stuff that has bewildered you for ages.
Click to expand...
Click to collapse
Feel free to ask any other questions.
Yea that's very simple way to make a Rom. I wouldn't call myself a dev or anything. The other custom roms require a lot more work like modifying system apks to add the extra features. This is just full unmodified stock with a kernel. I figured it would be a great base to flash cataclysm over. Seeing how it's recommended to flash cataclysm over a full stock Rom this is as close as it gets right now. People have had luck flashing cataclysm over other stock modified roms but I worry that those modifications may cause issues with the modifications of cataclysm. With that said I'm personally running it without cataclysm. I just removed a few gapps I'll never use flashed and installed around 10 team blackout apps, and applied magpie midnight theme for a almost fully blacked out experience.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Feel free to ask any other questions.
Yea that's very simple way to make a Rom. I wouldn't call myself a dev or anything. The other custom roms require a lot more work like modifying system apks to add the extra features. This is just full unmodified stock with a kernel. I figured it would be a great base to flash cataclysm over. Seeing how it's recommended to flash cataclysm over a full stock Rom this is as close as it gets right now. People have had luck flashing cataclysm over other stock modified roms but I worry that those modifications may cause issues with the modifications of cataclysm. With that said I'm personally running it without cataclysm. I just removed a few gapps I'll never use flashed and installed around 10 team blackout apps, and applied magpie midnight theme for a almost fully blacked out experience.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
As stated above by others, I was also surprised that there wasn't a flashable stock ROM available, primarily for those who wish to be stock, use xposed and or mods like Cataclysm.
This is working awesome; thanks @GavinMazey
Great idea, I'll probably be checking it out soon with CatMod. Any chance you could debloat it? It's not hard for me to just use Tibu to do it, but one less thing to do is always nice. No worries if you can't.
Thanks for the rom!
Thank you for this!
GeekMcLeod said:
Great idea, I'll probably be checking it out soon with CatMod. Any chance you could debloat it? It's not hard for me to just use Tibu to do it, but one less thing to do is always nice. No worries if you can't.
Thanks for the rom!
Click to expand...
Click to collapse
I'm not really planning on debloating, there is a plethora debloated roms for the n6. But if enough end up wanting it I might. But if I do it would be my personal debloat instead of removing as much as possible. Keeping it stock let's me update faster when google drops new images.
flashback7 said:
Thank you for this!
Click to expand...
Click to collapse
Thanks for checking it out.
Sent from my Nexus 6 using Tapatalk
+ 1 on NOT debloating. Every one could do it how they like it by themselves.
Thanks.. It's good to know I have an option to flash the zip. I might load up cataclysm tonight
This is great for those who want fresh out of box stock experience with working ANDROID PAY. Once you root it, trim it, customize it, then ANDROID PAY won't work.
cink40 said:
+ 1 on NOT debloating. Every one could do it how they like it by themselves.
Click to expand...
Click to collapse
Noted. That was my thought too stock bloated base for users to do what they want with it. I personally use most of the gapps included, I personally only delete sheets, slides, and fit (I may be a fatty lol). I've found most debloated roms remove too much so instead of having the gapps taking up system space I have to install them to internal storage taking up space where they don't need to be.
Too much free system space is wasted space imo.
Phrodini said:
Thanks.. It's good to know I have an option to flash the zip. I might load up cataclysm tonight
Click to expand...
Click to collapse
If your already on android m you should be good to flash this then cataclysm. Report back how it went if you do. Haven't had too much feedback on users actually flashing it. Hopefully because all works great [emoji12]
HueyT said:
This is great for those who want fresh out of box stock experience with working ANDROID PAY. Once you root it, trim it, customize it, then ANDROID PAY won't work.
Click to expand...
Click to collapse
That's exactly why I kept it unrooted. In theory someone could flash this Rom and then cataclysm without root and have a custom Rom with working Pay just no root. No where that I've been around me accepts pay so I am unable to test. But in theory it should work.
Sent from my Nexus 6 using Tapatalk
GavinMazey said:
Noted. That was my thought too stock bloated base for users to do what they want with it. I personally use most of the gapps included, I personally only delete sheets, slides, and fit (I may be a fatty lol). I've found most debloated roms remove too much so instead of having the gapps taking up system space I have to install them to internal storage taking up space where they don't need to be.
Too much free system space is wasted space imo.
If your already on android m you should be good to flash this then cataclysm. Report back how it went if you do. Haven't had too much feedback on users actually flashing it. Hopefully because all works great [emoji12]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I am thinking about using multirom with this zip, cataclysm, and a lollipop rom.. Maybe kitkat too for one game that only works on kitkat lol
Phrodini said:
I am thinking about using multirom with this zip, cataclysm, and a lollipop rom.. Maybe kitkat too for one game that only works on kitkat lol
Click to expand...
Click to collapse
Flashing cataclysm will replace the included kernel with cataclysm kernel which you'll need to check supports multirom, I'm not sure off the top of my head. But if not re flashing the included kernel by gerar_f after cataclysm will give you multirom support. Also I'm not entirely sure you can run kitkat and marshmallow in multirom at the same time. I haven't used it myself but I think (I may be wrong) that multirom uses your main kernel for all other roms. So a different android version may not work properly. Again I might be wrong.
Sent from my Nexus 6 using Tapatalk