Related
I'm looking for any ROM to work on the Hero i deleted the fonts from.
any rom that has valid signature and i can flash it and get the fonts back?
Thanks
Bashar . said:
I'm looking for any ROM to work on the Hero i deleted the fonts from.
any rom that has valid signature and i can flash it and get the fonts back?
Thanks
Click to expand...
Click to collapse
take a rom, open it with winrar or any extractor and take /system/fonts out of the zip..
(if you need sense fonts, use a flashable zip sense rom, otherwise AOSP)
AOSP fonts do also work on sense, the names are the same
root your phone..
then set up adb , some good guides here on the board..
connect phone with usb, no sdcard mounting
now:
Code:
adb remount
adb push yourfont.ttf /system/fonts
(repeat as long as you have ttf files: might work if you use *.ttf)
adb reboot
if you don't want to root, i don't know how to do it
EDIT: hope you are already rooted because with no fonts, how would you root your phone,
or install the necessairy files.. didn't notice it yet
grtz
that was not possible
i had to downlaod last rom at http://www.htc.com/uk/supportdownloadlist.aspx?p_id=283&act=sd&cat=all , install it back to 1.5, then upgrade all the way OTA till latest version for it (a.k.a 2.1) , now back to normal
unfortunately had todo it via windows
Bashar . said:
unfortunately had todo it via windows
Click to expand...
Click to collapse
you can setup adb in windows..
He used the RUU
@Bashar, if you root it again and want to experiment. Make sure you got a custom recovery. Easier to solve mess I guess You can create back-ups of your normal ROM in it as well. Anyway, glad it is back to normal.
riemervdzee said:
He used the RUU
@Bashar, if you root it again and want to experiment. Make sure you got a custom recovery. Easier to solve mess I guess You can create back-ups of your normal ROM in it as well. Anyway, glad it is back to normal.
Click to expand...
Click to collapse
Thank you
i installed rom manager and trying to get clockworkMod installed but doesn't seem gets there when i reboot, any idea why ?
EDIT: everytime i reboot into recovery even if manually using the ClockworkMod i get Android System recovery <2e>
Did you Ever Wanted your Own Custom ROM? Did you don't understand other Guides? Do you don't Like ROM Kitchens? Than this Guide is the right Guide for you! Just Try It and you can create your Own Custom ROM!
General Information
So, Before we start with this Guide, i just want to tell you some General Informations about [highlight]Custom Roms[/highlight]. When you buy your phone, you will have a [highlight]Stock ROM [/highlight]installed. A [highlight]Stock ROM [/highlight] is just that Software, your Company has created, especially for your phone. It's a Software like Android 2.3.4 with Touchwiz 4 or Android 4.0.4 with Sony UI. Those Softwares may be good, but there are many Things to Improve, for the Best Xperience, while using your Phone. A [highlight]Custom ROM [/highlight]can be complete different to [highlight]Stock ROM [/highlight], like [highlight]Cyanogenmod 10 [/highlight], or be just a improved Version of the [highlight]Stock ROM [/highlight]. To Build a [highlight]Custom ROM [/highlight] you need to know a few Words, and have a Phone with Root Acess + S-OFF / Unlocked Bootloader. So in this Guide we will concentrate on the Easy Way, the [highlight]Improved Stock ROM [/highlight]. You Can also Build a [highlight]ROM [/highlight] out of Source from Google, but thats too complicated for beginners. Setting up compile envirment can be quite complicated . So let's take a look at stuff you need to know:
[highlight]Root Acess[/highlight]
Complete Acess to all System Files, like Administrator on Windows. To Root Your Phone, search XDA. Rooting your Phone is done by putting su library to /system and manage acess with SuperSu or Superuser. When you buy your Phone, it doesn't have Root Acess. Root Acess is needed for installing CWM, mount your /system as Read & Writeable ----> You can delete system files, and installing apps to /system/app, by copying them to /system/app. By Rooting your Phone you loose Warranty, but you can reinstall stock software and no one will notice
[highlight]ClockWorkMod Recovery (CWM)[/highlight]
Recovery Mode of your Phone. In Recovery you can install flashable zips and roms, wipe and format your device, mount different partititons and fix permissions... To Get CWM search XDA. There are different Ways for every Device. You can enter recovery before your device is fully booted, and since touchscreen drivers are not yet available you need to use the volume buttons for controlling the recovery. There are different ways of entering cwm for every device.
[highlight]Rom & Kernel[/highlight]
ROM means: [highlight] Read-Only-Memory[/highlight] . The Funny Thing is that we can Read and Write on our Read-Only-Memory. Anyway, its a partition which includes large parts of the OS ----> operating system of your Phone. In a [highlight]ROM[/highlight] for Android Phones are included apps, framework, libs & many more and since android is modular, there is an app for everything (keyboard, launcher, statusbar). Together with a [highlight]Kernel[/highlight] it's the "Life" of your Phone.
The Kernel is needed for a working Phone. You Can Install Stock or Custom Kernel. When you buy a Phone Stock Kernel is preinstalled of course. The kernel includes many drivers, controlls the cpu and does many more... Just rember that word
General Information
1. Install Stock ROM to your Phone - This Can be Done by Flashing via Flashtool or Odin. You Need a Clean Base to Start. Recomnend is a Stable, Official ROM, like Gingerbread, Ice Cream Sandwich or maybe Jelly Bean.
2. Root the ROM. This Can be done with Different Tools, Very Popular is for Example SuperOneClick Tool.
Just search for "my device name root" in xda if your not sure
3. Improve Stock ROM on Your Phone. So, After You Have Installed the Stock ROM and Rooted the ROM You Can Start. Now You Need To Change Some Things, To Make the Stock ROM to a Customized ROM. You Can do a lot Things, Here are a Few Examples:
- Install Latest Superuser SuperUser
- Install Latest BusyBox Auto-Installer
- Supercharge the ROM, enable Zipalign etc.. ----> here
- Remove Bloatware. Use Es File Explorer to remove not longer needed apps in system/app partitition
- Tweak Build.prop by going with ES File Explorer to /system and editing your build.prop. now you can change the Name shown in Settings and do a lot more ----> http://forum.xda-developers.com/showthread.php?t=1227269
- Change the Bootanimation. You can find a lot of them by Going to themes and apps of your own device.
- Add or Change Apps. Check out Themes and Apps Selection of Your Device and Install a few Of Them, If You Are Allowed to use MooDeD Apps created by other Users
3.1 Now Delete/remove all backups in clockworkmod/backup folder
4. Now Make Sure You Have Installed CWM. If You Have Changed a Lot Things and You Think Your ROM is good enough, Boot to CWM, select wipe data/factory reset and Boot up again. If You Are Still able to Boot, Check the ROM for Bugs or Problems. Write them Down. Try to fix them. You can always take a logcat (adb logcat)
Than Boot again to CWM select wipe data / Factory reset ---> yes advanced ---> wipe battery stats ---> yes. Now Select backup & Restore ---> Backup.
5. Connect Your sd card to PC and go to Clockworkmod/backup folder. Now Go to the only 1 backup folder and copy "system.img" to your PC.
6. On PC Open Yaffey and Choose Open ---> system.img and than extract to empty folder called system.
7. Now You Will Get a Folder "system" which contains the System of your Phone. Now Create an Empty .zip file and paste in extracted Meta-inf folder Download and copy folder "system" inside. ROM should be flashable for NOW!
Remeber to mount /system before flashing // replace with mount Script for ur device... You can check this by dowoading any rom 4 ur device
NOTE: This has nothing to do with developmemt or original development in any way. Its theming a stock ROM in the simplest way...
Just Press thanks if this was helpfull in any way...
How to
[[ Placeholder ]]
[[ Placeholder ]]
[!][RESERVED][!]
[[ Placeholder ]]
1 year later:laugh:
Sorry... I will finish this guide later...
And so on...
Sent from my GT-S7500 using xda premium
To infinity and beyond!
saiz136 said:
To infinity and beyond!
Click to expand...
Click to collapse
Beyond Smart xD
Updated Thread and Added a First Guide
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
ruizit0 said:
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
Click to expand...
Click to collapse
There is a guide lol
jader13254 said:
There is a guide lol
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
ahaha sorry .. i was thinking that was a little intro explaining clocklowrk and stuff .. to a coocking tutorial ahaha
maybe you can expecify more in title or something
nice tutorial to create a rom this way .. i read somewhere that the next clockwork will have this feature
Will try..
Sent from my GT-N8000 using Tapatalk 2
kaipro said:
Will try..
Sent from my GT-N8000 using Tapatalk 2
Click to expand...
Click to collapse
You need different commands for wiping on g Note, just search your device forum
Sent from my LT18i using xda app-developers app
Where is the system.img? I didnt have one when i backed up with cwm
very noob-friendly !
CovXX said:
Where is the system.img? I didnt have one when i backed up with cwm
Click to expand...
Click to collapse
check clockworkmod/backup folder... there should be system.xxxx.img
Hi all.
I had an Orange UK Hero GSM on the latests official stock ROM and looked everywhere for a simple way to get Cyanogen 7 on it...
Most the 'simple' ways I found involved typing in text in a command line window and the ones I tried (including the official CyanogenMod instructions) did not work...
With a lot of looking around I've found a simple way that involves no typing and only downloading 3 files! So here goes... but before I do, remember I am not responsible for any damage you cause to your device. I am sharing the method that worked for me...
1) Put the attached apk files and the CyanogenMod 7 zip in the root directory of your SD card in the phone. The CyanogenMod zip can be got from: here.
2) Install the Universal Androot apk
3) Run the app to root your device (using SU option 2.1-2.2)
3) Install the RomManager 4.3 apk
4) Run the app. Choose install Clockwork Mod Recovery to install the recovery
5) Choose install ROM and when the phone boots into CWM Recovery select to install your CM7 zip from your SD card.
6) Reboot and you've got CM7.2 on your Hero!
Let me know if this works for you and hit the thanks button if it does! This guide would have saved me a day of trial and googling if someone else had written it first! :cyclops:
Thanks to the makers of Universal Androot and Rom Manager... it's their work that made this job so simple!
Thank you!!
Thank you for sharing the almost extinguished Rom Manager 4.3.apk
I've been looking for it for almost 3 days.
Thank you!!
Chris
afr33s said:
Hi all.
I had an Orange UK Hero GSM on the latests official stock ROM and looked everywhere for a simple way to get Cyanogen 7 on it...
Most the 'simple' ways I found involved typing in text in a command line window and the ones I tried (including the official CyanogenMod instructions) did not work...
With a lot of looking around I've found a simple way that involves no typing and only downloading 3 files! So here goes... but before I do, remember I am not responsible for any damage you cause to your device. I am sharing the method that worked for me...
1) Put the attached apk files and the CyanogenMod 7 zip in the root directory of your SD card in the phone. The CyanogenMod zip can be got from: here.
2) Install the Universal Androot apk
3) Run the app to root your device (using SU option 2.1-2.2)
3) Install the RomManager 4.3 apk
4) Run the app. Choose install Clockwork Mod Recovery to install the recovery
5) Choose install ROM and when the phone boots into CWM Recovery select to install your CM7 zip from your SD card.
6) Reboot and you've got CM7.2 on your Hero!
Let me know if this works for you and hit the thanks button if it does! This guide would have saved me a day of trial and googling if someone else had written it first! :cyclops:
Thanks to the makers of Universal Androot and Rom Manager... it's their work that made this job so simple!
Click to expand...
Click to collapse
great great , good post
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.
I just wanted to clarify that with S-OFF this module is useless
migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk
For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.
I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).
blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.
I have looked around and haven't seen anyone mention this so I thought I would post about it since I've been using it and thought it was cool. I hope others find this useful.
The thread I'm talking about: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan: http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool.
Thanks to @aukhan, @rlorange, @chenxialong, and other contributors.
Download the first .apk (Dual Boot Patcher). That is the only app that you should need to complete the process. A video guide is posted by @aukhan here: https://www.youtube.com/watch?v=h_i3GW_s-VE&spfreload=10
That is the best walkthrough I've seen.
Since it was requested, I've made a video walkthrough of this process: https://youtu.be/5VzYED1hhUA
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video doesn't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
I have run this with JasmineROM as the primary and CM13 as the secondary as well as CM13 as primary and JasmineROM as Secondary. I currently have this set-up to try different ROMs without needing to completely wipe my phone and deal with backups/restores. I also use it to use CM13 as my primary while having stock options (S-Pen, Car BT, and other Samsung stuff) available in a quick reboot.
Edit:
More Specific Instructions:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. CM13, Gapps, SuperSu, XPosed, datafixes, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/ and install it on your phone
3) Open ES File Explorer or another Root Explorer app and navigate to /sdcard/MultiBoot
4) Create a folder labeled "dual" in that directory (now there is a folder /sdcard/MultiBoot/dual)
5) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
6) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Secondary"
7) A file browser will now open. Navigate to /sdcard/MultiBoot/dual and save the patched zip file there.
8) You may now repeat steps 6 and 7 to add the rest of the zip files
9) Tap the check mark in the upper right to "Patch" all of the .zip files
10) Tap the three lines in the upper left again and select ROMs
11) Tap the phone icon in the lower right and push okay
12) Tap the plus button in the lower right and navigate to the /sdcard/MultiBoot/dual folder. Select the main ROM (CM13, Kyubi, JasmineROM, etc) and tap "keep location"
13) Repeat step 12 until all zips are added in the order you want them flashed (the order is important). If you mess up swipe the one that's wrong to the right to remove it from the list
14) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
15) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
16) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
17) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
Edit 2:
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition, data slot goes to internal storage, and Extsd slot goes to the External SD card. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition.
If you have problems make sure to set the kernel and update the ramdisk before flashing and that the files are in the right folder typed exactly as it says in the prompt when patching the file.
I have noticed many problems when using a non-Touchwiz ROM as stock and trying to dual boot to a Touchwiz ROM. I have had bootloop situations when trying to dual boot to Kyubi or PaulPizz from CM13, but with PaulPizz as primary I have no issues switching back and forth.
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
Edit 3: Video Tutorial: https://youtu.be/5VzYED1hhUA
If it is too blurry I can make another one, but I think you can see what you need to just fine. I hope it helps. I also forgot to mention that if you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Edit 4: I have now tested this on Marshmallow with success. I still recommend using a Touchwiz ROM as primary and you'll need to have a kernel that's permissive. I'm using Emotion, but I think Oscar's kernel should work as well. I have PaulPizzRom.VRU2CPF3.r-2 installed as primary with the CPF3 modem and Emotion kernel and CM13 as secondary (pretty much my daily driver at this point). Everything has been working so far.
Isn't there a kernel patch requirement for this to work?
Just tried it and working great for me. Jasmine primary, cm13 secondary. Definitely easier than messing with twrp to test roms. Thanks for the info!
jal3223 said:
Isn't there a kernel patch requirement for this to work?
Click to expand...
Click to collapse
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
shadeau said:
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
Click to expand...
Click to collapse
Awesome, thanks! I'm definitely going to give it a try.
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
jal3223 said:
Awesome, thanks! I'm definitely going to give it a try.
Click to expand...
Click to collapse
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
ssb13 said:
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
Click to expand...
Click to collapse
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
shadeau said:
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
Click to expand...
Click to collapse
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
ssb13 said:
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
Click to expand...
Click to collapse
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
ssb13 said:
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
Click to expand...
Click to collapse
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
shadeau said:
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
Click to expand...
Click to collapse
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel
Sent from my SM-N910V using Tapatalk
ssb13 said:
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel View attachment 3739482
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
shadeau said:
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
Click to expand...
Click to collapse
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
ssb13 said:
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
Click to expand...
Click to collapse
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
shadeau said:
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
Click to expand...
Click to collapse
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
ssb13 said:
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
Click to expand...
Click to collapse
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
shadeau said:
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
Click to expand...
Click to collapse
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
ssb13 said:
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
Click to expand...
Click to collapse
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
ssb13 said:
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
Click to expand...
Click to collapse
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
shadeau said:
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
Click to expand...
Click to collapse
Thanks.