Related
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S 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 version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
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.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img 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)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
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 Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
Q&A for [ROM][PORT][04.10] OnePlus One Stock ROM | CM11S | Verizon Edition | v4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I'm having trouble flashing v4 on my M7. The first time I tried flashing it, it said the install failed on my device because it is an "m7" and not an "m7vzw". I looked in previous posts in the ROM thread and I saw the OP recommended to check if the device is actually an "m7vzw" (which mine is), and then replace the original updater-script in the ROM zip folder with a different one that the OP uploaded. I did that, and tried flashing it again, but then it said this in recovery:
read_file() loading "tmp/releasekey" failed:
No such file or directory
E: Error executing updater binary in zip '/sdcard/CyanagenMod_11S_m7vzw_v4.zip'
Error flashing zip '/sdcard/CyanogenMod_11S_m7vzw_v4.zip'
I'm using TWRP v.2.8.0.2. Does somebody have any idea on how I can successfully flash this? I would really like to try it out.
That's what I meant. How can we get this ported over to the M8?
VMShock said:
I'm having trouble flashing v4 on my M7. The first time I tried flashing it, it said the install failed on my device because it is an "m7" and not an "m7vzw". I looked in previous posts in the ROM thread and I saw the OP recommended to check if the device is actually an "m7vzw" (which mine is), and then replace the original binary-script in the ROM zip folder with a different one that the OP uploaded. I did that, and tried flashing it again, but then it said this in recovery:
read_file() loading "tmp/releasekey" failed:
No such file or directory
E: Error executing updater binary in zip '/sdcard/CyanagenMod_11S_m7vzw_v4.zip'
Error flashing zip '/sdcard/CyanogenMod_11S_m7vzw_v4.zip'
I'm using TWRP v.2.8.0.2. Does somebody have any idea on how I can successfully flash this? I would really like to try it out.
Click to expand...
Click to collapse
WHY this rom cant work on my verizon one ，4 wiped。
[Q&A] [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Q&A for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ansh2000 said:
result is same as before.
Click to expand...
Click to collapse
TWRP 2.6.0.0 and ClockworkMod v6.0.5.3 upload pls.
can't install it
Hi ! I need help with this installation procedure, cause i put the code on the terminal emulator, and then, my cwm is deleted.. I want to try this cm rom ! Please help !
Problem with recovery
I didn't have problems before with installing any rom or recovery, I think I've passed through all of possible combinations, but this time, it's terribly buggy :/
I started from stock rom 2.3.6 XEO (as always) then installed CWM Custom Recovery "CWM-5.0.2.8_GAZZY.tar" (need some cwm to update, right?) but stock rom didn't find "flash_image" just like few other roms (arkas for ex.)
Finally Burnmode's KitKatSpecialEdition didn't alert about anything missing and it just jumped to the next line. (success I think, right?) The problem is that when I reboot into recovery it flashes a blank, black screen and reboots leaving my phone recovery-less ! What do I do wrong? Since then I tried many roms and most of them don't work anymore (no luck with cm10.2 for example, KitKat special edition works, so it's the only thing I can now run without bugs, but it's BurnMode's rom, it always works well)
I downloaded recovery.img "2014-12-04 22:43:18" which is the newest (at least now!) is there a problem with the recovery, my phone or maybe I am doing something wrong? My options are now very limited since many things crash my phone (can't flash a stock rom anymore, might be hard to do it again)
Hi
Thanks for your great work. I updated my cooper (s5830) to the latest release but my device won't boot. So I return back to the previous version.
For totoro??
Hi Sir, Im on Galaxy Y s5360 , no possibility for our totoro device?
Help!
help me when i'm trying to download cwm on github is error that i'm missing the Overall/Read permission. How can i fix it? Help
recovery
I couldnt download u recovery, u wot m8 with it i havrnt got perms, upload it normal or get REKT
Can we expect working cm12 on our devices? Or this is the end of the unofficial support?
The page is closed now. Is anybody known how long will be unable to download ROMs on this page? Are there any other links in which we can get RC14 for Callisto? Thanks for help!
Updates? LinkS?
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
anasahmad17 said:
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
Click to expand...
Click to collapse
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
steve8x8 said:
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
Click to expand...
Click to collapse
I tried finding the rom and the only one i could find on the inter-webs is here but the website is paid one so i cant download and i cant check the checksum
http://chomikuj.pl/kaktus47/Telefon....0.0-GT-I5510-callisto,4616249982.zip(archive)
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Prerequisites:
You must have flashed CWM6 using Odin before.
Also you need a second partition on your sdcard, formatted as ext4.
Preparation:
Put the files you need on the sdcard (normal vfat partition), shut down the phone.
Charge the phone's battery.
Now the really tricky stuff (if you mastered Odin, that's just a piece of cake though):
Start the phone into recovery.
Flash the ROM image, and wipe data.
Boot into Android, install and setup s2e to use the sd-ext partition.
Reboot into recovery.
Flash the gapps package, and possibly one of the keyboard zips (see http://forum.xda-developers.com/showpost.php?p=56625731&postcount=162 for those). You may have to switch off package checks in between.
Reboot into Android, and change your governor and io scheduler settings.
Done.
Edit: I've got requests to share the filespace - which should be accessible by link. I'm re-adding the URL now. Apologies to everyone who tried in vain
@steve8x8 Hi, I know it's been a long time but i hope you see this, but could you please be more specific with the steps? what files to use, what keys to press? Sorry it's been a while since i used this phone or any android phone, what odin version should i use?
Have you searched the 'net (and the archive.org) for the original 551 blog? It has/had a quite good explanation of almost everything related to this particular phone. Odin version doesn't matter much, I had used 4.34 (that was current when the instructions were written) and 4.43 IIRC, no difference. Make sure to get good instructions for the CWM flash, as this is the stage where most bricks happen.
To make things easier, I'm uploading the stuff related to the Odin step from my HD ("Odin" subfolder on GDrive), more than two years old. Use them on your own risk, and check the URLs provided.
Note that I didn't go directly for CM11, but installed CM10.2 first. I would have to read the instructions to tell whether this was actually necessary...
On the way, I upgraded the recovery (from the jenkins server that doesn't exist any longer, http://jenkins.androidarmv6.org/view/Developers/job/cm-recovery/24/ of Oct 2014) to 6.0.5.3. (IIRC I did this using the terminal emulator, not Odin, but that should be possible too. I'll upload the recovery.img)
You perhaps max have to create your own Odin-flashable recovery similar to the following (again, I assume no liability at all!):
- take a .tar.md5 as starting point, and unpack it (it's just a tar with a checksum appended)
- replace the recovery.img
- create a new tar file x.tar (name it as you like)
- (cat x.tar; md5sum x.tar) >x.tar.md5
- Odin flash that
I admit it becomes more and more difficult to keep the necessary tools, files, and instructions available and in shape for devices as old as this one (I'm still confused by the "KERNEL3" series.)
---------- Post added at 09:22 AM ---------- Previous post was at 09:00 AM ----------
Quick addendum: there's a new, stagefright-fixed cm11 available for callisto, see http://forum.xda-developers.com/showthread.php?t=2453085&page=27 - which is currently being debugged but looks promising (see page 29 of that thread)
---------- Post added at 10:09 AM ---------- Previous post was at 09:22 AM ----------
It seems that there's a lot of stuff still around if you search for the "galaxy-551" tag.
Bebek's GD might also be interesting (with Odin, CWM5, and more, but stopping at Gingerbread): https://docs.google.com/folderview?...SURkMEE&tid=0B-QaRW7SLPQPTHpaQXR5b1ZVMHc#list
1
bro help
thx for sharing
steve8x8 said:
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Click to expand...
Click to collapse
Please don't remove those files from gdrive!:good:
Danke sehr
I didn't plan to, and indeed they are still there. Is there anyone using a Callisto running CM11?
Last night I had a dream: There was a recent ROM upgrade for the Callisto (not sure whether Nougat or Oreo), and I had started to dig out all the old instructions and notes to make it happen.
Only in the morning, after having a big mug of coffee, I realized it was only a dream :'(
armv6 ghosts haunting...
Q&A for [ROM] CosmicROM [AOSP] [5.1] [DarkUI] [22 Mar 2015]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] CosmicROM [AOSP] [5.1] [DarkUI] [22 Mar 2015]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Unable to flash cosmic 5.1 status 7 error
i tried flashing the rom but i got a status 7 error, plz note that i m using an updated recovery and also i have also increased the internal memory of my i9082 in reference to another thread by @k2wl . plz help. the error says this rom is for i9082 and this device is a baffin. what should i do?
open zip then go to /META-INF/com/google/android/ folder and open updater-script with notepad++ or some editor compatible with linux style.
delete first line
" getprop("ro.product.device") == "i9082" || abort("This package is for "i9082" devices; this is a "" + getprop("ro.product.device") + "".");
"
and save file in zip again or if ask update it.
Thanks
dydy_vova said:
open zip then go to /META-INF/com/google/android/ folder and open updater-script with notepad++ or some editor compatible with linux style.
delete first line
" getprop("ro.product.device") == "i9082" || abort("This package is for "i9082" devices; this is a "" + getprop("ro.product.device") + "".");
"
and save file in zip again or if ask update it.
Click to expand...
Click to collapse
thx bro had the same problem will test it nd let u know
getting status error 7 even after flashing the recovery given by you.
error is saying is saying that yours is a baffin. currently i am using cosmic cm version 5.5 buld number KTU84Q.
i cant flash CosmicROM..with recovery philz touch
DJ Minh Bu said:
i cant flash CosmicROM..with recovery philz touch
Click to expand...
Click to collapse
please elaborate on the problem....is their any error message while installation ?
SMS
Hello.
Can I choose an operator for sending SMS, as well as with calls. ("Always ask")
waiting for the update
@k2wl bro wers the new update file we people are eagerly waitin for it dont take me wrong dude bt we all are huge fans of cosmic rom as well as your work hope we get to see the new file soon and we dont have to wait more and great work broda respect for u
Error 7 in build 20150323
@k2wl I downloaded your latest build of 23rd march still m stuck with the same status 7 error i even flashed my recovery again bt still with same trouble help me out as i badly love this rom
can i flash 5.0 gapps on this rom??????
Hello sir, can I flash lollipop 5.0 supported gapps on cosmic 5.1 ROM??????????
Still getting an error
I'm getting Baffin Error
I downloaded the new build posted but ain't working
Any solutions???
aaronjgeorge123 said:
I'm getting Baffin Error
I downloaded the new build posted but ain't working
Any solutions???
Click to expand...
Click to collapse
See post #4 and edit the script and it works
File Manager
I can't find File Manager in this ROM (cosmis 5.1). Please tell me how about it
azri harahap said:
I can't find File Manager in this ROM (cosmis 5.1). Please tell me how about it
Click to expand...
Click to collapse
Pick your favorite file manager from the play store and download it.
You can't find one the rom because there is no file manager included.
The file manager is a CM feature not AOSP, so you will miss more thing
See that is so hard
A small problem
In the 2nd update of this rom the status 7 error was not resolved....so i have tried removing the first line from the updater script....but then after installing and rebooting android logo flashes for a very long time...still not having any luck with it....i have used notepad++ to do all the updating and then again compressed all the files into a zip file....please tell me if i am doing something wrong or if i am missing something....
RichyE said:
Pick your favorite file manager from the play store and download it.
You can't find one the rom because there is no file manager included.
The file manager is a CM feature not AOSP, so you will miss more thing
See that is so hard
Click to expand...
Click to collapse
since cm 12 I never flash GAPPS. I prefer the '1 mobile market' in the hope that is in use less RAM. how do I can have a file manager without having to flash GAPPS? Please help me...
azri harahap said:
since cm 12 I never flash GAPPS. I prefer the '1 mobile market' in the hope that is in use less RAM. how do I can have a file manager without having to flash GAPPS? Please help me...
Click to expand...
Click to collapse
search for file manager in the 1mobile market and you will get allot to choice from
For example
ES File Explore
Solid Explorer
Pls help....
Pls help....
How to root (manual) for galaxy grand duos i9082 - CosmicROM [AOSP] [5.1] ?
Is this ROM support otg cable
I hope to be really
Can anyone add our device to the supported devices list ? This would be very helpful, especially since we have a large internal space, for testing out new ROMs...
Here is how to add support to any device :
https://forum.xda-developers.com/android/development/guide-dualboot-patcher-unsupported-t3647056
I wanted to try it, but I am using my phone on a daily basis and don't have an alternate VoLTE phone... Also I am a bit inexperienced in development... :crying:
Tried given steps..
1st latest version not worked when clicked on ROM, failed.
I tried bit old version say 9.3 build 179.. Clicking rom worked.
Then followed all steps but not seen X01BD device while patching zip.
This much i did.. Will check other ways.
Note: we need to check other or older version of dbp
sachinm said:
Tried given steps..
1st latest version not worked when clicked on ROM, failed.
I tried bit old version say 9.3 build 179.. Clicking rom worked.
Then followed all steps but not seen X01BD device while patching zip.
This much i did.. Will check other ways.
Note: we need to check other or older version of dbp
Click to expand...
Click to collapse
Thanks for trying
Did you follow the official method ? Which recovery are you using ? TWRP or PBRP ?
Yes
I have tried it finally... Both unofficial method as well as official..
1) Unofficial method does not seem to work, because the app crashes when we click on the ROMs section... This happens for all snapshots from 9.3.0.r340 onwards... I tried the snapshot before this one i.e. 9.3.0.r327 and there were no crashes. I continued with the unofficial method, flashed PATCH.zip, gave root permissions etc but this method did not work...
2) I tried the official method. I forked the project on Github, made the neccessary changes to the asus.yml file and created a pull request.
Here : https://github.com/chenxiaolong/DualBootPatcher/pull/1380
Now we wait for the changes to be merged with the main repo ... Then test the new release...
I didn't have enough bandwidth, otherwise would have built the apk from source myself... Still there is time ... I'll try to see if I can build the apk ....
Hey guys ... Can anyone please help in building this apk ?
Here is my repository which I forked from the official :
https://github.com/Tyakrish/DualBootPatcher
Just fork from my link and build the apk using the steps described here :
https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-from-source
And here :
https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-using-docker-images
Any update on DBP
sachinm said:
Any update on DBP
Click to expand...
Click to collapse
Unfortunately no... @chenxiaolong has not yet merged the commits with the main repo
There are a lot of commits still waiting...
You can check the status of the commit here:
https://github.com/chenxiaolong/DualBootPatcher/pull/1380
I dont currently have a build environment set up... Otherwise I would have built an unofficial version to test on our device...