Related
[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions..
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
Hi all,
This dev thread is to continue the multiboot thread that I starded few months ago in general section.
To read history of the project you can take a look here http://forum.xda-developers.com/showthread.php?t=2577211
With Multiboot, you can launch any ROM from your internal card or your external sdcard. It is a TWRP recovery ROM modified to add this feature.
This feature is possible thank's to kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827).
I adapted this method to be able to apply it quite easily on any android device.
This method includes few pieces of software ( sources will be published) :
kexec-hardboot : kernel patch from mkasic
hardboot-reserve : new kernel patch
kload-hardboot : new userspace program
Next part of the method is an on the fly modification of initrd ramdisk before injecting new kernel/initrd. Early versions of multiboot (before v1.2) were simply modify [on fs] section of init.rc to replace original block devices ( mmcblk0p14, mmcblk0p15 etc ) by loop devices pointing to img files.
Since Multiboot v1.2, a new method is used to replace original filesystems : a script replace original init binary, his goal is to prepare all the filesytems before launching original init.
All this method is done by shell scripts that you can check in /sbin and /multiboot directories when booted into recovery.
Creating img files (raw) is very efficient on internal sdcard as this card is formatted ext4 and img files can be thin provisiionnig ( sparse files ).
Unfortunaltely, external sdcard are offently fat32 or exfat formated. Those filesystems do not support thin provisionning ( note also that multiboot supprot only vfat for the moment ).
Creating img files on vfat filesystems is very long process and consume lot of space.
Version Multiboot V2.1 add support for ubuntu touch 14.04 support ( only img files )
Version .Multiboot V20 introduced a new feature : qcow2 support for external sdcard.
With qcow2 image files, we can create small images which grows only when needed.
You can check some video demonstrating features of multiboot on youtube channel : http://www.youtube.com/channel/UCefO8F4YX6qMQsqpBHTqTqQ
Main advantages of using qcow2 :
thin provisionning
snapshots
compression
liveboot ( livefull if small rom, "livedvd-like" if bigger roms )
Some problem (and solutions) of qcow2 :
need target kernel with nbd support - nbd is very easy to activate when compiling kernels but not already activated on kernels. Decimalman kernels already are compiled with it. http://forum.xda-developers.com/showthread.php?t=2226889
Slow speed on standard : speed on qcow2 especially when first installation is not good. To reduce this, livesnap booting mode gives very good speed.
suspend/resume : on tw43 kernels, deepsleep can hang the system. To correct it, their are 2 methods : adding a wakelock or apply a small patch to nbd.c sources.
Some details about qcow2 booting mode :
- standard : qcow2 images are acceded read/write directly on sdcard ( not recommended especially in firsts boot )
- livesnap : qcow2 images are acceded read, writes are done in zram snapshots. commit are done at reboot time : this is the recommended mod. If you install apps, you'd better to reboot first to commit qcow2. Note that if modifications are big, reboot can be long ( few minutes ), be patient. Note also that in this mode, I added a wakelock to fix suspend/reboot of tw roms.
- liveboot : same that livesnap but without commit - Same than a LiveCD in linux world. reboot speed is regular
- fulllive : only for small roms ( say ~500M ). All qcow2 are copied to zram at boot and mounted from memory. No internal/external card needed. very good speed.
- livesnap2 : same than livesnap but without wakelock. Best for speed and battery. Working except tw43. Download my modified dkp kernel to use this option on tw43 roms.
Important recommendations :
- when choosing qcow2, always choose the right nbd kernel as the last zip to install ( and don't reboot after Aroma installer )
take dkp kernels for tw43 and kk4.4.2 : http://forum.xda-developers.com/showthread.php?t=2226889
or kernels I compiled
- please follow videos on youtube
Here are last video I did to demonstrate qcow2 features. Some parts of video are boring ( during compression or commit ) but I wanted to let it go live to give an idea of processing times.
Downloads : http://www.androidfilehost.com/?w=files&flid=12801
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
reserved
First
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Love your work Philippe. This has been amazing to use for testing out multiple roms and still maintaining my daily driver. I'm a crack flasher so its nice having the options to constantly change.
Sent from my SCH-I535 using Tapatalk
Totally forgot about this, I'll have NBD included in my next kernel so this can work
this is awesome ! i been looking for muilt-boot since i got an S3 !
it's working great!
Awesome!
Now does it matter what bootloader you're on for this?
i want to try this... but the bandwidth Nazi's at work wont let me download and watch YouTube videos. would the main ROM need to be on the internal memory? or would it matter? just wondering.
Do these videos have audio? kinda hard to follow... or it just my laptop?
Restore
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
PwnCakes193 said:
Totally forgot about this, I'll have NBD included in my next kernel so this can work
Click to expand...
Click to collapse
I will add a link to your kernel in first message when it becomes compatible with qcow2 support.
vbetts said:
Now does it matter what bootloader you're on for this?
Click to expand...
Click to collapse
There is no prerequisite about bootloaders versions. Just be sure that your bootloader is unlocked ( I mean that you can install custom recovery images - for example, verizon 4.3 ota update locked the bootloader )
stanguay said:
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
Click to expand...
Click to collapse
As multiboot feature does not have relation with this part of twrp, not sure if it is linked with multiboot.
Do you have same behavour with original twr2.7.0 ?
Philippe,
ubuntu touch trusty in progress
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I remember the last time someone built Ubuntu Touch to the d2att S3, but we ran into the same issues as you previously mentioned. Will there ever be a way to get the data to work?
codemonkey98 said:
Will there ever be a way to get the data to work?
Click to expand...
Click to collapse
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Phil_Suz said:
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Click to expand...
Click to collapse
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
shekinahsmoke said:
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
Click to expand...
Click to collapse
Hi shekinahsmoke, no it is not necessary at all. It's better to install all zip in one shot, but I did this demo to show that you can come back to multiboot, select an already created rom and apply another zip ( gapps in this example ) even after first installation.
codemonkey98 said:
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
Click to expand...
Click to collapse
rani9990 said:
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Phil_Suz said:
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Click to expand...
Click to collapse
I'm glad to hear. I appreciate you shedding some light towards us with Ubuntu Touch and your support for multiboot. :good:
Hi All,
Multiboot v2.1 is now ready on same download link ( http://www.androidfilehost.com/?w=files&flid=12801 )
This version add support for unbutu touch 14.04.
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I would love to try your touch port I have been using your recoveries for a few weeks now and just flash the touch wip Rom that is on the site but to have a simi-working port to play with would be awesome.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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
Q&A for [kernel][stock][D85520P][init.d][bumped]Stock EXperience (for) You -- SEXY
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 [kernel][stock][D85520P][init.d][bumped]Stock EXperience (for) You -- SEXY. 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!
Sexy kernel question
Hello . Is it possible to create a version of the set selinux permissive . Alternatively, if there is any init.d script that is changing. Greetings
mnkowalski said:
Hello . Is it possible to create a version of the set selinux permissive . Alternatively, if there is any init.d script that is changing. Greetings
Click to expand...
Click to collapse
Hello,
I did it and i can share if you want but you better use init.d to do this:
Create a file named 07setpermissive in /etc/init.d folder with inside this simple code, and give 755 permission to this file (with a root explorer).
Code:
#!/system/sh
setenforce 0
Reboot, and it's done (SELinux is set to "permissive"). If you want to disable it, you can tape in a terminal emulator;
Code:
su
setenforce 1
If you really need, i can share the same thing done in ramdisk.
I would be grateful for it
For many people this will be useful . I would appreciate it if he had se linux kernel permessive
mnkowalski said:
For many people this will be useful . I would appreciate it if he had se linux kernel permessive
Click to expand...
Click to collapse
Done, links are in original thread OP http://forum.xda-developers.com/lg-g3/development/kernel-stock-experience-sexy-t3120751
or
http://forum.xda-developers.com/showpost.php?p=61061948&postcount=8
You can hit thank's if it helps
Maybe I'm doing something wrong but the scripts in the init.d do not work, so it just me . I created a script to test init.di was not a log file . When installed with supermarket universal program init.d script then she began to move. I installed both kernels and nothing
mnkowalski said:
Maybe I'm doing something wrong but the scripts in the init.d do not work, so it just me . I created a script to test init.di was not a log file . When installed with supermarket universal program init.d script then she began to move. I installed both kernels and nothing
Click to expand...
Click to collapse
Did you give the right permissions to your script?
What does this script (code)?
permission is ok
Script :
#!/system/bin/sh
echo init.d is working >> / storange /emulated/0/initdsupport.txt
Using the program -> script starts , uninstall the program and stops working script
Sorry for bad english
mnkowalski said:
permission is ok
Script :
#!/system/bin/sh
echo init.d is working >> / storange /emulated/0/initdsupport.txt
Using the program -> script starts , uninstall the program and stops working script
Sorry for bad english
Click to expand...
Click to collapse
Try to write in /data, it should work
echo "init.d is working" >> /data/initdsupport.txt
None of this after the change does not work still , but with the application from google play test log appears and init.d works. I give up. If I ask for a hint
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=pl
with this application works
mnkowalski said:
None of this after the change does not work still , but with the application from google play test log appears and init.d works. I give up. If I ask for a hint
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=pl
with this application works
Click to expand...
Click to collapse
It didn't work because the path of sdcard is not good in your script.
If you want to write log in sdcard (internal storage) the code must be
Code:
#!/system/bin/sh
echo "init.d is working" >> /mnt/sdcard/initdsupport.txt
instead of your
Code:
#!/system/bin/sh
echo "init.d is working" >> /storage/emulated/0/initdsupport.txt
I just tested it, and it works well with my moded 20p ramdisk, without need of another system mod.
You just have to use /mnt/sdcard instead of /storage/emulated/0
App you are talking about is an emulation of init.d (not real init.d, as ramdisk supports), it uses install-recovery.sh.
http://forum.xda-developers.com/showthread.php?t=1933849
Can I install any of these kernels over one of your previous 5.x ROMs ( such as Androidnow HD). Or do I need to install the entire new ROM ?
If I can install just the kernel then do I need to root it ?
Many thx
soupratt said:
Can I install any of these kernels over one of your previous 5.x ROMs ( such as Androidnow HD). Or do I need to install the entire new ROM ?
If I can install just the kernel then do I need to root it ?
Many thx
Click to expand...
Click to collapse
Hi,
I don't know if i understand well your questions.
I didn't test all possibles combos (all possibles shared stock or based stock) roms with these kernels (ramdisks) moded, i think you can understand that
You can easily test it and report the result if you want, I (we) 'll be interested to read this.
For that, you need to know how to flash a kernel (custom recovery is the best solution), how to backup the one you used before, how to boot on custom recovery with hard key for eventually restoring this one you backuped before, how to quit a secure boot error screen (removing battery) that you can meet with a bad kernel, and, of course, that root is really needed for doing all of that.
Posted without using google translation, sorry for my english
6ril1 said:
Hi,
I don't know if i understand well your questions.
I didn't test all possibles combos (all possibles shared stock or based stock) roms with these kernels (ramdisks) moded, i think you can understand that
You can easily test it and report the result if you want, I (we) 'll be interested to read this.
For that, you need to know how to flash a kernel (custom recovery is the best solution), how to backup the one you used before, how to boot on custom recovery with hard key for eventually restoring this one you backuped before, how to quit a secure boot error screen (removing battery) that you can meet with a bad kernel, and, of course, that root is really needed for doing all of that.
Posted without using google translation, sorry for my english
Click to expand...
Click to collapse
Hi 6ril1 and thank you for your response.
I probably wasn't very clear. What I wanted to know is whether I can install just the 20p kernel on phone which has a rom with an earlier kernel (like 20i or similar). Would the 20p kernel have any issues with a ROM designed for an earlier kernel. Up to know I used Seven's Androidnow HD ROM but unfortunately he has pull out support for newer ROMs due to some asshat distributing his ROMs without consent. The last ROM he had was 14 but it wasn't fully optimised. I am using his earlier 10.3 Androidnow HD ROM. So I was wondering if your 20p kernel will work ok with having to install a whole new ROM.
Cheers
soupratt said:
Hi 6ril1 and thank you for your response.
I probably wasn't very clear. What I wanted to know is whether I can install just the 20p kernel on phone which has a rom with an earlier kernel (like 20i or similar). Would the 20p kernel have any issues with a ROM designed for an earlier kernel. Up to know I used Seven's Androidnow HD ROM but unfortunately he has pull out support for newer ROMs due to some asshat distributing his ROMs without consent. The last ROM he had was 14 but it wasn't fully optimised. I am using his earlier 10.3 Androidnow HD ROM. So I was wondering if your 20p kernel will work ok with having to install a whole new ROM.
Cheers
Click to expand...
Click to collapse
Hi,
Just try it, after the usual precautions (Make kernel backup before in custom recovery. It means backup boot partition)
Flash kernel, and if it doesn't work on your rom, restore the last one you backuped, that's all
I tried it with an older lp stock with succes (these moded boot worked with older stock firmware).
As i answered you before, if you have a security error screen (following by a black screen without any possible acces) on boot with the new kernel, remove battery, reboot in custom recovery with hard key combo (=> buttons power + volume down, release when logo appears, and again power + vol down, until custom recovery acces appears), and restore your previous kernel that worked. As simple like that
Of course, prerequisite is that you have twrp installed.
Hi
Im using zenfone 4 a400cg stock rom with android lollipop.i need help to enable init.d on my device as i have done all method found on the internet but still no result...please some 1 help x.x
Sent from my ASUS_T00I using XDA Free mobile app