Related
Several questions:
1. If I use gapps with AndDiSa's latest ADS_Magpie (ADS_magpie-20110510-signed.zip), does it require the newer version of gapps (GAPPS: 20110508b) linked on ezterry's page?
2. If the answer to 1 is yes, any special advice (definite DO's or DON'Ts)?
Some background:
Have used AndDiSa's ADS_Magpie on rooted G1 for a few weeks and have been very pleased with it.
Checked his page today at http://dl.dropbox.com/u/9870397/android/ADS_magpie/index.html today and saw he has a new version numbered 20110510.
Since it is based in part on ezterry's Gingerbread work (Source Code Repo for ezGingerbread development (Dream and Sapphire)), I've also been following that thread.
With ezterry's GINGERBREAD-DS-Alpha-20110509-1.zip, he includes a statement that reads "Starting this version you must use GAPPS: 20110508b due to the new Platform key in use." That is the reason for my question.
Thanks for your help.
If you do a no wipe install it should work without installing the new gapps due to the backup script included. I didn't have the chance to test it deeply, so I cannot guarantee.
If you do a clean install, the new gapps should work fine.
Sent from my Gingerbread on Dream using XDA App
Edit: Most likely it's more secure to erase system, then flash the rom and then flash the new gapps
Thanks, AndDiSa. I made a full backup (gapps, nand+ext) from recovery and flashed the latest - no problems.
Really enjoy GB with magpie on my G1, getting another 6 months with it will be much more satisfactory.
Thanks for sharing this with the community!
anyone can pelase share the ROM link with me for ADS_Magpie..
evertime i searched i got this LINK
Take the link from my signature ...
AndDiSa said:
Take the link from my signature ...
Click to expand...
Click to collapse
thanks...isn't there any forum for this...where u can post some screen shots and also that will be easily accessible... just a suggestion.
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
NOTE: This guide may also work for other Samsung devices. So if you were told to come here and you have a different device, it was not an error - just make sure you use a base ROM from your own device, not from the I9300! For all other Galaxy S3 variants, this guide might not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
I'd like to thank klander for testing and providing feedback, which is always appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE FOR MAKING YOUR ROM:
NOTE: If you have a non-I9300 device and were told to follow these instructions, then use a base ROM from that device, NOT a ROM meant for the I9300!! The same steps below, however, (and common sense) should be used.
First, you need a rooted Samsung Galaxy S3 I9300 with a custom recovery menu, which allows flashing of custom ROMs.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Put one or more of your base ROM(s) under the original_update folder. For the Samsung Galaxy S3 I9300, there is support for the following formats (that I know of) which can be placed in that folder:
Stock firmware:
system.img, boot.img, cache.img (and optionally: modem.bin)
TAR/ZIP file containing the above. NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
OR Custom ROM:
must be a ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods such as CyanogenMod, due to potential file structure incompatibility issues)
OR Nandroid backup from custom recovery image:
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
Optional: Disable boot sounds
Optional: In the Advanced options menu: De-odex your ROM (your mileage may vary as to whether this works 100%)
Optional: Add or remove the modem.bin from your working folder
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin. Make a Nandroid backup of your current system before you flash anything!
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss the Samsung Galaxy SIII GT-I9300 in this thread!
Most of all, have patience, take your time and enjoy!!
just what i need
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Are we still meant to be extracting the img files manually to get them working?
Kangburra said:
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Click to expand...
Click to collapse
I'm not doing additional work, but if you'd like you could make a plugin for the kitchen, which would go under the /scripts/plugins folder and can be accessed from the Advanced menu of the kitchen. I can advertise it in the kitchen thread (in the plugins section) as a separate download under your name.
Are we still meant to be extracting the img files manually to get them working?
Click to expand...
Click to collapse
With Cygwin the kitchen will give you instructions on which program to open and how to use it (manually). The programs are found in the kitchen.
With Linux/Mac, it is all automated and very quick.
Just when I thought this kitchen was a goner, you came along and made it work again
I have just put the French zip into the kitchen and it fails to extract the img files.
Available ROMs:
(1) I9300XXDLIH_I9300VFGDLJ1_SFR.zip
Enter selection number (default=1, cancel=0, r=refresh):
Selected I9300XXDLIH_I9300VFGDLJ1_SFR.zip
The new working folder will be named WORKING_101712_171605
Change the name (y/n)? (default: n):
Creating working folder WORKING_101712_171605 ...
Extracting ROM ...
Error: No system folder found!
Press Enter to continue
Click to expand...
Click to collapse
It works after manually extracting so no big deal
Kangburra said:
I have just put the French zip into the kitchen and it fails to extract the img files.
It works after manually extracting so no big deal
Click to expand...
Click to collapse
If the zip contains a tar file then it's not going to work, you need to unzip the tar file.
The best tool for deodex Roms!
THANKS dsixda! :good:
Regards
adesirello (AndyX ROM)
Awesome job mate :good:
tomorrow`s homework !
thanx !
Perfect! Just two days ago i was think at dsixda kitchen! I don`t have enough thanks for this!
Great.
Just what i was looking for.
dsixda said:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
IMPORTANT: For all other Galaxy S3 variants, this guide may not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
Click to expand...
Click to collapse
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
L335K1 said:
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
Click to expand...
Click to collapse
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
dsixda said:
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
Click to expand...
Click to collapse
yea i created the init.d folder first, (using v29 so it gives u warning anyways), but it still does this. i have to add init.d support manually through my script. but this is awesome, i just gotta remember not to use that feature.. i did both logcat and recovery logs but couldnt make heads or tails of it. it was easier to go back through ur kitchen, add 1 feature at a time until i found the culprit. thanks heaps
Please link to download the kitchen, thank you very much.
misacek said:
Please link to download the kitchen, thank you very much.
Click to expand...
Click to collapse
First post.
This is great!
Thanks dsixda.
YZ.
Please not see me? can give direct link? thank you very much
misacek said:
Please not see me? can give direct link? thank you very much
Click to expand...
Click to collapse
If you refuse to or are unable to read post #1 then you'll have trouble using - and even installing - the kitchen.
Welcome to the [STICKY] I9505G GE GALAXY S IV ( INDEX ) ROM's / LINKS / HOW TO THREAD formally the DISCUSSION GUIDE
This is the Official Index Roll up thread for the I9505G Google Edition Galaxy S IV. In this Index you will find helpful, links, guides, how to's and instructions for your I9505G.
Please Post any links or helpful information in this thread or you can PM me so I can link it in the OP ( If your on the I9505/I9500 Please do NOT ASK about development for your device this is for the I9505G ONLY
(DISCLAIMER) As always I nor anyone is responsible if you cannot follow instructions in this or any other thread. We assume NO liability for bricks, loss of job, or the end of life as we know it.
GUIDES & LINKS
How to get CM 10.1 & CM 10.2 working on the I9505G
How Unlock the Bootloader for the I9505G
[OTA] OTA ZIP 4.3 for I9505G
How to Update your Baseband to get the 4.3 OTA
TOUCHWIZ Development Thread Q&A
Camera Save to SD Card for Google Edition ROM's
I9505G How to Set Device Mount Points in Android Kitchen GE S IV
4.3 SD Card Issue Fixed
How to upgrade a Stock+Root+Custom_Recovery I9505G from 4.3 to 4.4 and keep all Data
ROOTING THREADS
How to Root 4.2, 4.3, 4.4 JB, Kit Kat I9505G
ROM's
[ROM][Linaro-4.8] XenonHD-4.4.2 Alpha 1 (5/1/14) *Truly Stable, Fast & Butter
GOOGLE LITE EDITION 4.2.2 v.2 MFD
GOOGLE LITE EDITION 4.3 I9505GUEUBMH1 Ktoonsez Kernel
TOUCHLITE GE TOUCHWIZ ROM
[ROM] Google Edition 4.3 [Clean][Deodex][276MB]
RECOVERY
How to install TWRP via Odin on the I9505G
TWRP for the I9505G
[BETA][RECOVERY] ClockworkMod Recovery 6.0.3.6
[ODIN[TAR] Stock Recovery Images
MODEMS
ODIN TAR MODEMS
STOCK FIRMWARE LEAKS
Stock ODIN FIRMWARE Leaked 4.3 MFP
Stock ODIN FIRMWARE Leaked 4.3 MG8
ODIN AND HEIMDAL PACKAGES
Stock HEIMDAL 4.2.2 MFD back to Stock
[ODIN][TAR] I9505GUEUAMFD 4.2.2 Full Rooted Restore
[ODIN][TAR] I9505GUEUBMH1 4.3 Full Rooted Restore
[ODIN][TAR] I9505UEUBMH5 4.3 Full Rooted Restore
[ODIN][TAR] I9505GUEUBMKG 4.4 Full Rooted Restore
[ODIN][TAR] I9505GUEUBML4 [4.4.2] Full Rooted Restore
[ODIN][TAR] 4.4.3 I9505GUEUCNE3 Full Rooted Restore
[ODIN][TAR] 4.4.4 I9505GUEUCNF3 Full Rooted Restore
Reserved
Big Thanks to Illogic6 for being the Very 1st Person to get Touchwiz Booted to the I9505G post #31 and SamuriHL for solving the Baseband Update Issue and Chainfire
Modem Update : Due to the secure boot loader we cannot flash modems via cwm or any other custom recovery. You MUST update your firmware via Odin
Touchwiz Works with some ROM's like BareBones from the I9505 forum being successfully booted on the I9505G. TW Development is ongoing for the I9505G but with the small partition size some issues exist, and are being researched and worked out.
http://forum.xda-developers.com/showthread.php?t=2405273
11/28/2013 : KitKat initial release this week New Updated Odin Packages and ROM's please check A&D section
DONT FORGET TO THANK THE MEMBERS AND DEVS WORKING HARD ON THE I9505G DEVELOPMENT
07/21/2014: I just wanted to make a note that I still get emails and requests for help and although I am no longer doing any sort of work on the I9505G I will try to help you out if you PM me. PLEASE BIG THANK YOU TO @SamuraiHL he is really the one maintaining everything for I9505G Owners and if you have not thanked him please do. Actually without volunteering him he is your best POC for anything current. I will maintain the thread for organization now and then. ALOHA
MJHawaii said:
Reserved :good:
Click to expand...
Click to collapse
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
wilbarger said:
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
Click to expand...
Click to collapse
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
One person you might contact is mohan_kr. He has come over to the S4 from the Skyrocket recently. Excellent at working on the ROM's. Sorry I can not be of assistance, but I am not very advanced on Android.
wilbarger said:
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
Click to expand...
Click to collapse
wilbarger said:
One person you might contact is mohan_kr. He has come over to the S4 from the Skyrocket recently. Excellent at working on the ROM's. Sorry I can not be of assistance, but I am not very advanced on Android.
Click to expand...
Click to collapse
That's what this thread is for though for everyone to get together share information and collaborate.
Chahk's post about mount points and getting other CM/AOSP ROMs working on I9505G deserves its own link:
http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
MJHawaii said:
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
I saw Chahk post and it is helpful this is where I'm at right now read above. I did pm Chahk and a few others for help. I will work on it a little later this weekend
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
irishrally said:
Chahk's post about mount points and getting other CM/AOSP ROMs working on I9505G deserves its own link:
http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
Click to expand...
Click to collapse
x2
I've found that very useful. Been able to get every AOSP/CM based ROM to boot by editing the updater-script to match the correct partition.
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion? That was the only bug I've found. Unfortunately, that flared up my phone OCD enough to go back to the 4.3 leak.
Thanks for putting this thread together, OP!
illogic6 said:
x2
I've found that very useful. Been able to get every AOSP/CM based ROM to boot by editing the updater-script to match the correct partition.
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion? That was the only bug I've found. Unfortunately, that flared up my phone OCD enough to go back to the 4.3 leak.
Thanks for putting this thread together, OP!
Click to expand...
Click to collapse
Your Welcome. So I read on the other thread and I know myself and others are looking at how we can port other ROMs specifically touchwiz over to the G the partition as you know is an issue but I think with collaboration can be solved soon.
Keep it coming let's solve problems!
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Your Welcome. So I read on the other thread and I know myself and others are looking at how we can port other ROMs specifically touchwiz over to the G the partition as you know is an issue but I think with collaboration can be solved soon.
Keep it coming let's solve problems!
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I took a TW ROM and edited the script for our devices. It boots, but the display never kicks on. You get the boot animation sound and it even mounts the storage on my computer.
illogic6 said:
I took a TW ROM and edited the script for our devices. It boots, but the display never kicks on. You get the boot animation sound and it even mounts the storage on my computer.
Click to expand...
Click to collapse
Wow that's great maybe you can help me with my script it sounds like your further along than some. I wonder what would cause the display bug doesn't sound like a boot issue
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Wow that's great maybe you can help me with my script it sounds like your further along than some. I wonder what would cause the display bug doesn't sound like a boot issue
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
illogic6 said:
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion?
Click to expand...
Click to collapse
I think this might be fixed in the newest CM nightly. I've took about 20 selfies with the front facing camera and haven't had distortion at all. Before I'd get it every 3 or 4 photos.
Edit: Disregard the above. The problem is back, but I'm thinking it might be the 4.3 camera zip I've been using. Hmmmmmmm......
I think I jumped the gun a bit on rooting my I9505G right when I got it. I've never successfully rooted it, but I managed to get on the 4.3 ROM with a few quirks here and there. My ultimate goal is to get Paranoid Android with halo running, but I'll have to dedicate a day to the whole process. I'll be keeping track of this thread.
illogic6 said:
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
Click to expand...
Click to collapse
Thanks a lot I will take a look tomorrow and see what I can do
Sent from my GT-I9505G using Tapatalk 2
illogic6 said:
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
Click to expand...
Click to collapse
Great work Illogic I wonder why TW will not display I tried as well but I did not get as far as you mine fails during the installation.
Also did you see my post on getting Cygwin to set device mount points that in itself will speed things up
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Great work Illogic I wonder why TW will not display I tried as well but I did not get as far as you mine fails during the installation.
Also did you see my post on getting Cygwin to set device mount points that in itself will speed things up
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I haven't used Cygwin before. I'll take a look at it today.
Also going to mess around with TW a little more. Maybe we just need some libs from the stock 9505g rom or something.
Update: I'm afraid I may have mislead you earlier. It appears that you need more than just the updated update-script in order to get touchwiz to boot. You also need a kernel from one of the 4.3 leaks. Here's the one I've been using. (Attached) Not only does it boot, but the soft keys work and you can hear the sound effects of the lock screen. I'm very close.
illogic6 said:
I haven't used Cygwin before. I'll take a look at it today.
Also going to mess around with TW a little more. Maybe we just need some libs from the stock 9505g rom or something.
Update: I'm afraid I may have mislead you earlier. It appears that you need more than just the updated update-script in order to get touchwiz to boot. You also need a kernel from one of the 4.3 leaks. Here's the one I've been using. (Attached) Not only does it boot, but the soft keys work and you can hear the sound effects of the lock screen. I'm very close.
Click to expand...
Click to collapse
Wow Illogic your close bro thanks for your hard work the libs does sound like it would cause the display problem I'm gonna play around with this too. All I did was unpack stock 4.3 and zip and deo the files with root. The problem I am having is that I am still learning U-scripts and so I cannot get anything to flash. I get failed on 0p21 even though its changed. Maybe I can pm you what I did later and get your feedback cuz your miles ahead of me
Sent from my GT-I9505G using Tapatalk 2
I've merged libs from the leaked 4.3 build into the TW ROM without overwriting anything. Didn't seem to change anything. At this point, I'm playing with magic I don't understand so not sure how much farther I'm going to get.
Would really like figure out which files in the system are responsible for the display. Perhaps we need to overwrite those files. Google is failing me so far.
---------- Post added at 04:45 PM ---------- Previous post was at 04:29 PM ----------
Tada! :victory:
The error message goes away. Right now, the web browser force closes... that might be because of the ROM I was modifying. What I did was use the 4.2.2 kernel that shipped with the google play phones. That booted AND activated the display.
http://i.imgur.com/HZaraPK.jpg
. Ok, i will not introducing me as i belive man's dignity depends on his works,...so let's come to the point, many of u know that google has released so many Android one device & all of them doesn't have stock rom flashable zip available as mine is KPX44...so i decided to share my works on this in xda, & sharing a way on creating flashable zip of any 4.4.x or 5.x rom for any Android One phones.....
Today i will give u a meta-inf folder & inbuilt read me.txt which will direct u on how to do this which will make your rom flashable via any custom recovery....
Download required files from attachment & then extract
the inside content & follow read me first.txt carefully....
Thanks all for reading.... & any query about this don't forget to comments here.....
Great effort ....
I personally tried this on 5.1 stock ...
So I suggest some corrections
Inside com/android folder this file otacert is really not needed
That file is cm ota certificate which nothing to do any thing with other custom ROM or stock ROM and even if these files present it won't harm also ....
If you are making zip for stock ROM
symlink also differ from ROM to ROM depending upon contents of xbin and bin folders. Along with version of busybox used in respective ROM ....
So modding scripts inside the updater script is needed depending upon contents and files of ROM ....either ROM is KitKat or Android L
Any way great effort mate thanks so much ....
Sent from my Micromax AQ4501 using Tapatalk
Thanks Adi for your advice, i know otacert is not needed but i m too lazy to remove it.... & belive me or not this will definitely works with any rom, i have tried with several & they boot fine... so don't need to worry about it...& finally i make this script universal so what it will works anyhow....
d41x4x said:
. Ok, i will not introducing me as i belive man's dignity depends on his works,...so let's come to the point, many of u know that google has released so many Android one device & all of them doesn't have stock rom flashable zip available as mine is KPX44...so i decided to share my works on this in xda, & sharing a way on creating flashable zip of any 4.4.x or 5.x rom for any Android One phones.....
Today i will give u a meta-inf folder & inbuilt read me.txt which will direct u on how to do this which will make your rom flashable via any custom recovery....
Download required files from attachment & then extract
the inside content & follow read me first.txt carefully....
Thanks all for reading.... & any query about this don't forget to comments here.....
Click to expand...
Click to collapse
Would you please do the same for N900AUCUBMI1 (Samsung Galaxy Note 3 N900A At&T)?
Hello everyone,
I have successfully built a package for this device. While the factory images is android-6.0.1_r5, this package features android-6.0.1_r10 along with the optimization flags I use for my other devices.
Instructions:
You need to get a custom recovery, this recovery should work
Boot into twrp
flash the package
optional: factory reset.
I haven't tested this as I am at work currently, so if anyone want to try before I get home do it
LINK
XDA:DevDB Information
AOSP for Pixel C, ROM for the Google Pixel C
Contributors
Khaon, Namastaz
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Beta Release Date: 2016-01-12
Created 2016-01-12
Last Updated 2016-01-12
Sweet! Does this have root integrated, by chance?
oRAirwolf said:
Sweet! Does this have root integrated, by chance?
Click to expand...
Click to collapse
No it doesn't. I could tho, I will see how thing evolves. I had my nexus 10 ramdisk patched for SuperSU. But I think now the flashing package cheks your partitions.
Guys just a reminder: don't flash SuperSU ZIP directly. That goes for stock as well as builds like khaon's (just a heads up), but rather one of the existing root options. Flashing a ZIP that tries to modify the kernel, like SuperSU systemless will fail on the Pixel C and might semi-brick your tablet.
cheep5k8 said:
Guys just a reminder: don't flash SuperSU ZIP directly. That goes for stock as well as builds like khaon's (just a heads up), but rather one of the existing root options. Flashing a ZIP that tries to modify the kernel, like SuperSU systemless will fail on the Pixel C and might semi-brick your tablet.
Click to expand...
Click to collapse
I read somewhere you were saying that the boot image is chromeos alike. Could you link me some source-code so I can see and understand the differences and how chromeos bootimage are built ? I looked at the chromeos's sources but i couldnt figure out where to look at.
Basically the kernel image is a depthcharge (the bootloader) payload that contains the Android kernel which then boots Android.
Depthcharge (bootloader source code with fastboot code): https://chromium.googlesource.com/chromiumos/platform/depthcharge/
Other relevant project there is also vboot_reference.
---------- Post added at 11:49 AM ---------- Previous post was at 11:37 AM ----------
It's not just ChromeOS-like... up to the point where the Android kernel boots Android it's completely like on a Chromebook.
But, sourse code?
So is this using the stock boot image?
Sorry for the late reply...
Martin_Devil said:
But, sourse code?
Click to expand...
Click to collapse
Ewww, I am using this android revision
This tag points to the marshmallow-mr1-release.
There are no sources as it was built with the default sources, however, this was the build platform
bill3508 said:
So is this using the stock boot image?
Click to expand...
Click to collapse
Yes it is using the stock boot image.
Thank you! Could someone please upload the build.prop file? TIA!
Thanks a ton man. I've heard this device is more difficult than other devices to build for. When my type C cables and adapters show up tomorrow I will be unlocking the bootloader, flashing TWRP, nand backup, and then I'm going to try your ROM and then the kernel that's available. So it's going to be a good day .
Sjflowerhorn said:
Thanks a ton man. I've heard this device is more difficult than other devices to build for. When my type C cables and adapters show up tomorrow I will be unlocking the bootloader, flashing TWRP, nand backup, and then I'm going to try your ROM and then the kernel that's available. So it's going to be a good day .
Click to expand...
Click to collapse
You may just want to root the stock ROM. This ROM has not been updated to the new base, which has fixes for the touchscreen issues.