Related
Hello. How are you? I Would like to request ( i dont really know if is possible) the possibility of creating A2SD on cursorsense or a Stock with root 3.05.401.3. Do you think is possible? I Like speed and sense, just missing the A2SD . Thank you wherever is possible or not. I'll await a reply. =) Regards
The feature of a2sd must be supported by kernel,because the script would not be executed if sd is not mounted so we have to make some change to kernel that we could have sd mounted before the a2sd script's exed.
-------------------------------------
Sent via the XDA Tapatalk App
cadetnudt said:
The feature of a2sd must be supported by kernel,because the script would not be executed if sd is not mounted so we have to make some change to kernel that we could have sd mounted before the a2sd script's exed.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
cursor tried working on this for his rom but i guess there was no possible solution
i hope it is possible though, my phone gets full from hardly any apps
oh. if is on framework, there are issues wich is hard to make work i presume. Hm Well If is possible wouuld be great =). Thank you for replying
Not the framework, the linux kernel. It would need to support one of the ext filesystems (ext2, ext3, ext4). You can check whether it does by executing
Code:
adb shell cat /proc/filesystems
and looking for any of the ext's in the output. If it's not there, one would need to recompile the kernel adding this support.
Hmm although I don't really know why nobody uses yaffs on partitions of the sdcard - anybody know whether it would work? Or make sense?
The kernel does support ext2/3/4 but the problem is that it executes the app2sd script before it mounts the SDcard.
Perhaps the new apps2sd script would solve the issue. (new as in cm5)
yeah I just found http://wiki.theandroidkitchen.com/index.php?title=CursorSense32A_FAQ which kind of explains this. I'm not really content with that explanation though, if it were as simple as tweaking the apps2sd script surely cursor would have implemented it?
EDIT I just looked at the apps2sd script on my current rom (see signature) and as I suspected, it's the script itself that issues the command to mount the sdcard ext partition. So that explanation kinda doesn't make sense to me.
There's an init.rc script that comes with the kernel (boot.img). But the kernel takes a while to load up the SD for some reason and hence the issues.
It's easy to edit but I'm not exactly sure what has to be edited.
On my cousin's phone I just moved the system dalvik-cache to /cache to free up about 20 MB.
Also move market cache to /cache:
Clean it out and symlink to /cache
cd /data/data/com.android.vending
rm -R cache
mkdir /sdcard/cache/market
ln -s /sdcard/cache/market cache
Click to expand...
Click to collapse
Or just move first and then symlink it
You can query the size of a folder using: du -hs
If you really really want Apps2SD someone can look into it. It can be solved by using an alternate kernel (sanpei). But there hasn't been much activity with 1.5 Sense ROMs here on xda.
Alternately you can find plenty of 32A 1.5 Sense ROMs on international forums.
Reference here:
http://gailly.net/android/android-tips.html
Thank you everyone. You guys as always are great. Im sorry to request a 1.5 android with a2sd. Without wanting to consider the devs work as in my opinion all work is really great, i was interested on a simple stable fast rom with sense with a2sd because happens that most wich has sense becomes very slow for me on daily use. The roms i had an excelent experience was villain 3.4 for magic ( cant use because it freezes but great release never had slow issues) its a 2.1 android. Also capyslide 1.6 ( only issues was that wasnt completle stable but o loved it. The rc became very slow compared to the other previous versions )
Sorry to post this opinion. But ive been looking and since most of roms 2.1 android are slow compared to what i need, at least i didnt had the experience i expected, cyanogenmod 5.07 in my opinion at speed has grown alot compared to the 4.2.1.15 version to bad isnt sense where i have a preference ( imagine for example i work as agent of a doctor, make alot of calls and in emergency situations if my phone is slow when i need to call an ambulance, im giving an example of the emergency situations wich might happen ) so prefered to roll back until there was. a more mature rom 2.1.
Thank you for all wich are reading and replying =)
That is the main reason of my request. Thank you
-------------------------------------
Sent via the XDA Tapatalk App
jgcaap said:
Thank you everyone. You guys as always are great. Im sorry to request a 1.5 android with a2sd. Without wanting to consider the devs work as in my opinion all work is really great, i was interested on a simple stable fast rom with sense with a2sd because happens that most wich has sense becomes very slow for me on daily use. The roms i had an excelent experience was villain 3.4 for magic ( cant use because it freezes but great release never had slow issues) its a 2.1 android. Also capyslide 1.6 ( only issues was that wasnt completle stable but o loved it. The rc became very slow compared to the other previous versions )
Sorry to post this opinion. But ive been looking and since most of roms 2.1 android are slow compared to what i need, at least i didnt had the experience i expected, cyanogenmod 5.07 in my opinion at speed has grown alot compared to the 4.2.1.15 version to bad isnt sense where i have a preference ( imagine for example i work as agent of a doctor, make alot of calls and in emergency situations if my phone is slow when i need to call an ambulance, im giving an example of the emergency situations wich might happen ) so prefered to roll back until there was. a more mature rom 2.1.
Thank you for all wich are reading and replying =)
That is the main reason of my request. Thank you
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
1)
CM4 and CM5 are both mature ROMs. You just have to downgrade your radio.
If you don't want to, use any one of the new radio ROMs with sanpei kernel that have apps2sd support.
I have a HTC Dream running CM5 and I don't see how CM5 can be considered slow at all. If you are really looking for speed, use CM5 with SetCPU to overclock to 576 MHz and you will see a noticable performance increase. rps13 is working on ironing the kinks in the 710 MHz oc so look at that one too.
If you limit your background apps, the ROM really flies. Just flash stock CM5 and bcrook's officially supported kernel port instead of one of the ones you see in these forums until you see more verification amongst the users for stability of those specific ROM blends. Cyanogenmod.com forums is your best bet.
2)
If you are keen on using a Sense ROM, you should be able to take a apps2sd enabled sanpei .32.9 kernel (boot.img and wlan.ko as usual) and flash it to Cursorsense to get working apps2sd.
3)
The .27 kernel Cursorsense is based on may have issues mounting the sd card quickly for apps2sd to happen.
Finally there is the option of flashing .9 (or some other version) version of Cursorsense where apps2sd was actually enabled, but you may run into issues.
Mod edit.: not (yet) dev related, moved to general
xaueious said:
1)
CM4 and CM5 are both mature ROMs. You just have to downgrade your radio.
If you don't want to, use any one of the new radio ROMs with sanpei kernel that have apps2sd support.
I have a HTC Dream running CM5 and I don't see how CM5 can be considered slow at all. If you are really looking for speed, use CM5 with SetCPU to overclock to 576 MHz and you will see a noticable performance increase. rps13 is working on ironing the kinks in the 710 MHz oc so look at that one too.
If you limit your background apps, the ROM really flies. Just flash stock CM5 and bcrook's officially supported kernel port instead of one of the ones you see in these forums until you see more verification amongst the users for stability of those specific ROM blends. Cyanogenmod.com forums is your best bet.
2)
If you are keen on using a Sense ROM, you should be able to take a apps2sd enabled sanpei .32.9 kernel (boot.img and wlan.ko as usual) and flash it to Cursorsense to get working apps2sd.
3)
The .27 kernel Cursorsense is based on may have issues mounting the sd card quickly for apps2sd to happen.
Finally there is the option of flashing .9 (or some other version) version of Cursorsense where apps2sd was actually enabled, but you may run into issues.
Click to expand...
Click to collapse
Could you please explain what i should really do in orther to be able to use app2SD on cursor?
I like Cyanogenmod but the thing is i prefer much more the sense. I know i'm a bit dificult with taste but sense i moved to sense i didnt want anything else.
I would be happy to try your suggestion on cursorsense. I need to get the boot img of sanpei. but how exacly would it work? You know wher ei can find a tutorial or something wich would give me a begining to start? Thank you
Cursorsense in his rom said once:
I need to make something clear to everyone here...
Apps2SD is definitely a good option for people who need it, but I can't deliver it with this ROM.
The kernel doesn't load the SD card soon enough to handle the automatic Apps2SD script.
Guys, I really want to help you out here, but I don't know if I can.
Maybe another ROM might be best if you need the space... sorry eyegor.
Click to expand...
Click to collapse
Instead of automatic how about manualy? For instance a system as Cyanogenmod but. instead of loading the apps automaticaly, we have a loader(wich would work as an emulator or something identical) wich run the apps wich are installed on the SD Card?
To activate this option this loader must work as an app, and we could install apps from it. Wouldnt be this way more stable?
I am not the developer, i only ported this great rom to Captivate.
ORIGINAL THREAD: Everything you need to know is written here
Captivate Version changes:
Glitch Kernel 369mb Ram
H3llstorm GPS fix
JHJV9 modem
Internal is SDcard
Removed front camera files
I ported this rom for personal use, but since it was so good and not available here, i thought it was good to share it.
Some Suggestions:
- If you want to change internal/external mount flash one of these zip with CWM
- If you want to change kernel parameters (liveOC, frequencies, governors...) use NSTools (free on Google Play)
- If you want another modem, flash one of these with CWM
reserved
I would love to flash this but every time I do, it aborts immediately. I flashed CM9 then this and still it aborts immediately. Thank you for porting it to the cappy and thanks for your work.
---------- Post added at 09:03 AM ---------- Previous post was at 08:28 AM ----------
Never mind I did get it to flash looks nice.. thank you for your work once again.
I will give a try
Looks nice, about to flash but if we want to change kernels do we have to run the cleaning script or not?
Sent from my SGH-I897 using xda premium
Did you have permission from the original team that made this rom to post this?
one problem--- whenever i change kernel to devil for this rom, it wont let me read my sdcard anymore. I mean internal memory.
Thanks!
A nice ROM, thanks for it.
Thread closed
Permission was not received for this port, links removed.
Hello,
I'm successfully booting a second Rom on my SD Card. Here is what I did
- Build custom ICS kernel. Source from SpeedMod K3-3
- Make a copy of current rom and put on SD card.
- Boot the rom on the SD Card using the custom kernel
I'm currently testing a function to switch the rom by pressing the home/or any key button during boot.
I'll post the kernel and instruction how to setup a rom on the SD card soon.
Reserved
Reserved1
I'm liking the sound of this.....
Not sent from an I phone....cos I'm not a fanny.
heard that it's more difficult than on htc devices. nice though if u manage to get it working. looking forward to this, thanks!
chuandinh said:
Hello,
I'm successfully booting a second Rom on my SD Card. Here is what I did
- Build custom ICS kernel. Source from SpeedMod K3-3
- Make a copy of current rom and put on SD card.
- Boot the rom on the SD Card using the custom kernel
I'm currently testing a function to switch the rom by pressing the home/or any key button during boot.
I'll post the kernel and instruction how to setup a rom on the SD card soon.
Click to expand...
Click to collapse
I'm sorry, but placeholders aren't allowed in Development. When you're ready to post with files, links, etc. you can then open up a thread in Development.
Sounds good.
Sent from my GT-N7000 using Tapatalk 2
Im waiting please update the thread with kernel and instructions asap.
Thanx for your work
Mark me as very interested
Oh my good ,,, we are waiting ^_^
Interesting, looking forward to it!
Sent from my GT-N7000 using xda premium
Update: Sorry guys, I've been busy, so I couldn't have enough time to write the instruction. It's very easy to set up with my scripts.
1. Install any ICS rom - flash the rom like you've been doing. (be careful about EMMC brick, please don't wipe using unsafe kernel, even if you are on my modified kernel)
2. Flash my scripts using CWM to copy current rom to the SD card.
3. Flash My modified speedmod ICS K3-3
4. Reboot
Please note that, this method only works if both roms are ICS. It will not work if you have one rom is GB and one rom is ICS. Unless, somebody can make a kernel that works for both GB and ICS.
I'm test couple of changes to the config file before upload the script & kernel.
wow great
please post some videos too
Looks promissing
A rom to be used on work and another to use at home *_*
Will the apps be shared between the roms?
Good idea, that's what I'm trying to do. I have a init script that you can use the same application file to save space. It's working on my old roms. I've not tested it with ICS roms. I got a lot of force closes when I try to share both apk and data.
projeto56 said:
Looks promissing
A rom to be used on work and another to use at home *_*
Will the apps be shared between the roms?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1748588 for updates
Hello,
I'm a little late to the Razr M game, but I just got a device off ebay since it's only about a year old and in great shape and quite cheap :good:
In any case, I've so far managed to unlock the radio for Tmobile in the US (GSM), and root it the device. Unfortunately, I didn't know when i bought it about the inability to unlock the bootloader with OTA from May and beyond, which mine is according to fastboot. I believe I came across the actual number being 98.18.78 somewhere.
So I've been doing a lot of reading, got SafeStrap running, made a stock backup, and am testing on slot1. However, I can't seem to get any CM ROM's running! Most of them 'boot' but then all I get is a blank screen, though I can connect with adb and therefore confirm that it does actually run some CM build.
I'm first of all somewhat confused on what ROM i should be using. I've found several links that should seem like they work, but none have succeeded (all have that halfway functionality that only works in ADB):
http://d-h.st/FgU
http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/index.php?device=xt907
http://goo.im/devs/Hashcode/scorpion_mini/cm10.1
http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907
I found these in various threads on XDA and droidrazr.com. I basically read the entire 55 pages of http://forum.xda-developers.com/showthread.php?t=2012093 and since the link in the first page is dead I tried all the links that came up on the thread, which got a couple of the links in my list above.
Also, I did run across the tip that I had to mount system in SafeStrap to get these working, no success. And what's this thing about having to wipe dalvik and system and cache two or three times??
Basically I'd like the proper, up to date link that should be working, along answer to above question and and other tips!
Thanks!!! I love the phone otherwise it's great
UPDATE:
I did manage to get an CyanogenMod spinning forever startup screen with an ancient rom described here http://www.droidviews.com/install-first-aosp-based-unofficial-cm10-rom-on-motorola-droid-razr-m-xt907/ which appears to have come again from the thread mentioned above. The link is now gone but I have the .zip that I must have snagged right before it disappeared!
flyingsilverfin said:
Hello,
I'm a little late to the Razr M game, but I just got a device off ebay since it's only about a year old and in great shape and quite cheap :good:
In any case, I've so far managed to unlock the radio for Tmobile in the US (GSM), and root it the device. Unfortunately, I didn't know when i bought it about the inability to unlock the bootloader with OTA from May and beyond, which mine is according to fastboot. I believe I came across the actual number being 98.18.78 somewhere.
So I've been doing a lot of reading, got SafeStrap running, made a stock backup, and am testing on slot1. However, I can't seem to get any CM ROM's running! Most of them 'boot' but then all I get is a blank screen, though I can connect with adb and therefore confirm that it does actually run some CM build.
I'm first of all somewhat confused on what ROM i should be using. I've found several links that should seem like they work, but none have succeeded (all have that halfway functionality that only works in ADB):
http://d-h.st/FgU
http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/index.php?device=xt907
http://goo.im/devs/Hashcode/scorpion_mini/cm10.1
http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907
I found these in various threads on XDA and droidrazr.com. I basically read the entire 55 pages of http://forum.xda-developers.com/showthread.php?t=2012093 and since the link in the first page is dead I tried all the links that came up on the thread, which got a couple of the links in my list above.
Also, I did run across the tip that I had to mount system in SafeStrap to get these working, no success. And what's this thing about having to wipe dalvik and system and cache two or three times??
Basically I'd like the proper, up to date link that should be working, along answer to above question and and other tips!
Thanks!!! I love the phone otherwise it's great
UPDATE:
I did manage to get an CyanogenMod spinning forever startup screen with an ancient rom described here http://www.droidviews.com/install-first-aosp-based-unofficial-cm10-rom-on-motorola-droid-razr-m-xt907/ which appears to have come again from the thread mentioned above. The link is now gone but I have the .zip that I must have snagged right before it disappeared!
Click to expand...
Click to collapse
There is not much.
You will not find much better than Mhous33's dst & my sd swap here : http://forum.xda-developers.com/showthread.php?t=2442384
There is also one at RZR http://www.droidrzr.com/index.php/topic/33740-rom-jb-98163-xt907-rage-m-v10-1232013/
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
Your boot ,which includes the kernel & recovery are locked. All the roms you list use a non stock kernel.
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
There are others but they are not current.
Well, none of the custom ROMs out now will work with SS. Their are some stock based ROMs, one of which was posted by Avi, that will work with SS. There are some older ROMs that were designed for SS and they were built prior to April (when our bootloader was unlocked). You'll have to dig back a couple of page to find them. I know there was SS compatible CM10 in that link you posted, but I don't think the link is active for it anymore. If you decide to run an older SS compatible ROM on your newer system version, you're going to run into kernel issues. Things like the gallery not working and WiFi signal being weak. Your best bet right now is to load a stock ROM on slot 1 and start tweaking that with XPosed and enabling Init.d so you can get some performance tweaks going.
Thanks for the response, I'll check those out. Glad to find some up to date roms haha
aviwdoowks said:
Your boot ,which includes the kernel & recovery are locked. All the roms you list use a non stock kernel.
Click to expand...
Click to collapse
This is something I didn't realize/know before, good to know! That would explain some of the problems. May I ask how you know they don't use stock kernels? Just experience in the development process or is there a way to check?
RikRong said:
Your best bet right now is to load a stock ROM on slot 1 and start tweaking that with XPosed and enabling Init.d so you can get some performance tweaks going.
Click to expand...
Click to collapse
Thanks for the info, I'll have to do some research if aviwdoowks's pointers dont work out! Second day fiddling with this stuff on android so I don't know what XPosed is/what Init.d does (although I think Ubuntu has that file too...)
Also, I tried the DeadCalm SS rom and i get an
E:signature verification failed
error
flyingsilverfin said:
Thanks for the response, I'll check those out. Glad to find some up to date roms haha
This is something I didn't realize/know before, good to know! That would explain some of the problems. May I ask how you know they don't use stock kernels? Just experience in the development process or is there a way to check?
Click to expand...
Click to collapse
Word would get round if they did, but What vzw wants moto to do to a phone is not what cwm wants to do. 4 cyl hi mpg VS racing v8
Same problem with the xt907-98.30.1-deodexed rom:
E: signature verification failed
Not sure what's wrong with BOTH of these?
Sorry, didn't do enough testing. Disabled zip verification and it wrote, just have to see its working!
flyingsilverfin said:
Thanks for the info, I'll have to do some research if aviwdoowks's pointers dont work out! Second day fiddling with this stuff on android so I don't know what XPosed is/what Init.d does (although I think Ubuntu has that file too...)
Also, I tried the DeadCalm SS rom and i get an
E:signature verification failed
error
Click to expand...
Click to collapse
Did you mount system before installed it?
All SS roms need mounting.
My link has steps.
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I think DC is not SS ready.
---------- Post added at 09:18 PM ---------- Previous post was at 09:08 PM ----------
DC flashes the damn skull bootlogo, easy to delete the bootlogo & # out instructions in the updater-script, other things too for a DIY SS rom
---------- Post added at 09:21 PM ---------- Previous post was at 09:18 PM ----------
DL my SS deodexed & use it as a templet as to what items need to be taken out.
Root Explorer is all you need.
Thanks for the help and links, I have the deodexed SS version from your link working. I see that it is not a debloated version; is the odexed version debloated?
Also I was originally hoping for a ROM with functionality like Cyanogenmod, but I guess the situation is too specific for that too happen. I might be interested in getting to ROM making/customizing at some point, I did some preliminary reading, I should be able to edit the deoxed SS ROM and then 'stitch it up again' in simplest terms, and it will still work on my device, correct? I feel like editing a ROM would be a great way to learn more about Android/Linux/bootloaders etc before I go to college.
flyingsilverfin said:
Thanks for the help and links, I have the deodexed SS version from your link working. I see that it is not a debloated version; is the odexed version debloated?
Also I was originally hoping for a ROM with functionality like Cyanogenmod, but I guess the situation is too specific for that too happen. I might be interested in getting to ROM making/customizing at some point, I did some preliminary reading, I should be able to edit the deoxed SS ROM and then 'stitch it up again' in simplest terms, and it will still work on my device, correct? I feel like editing a ROM would be a great way to learn more about Android/Linux/bootloaders etc before I go to college.
Click to expand...
Click to collapse
The odexed is DST which means a debloated to the same specs at the Telstra build. The SD swap works on both.
aviwdoowks said:
The odexed is DST which means a debloated to the same specs at the Telstra build. The SD swap works on both.
Click to expand...
Click to collapse
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
flyingsilverfin said:
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
Click to expand...
Click to collapse
Telstra is the Australian firmware, I believe. If you want to port CM, you need to pull from their source. The DST ROM is a stock Moto ROM that's built by the Moto software team. You can't really take that and change it into a CM port, but you can make your own build environment and start building CM.
flyingsilverfin said:
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
Click to expand...
Click to collapse
Telstra is a carrier for the xt905. There are builds posted in our dev section. Any telstra rom is encrypted & if flashed w/ Rsd or Fastboot will brick an xt907.
Very difficult. Edit impossible.
RikRong said:
Telstra is the Australian firmware, I believe. If you want to port CM, you need to pull from their source. The DST ROM is a stock Moto ROM that's built by the Moto software team. You can't really take that and change it into a CM port, but you can make your own build environment and start building CM.
Click to expand...
Click to collapse
Alright thanks for the info. I was just doing some reading on the Linux Kernel. Since I am stuck with the stock motorola kernel, but this implements all the things I need to make the upper level, platform independent sys calls and other api's, there shouldn't be a need to build a special kernel for a cyanogenmod port, correct? If i port the higher level things everything that is implemented in cyanogenmod should work... am I getting this right? I'm trying to figure out what the OS kernel requirements are.
Q&A for [PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
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:
Support for Galaxy S4 Mini GT-I9195
Hi, I tried this on a GT-I9195 using the "Galaxy S4" preset... Both ROMs seem to be installed, but once I install the second ROM, there doesn't seem to be any way to boot back into the first ROM.
I'd love for this to work on my device (serranoltexx). Could I help add support for this device in some way?
Thanks
utjunkie said:
Hi, I tried this on a GT-I9195 using the "Galaxy S4" preset... Both ROMs seem to be installed, but once I install the second ROM, there doesn't seem to be any way to boot back into the first ROM.
I'd love for this to work on my device (serranoltexx). Could I help add support for this device in some way?
Thanks
Click to expand...
Click to collapse
I started to wonder how did you install them in the first place???
qtwrk said:
I started to wonder how did you install them in the first place???
Click to expand...
Click to collapse
There were no errors and both ROMs are physically taking up the space; just it boots into the second ROM no matter what I do. It sounds like it's pretty close, can I help make this work?
Dual Boot with MIUI 4.9.26
Hello,
i tried to install the MIUI v5 4.9.26 Multilang but I got the error in the picture attached to this post.
Could you help me to install It? I have Omega ROM for first space and for the second I would install MIUI. I've already patched the ROM with the app for Android on the Omega and the tool create a dual.zip of the original MIUI ROM. I tried to flash it from recovery (TWRP 2.8.0.1 with Aroma MOD)
Thanks,
Whity
utjunkie said:
There were no errors and both ROMs are physically taking up the space; just it boots into the second ROM no matter what I do. It sounds like it's pretty close, can I help make this work?
Click to expand...
Click to collapse
i assume you followed instruction precisely ?
tried both app switcher and zip file switcher ?
Cam someone send me the link to the snapshots?
Sent from my GT-I9505 using Tapatalk 2
Alucard 1.4oc kernel issues
Hey, i am trying to flash Alucard 1.4oc over SlimKat on my Dual partition.. The patched script seems to install fine, but my boot just stops at the Samsung logo, vibrates twice and restarts... I can see that they made some changes to their updater_script, but I have not figured out if this is the source of my problems,or if it is not related to my multi-boot at all..
So, i just wanted to know if anyone has patched 1.4oc on anything other than Primary with success.
App Sharing
twcobra said:
+1
Click to expand...
Click to collapse
sronweb said:
As I understood from previous posts there is some work in progress but nothing yet released. Currently you can share only apps (which is a lot for me...)
Click to expand...
Click to collapse
Well, I was trying to reply to the question on app sharing. I have used both the full share and the individual. I stopped the full share because of the differences between Gapps with the different ROMS. However, the full share seems like a better bet because it is a straight swap of partitions. The individual app sharing has been working, but as it has been noted, data is not part of that... Also, i find the use of hard links challenging when i am trying to look at my filesystem and figure out what is where. Not to mention that it doesn't really let you manage all the apps you care about for all the ROMS in one place. I have needed to go to every ROM if i want to uninstall a shared app and really have it go away.
that said, i don't really want to go down the path of partitioning my external sd card and using something like Link2SD. I am going to wait and see what our patch master produces for his latest updates that try to handle sharing of data, as well.
Response to Primary Rom update question
1) From recovery, flash the DualBootUtilities
2) Select Primary
3) Do a full wipe
4) Exit to recovery
5) From recovery, install your new primary ROM as usual
The big point noted by the OP is to avoid using recovery wipe utilities because they may wipe parts/all of secondary ROMS (those in Dual and MultiSlots)
---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------
So, I can get these kernels to boot up fine from the primary ROM which is current some recent nightly of CM11
However, when i flash over my dual (SlimKat 8.10) or multi-slot-1 (DirtyUnicorns v8.2) i can't get past the initial Samsung logo. The phone vibrates once .... twice .... then reboots.
EDIT: I should note that i have 2 other kernels that are booting fine for my secondary ROM
Can someone confirm if they are using either of these Alucard kernels succesfully on something other than the PRimary ROM.
thanks
FuzzyPete said:
1) From recovery, flash the DualBootUtilities
2) Select Primary
3) Do a full wipe
4) Exit to recovery
5) From recovery, install your new primary ROM as usual
The big point noted by the OP is to avoid using recovery wipe utilities because they may wipe parts/all of secondary ROMS (those in Dual and MultiSlots)
---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------
So, I can get these kernels to boot up fine from the primary ROM which is current some recent nightly of CM11
However, when i flash over my dual (SlimKat 8.10) or multi-slot-1 (DirtyUnicorns v8.2) i can't get past the initial Samsung logo. The phone vibrates once .... twice .... then reboots.
EDIT: I should note that i have 2 other kernels that are booting fine for my secondary ROM
Can someone confirm if they are using either of these Alucard kernels succesfully on something other than the PRimary ROM.
thanks
Click to expand...
Click to collapse
Ok, got my kernel patched and working. As it stands right now, it looks like the current releases of the Alucard AOSP kernel (1.4oc) do not patch correctly. I confirmed this for 1.4h and 1.4oc. It took a lot of painful sleuthing, but i finally determined that the Alucard kernel for AOSP gets a patch for the init binary. I could not tell from the commits why this was needed originally, but it appears that Alucard changed something on his end, or the ROMS have changed something else on their end or whatever.. Regardless, the init_kk binary is now incompatible with 1.4 AOSP kernel.. I didn't have a dev environment handy to just change the config and rebuild the DualPatcher app, so i did the following to confirm:
1) Ran the DualPatcher app for the 1.4oc kernel
2) Started recovery, and flashed the patched kernel
3) went to the shell, unpacked the ramdisk and replaced the patched init with the original from the Alucard kernel ramdisk
4) repacked the boot.img, copied it to MultiKernels
5) rebooted
At this point, my ROM booted fine.
9.0 Apk crashing
I also have the same problem. Tried to patch several different ROM for S5 but the app crashes at 0%. Using the 9.0 app
App crashes 9.0
I have the same problem. 9.0 app crashes at 0% when trying patch S5 dual boot ROM. Changed to standard patcher option and tried various ASOP ROMs.
Tried to patch 5.0 PA GAPPs with latest dbug apps failed. Patched CM12 is running ok.
I have a problem updating my ramdisk on the secondary rom(slimkat 4.4.4), can you help me?
I have a problem failed to patch kennel..
Both on v9 debug and v8
I am on ozcan rom v6.2
I have also tried on CM12 but does not work please help
ouwesh said:
I have a problem failed to patch kennel..
Both on v9 debug and v8
I am on ozcan rom v6.2
I have also tried on CM12 but does not work please help
Click to expand...
Click to collapse
Use the 17mb version on alpha 9.0
Dualboot TW Update
Hi guys,
I'm using the Dualbootoption developed inhere. As primary I'm using TW, as secondary DirtyUnicorns. Now the thing: I could make a Update of Touchwiz by Kies. I now, Root Rights will be removed and the Bootloader will be closed. So after the update I have to unlock the Boodloader and to root the Phone again to use the Dualboot Option or only to unlock the bootloader.
Just a few Information please
Best Regards,
Aeneas
AeneasG said:
Hi guys,
I'm using the Dualbootoption developed inhere. As primary I'm using TW, as secondary DirtyUnicorns. Now the thing: I could make a Update of Touchwiz by Kies. I now, Root Rights will be removed and the Bootloader will be closed. So after the update I have to unlock the Boodloader and to root the Phone again to use the Dualboot Option or only to unlock the bootloader.
Just a few Information please
Best Regards,
Aeneas
Click to expand...
Click to collapse
I think you must be rooted to set the kernel for your primary rom, and also have an unlocked bootloader to have custom recovery so you can flash dualboot patched roms
jigsawcrank said:
I think you must be rooted to set the kernel for your primary rom, and also have an unlocked bootloader to have custom recovery so you can flash dualboot patched roms
Click to expand...
Click to collapse
Yeah that's clear. But I have the dualboot option yet. To change after the update its enough only to root the smartphone or also to unlock the Bootloader?
Regards,
Aeneas