/include/disclaimer or warning.h
/*
* Your warranty is not void as I Think!!
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you, Hard, a Lot $ Lot:laugh::laugh::laugh:
* But I will always be here to HELP! You...
*/
Features
> Made by [email protected]
> Support for all GPT Partitions...:highfive:
> Special EFIDroid Support..
> Secret Tweaks...:victory:
> Specially for Hard Working Dev's like @yoAeroA00...
> Advanced Backup...
> Advanced Restore...:angel:
> Advanced Mounting Points..:highfive:
> Advance Itself...:laugh:
> You tell???
XDA:DevDB Information
yoAeroA00 TWRP 3.0.2.1 Developers Edition Recovery for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, Lovely Nokia X2 Users & Fans...
Source Code: http://PM me if you need that...
Version Information
Status: Stable
Created 2017-01-22
Last Updated 2019-02-06
DOWNLOADS
Yes! Baby.. Made In INDIA
If you need any kind of live help than come on Slack
> Build's of TWRP 3.0.2.1 :- [20170122]
NOTE: If you need Support for any Awesome Feature than Comment in this Post or PM me... :good::good:
Enjoy!!:laugh:& In response to Continue this Project Push the Thump'sUP!! Bro...:good:
Development Catalogue
>Build 20170122 :- First Initial TWRP 3.0.2.1 Release with a Lot of Custamizations and Features...
is these supporting sdext partition ?
after trying not supported :crying:
frnsl3 said:
is these supporting sdext partition ?
after trying not supported :crying:
Click to expand...
Click to collapse
Use EFIDroid instead of SDExt...:fingers-crossed:
Because if you use SDExt than you need to partition your SD Card from PC but in EFIDroid Partitioning of SDCard is not Required...
yoAeroA00 said:
Use EFIDroid instead of SDExt...:fingers-crossed:
Because if you use SDExt than you need to partition your SD Card from PC but in EFIDroid Partitioning of SDCard is not Required...
Click to expand...
Click to collapse
i need sdext because need more internal storage in ROM , if efidroid can do this can you write some tutorial for this.
thx
frnsl3 said:
i need sdext because need more internal storage in ROM , if efidroid can do this can you write some tutorial for this.
thx
Click to expand...
Click to collapse
It can do more than that...[emoji41]
Like you can customize the size of each partition as per your need...
I had written a guide about it on it's thread..[emoji6]
Sent from my ara using XDA-Developers Legacy app
Good luck bro and thanks
You are new level ... ????
Thx pro .... You are the best of all
yoAeroA00 said:
DOWNLOADS
> Build's of TWRP 3.0.2.1 :- [20170122]
Click to expand...
Click to collapse
How your project is better than this?
SimonVN said:
Recovery Project v3.0.2-0.1
for Nokia X2
Downloads
Flashable ZIP: twrp-3.0.2-0.1-flashable-ara.zip
Recovery image file only: twrp-3.0.2-0.1-20160531-ara.img
Click to expand...
Click to collapse
mirfatif said:
How your project is better than this?
Click to expand...
Click to collapse
I just add sd-ext support for user who want to use Link2SD. I have tried yoAreoA00 TWRP and see there's too many unnecessary partitions. The flashable zip has a bug also (The dd script call the wrong image name, I have to extract it and flash the IMG file myself).
SimonVN said:
I just add sd-ext support for user who want to use Link2SD. I have tried yoAreoA00 TWRP and see there's too many unnecessary partitions. The flashable zip has a bug also (The dd script call the wrong image name, I have to extract it and flash the IMG file myself).
Click to expand...
Click to collapse
Same here. I also flashed the image through RASHR
But backing up Modem partition is a good thing. Also sd-ext support should be added
mirfatif said:
How your project is better than this?
Click to expand...
Click to collapse
Hmm... Again... It is for advanced users specially Dev's and as you guys were reporting errors in networks, sims, .... It supports backing up every partition of Nokia x2 ,ya every.. For future safety.. And even your imei.. And see features list...
Sent from my Nokia ara using XDA Labs
yoAeroA00 said:
Hmm... Again... It is for advanced users specially Dev's and as you guys were reporting errors in networks, sims, .... It supports backing up every partition of Nokia x2 ,ya every.. For future safety.. And even your imei.. And see features list...
Click to expand...
Click to collapse
Personally I liked it and have plan to use it unless a better version is released. So the credit goes to you.
But support for sd-ext might also have been a good addition in case someone has a natural inclination towards 2nd partition.
mirfatif said:
Personally I liked it and have plan to use it unless a better version is released. So the credit goes to you.
But support for sd-ext might also have been a good addition in case someone has a natural inclination towards 2nd partition.
Click to expand...
Click to collapse
I.........Agree:good:
Sent from my Nokia ara using XDA Labs
extractTarFork() process ended with ERROR=255
I'm in trouble
I:
Backed up my (CM11) system, boot, data and cache to SD card using your recovery
Successfully flashed Factory Firmware 2.1.0.13 using NCS
Unlocked bootloader through fastboot
Flashed yoAeroA00-R.img (extracted from yoAeroA00-TWRP-3.0.2.1_20170122.zip) through fastboot
Booted into recovery
Tried to restore my backup
But now I'm continuously getting this error:
extractTarFork() process ended with ERROR=255
Googled a bit and tried following one by one:
Wiped /data by manually selecting FS ext4 from advanced options
Fixed SELinux Contexts
Unmounted /data before restoring backup
Nothing works.
HELP!!!
EDIT:
Issue resolved. I booted to ROM and flashed recovery through RASHR. Everything is normal now
mirfatif said:
I'm in trouble
I:Backed up my (CM11) system, boot, data and cache to SD card using your recovery
Successfully flashed Factory Firmware 2.1.0.13 using NCS
Unlocked bootloader through fastboot
Flashed yoAeroA00-R.img (extracted from yoAeroA00-TWRP-3.0.2.1_20170122.zip) through fastboot
Booted into recovery
Tried to restore my backup
But now I'm continuously getting this error:
extractTarFork() process ended with ERROR=255
Googled a bit and tried following one by one:
Wiped /data by manually selecting FS ext4 from advanced options
Fixed SELinux Contexts
Unmounted /data before restoring backup
Nothing works.
HELP!!!
Click to expand...
Click to collapse
Data is encrypted so let your phone boot to stock ROM than try restoring data partition...
yoAeroA00 said:
Data is encrypted so let your phone boot to stock ROM than try restoring data partition...
Click to expand...
Click to collapse
Thanks. I flashed recovery through RASHR and everything worked well
Backup / Restore Encrypted /data Partition
yoAeroA00 said:
Data is encrypted so let your phone boot to stock ROM than try restoring data partition...
Click to expand...
Click to collapse
Is there a way to backup / restore encrypted /data partition?
mirfatif said:
Thanks. I flashed recovery through RASHR and everything worked well
Click to expand...
Click to collapse
What do you mean by RASHR??
Related
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
cyanogen said:
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (howto).
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. WIPE (wipe data/factor reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Latest version: 7.2.0-bravo - 18/03/2012
Download: CyanogenMod Mirror Network
Also available for download via ROM Manager
Google Addon:
Download: http://goo-inside.me/google-apps/
CM7 HBOOT r2 by Alpharev | xda thread
Change partition table size 145/5/287 (system/cache/size)
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7r2.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD:
Simple2Ext (Easy with a GUI)
CM7 Legacy App2SD Addon Script (For Advanced user, Command Line)
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
reserved for future use
Thank you!
Cant wait to see first CM9 Nightlies (yes i know it will be difficult to do because of HTC and QCOM but i still have hope)
Gr8!I'm downloading now,i know it takes too much to have such another rc version,thank you devs!
Sent from my HTC Desire using XDA
Download is very very slowly... :-(
Inviato dal mio HTC Desire usando Tapatalk
Quit complaining about the downloadspeed. Do you have any idea how many of us are probably downloading this rom right now?
via xda app
i try all rom,not all but many,and today is my first cyanogenmod
thanks
Jordywild said:
Download is very very slowly... :-(
Click to expand...
Click to collapse
http://www.cyanogenmod.com/blog
7.2RC1 is out for "only" 70 devices
Its probably placebo but this release candidate seems a lot smoother than the last nightlies. So issues so far. :thumbup:
via xda app
Im having problems installing market applications like:
SMS backup and restore
Call logs backup and restore
and other applications
Just in case you have successfully installed one of the following please post it. Maybe its my installer or something.
Thanks!
SMS backup and restore is fine. I just had my messages restored. Same with the other apps. I would suggest a clean install if you are having trouble.
via xda app
Thanks for everyones hard work on this. If upgrading from 7.1 can someone confirm if I need to do a wipe?
Thanks,
Womble
Update from CM 7.1.0 work? Because i get bootloop...
19blacktiger77 said:
Update from CM 7.1.0 work? Because i get bootloop...
Click to expand...
Click to collapse
Have you got EXT4 partition?
Is Cyano 7.2 compatible with EXT4 o EXT3 partition?
Jordywild said:
Have you got EXT4 partition?
Is Cyano 7.2 compatible with EXT4 o EXT3 partition?
Click to expand...
Click to collapse
I'm running 7.2.0RC1 with an ext3 partition. I have S2E installed for app2sd. I didn't upgrade from 7.1 though, I did a full wipe when I installed 7.2.0RC1.
frankoid said:
I'm running 7.2.0RC1 with an ext3 partition. I have S2E installed for app2sd. I didn't upgrade from 7.1 though, I did a full wipe when I installed 7.2.0RC1.
Click to expand...
Click to collapse
Full wipe?
I've got "only" 90 app installed.
Ok: I need a backup with Titanium.
You need to modify mountsd on the initd folder prior to flashing if you want the rom to see your ext4 partition... or flash ManU kernel.
http://forum.xda-developers.com/showpost.php?p=23017080&postcount=6689
via xda app
GPS does not works with this version... back to 7.1
Home button does not work... buggy...
Back to 7.1!
Jordywild said:
Have you got EXT4 partition?
Click to expand...
Click to collapse
Yes!
stankyou said:
You need to modify mountsd on the initd folder prior to flashing if you want the rom to see your ext4 partition... or flash ManU kernel.
http://forum.xda-developers.com/showpost.php?p=23017080&postcount=6689
via xda app
Click to expand...
Click to collapse
carval2k said:
GPS does not works with this version... back to 7.1
Click to expand...
Click to collapse
I will stay on 7.1 too...
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
WARNING: I've bricked my tablet into APX mode around the 10th time of flashing this ROM (recovery froze and it rebooted into APX). The new (Update 1) recovery should be safer than the old one, but flash at your own risk!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Device-specific source code for the Acer A700 are available from https://github.com/CyanogenMod/android_device_acer_a700 and https://github.com/CyanogenMod/android_kernel_acer_t30
Do not submit bug on CyanogenMod issue tracker
Downloads
Latest Nightly: http://get.cm/?device=a700
Google Apps: http://goo.im/gapps
Installation
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165 (note that the old touch version will not work because of incorrect default.prop from CWM builder)
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Changelog
A rough changelog is (will be) available here:
http://changelog.bbqdroid.org/#/cm10/a700 or http://cm10log.appspot.com/?device=a700
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Older pre-nightly Download
See this post.
Note to Official JB Users
Jelly Bean bootloader is only supported on 201212023-EXEPRIMENTAL and later NIGHTLIES.
Awesome!
will flash it later when back from work and provide feedback (too annoyed with the stock rom atm) so i will give it a go!
cheers
Awesome! Pace is speeding up. Thanks for your efforts.
pawitp said:
...
[*]Install CWM recovery from http://www.mediafire.com/?9usi98fs7jpdf7w (the touch version in the other thread will not work because of incorrect default.prop from CWM builder)
...
Click to expand...
Click to collapse
The CWM is not the one from the "CWM Recovery 6.0.1.0 for A700" thread, right?
Cheers
Peter
aticatac said:
Awesome! Pace is speeding up. Thanks for your efforts.
The CWM is not the one from the "CWM Recovery 6.0.1.0 for A700" thread, right?
Cheers
Peter
Click to expand...
Click to collapse
No, read inside the brackets
The "CWM Recovery 6.0.1.0 for A700" has broken build prop and will cause the device check to fail.
pawitp said:
No, read inside the brackets
The "CWM Recovery 6.0.1.0 for A700" has broken build prop and will cause the device check to fail.
Click to expand...
Click to collapse
Actually, I did read inside the brackets, but the CWM in the mentioned thread is not a touch version, or so I thought, that's why I asked.
EDIT: Now I realised that we were talking about the exact same thread title.
Anyways, I will flash this one, give it a whirl and read twice or more next time.
Jeez, where is my mind...
Thanks again.
Does the CM10 include the performance update?
does anyone else get e:Can't mount /sdcard/ ?
cwm tells me can't mount sdcard and emmc but data, cache and system mount fine (backup even stores on the sdcard under cwm folder)
Can you give us the MD5 CWM recovery ? Thx
ups forgot the most important screen
just redid it same error
PS:
(used your recovery.img as stated above)
Buster99 said:
ups forgot the most important screen
just redid it same error
PS:
(used your recovery.img as stated above)
Click to expand...
Click to collapse
dou you have an external sd card?
looking forward for cm on the a511. have fun with your a700
Sent from my A511 using XDA Premium HD app
What size should do the Nandroid Backup ? Mine do 15Mo !
Blindie said:
dou you have an external sd card?
Click to expand...
Click to collapse
yes but took it out prior flashing the recovery.img so atm no - no 2nd sdcard
Does it wipe the internal storage ?
imtheyoyo said:
What size should do the Nandroid Backup ? Mine do 15Mo !
Click to expand...
Click to collapse
mine is 165mb
aibo said:
Does it wipe the internal storage ?
Click to expand...
Click to collapse
should not since after successfull install you wipe cahce and dalvik not sd
i just reflashed the recovery - still no joy
Very nice ! Tanks a lot !
But no sound for me ...
Have you got sound ?
enico64 said:
Very nice ! Tanks a lot !
But no sound for me ...
Have you got sound ?
Click to expand...
Click to collapse
I have sound.
So far so good, thank you.
I do enjoy the lack of bloat.....
aibo said:
Does it wipe the internal storage ?
Click to expand...
Click to collapse
The installer doesn't, but you'll need to wipe data for it to boot successfully. Wiping data won't wipe your internal sdcard though.
I'm getting the triangle of death after flashing the recovery in the OP...
I had the other CWM you posted in the other thread which the tablet seemed to boot into just fine.
i'm running a a700 with the a701 rom from way back, is that my issue?
This ROM is for the KOREAN version of the Galaxy S5 with Snapdragon 805 -- G906S and K906K
LATEST VERSION CONFIRMED WORKING FOR THE G906L. See here
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
ROOT AND CUSTOM RECOVERY
Please go to this thread to get the custom recovery and how to root your device.
prodigiez has done an incredible job of finding and maintaining all the pieces that we need to root and play with our devices.
Per that thread: Do not wipe/factory reset to install this ROM. That may soft brick your phone. Just install the ROM on top of your stock ROM.
ROM FEATURES:
rooted
Doedex
Busybox
Knox has been removed
Added XPosed
No Wipe
Removed Korean characters from phone keypad
Added S5 International boot animation
SHealth is working with XPosed
Changed 3G to dispplay H or H+ depending on connection (LTE will display the same).
ijotech made an excellent video showing the installation and features of this ROM. You can find it here
Enjoy!
======================================================
TIPS
Thanks to hadinz you can finally have the camera shortcut in your lock screen while using secured lock-screen. Please follow the steps below:
"Go to system/csc/ and rename costumer.xml to costumer.xml.backup and then reboot... go to settings lockscreen/shortcut/camera and done.use root browser for renaming."
This also has the nice side effect to enable "Data Roaming" and VoLTE.
---------------------------------------------------------------------------------------
Please follow ijotech steps to get SHealth working after first boot. Not needed if you are flashing a newer version of the ROM and you already followed this procedure.
0. Optional: Link SHealth to your Samsung account and backup the data
1. Clear SHealth data and Health Services cache and data
2. Start SHealth and configure it (restore from backup)
3. Configure XPosed
======================================================
OTHER FILES AND TOOLS
Original G906S Bootanimation
DOWNLOAD here
MD5: 379deb9f337275dfa155b76b658feb7f
---------------------------------------------------------------------------------------
Add On Zip File for Stock Rooted ROMs -- NJ2
This Zip File includes the following features for Stock Rooted ROMs for those of you who don't want to flash this custom ROM but want these features:
XPosed
SHealth working with XPosed
Removed Korean characters from phone keypad
Added S5 International boot animation
Changed 3G to display H or H+ depending on connection (LTE will display the same).
DOWNLOAD here
MD5: df64e5339b0e6486b33aac2aa684363d
Install from custom recovery.
If you only want to replace the Dialer to remove the Korean characters, you can download the Replace_Keypad.zip file found at the end of this post. Once downloaded, unpack the file and double click on Replace_Keypad.bat.
If you only want to replace 4G with H/H+, you can download the Replace_4G.zip file found at the end of this post. Once downloaded, unpack the file and double click on Replace_4G.bat.
---------------------------------------------------------------------------------------
EFS BACKUP/RESTORE TOOL
I have put together a small batch file for Windows to backup and restore the EFS partition.
You must be rooted for this to work.
Download link and screenshots are at the bottom of this post.
BY USING THIS BATCH FILE YOU ACCEPT THAT I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE
---------------------------------------------------------------------------------------
MODEMS
WARNING: CHOOSE THE MODEM ACCORDING TO YOUR DEVICE: S OR K
To flash: Download the file that you need for your device. **DO NOT** extract the contents of the file. Flash with ODIN in download mode. In Odin add the file in CP.
Only use Odin 3.09 from here
If the modem is not updated, flash again the file.
MODEM G906S NJ2 -- Download here
MD5: b2fe7405a7dbb86f5bcc7f1aa3ff0c4f
MODEM G906K NK1 -- Download here
MD5: 6eb7a51ab6364df1fb4f05ccd6e08e29
======================================================
ROM DOWNLOADS
UPDATE 2014-11-22
UNIFIED VERSION FOR: S AND K
ROM FOR G906 K and S BASED ON G906KKTU1ANK1
Download here
MD5: 1ec741dd9754d5b925a36e2e431648bb
Change Log:
New Base change
Reported working: Hidden Menu and Voice Recording, and everything else!
========================================
Donations are not required, but are appreciated.
very good thread
great... Miscom rom
Thanks for the rom.
This phone is great + this Rom it becomes the best of the best
Can I use this rom on my tmobile Gs5? Thanks
Sent from my SM-G900T using XDA Free mobile app
Good job pal.. Thx for the contribution
xda23 said:
Can I use this rom on my tmobile Gs5? Thanks
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
No. He says at the top it is for the Korean 805 version.
miscom said:
This ROM is for the KOREAN version of the Galaxy S5 with Snapdragon 805 -- G906S and K906K
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
ROOT AND CUSTOM RECOVERY
Please go to this thread to get the custom recovery and how to root your device.
prodigiez has done an incredible job of finding and maintaining all the pieces that we need to root and play with our devices.
Per that thread: Do not wipe/factory reset to install this ROM. That may damage your phone. Just install the ROM on top of your stock ROM.
ROM FEATURES:
rooted
Doedex
Busybox
Knox has been removed
Added XPosed
No Wipe
Removed Korean characters from phone keypad
Added S5 International boot animation
SHealth is working with XPosed
Changed 3G to dispplay H or H+ depending on connection (LTE will display the same).
Enjoy!
========================================
Original G906S Bootanimation
DOWNLOAD here
MD5: 379deb9f337275dfa155b76b658feb7f
========================================
UPDATE 2014-08-06
ROM BASED ON G906KKTU1ANG8 v1.1a
Download here
MD5: e93fd16ade9baf75c857737df0e46f10
--------------------------------------------------------------------------------
UPDATE 2014-08-14
ROM BASED ON G906KKTU1ANH2 v1
Download here
MD5: 25c4fcaa1ae24ff8ba49178ba0db10e4
Change Log:
Just base change
========================================
Please follow ijotech steps to get SHealth working after first boot. Not needed if you are flashing a newer version of the ROM and you already followed this procedure.
0. Optional: Link SHealth to your Samsung account and backup the data
1. Clear SHealth data and Health Services cache and data
2. Start SHealth and configure it (restore from backup)
3. Configure XPosed
========================================
Click to expand...
Click to collapse
Great work. I imagine that you must download the zip and install from recovery and use the option install zip and you search the file.
My question is why can whe not wipe the phone?
Can whe use the other option of CWM for format the data internal memory?
Is there some video on YouTube to see the options of these ROM? Have you included some auto update for future updates or must she reinstall all the new version?
Which of the 2 files is the latest version the v1.0 or v.1.1
Must whe install bootlogo or is it optional?
pollet82 said:
Great work. I imagine that you must download the zip and install from recovery and use the option install zip and you search the file.
My question is why can whe not wipe the phone?
Can whe use the other option of CWM for format the data internal memory?
Is there some video on YouTube to see the options of these ROM? Have you included some auto update for future updates or must she reinstall all the new version?
Which of the 2 files is the latest version the v1.0 or v.1.1
Must whe install bootlogo or is it optional?
Click to expand...
Click to collapse
Yes, you download the ZIP file and flash it from recovery. There is a bug in the only available CWM recovery. If you need to wipe data, I would recommend that you format the data partition. Never use Wipe/Factory Reset.
I don't have any videos for the ROM features. Besides the changes listed in the OP, this is pure stock. Everytime that there is an update you would have to download the new ZIP file and flash it from recovery.
No need to install the Boot animation unless you want the Korean boot animation back.
The ROM versions are based on the Samsung versions and the changes I make to each version.
For instance, the Samsung version is NG8 and is followed by 1.1a it means that I have made a few revisions to the ROM based on NG8.
After NG8 came NH2 (H after G) and the ROM based on version NH2 has only had one revision (version 1).
I hope that this makes sense. Always look at the update date to determine which one is the latest version.
I will make a video of this rom if you like and post it on my youtube channel. Like a video tour
ijotech said:
I will make a video of this rom if you like and post it on my youtube channel. Like a video tour
Click to expand...
Click to collapse
That would be great! Thank you!
Let us know once done.
install and overview of his rom Video
http://youtu.be/4aomOpDVhbM
http://youtu.be/4aomOpDVhbM
i made this video youtube still processing it but soon it will be up
miscom said:
That would be great! Thank you!
Let us know once done.
Click to expand...
Click to collapse
Is there any way to get rid of the annoying "set warranty bit:kernel" message once you've installed the custom ROM?
Also same question for the korean characters on the boot logo.
Thanks a lot in advance!
OliTc said:
Is there any way to get rid of the annoying "set warranty bit:kernel" message once you've installed the custom ROM?
Also same question for the korean characters on the boot logo.
Thanks a lot in advance!
Click to expand...
Click to collapse
As far as I know, The "set warranty bit:kernel" is either coming from the recovery's kernel or the ROM's kernel. Both have been modified not conforming to the Samsung security model. Therefore the message.
Those Korean characters are coming from the bootloader itself prior to loading Android's kernel. I am not sure how to modify that. Maybe Hex Editing the boatloader file and flashing it back with Odin?
Hey Miscom:
I really appreciate your development with the G906S/K. There aren't many devs for this device yet so you are a pioneer in the field!
Couple quick questions:
Does the international Samsung boot animation you added in replace the branded animation?
Let me elaborate: so initially the phone boots up saying S5 LTE-A, then followed up by the corresponding telecommunication company animation. So SKT on the G906S and Olleh on the G906S.
That bloat ware animation is the one that is removed and replaced, right?
Secondly, is the H/H+ vanilla to other phone variants of TouchWiz?
Also could you enlighten me on the following features:
Xposed
No Wipe
Thanks man
miscom said:
Yes, you download the ZIP file and flash it from recovery. There is a bug in the only available CWM recovery. If you need to wipe data, I would recommend that you format the data partition. Never use Wipe/Factory Reset.
I don't have any videos for the ROM features. Besides the changes listed in the OP, this is pure stock. Everytime that there is an update you would have to download the new ZIP file and flash it from recovery.
No need to install the Boot animation unless you want the Korean boot animation back.
The ROM versions are based on the Samsung versions and the changes I make to each version.
For instance, the Samsung version is NG8 and is followed by 1.1a it means that I have made a few revisions to the ROM based on NG8.
After NG8 came NH2 (H after G) and the ROM based on version NH2 has only had one revision (version 1).
I hope that this makes sense. Always look at the update date to determine which one is the latest version.
Click to expand...
Click to collapse
Tanks for the answer.
When whe install the roms what options can whe use for erase/format the memory off thease options?
* Wipe Data/Factory Reset
* Wipe Cache Partition
* Advanced -> Wipe Dalvik Cache
* Mounts and Storage -> format /cache
* Mounts and Storage -> format /system
* Mounts and Storage -> format /data
* Mounts and Storage -> format /sdcard
* Mounts and Storage -> format /emmc
Teorical whe can only use format /cache, format /data, format /sdcard and format /emmc is thease right?
xNiNELiVES said:
Hey Miscom:
I really appreciate your development with the G906S/K. There aren't many devs for this device yet so you are a pioneer in the field!
Couple quick questions:
Does the international Samsung boot animation you added in replace the branded animation?
That is correct.
Let me elaborate: so initially the phone boots up saying S5 LTE-A, then followed up by the corresponding telecommunication company animation. So SKT on the G906S and Olleh on the G906S.
That bloat ware animation is the one that is removed and replaced, right? Right.
Secondly, is the H/H+ vanilla to other phone variants of TouchWiz?
Yes. This is the first time that I see a Samsung device not showing H/H+. That's why I made the change as suggested by prodigiez Could this be how it's use in Korea?.
Also could you enlighten me on the following features:
Xposed
No Wipe
XPosed: An advanced framework that allows you to tweak your device to your heart's content. The best way to understand it, it's to use it. Be careful, though, you may do something with that may create issues. In that case just reflash the ROM and start over.
No wipe: The ROM will not wipe the data partition during installation
Thanks man
Click to expand...
Click to collapse
My answers above in red.
pollet82 said:
Tanks for the answer.
When whe install the roms what options can whe use for erase/format the memory off thease options?
* Wipe Data/Factory Reset
* Wipe Cache Partition
* Advanced -> Wipe Dalvik Cache
* Mounts and Storage -> format /cache
* Mounts and Storage -> format /system
* Mounts and Storage -> format /data
* Mounts and Storage -> format /sdcard
* Mounts and Storage -> format /emmc
Teorical whe can only use format /cache, format /data, format /sdcard and format /emmc is thease right?
Click to expand...
Click to collapse
You can format /data and /cache. Never format the SDCard. This would wipe your pictures and other documents that you may have there.
And never format /emmc.
miscom said:
You can format /data and /cache. Never format the SDCard. This would wipe your pictures and other documents that you may have there.
And never format /emmc.
Click to expand...
Click to collapse
Ok, but my propose is to know when i can use thease formats, i mean when i will sell the phone i will erase it completly, then i must use the:
Mounts and Storage -> format /cache
Mounts and Storage -> format /data
Mounts and Storage -> format /sdcard
Mounts and Storage -> format /emmc
Is thease correect?
The format emmc is for the external SD card?
The only think that its not allowed is to wipe the phone?
pollet82 said:
Ok, but my propose is to know when i can use thease formats, i mean when i will sell the phone i will erase it completly, then i must use the:
Mounts and Storage -> format /cache
Mounts and Storage -> format /data
Mounts and Storage -> format /sdcard
Mounts and Storage -> format /emmc
Is thease correect?
The format emmc is for the external SD card?
The only think that its not allowed is to wipe the phone?
Click to expand...
Click to collapse
I see your point now. Yes, you would format /cache, /data and /sdcard. I would **not** format /emmc. I have never done it and I have read that doing that creates issues. I would remove the external SD Card and format it in a PC.
NOTE:As i have already moved on to the S6 edge, the amount of support that i can provide would be minimal
THIS IS COMPATIBLE WITH ALL VARIANTS OF THE NOTE 3.
Firstly f2fs can only be used with f2fs compatible KERNEL'S and if you brick your device,Its just because you didnt read and follow the instructions listed from this part of the OP.
Before we start,I would like to thank @psycho4us4 who had allowed me to start a guide thread on the Note3 Forums on f2fs based on his thread from the Note2 http://forum.xda-developers.com/note-2-tmobile/development/how-to-conversion-t2853975
Kernel's with full f2fs support>System,Cache,Data
-Lean Kernel http://forum.xda-developers.com/showthread.php?t=2488082
(Tested)
-Shinto kernel.
http://forum.xda-developers.com/showthread.php?t=2895089
(Tested)
Feel free to inform me on kernels which have full support with all 3 partitions mentioned
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INSTRUCTIONS FOR CONVERSION OF EXT4 TO F2FS
1.Make sure you have the latest TWRP Recovery on your device(V2.8.1.0 Should be good to go) Get it here> http://teamw.in/project/twrp2
2.In the { Settings } menu of TWRP make sure the [ Use rm -rf instead of formatting ] is unchecked MAKE A FULL, COMPLETE BACKUP with TWRP 2.8.1.0 ( I can't stress this enough if you don't want to use Odin). Keeping in mind that whatever format your partitions are is what format they will be backed up as, such as EXT2, EXT3, EXT4, FAT, F2FS, etc. This will wipe INTERNAL SD so please make a backup of it to your EXT SD CARD/EXTERNAL MEMORY DRIVE.
3. Next from TWRP home, select { WIPE }
4. Then select { ADVANCED WIPE }
5. Then select { CACHE } and click { REPAIR OR CHANGE FILE SYSTEM }
6. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
7. Now select { SYSTEM } and click { REPAIR OR CHANGE FILE SYSTEM }
8. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
9. Then select { DATA } and click { REPAIR OR CHANGE FILE SYSTEM }
10. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
11. Next from TWRP home, click { Settings } then { X } the box that says [ Use rm -rf instead of formatting ].
12. Hit the back button, then select { Restore }. Click on the package you want to restore ( this is the backup you made in step #2 )'
13. Next { X } the boxes { CACHE, SYSTEM, and DATA ONLY }. Then SWIPE TO RESTORE.
14. ALL DONE now just click { Reboot System }
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Just in case you have a problem and you needed to convert back to EXT4,Here is how you do it
INSTRUCTIONS FOR CONVERSION FROM F2FS TO EXT4
1. If you don't already have a backup that you want to use ( backed up with the [ Use rm -rf instead of formatting ] UNCHECKED ) then make one using Step 2 from above instructions.
2. Follow steps 2 through 14 from above, the only thing you have to do different is, instead of choosing { F2FS } for the file format you can choose ANY of the options available as long as the KERNEL you are running supports the format you are switching to.
3. That"s it
3a. If you already have a backup done with the format you desire all you have to do is make sure the [ Use rm -rf instead of formatting ] option is UNCHECKED then restore the { CACHE } AND { SYSTEM } partitions from the package you desire that was made in the format you desire.
3b. The { DATA } has to be done manually by following steps 3, 4, 9, 10 but then hit the back button till your at the TWRP home screen. Next do step 11. Then restore the { DATA } partition from the same backup as mentioned in step 3a.
3c. Reboot and done!
--------------------------------------------------------------------------------------------------------------------------------
sorry to ask that but what's the interest of that manipulation??????
rayman95 said:
sorry to ask that but what's the interest of that manipulation??????
Click to expand...
Click to collapse
In my opinion, f2fs would definitely boost the speed of your device or rather smooth it out and help with reliability.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
In my opinion, f2fs would definitely boost the speed of your device or rather smooth it out and help with reliability.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
Great. Thanks for the guide. I'm sure you note 3 users will love this.
Thank you for this !
Testing right now.
i'll backup everything and save in external microsd, never know ...
---------- Post added at 07:59 PM ---------- Previous post was at 07:35 PM ----------
I receive the message 'FAILED' when attemting to restore the system partition, but only at the and, after restoring all of the 2 GB
going on, maybe it'll work ...
adario73 said:
Thank you for this !
Testing right now.
i'll backup everything and save in external microsd, never know ...
---------- Post added at 07:59 PM ---------- Previous post was at 07:35 PM ----------
I receive the message 'FAILED' when attemting to restore the system partition, but only at the and, after restoring all of the 2 GB
going on, maybe it'll work ...
Click to expand...
Click to collapse
Try slimming down your system partition before you make the backup. It's got to be twrp blocking the restoration of such a large system partition. We have the same issue with the note 2. Only for some users though.
psycho4us4 said:
Try slimming down your system partition before you make the backup. It's got to be twrp blocking the restoration of such a large system partition. We have the same issue with the note 2. Only for some users though.
Click to expand...
Click to collapse
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
adario73 said:
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
Click to expand...
Click to collapse
I hear ya. I also think it's time for someone to talk to bigbiff about this issue. Whatcha think @lanchua
psycho4us4 said:
I hear ya. I also think it's time for someone to talk to bigbiff about this issue. Whatcha think @lanchua
Click to expand...
Click to collapse
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
adario73 said:
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
Click to expand...
Click to collapse
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
Hit me on hangouts.
[email protected]
Ianchua said:
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
i'm on XNote ( not the S5 port ), the last version published here ...
thank you for this.
I'm really curious to see the performances of f2fs on note3
adario73 said:
i'm on XNote ( not the S5 port ), the last version published here ...
thank you for this.
I'm really curious to see the performances of f2fs on note3
Click to expand...
Click to collapse
Alright. By the way which Variant of the Note3 are you using?
And trust me, the effects is very visible ask the Note 2 guys who used it! They will tell you that its real good! And touchwiz lag? It tamed it
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Alright. By the way which Variant of the Note3 are you using?
And trust me, the effects is very visible ask the Note 2 guys who used it! They will tell you that its real good! And touchwiz lag? It tamed it
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
you are making me VEEEERY curious !
the variant i have is HLTE N9005
adario73 said:
you are making me VEEEERY curious !
the variant i have is HLTE N9005
Click to expand...
Click to collapse
Than you should be good to go.
Try this steps,
After formatting one partition and converting it, reboot to recovery before moving on to format and convert other partitions from there.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Than you should be good to go.
Try this steps,
After formatting one partition and converting it, reboot to recovery before moving on to format and convert other partitions from there.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
The only partition that fails ( to restore ) is system.
So, if i well understood, i should try the following :
- format the system partition;
- restart recovery;
- restore the partition from the backup.
ok, i'll try !
thank you again !
EDIT : tried and does not work, reverting again to ext4
adario73 said:
The only partition that fails ( to restore ) is system.
So, if i well understood, i should try the following :
- format the system partition;
- restart recovery;
- restore the partition from the backup.
ok, i'll try !
thank you again !
EDIT : tried and does not work, reverting again to ext4
Click to expand...
Click to collapse
Does the back up of your ROM consist of a F2FS compatible kernel? If it does not, than it could be why your system refused to get restored.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Does the back up of your ROM consist of a F2FS compatible kernel? If it does not, than it could be why your system refused to get restored.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
At the moment i'm using Ultimate Kernel, which is F2FS compatible.
What if i format using F2Fs and then do a clean install ?
Will i be able to restore a Titanium backup ? ( why not ... )
adario73 said:
At the moment i'm using Ultimate Kernel, which is F2FS compatible.
What if i format using F2Fs and then do a clean install ?
Will i be able to restore a Titanium backup ? ( why not ... )
Click to expand...
Click to collapse
Yes definitely. Just remember to put your TB backup folder in External SD card.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Yes definitely. Just remember to put your TB backup folder in External SD card.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
OK, flashing right now on F2FS partition, will report later ( after succesful apps restore )
...
...
not booting ...
clean install failed !!!
...
...
flashed LeanKernel, doesn't boot .
it really seems i can't use F2FS goodness on my Note3
adario73 said:
OK, flashing right now on F2FS partition, will report later ( after succesful apps restore )
...
...
not booting ...
clean install failed !!!
...
...
flashed LeanKernel, doesn't boot .
it really seems i can't use F2FS goodness on my Note3
Click to expand...
Click to collapse
Okay. Try this once more,
Try Conerting the System to f2fs first than convert the rest there after.
Reboot to recovery after doing all this
For the restore part. Restore System,cache and data separately with reboot to recovery in between.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Code:
#include
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy ACE 3 LTE. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card (non tested)
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation, Note: Only manual installation is supported, because this mod is not officially supported.
MultiROM has 3 parts you need to install:
MultiROM
Modified recovery
Patched kernel
Now let's head to the installation. Note: Your primary ROM is recommended to be lollipop, because it doesn't act well as a secondary, due to enforcing selinux. Although you can use it as secondary, but change it's selinux status. My setup is Lollipop as primary, and KitKat as secondary. Stock ROM was not tested, because I hate it
I spent about 5 days working on this. My head will explode There is a tiny issue. MultiROM boot menu does not show up as it should. That's why we should use the MultiROM manager apk. and switch ROMs from the app.
Attention: The steps are if you use CM-12.1 as primary ROM
Kernel for Stock ROM with kexec-hardboot patch here
Step 1: Install this patched kernel over CM12.1. Or this, if you want OC.
Step 2: Install the modified Multirom Manager apk, I added support for our device
Step 3: Install Multirom
Step 4: Install MultiROM TWRP, via previous TWRP recovery, it can flash images
Step 5: Reboot into new recovery
Step 6: Install CM11, as secondary ROM!!
Step 7: Go to recovery-->Advanced-->MultiRom-->List ROM-->Choose CM11-->Flash Zip. Flash either stock kernel, or oc_kernel. Both include the necessary kexec-hardboot patch. Usually Multirom requires only primary ROM to have the kexec-hardboot patch, but in our case it does not work this way.
Now you are ready to switch ROMs. Ooh, almost forgot. MultiROM boot manager will show up if you connect the phone for offline charging, you will find out what happens on each case. This is the only bug that I can't resolve yet. Although multirom can be used, with this bug.
Code:
Update 20150829: Download everything from this [URL="https://androidfilehost.com/?w=files&flid=37974"]folder[/URL]
Kernel will be updated when ROM is built
Changelog: Re-implemented kexec hardboot and fixe last_kmsg creation
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
NOTE: If secondary ROM does not boot, select Restorecon under multirom
Click to expand...
Click to collapse
Switch ROMs from the MultiRom manager app
NOTICE: I can't guarantee it will work on other variants rather than "R"
To uninstall Multirom simply flash this
You current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
CM12.1 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-12.1
CM11 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-11.0
Stock kernel for stock rom w/ kexec-hardboot patch - https://github.com/kostoulhs/android_kernel_samsung_loganrelte/tree/master
MultiROM device tree - https://github.com/kostoulhs/android_device_samsung_loganreltexx/tree/multirom
Big thanks to Tasssadar for this awesome utility.
Also thanks @Grarak for the melius patch, i was based on it
Reserved
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Levivig said:
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Click to expand...
Click to collapse
Exactly
Sent from my GT-S7275R
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
F. Dutch said:
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
Click to expand...
Click to collapse
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
kotzir said:
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
Click to expand...
Click to collapse
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
zh_eco said:
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
kotzir said:
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
Click to expand...
Click to collapse
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Or just we will never can install ROMs on the SD card ?
Sent from my GT-S7275R using XDA Free mobile app
zh_eco said:
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
kotzir said:
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
Click to expand...
Click to collapse
So we will stay do this , just if we install a ROM in the SD card .
Or what ?! :|
OK , after flashing the stock kernel with kexec-hardboot patch, I can't flash any other kernel like arasma kernel in my stock ROM(4.2.2) ?
If I can't .. Can you make a kexec-hardboot patch for arasma kernel ?
Here : http://d-h.st/aYr
Or .. Can you make the lollipop kernel (1.7GHz) work on the stock ROM ?
Sent from my GT-S7275R using XDA Free mobile app
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
zh_eco said:
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
Click to expand...
Click to collapse
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
kotzir said:
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
Click to expand...
Click to collapse
:good::good: Nice Work Man
zh_eco said:
Can I Make My Setup Like This ? :
...my sd card use ext4 partition , is this partition supported ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
May I ask why you do this?
MTP practically destroys any real world benefit that EXT could possibly offer you, and if you use UMS et al you'll hit permissions issues with the media that completely ruin its ability to function as removable storage unless every single one of the systems it touches only has a single user or you carefully craft the system environment so that the user always has the same UID.
It's just weird to use a journalled filesystem with access permissions as removable storage. Either MTP destroys any gains you might possibly get, or UMS makes it impossible to access the contents of the volume on ~99% of all the systems you'll ever encounter in the wild. Ever wondered why you never see external storage volumes with permission based filesystems? This is why. It's largely silly.
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
F. Dutch said:
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
Click to expand...
Click to collapse
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
kotzir said:
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
Click to expand...
Click to collapse
Thanks but the only backups i have of stock are made with CWM. When i try to restore it says .Android_secure.vfat.Tar and .Android_secure.vfat.Tar.a are missing so i can't restore and make a backup with TWRP. Found some info about it and trying tot make it work right now.
kotzir said:
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
Click to expand...
Click to collapse
Thank U Very Much @kotzir For Adding My Videos To "OP"
Small update, check OP