Database Info

A fix for POLA100, Haret and waiting for notbusy error

I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post

Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it

I update this option in the kernel.
Now double vibration is disable by default.

You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye

This flag now do nothing, so it's indifferent

GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!

@foxct2005 : you can flash it month ago!
All these problems are only for haret!

l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.

big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!

leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.

Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..

DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.

thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much

loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.

leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.

loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).

leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol

loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?

leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...

loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.

[DEV] [ALPHA] CyanogenMod 7.2

Hi everybody!
Today I share my CM7.2 build and the device folder needed for build.
Firstly, here is the flashable zip:
http://depositfiles.com/files/3ppjnzlbd
Just put it to your SD card and flash with CWM.
What works:
- It boots.
- Theme chooser.
- Screenshot.
- Sound playing and recording.
- GPS
- Vibration (Sometimes buggy.)
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
It is going to be a very hard work to make it fully functionable. In the followings, I share my CM7.2 (and CM7. It is the same.) device folder. Here is a little readme for building. I assume the devs who are involved in the CM-development already know this (especially the first steps).
- Check out the latest CyanogenMod 7.2 sources:
repo init -u git://github.com/CyanogenMod/android.git -b gb-release-7.2
repo sync
- Put the device files into device/samsung/galaxyr
- Move cyanogen_galaxyr.mk (from the attached zip) into vendor/cyanogen/products directory.
- Open vendor/cyanogen/vendorsetup.sh and add the following line:
'add_lunch_combo cyanogen_galaxyr-eng' (Without quotes)
- Open vendor/cyanogen/AndroidProducts.mk and add the following:
'$(LOCAL_DIR)/cyanogen_galaxyr.mk' (Without quotes)
- Go to your device folder (device/samsung/galaxyr), put your phone on USB and run extract-files.sh
(It is important to run in the device folder, because it works with relative paths!)
(Your phone must have a stock or stock-based rom to copy the necessary proprietary files!)
- In your top CM source dir, execute:
'. build/envsetup.sh' (Without quotes)
- Finally:
'brunch cyanogen_galaxyr-eng' (Without quotes)
- Wait for it to finish. Flash and enjoy!
Here is the link for the GitHub repository:
https://github.com/Adam77Root/android_device_samsung_galaxyr
Some information about the files:
- The files (especially galaxyr.mk) are bloated with options and settings. I have concerns about the usefulness of some of them. We may not need them in a final/stable build.
- The kernel is the stock ZSLE6 kernel.
- gpswrapper, libaudio, libexifa, libjpega and libsensors were copied from c1-common with little modifications.
Some notices I have come across during the development:
- If we set TARGET_HAVE_TEGRA_ERRATA_657451 to true, we get a plenty of segmentation faults. On CM9, I was able to trace back the problem to this setting! CM7 (and obviously 7.2, I didn't tried) doesn't show the segfaults, probably because init and adb can't load. That's why TeamGalaxyR's rom boots to Samsung splash screen. If you try 'adb shell' on that rom, it immediately closes, because it cannot connect. After I had set this option off, I was able to build working images.
I hope other developers will start working on CM as soon as they can. It is a great project. I will also put every effort into this project, but I won't have access to my files for a week from tomorrow. However, I will stay tuned and be able to post here.
I attach two screenshots I took yesterday.
UPDATE:
Epsylon3 made some progress. The most important: Wifi is working now!!
Get it here: http://dedib.ath.cx/galaxyr/
Every modification to devices have risks. Flash this at your own risk!
Have fun and enjoy!

Thanks man (sorry i have no thanks left, i will hit later)
will try this , after i backup...

OMG OMG OMG... Now downloading. Will Flash and Revert with feedback soon... In short Reserved!!!
(⊙o⊙)Android & iOS Superuser!←_←

Ya.. Me too gonna test and feedback.... Reseved for feedback...
EDIT:
Its not working dude...
I flashed it over ZLES6 and also indian one... but it does not boot to the home screen...
And android logo comes up with black background and it just keeps on blinking...
No success on my phone
EDIT:
Sorry for wrong info.. I forgot to completewipe the device.. Its booting fine and the issues above mentioned are present.. however thanks a lot dude......

Hello Adam77Root Will you pls add some screenshot of it
Also Thanks Given

I am sad that i am off the system. Someone flash it and test it. Finally CM7.2 on r. Next would be fully working cm7 and later cm9(i hope.). Thanks given
Sent from my GT-I9103 using xda app-developers app

Thank you everybody! I added two screenshots to the first post.

in the office now,,can't donwload here due to limited downloads here..will test it at homies...:laugh::fingers-crossed::cyclops:

That's one small step for man, one giant leap for mankind. :laugh::laugh:

Adam77Root said:
Hi everybody!
Today I share my CM7.2 build and the device folder needed for build.
Firstly, here is the flashable zip:
http://depositfiles.com/files/3ppjnzlbd
Just put it to your SD card and flash with CWM.
What works:
- It boots.
- Theme chooser.
- Screenshot.
- Sound playing and recording.
- GPS
- Vibration (Sometimes buggy.)
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
It is going to be a very hard work to make it fully functionable. In the followings, I share my CM7.2 (and CM7. It is the same.) device folder. Here is a little readme for building. I assume the devs who are involved in the CM-development already know this (especially the first steps).
- Check out the latest CyanogenMod 7.2 sources:
repo init -u git://github.com/CyanogenMod/android.git -b gb-release-7.2
repo sync
- Put the device files into device/samsung/galaxyr
- Move cyanogen_galaxyr.mk (from the attached zip) into vendor/cyanogen/products directory.
- Open vendor/cyanogen/vendorsetup.sh and add the following line:
'add_lunch_combo cyanogen_galaxyr-eng' (Without quotes)
- Open vendor/cyanogen/AndroidProducts.mk and add the following:
'$(LOCAL_DIR)/cyanogen_galaxyr.mk' (Without quotes)
- Go to your device folder (device/samsung/galaxyr), put your phone on USB and run extract-files.sh
(It is important to run in the device folder, because it works with relative paths!)
(Your phone must have a stock or stock-based rom to copy the necessary proprietary files!)
- In your top CM source dir, execute:
'. build/envsetup.sh' (Without quotes)
- Finally:
'brunch cyanogen_galaxyr-eng' (Without quotes)
- Wait for it to finish. Flash and enjoy!
Here is the link for the GitHub repository:
https://github.com/Adam77Root/android_device_samsung_galaxyr
Some information about the files:
- The files (especially galaxyr.mk) are bloated with options and settings. I have concerns about the usefulness of some of them. We may not need them in a final/stable build.
- The kernel is the stock ZSLE6 kernel.
- gpswrapper, libaudio, libexifa, libjpega and libsensors were copied from c1-common with little modifications.
Some notices I have come across during the development:
- If we set TARGET_HAVE_TEGRA_ERRATA_657451 to true, we get a plenty of segmentation faults. On CM9, I was able to trace back the problem to this setting! CM7 (and obviously 7.2, I didn't tried) doesn't show the segfaults, probably because init and adb can't load. That's why TeamGalaxyR's rom boots to Samsung splash screen. If you try 'adb shell' on that rom, it immediately closes, because it cannot connect. After I had set this option off, I was able to build working images.
I hope other developers will start working on CM as soon as they can. It is a great project. I will also put every effort into this project, but I won't have access to my files for a week from tomorrow. However, I will stay tuned and be able to post here.
I attach two screenshots I took yesterday.
Every modification to devices have risks. Flash this at your own risk!
Have fun and enjoy!
Click to expand...
Click to collapse
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom

azhar.munshi said:
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
Click to expand...
Click to collapse
The thread is tagged as [DEV]. It is not a functional rom, only a preview. Don't try it if you don't want.
Sent from my GT-I9103

azhar.munshi said:
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
Click to expand...
Click to collapse
First LEARN to appreciate the work man, !!

gearbox87x said:
That's one small step for man, one giant leap for mankind. :laugh::laugh:
Click to expand...
Click to collapse
:good:

Marked as DEV man..
First show some respect. He is trying to do something that Samsung cannot do.
Encourage, but dont ever EVER discourage..
Kudos to the Dev. I will surely test it..

azhar.munshi said:
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
Click to expand...
Click to collapse
You have to understand what a huge leap this is in the development of CynaogenMod for our device...
this ROM is obviously not suitable for daily use.... but this ROM gives us a ray of hope that a fully functional CynaogenMod working on our galaxy r is just round the corner.... Kudos to the developer for such an outstanding development and hope he provides a fully functioning CM 7.2 very soon
Sent from my GT-I9103 using xda app-developers app

@OP to get rid of such things better change title as PRE ALPHA or something.

I tested....
i can't wait for the Full release...!!
really appreciable Work man....!

great..

Thank you everybody! If you know somebody, who can help in development, please contact him/her. I will definitely write to Epsylon3. I'm not really familiar on the forum yet.
xlm13x said:
@OP to get rid of such things better change title as PRE ALPHA or something.
Click to expand...
Click to collapse
I append that tag.
gearbox87x said:
I tested....
i can't wait for the Full release...!!
really appreciable Work man....!
Click to expand...
Click to collapse
Thanks! Creating a full/stable release will take a lot of time.

Hey thnx for creating cm 7 for our device. but i see that u r using 2.3.7 as the android version. Cant it be ics. Plz plz try to do this i luve ics and we hv been waiting for ics from a long time.

[Q]Compiling from source for SGS4G

Hey guys i need a little guidance. I'm trying to compile a SGS4G version of the CM10.1 ROM ive been building for the grouper and running in to some issues. For now Im using airfluip1's Kernel and device tree with source from CM and my Github. To narrow down the issues I swiched back to the stock 4.6 toolchain till i can get this working. It builds fine with no errors but comparing it to airfluip1's roms zip file i only have the boot.img, system folder, and META-INF folder. When i add the missing files like ex: updater.sh, modem.bin, bml_over_mtd.sh...etc wont go past the splash screen and dosent even make it to the bootanimation :crying: and i end up loseing CWM. if i switch my boot.img out with airfluip1's it fixes everything, boots right up, CWM is working properly, and the ROM is fine other than the Known CM10.1 bugs like multiple text, network issues. I never compiled a ROM that had the recovery with the boot.img and don't know if there's someting special you have to do with it to get it to work. any help is appreciated thanks guys

It might be that the latest kernel commits cause the rom not to boot. If you look up a guide on how to do a git reset in the kernel directory you might be able to compile a bootimage that works fine.
The kernel source is under
kernel/samsung/galaxys4gmtd
If you do a git log in that directory you will see the commit history with the hashes for each commit. If you do
git reset --hard sha1_hash
You can go back to a previously working commit, which might be trial and error
To speed up your testing process, instead of compiling the whole rom again you can try doing a
mka bootimage
Instead of
mka bacon
As far as the missing files, I don't have any input on that.
I'm finally back with my build rig and I finished syncing cm10.1 last night so I'll be trying to get some builds going tonight too.

FBis251 said:
It might be that the latest kernel commits cause the rom not to boot. If you look up a guide on how to do a git reset in the kernel directory you might be able to compile a bootimage that works fine.
The kernel source is under
kernel/samsung/galaxys4gmtd
If you do a git log in that directory you will see the commit history with the hashes for each commit. If you do
git reset --hard sha1_hash
You can go back to a previously working commit, which might be trial and error
To speed up your testing process, instead of compiling the whole rom again you can try doing a
mka bootimage
Instead of
mka bacon
As far as the missing files, I don't have any input on that.
I'm finally back with my build rig and I finished syncing cm10.1 last night so I'll be trying to get some builds going tonight too.
Click to expand...
Click to collapse
Thanks for the reply ... I've been having this issue for almost a week.. I might have set it up wrong I've been just doing brunch galaxys4gmtd to start the build. I'll have to look into mka. Should the kernel source be in kernel/samsung/galaxys4gmtd? In his device/samsung/galaxys4gmtd/BoardConfig.mk its targeting the kernel source to kernel/samsung/aries so that where I put it
EDIT: Was just set up weird by me...had to re add the vendersetup.sh back that he deleted from the device tree, did a lunch full_galaxys4gmtd-userdebug, then brunch galaxys4gmtd, and it compiled fine with the files I was missing and the kernel booted :beer:
Sent from my Nexus7 using Tapatalk HD

DJLamontagneIII said:
Thanks for the reply ... I've been having this issue for almost a week.. I might have set it up wrong I've been just doing brunch galaxys4gmtd to start the build. I'll have to look into mka. Should the kernel source be in kernel/samsung/galaxys4gmtd? In his device/samsung/galaxys4gmtd/BoardConfig.mk its targeting the kernel source to kernel/samsung/aries so that where I put it
EDIT: Was just set up weird by me...had to re add the vendersetup.sh back that he deleted from the device tree, did a lunch full_galaxys4gmtd-userdebug, then brunch galaxys4gmtd, and it compiled fine with the files I was missing and the kernel booted :beer:
Sent from my Nexus7 using Tapatalk HD
Click to expand...
Click to collapse
Awesome, I'm glad you got it working. . I haven't tried an aries build yet, but yes BoardConfig.mk is correct. You should try doing:
lunch cm_galaxys4gmtd-userdebug
mka bacon
I'm not sure, but the full_ prefix might be preventing the files that help flash the rom to be included with the zip file.

good job.
Also, yes kernel should be in kernel/samsung/aries.
EDIT: it is a smart decision not to use my airfluip1 stuff, and rather those from teamuserdebug.
Why, well, my latest kernel tree was only used to pull request to anak1n, so it is not even the kernel with my changes. So FFC/Compass/latests fixes won't be there.
Also, you might be using the common aries common from cyanogenmod... FFC from device tree side will be borked, and Aries Parts won't work.
Please use teamuserdebugs repos.
---------- Post added at 10:10 PM ---------- Previous post was at 10:05 PM ----------
FBis251 said:
Awesome, I'm glad you got it working. . I haven't tried an aries build yet, but yes BoardConfig.mk is correct. You should try doing:
lunch cm_galaxys4gmtd-userdebug
mka bacon
I'm not sure, but the full_ prefix might be preventing the files that help flash the rom to be included with the zip file.
Click to expand...
Click to collapse
Or brunch cm_galaxys4gmtd-eng
which runs both commands, and the eng builds are better since you have a debuggable kernel.

Thanks for the tip i used team userdebug's repos and roms been running great haven't had time to mess with the updated toolchains yet but il have something up to play with in a day or two
Sent from my SGH-T959V using Tapatalk 4 Beta

Multi Boot Menu for Xperia Z1 Compact

Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse

No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:

munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app

Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it

Sounds definitely awesome!

Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.

Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!

munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?

XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!

munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL

XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!

munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.

New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!

I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?

munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback

Solved! Will give you soon cm11 in multiboot!

munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:

Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!

Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47

Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?

[DEV ONLY]{RECOVERY] TWRP 2.3 GB

I have tried to compile TWRP 2.3.
It compiled with errors, but after solving a few errors, it was built successfully.
However, on flashing the zip via CWM, no effect took place, I am attaching my TWRP.
Anybody with knowledge and experience can help me compiling a successful build.
XDA:DevDB Information
TWRP 2.3, Tool/Utility for the Samsung Galaxy Y GT-S5360
Contributors
Nachiket.Namjoshi, DC07
Version Information
Status: Testing
Created 2014-06-08
Last Updated 2014-06-08

Downloads
DOWNLOADS
Removed
Go Here for working Builds: https://forum.xda-developers.com/galaxy-y/development/recovery-twrp-3-0-3-0-touch-recovery-t3550609

Reserved
Problems and Changelogs
Changelogs
latest update: Sun, Jun 8 ,2014.
v1.0a(alpha)
-Initial build (doesnt boot into twrp)
Problems and Errors(Intended for the ones who are willing and are able to help)
P.S you can read it but in case you dont understand what you are reading please refrain from posting questions about them in this thread.
If you are really curios, shoot me a PM or USE_THIS_LINK
Several errors (so cant paste) while compiling a otapackage (make -j4 recoveryzip)
Code:
Several mistakes in [B]bootable/recovery/updater/install.c[/B]
some [B]int[/B] not already declared,
some [B]arguments[/B] not appropriately passed in some [B]functions[/B] namely
[B]make_ext4fs(const char *filename, const char *directory,
char *mountpoint, int android, int gzip, int sparse);[/B]
and applypatch funtion...
all this is found on install.c
probably the reason why things arent built properly while [B]make recoveryzip[/B]
hence the size... 1mb
A few errors about the libs which are never compiled !
Code:
collective errors:
libopenaes.so, libblkid.so not a prelink map
These libs are never ever built !
Hence the errors.
Update01
After Solving and re-writing almost all of install.c and the update folder
got this stop
Code:
make: *** No rule to make target `out/target/product/totoro/obj/STATIC_LIBRARIES/libselinux_intermediates/libselinux.a', needed by `out/target/product/totoro/obj/EXECUTABLES/updater_intermediates/LINKED/updater'. Stop.
make: *** Waiting for unfinished jobs....
I think I should halt for today....
update02
recovery.img looks fine, however, there seems to be some problem
if I mount the img (dont ask me how to )
and calculate the size of all the files and folders,
it roughly comes upto 738 kb
but recovery.img is of 4.7 mb
Moreover, If i try
Code:
[B]make -j4 recoveryzip[/B]
there are still errors in install.c (make_ext4fs function errors)
Will try to dig into this again.
and update the thread with my findings :cyclops:
till then, if anyone can advice something, you can.
Update03
No progress yet...
Taking a rest now,
and i need a lil help in this... if anybody has ported before, plz post it here
Brief overview of things:
Getting a recovery.img of 4.7 mb but when executing
Code:
make -j4 recoveryzip
I get the recovery.zip to be 577.6 kb
however, by playing with the code, Its building the extra libs
but NOT adding them to the zip
so, need a proper updater-script

i think you must include it on a kernel., because the recovery of our sgy is not separated to the kernel.,

rio. said:
i think you must include it on a kernel., because the recovery of our sgy is not separated to the kernel.,
Click to expand...
Click to collapse
not really... I believe that if a flashable CWM can be created... a flashable TWRP can also be created...
Anyways, I was going to try dumping it into a prebuilt kernel...
but the issue is my odin doesnt work (in case of bricks)
and it can also hardbrick the device if dumped on to a kernel

Nachiket.Namjoshi said:
not really... I believe that if a flashable CWM can be created... a flashable TWRP can also be created...
Anyways, I was going to try dumping it into a prebuilt kernel...
but the issue is my odin doesnt work (in case of bricks)
and it can also hardbrick the device if dumped on to a kernel
Click to expand...
Click to collapse
oohh sorry i didn't wsee the zip. i thought you just build only img..
i checked the zip and there is no killrecovery.sh which is called by the updater-script..

rio. said:
oohh sorry i didn't wsee the zip. i thought you just build only img..
i checked the zip and there is no killrecovery.sh which is called by the updater-script..
Click to expand...
Click to collapse
oopss... im soo sorry, uploaded the wrong zip
EDIT:
Thread has been updated for the Devs and ppl who can help me.

Nachiket.Namjoshi said:
oopss... im soo sorry, uploaded the wrong zip
Click to expand...
Click to collapse
i checked your zip..
i guess you haven't used any theme.. there is no any images, fonts, twrp,ui.xml in res folder.. and i'm not sure if there are any 240x320 theme officailly available..
and you are missing 30+ libraries and some binaries in the sbin folder..
and mke2fs.conf,twrp.fstab in the /etc folder
and supersu folder
and selinux stuffs..
don't know why you are getting the install.c errors..
which branch are you using.. you need to use latest cm11 with twrp patches or omni branch to build twrp 2.7.x
for the not a prelink map error i think you need to add shared libraries or somethinh like that in prelink-linux-arm.map
anyways.. nice work. and keep trying... you can also ask for help in the official twrp thread here at xda..

psych.half said:
i checked your zip..
i guess you haven't used any theme.. there is no any images, fonts, twrp,ui.xml in res folder.. and i'm not sure if there are any 240x320 theme officailly available..
and you are missing 30+ libraries and some binaries in the sbin folder..
and mke2fs.conf,twrp.fstab in the /etc folder
and supersu folder
and selinux stuffs..
don't know why you are getting the install.c errors..
which branch are you using.. you need to use latest cm11 with twrp patches or omni branch to build twrp 2.7.x
for the not a prelink map error i think you need to add shared libraries or somethinh like that in prelink-linux-arm.map
anyways.. nice work. and keep trying... you can also ask for help in the official twrp thread here at xda..
Click to expand...
Click to collapse
Exactly... missing libs are the reasons, but there is absolutely no way of making these libs individually, well, I can try porting from other device as my last option..
and the most head-banging error is those install.c :/
I use twrp 2.7 branch (refer the link in the OP)
and Im building this with CM7 sources as it was GB

i tried to run your recovery file thru terminal but it doesn't show any action, can u pls upload your source?
i agree with @psych.half
some files are missing that must be call by recovery..
i don't know much about compiling a binary so pls update this thread on your progress. am willing to help

rio. said:
i tried to run your recovery file thru terminal but it doesn't show any action, can u pls upload your source?
i agree with @psych.half
some files are missing that must be call by recovery..
i don't know much about compiling a binary so pls update this thread on your progress. am willing to help
Click to expand...
Click to collapse
Yeh, Im currently updating github with todays changes...
I will now stop for today...
EDIT: Here, are the sources you asked for.

you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.

SpaceCaker said:
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
Click to expand...
Click to collapse
Yeah we got our mistake and reverted back to twrp2.3 and cm7 compatible build tools as Minus40 said.
He forgot to update the thread.
and the new twrp.zip in post #3 is twrp2.3,
stopped the work on this for today, will continue tomorrow,
Thanks for pointing it out anyways
Regards

recovery works on GT-S5367? (Galaxy Y TV)

EsromG5 said:
recovery works on GT-S5367? (Galaxy Y TV)
Click to expand...
Click to collapse
I doesn't work with original Galaxy y

Galaxy pocket devs
ı heard about galaxy pocket devs has finished twrp on pocket this can help you

Pocket has also new camera lib for cm9
Only proplem is Audio (On MadTeam)

SpaceCaker said:
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
Click to expand...
Click to collapse
Updated thread, sorry, was in a hurry yesterday, forgot to update it just like post #13 by @DC07 says...
Sorry,
So, I can smell the victory though

Good News
I am getting a recovery.zip of a larger size, and finally, the build tools are working great and building the missing libs too...
thanks anyway @Minus40 for giving me the libs, but those libs are not gonna work on this device, its a bit complicated architecture...
Anyway, this is a good break through, ill update the github by the end of the day.
I hope to have a working TWRP by the weekend
presently, build tools error is that it doesnt dump proper permissions for the extra libs, will try give them the proper permissions (which i dont really know, which perms to give), a few days more and it'll be done.

Nachiket.Namjoshi said:
I am getting a recovery.zip of a larger size, and finally, the build tools are working great and building the missing libs too...
thanks anyway @Minus40 for giving me the libs, but those libs are not gonna work on this device, its a bit complicated architecture...
Anyway, this is a good break through, ill update the github by the end of the day.
I hope to have a working TWRP by the weekend
presently, build tools error is that it doesnt dump proper permissions for the extra libs, will try give them the proper permissions (which i dont really know, which perms to give), a few days more and it'll be done.
Click to expand...
Click to collapse
Try twrp 2.2.2.0 for cm7.