(Q) S6 port for N900 exynos - Galaxy Note 3 Developer Discussion [Developers Onl

Any one help I am porting s6 apps from note 4 exynos and also have s4 exynos both compared to same chipset to n3 900 after flashing stuck on boot animation
Logcat art runtime error
and I copied 3 runtime related lib files from port rom now screen is blank after Samsung logo
Log cat
Service waiting for media policy
I edited framework and smali values to disable signature check still black screen but log cat running
Sent from my SM-N900 using Tapatalk

samjsrmj said:
Any one help I am porting s6 apps from note 4 exynos and also have s4 exynos both compared to same chipset to n3 900 after flashing stuck on boot animation
Logcat art runtime error
and I copied 3 runtime related lib files from port rom now screen is blank after Samsung logo
Log cat
Service waiting for media policy
I edited framework and smali values to disable signature check still black screen but log cat running
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
which ROM are you using as base and port?
which method are you using to port?

Stock rom as base port part from s6 dump part from s4 9500
The method dsixda kitchen
Sent from my SM-N900 using Tapatalk

samjsrmj said:
Stock rom as base port part from s6 dump part from s4 9500
The method dsixda kitchen
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
may be you should use CM 12 (5.0.2) as base because base and port must have same android version
and use this method
http://forum.xda-developers.com/showthread.php?t=2245786
OR
http://forum.xda-developers.com/showthread.php?t=1908008

samjsrmj said:
Any one help I am porting s6 apps from note 4 exynos and also have s4 exynos both compared to same chipset to n3 900 after flashing stuck on boot animation
Logcat art runtime error
and I copied 3 runtime related lib files from port rom now screen is blank after Samsung logo
Log cat
Service waiting for media policy
I edited framework and smali values to disable signature check still black screen but log cat running
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Wait for 5.1.1 official update. Then you can easily port S6, Note 5 and S6 Edge+ roms, because they are running 5.1.1

Vishnu pv said:
Wait for 5.1.1 official update. Then you can easily port S6, Note 5 and S6 Edge+ roms, because they are running 5.1.1
Click to expand...
Click to collapse
Good news....hope samsung gives us 5.1.1 soon then

Modifying Framework causes you to have a bootloop.

Related

Cyanogenmod 11 for T211 (galaxy tab 3 inch 7 3g)

Hi for all, I port cm11 for galaxy tab 3 inch 7 3g. But this rom have a lot of issue. I work very hard to solve this. I'm new develop but I'm try.
What work ?
boot,touch,gpu
What the problems ?
wifi
force close every time systemui
You can access first time menu, when you reboot you can't access.
etc.
I think this problem occur because the kernel. My occur kernel is the stock. I search solution to solve this problem and I accept any people expert on my group because I'm alone.
- Make sure you're running latest PhilZ Touch or CWM (TWRP not updated yet for SELinux)
- Copy CM to your SDCard
- Boot into Recovery and MAKE A BACKUP
- DO A DATA WIPE / FACTORY RESET
- Flash CM zip from SDCard
- Reboot
Cyanogenmod 11 beta 1
http://www.4shared.com/zip/RXv69DCwce/cyanogemod_11_beta_1_Galaxy_ta.html?
Hi dude good courage to bring CM for us....best to tag this [Dev] to get attention from the Developers here
Sent from my SM-T211 using XDA Premium 4 mobile app
andynroid said:
Hi dude good courage to bring CM for us....best to tag this [Dev] to get attention from the Developers here
Sent from my SM-T211 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks by attention , I need person expert to develop a kernel
GREAT JOB
:good: :laugh: this is what all st-211's users have beeen waiting for .I´ll test it as soon as wifi works ( i need it for work :silly: )
Problem with kernel source ;-;
hehk1234 said:
I think this problem occur because the kernel. My occur kernel is the stock. I search solution to solve this problem and I accept any people expert on my group because I'm alone.
I recorded a video about this https://www.youtube.com/watch?v=Lh1E2ybjQF4
Click to expand...
Click to collapse
I can't find any KitKat source for Tab 3 7.0 3G for now
A guy here on the forum, almost succeeded porting KK but Wi-Fi still don't work.
We need a device with similar specs (CPU, GPU, RAM etc) running KK or having KK Source
I will asked the member who ported it to SM-T210 on how he did build the kernel.
Hi for all, I port cm11 for galaxy tab 3 inch 7 3g. But this rom have a lot of issue. I work very hard to solve this. I'm new develop but I'm try.
What work ?
boot,touch,gpu
What the problems ?
wifi
force close every time systemui
You can access first time menu, when you reboot you can't access.
etc.
Click to expand...
Click to collapse
Nice work, BTW.
Keep trying :good:
Note:
You should mention developers like @ketut.kumajaya ; @gr8nole ; @safariking etc to wish their attention :angel:
Good luck.
galaxy tab 4 7.0
Nonta72 said:
I can't find any KitKat source for Tab 3 7.0 3G for now
A guy here on the forum, almost succeeded porting KK but Wi-Fi still don't work.
We need a device with similar specs (CPU, GPU, RAM etc) running KK or having KK Source
I will asked the member who ported it to SM-T210 on how he did build the kernel.
Nice work, BTW.
Keep trying :good:
Note:
You should mention developers like @ketut.kumajaya ; @gr8nole ; @safariking etc to wish their attention :angel:
Good luck.
Click to expand...
Click to collapse
Galaxy tab 3 7.0 and galaxy tab 4 7.0 have same gpu and powered by marvell pxa galaxy tab 4 7.0 run on 4.4.2 galaxy tab 4 7.0 3g kk source http://opensource.samsung.com/reception/receptionSub.do?method=search
Please stop mentioned me about this T21x development. I don't own this device, hard for me to fix a specific issue. All my works and instructions available on github, @gr8nole works also available on github. Sometimes I just come and asking for a log but don't expect a solution from me. Sometimes I check gr8nole source, I'll give an advice if necessary.
ketut.kumajaya said:
Please stop mentioned me about this T21x development. I don't own this device, hard for me to fix a specific issue. All my works and instructions available on github, @gr8nole works also available on github. Sometimes I just come and asking for a log but don't expect a solution from me. Sometimes I check gr8nole source, I'll give an advice if necessary.
Click to expand...
Click to collapse
Ok, You know any dev expert have SM-t211 ?
ketut.kumajaya said:
Please stop mentioned me about this T21x development. I don't own this device, hard for me to fix a specific issue. All my works and instructions available on github, @gr8nole works also available on github. Sometimes I just come and asking for a log but don't expect a solution from me. Sometimes I check gr8nole source, I'll give an advice if necessary.
Click to expand...
Click to collapse
Sorry for mentioning Ketut
Always respect your work
---------- Post added at 08:47 PM ---------- Previous post was at 08:32 PM ----------
Anil Shovo said:
Galaxy tab 3 7.0 and galaxy tab 4 7.0 have same gpu and powered by marvell pxa galaxy tab 4 7.0 run on 4.4.2 galaxy tab 4 7.0 3g kk source http://opensource.samsung.com/reception/receptionSub.do?method=search
Click to expand...
Click to collapse
I know Tab 3 and 4 are using same GPU
However, CPUs are a bit different (Quad vs Dual).
So, that could be a problem. Ketut wrote on one of his posts he was trying to port Tab 4 7.0 KK to Tab 3 7.0 since both are powered by a Marvel CPU and Vivante GPU.
BTW, he just told he no longer a Tab 3 7.0 so we're unlucky about him.
I dont know how to contribute. What can I help? I am not a dev, but can not wait that cm11 com to my tab 3 7..
Sent from my SM-T211 using Tapatalk
same
Nodali said:
I dont know how to contribute. What can I help? I am not a dev, but can not wait that cm11 com to my tab 3 7..
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
me toooo
Nodali said:
I dont know how to contribute. What can I help? I am not a dev, but can not wait that cm11 com to my tab 3 7..
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
We will wait a blackhawk kernel 2.2 . Maybe the dev can addict support for cm 11. If you go to the topic of "blackhawk kernel" you see the users of galaxy tab 3 7 wifi have same problem
hehk1234 said:
Thanks by attention , I need person expert to develop a kernel
Click to expand...
Click to collapse
No one as best as @ketut.kumajaya did...
But @gr8nole is developing similar device T210, he's the best one too..
---------- Post added at 10:20 PM ---------- Previous post was at 10:01 PM ----------
hehk1234 said:
We will wait a blackhawk kernel 2.2 . Maybe the dev can addict support for cm 11. If you go to the topic of "blackhawk kernel" you see the users of galaxy tab 3 7 wifi have same problem
Click to expand...
Click to collapse
or... should we donate him for buying the device?
they work nice
bangdes said:
No one as best as @ketut.kumajaya did...
But @gr8nole is developing similar device T210, he's the best one too..
Click to expand...
Click to collapse
they work nice i like 1 more devloper @bieltv.3 he is best devloper for me and Stop mentioning ketut and gr8nole they are feeling boar
Wow, nice work!
:thumbup:
Sent from my GT-P3100 using XDA Premium 4 mobile app
Hmmm... Tempted to help, @hehk1234 could you pull the logcat please?
Sent from my GT-I9300 using XDA Premium 4 mobile app
@hehk1234 i think there's something wrong when you build this rom, check a look your build.prop :
there's 2 'ro.build.id' and 'ro.build.display.id' in a build.prop with different android type, Kitkat (KTUxxx) vs Jellybean (JZOxxx) it will make a conflict....
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84M <----- this is id for KITKAT
ro.build.display.id=cm_lt02wifi-userdebug 4.4.3 KTU84M eba7697e4e test-keys
ro.build.id=JZO54K <------ and this is id for JELLYBEAN
ro.build.display.id=JZO54K.T211ZSAMI3 <------ and this is a stock rom id (how could be here?)
ro.build.version.incremental=eba7697e4e
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.3
ro.build.date=Thu Jun 19 12:58:09 EDT 2014
ro.build.date.utc=1403197089
ro.build.type=userdebug
ro.build.user=dave
ro.build.host=noletude
ro.build.tags=test-keys
bangdes said:
@hehk1234 i think there's something wrong when you build this rom, check a look your build.prop :
there's 2 'ro.build.id' and 'ro.build.display.id' in a build.prop with different android type, Kitkat (KTUxxx) vs Jellybean (JZOxxx) it will make a conflict....
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84M <----- this is id for KITKAT
ro.build.display.id=cm_lt02wifi-userdebug 4.4.3 KTU84M eba7697e4e test-keys
ro.build.id=JZO54K <------ and this is id for JELLYBEAN
ro.build.display.id=JZO54K.T211ZSAMI3 <------ and this is a stock rom id (how could be here?)
ro.build.version.incremental=eba7697e4e
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.3
ro.build.date=Thu Jun 19 12:58:09 EDT 2014
ro.build.date.utc=1403197089
ro.build.type=userdebug
ro.build.user=dave
ro.build.host=noletude
ro.build.tags=test-keys
Click to expand...
Click to collapse
These 2 lines also means that build.prop came from my T210 build and was edited...
Code:
ro.build.user=dave
ro.build.host=noletude
gr8nole said:
These 2 lines also means that build.prop came from my T210 build and was edited...
Code:
ro.build.user=dave
ro.build.host=noletude
Click to expand...
Click to collapse
Whoaa! Glad to see you here...
Of course, basically T210 and T211 is similar device with different in simcard. And we really sure what your build in T210 is gonna be useful, very useful, for our T211.
We're really need your advice... please :crying:
bangdes said:
Whoaa! Glad to see you here...
Of course, basically T210 and T211 is similar device with different in simcard. And we really sure what your build in T210 is gonna be useful, very useful, for our T211.
We're really need your advice... please :crying:
Click to expand...
Click to collapse
Are you guys actually compiling or just trying to flash the T210 version?
Either way, it doesn't really matter if we don't figure out the hwcomposer and wifi (which isn't looking very promising).

[TOOL] [MultiSystem] MultiROM and Recovery Replacement for Android

​
MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices.
★ Disclaimer:
This service is FREE of charge, use it at your own risk, take it or leave it !
Click to expand...
Click to collapse
THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USE AT YOUR OWN RISK!
Click to expand...
Click to collapse
MultiSystem is a powerful tool and can perform potentially dangerous and/or destructive operations on your device and data that may affect your life. While it is unlikely to do irreversable damage to your device, it is not impossible, and you should proceed with caution. Loss of data and/or the need to re-flash a full stock (manufacturer-supplied) firmware IMGs (usually requiring a computer) is always a possibility, and is increasingly likely if you do not know what you are doing. It is possible to lose root access when using MultiSystem on locked-bootloader devices running unexpoitable (bu rooted) Android firmware, without careful reading of documentation or following the instructions. Please consult with expert users before performing actions you do not comprehend.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Notes:
To devs: Please do not use/port MultiSystem to any other device. If you'd like to add support for your device, please contact me!
Click to expand...
Click to collapse
To users: This thread is only for DEVELOPMENT. If you need a place for general discussions, go to MultiSystem Q&A thread.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Features:
Keeps stock system partition safe/rooted
Permenant root survival with proper use
MultiROM support via virtual ROMs
Unlimited number of virtual ROMs
Booting options to choose stock, primary, or secondary virtual ROM
Any of the virtual ROMs can work as a recovery replacement
Flashing multiple ROMs at the same time without a reboot
Ability to create/install ROMs on Linux to microSD card
Great performance & battery life on virtual ROMs
Recovery solution to install ROMs or Mods
Easy upgrade to newer versions of Android
Ability to safely apply OTA updates to virtual system
Permissive SELinux and other kernel tweaks
Safe flashing that doesn't trip KNOX flag on Samsung devices
Wrapper script runs via ADB or a Terminal Emulator on device
APK to manage all MultiSystem functions with a nice UI and extra options
Management for the best performance & user experience
Support for all Android devices with microSD card
Portability to almost all devices
Compatibility with all Android versions
Click to expand...
Click to collapse
★ ChangeLog:
Check the updated changelog in the main development thread!
Click to expand...
Click to collapse
★ Instructions:
Check the updated instructions in the main development thread!
Click to expand...
Click to collapse
★ Downloads:
Download the latest version from the main development thread!
Click to expand...
Click to collapse
★ Credits:
@ChainFire - for SuperSU & FlashFire
@Hashcode - for Safestrap Recovery
@[NUT] - for XZDualRecovery
@Androguide.fr - for APKreator & various libraries/apps
Jack Palevich - for Terminal Emulator for Android
@osm0sis - for Android Image Kitchen
All authors of binaries/libraries, source codes, or tutorials...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'd like to thank everyone who made a donation just to show appreciation.
It's fine to just click Thanks! or enjoy my work without saying anything.
A donation is to show appreciation of the work I have done already.
A donation is not by any means in expectation of future work.
A donation doesn't entitle for preferred/private support/requests.
A donation is meant as a gift - always appreciated, never required.
Click to expand...
Click to collapse
Verizon Samsung Galaxy Note 4 (N910V), Note 3 (N900V) & LG G3 (VS985)
Hit thanks, follow thread & add 5-star rating/review... Donations are always appreciated!
​
XDA:DevDB Information
MultiSystem, Tool/Utility for the AT&T Samsung Galaxy S 5
Contributors
hsbadr
Source Code: https://github.com/hsbadr/MultiSystem
Version Information
Status: Testing
Current Stable Version: 1.3.1
Stable Release Date: 2015-05-09
Current Beta Version: 1.1.1
Beta Release Date: 2015-05-02
Created 2015-05-06
Last Updated 2015-05-10
Supported Devices
Samsung Devices​
Samsung Galaxy Note 3​
Samsung Galaxy Note 3 - Verizon Variant [Retail Edition]
Samsung Galaxy Note 3 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 3 - AT&T Variant
Samsung Galaxy Note 3 - T-Mobile Variant
Samsung Galaxy Note 3 - Sprint Variant
Samsung Galaxy Note 3 - International Variant
Samsung Galaxy Note 4​
Samsung Galaxy Note 4 - Verizon Variant [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 4 - Verizon Varian [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - AT&T Variant (ROOT Required!)
Samsung Galaxy Note 4 - T-Mobile Variant
Samsung Galaxy Note 4 - Sprint Variant
Samsung Galaxy Note 4 - International Variant
Samsung Galaxy S4​
Samsung Galaxy S4 - Verizon Variant
Samsung Galaxy S4 - AT&T Variant
Samsung Galaxy S4 - T-Mobile Variant
Samsung Galaxy S4 - Sprint Variant
Samsung Galaxy S4 - International Variant
Samsung Galaxy S5​
Samsung Galaxy S5 - Verizon Variant
Samsung Galaxy S5 - AT&T Variant
Samsung Galaxy S5 - T-Mobile Variant
Samsung Galaxy S5 - Sprint Variant
Samsung Galaxy S5 - International Variant
Click to expand...
Click to collapse
LG Devices​
LG G3​
LG G3 VS985 - Verizon Variant (Under Testing + more features utilizing Bump!)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+++
Reserved #2
Reserved #3
Reserved #4
Reserved #5
Thk you
.......... awesome work, downloading now...........
Very excited to see what this can do! Great work.
Waiting to see posts of people asking things that are explained here in the Q&A. One of the best ones I've seen too. Great work man.
http://forum.xda-developers.com/att-galaxy-s5/help/qa-multisystem-android-t3101217
this sounds awesome, looks like am going to have fun like with my htc-hd2 while back. ill wait for some feedback before i start playing with my s5
talkingmonkeys said:
Very excited to see what this can do! Great work.
Waiting to see posts of people asking things that are explained here in the Q&A. One of the best ones I've seen too. Great work man.
http://forum.xda-developers.com/att-galaxy-s5/help/qa-multisystem-android-t3101217
Click to expand...
Click to collapse
wrong topic lol
MultiSystem v1.3
Download the latest version from the main development thread!
hsbadr said:
Download the latest version from the main development thread!
Click to expand...
Click to collapse
Updated to 1.3, green led shows now, nice work thanks!
Sent from my twi5ted SM-G900A using Tapatalk
Rakuu said:
Updated to 1.3, green led shows now, nice work thanks!
Click to expand...
Click to collapse
Great! Please post your experience/steps (preferably with screenshots or videos) here for other users
Can't wait to try this out....ordering a 64 GB SD card this weekend since my 32 only has a couple gigs left....will be loading this up once it gets here!
d34thbl00m said:
Can't wait to try this out....ordering a 64 GB SD card this weekend since my 32 only has a couple gigs left....will be loading this up once it gets here!
Click to expand...
Click to collapse
Just did the same thing!
Ok backed up everything from my sdcard. Since its a 64 GB and it only actually has 59.62 GB I partitioned a 44 gb FAT32 Primary partition for my things and a 15.62 GB EXT4 Primary Partition for multisystem, roms and backups. Which could even be too much but it could make it easier for me to test multiple roms I'm working on so I'll go with that.
I left TMS5 1.0 that I'm running as my main system. After fixing my sd card up and putting it back in my device I installed the multisystem.apk and installed multisystem. Flashed the multisystem.zip in flashfire and upon reboot the green light came on and selinux is set to permissive. Next was Create Virtual IMG. I did this and waited for the red led indicator to go away then set it as my primary virtual system image. Rebooted and clicked volume up as the green led indicator was up and it rebooted into the virtual rom I just made. I made sure by running the terminal command listed in the Q&A to see which one is mounted and it was loop0 as he said.
Great work man. Now time for the fun to begin! Thanks for this. About to test the new version of my rom and see if it works good with this.
Note to other users DO NOT FLASH TMS5 1.0 or AllianceROM that are in our forum. They point to the main system. I'll have to update the updater-scripts for these. I'll get to it soon enough. If you already are on this read the Q&A and make the adjustments yourself if you think you can or ask me and I will.
talkingmonkeys said:
Ok backed up everything from my sdcard. Since its a 64 GB and it only actually has 59.62 GB I partitioned a 44 gb FAT32 Primary partition for my things and a 15.62 GB EXT4 Primary Partition for multisystem, roms and backups. Which could even be too much but it could make it easier for me to test multiple roms I'm working on so I'll go with that.
I left TMS5 1.0 that I'm running as my main system. After fixing my sd card up and putting it back in my device I installed the multisystem.apk and installed multisystem. Flashed the multisystem.zip in flashfire and upon reboot the green light came on and selinux is set to permissive. Next was Create Virtual IMG. I did this and waited for the red led indicator to go away then set it as my primary virtual system image. Rebooted and clicked volume up as the green led indicator was up and it rebooted into the virtual rom I just made. I made sure by running the terminal command listed in the Q&A to see which one is mounted and it was loop0 as he said.
Great work man. Now time for the fun to begin! Thanks for this. About to test the new version of my rom and see if it works good with this.
Note to other users DO NOT FLASH TMS5 1.0 or AllianceROM that are in our forum. They point to the main system. I'll have to update the updater-scripts for these. I'll get to it soon enough. If you already are on this read the Q&A and make the adjustments yourself if you think you can or ask me and I will.
Click to expand...
Click to collapse
WAIT WAIT WAIT HOLD UP WE HAVE SELINUX PERMISSIVE HOLY CRAP WE CAN DO VIPER AUDIO NOW. This is awesome! Woooooooo!
Aaaaand never mind, installed viper driver but its still the same, the driver status is still abnormal, so i guess not
Sent from my twi5ted SM-G900A using Tapatalk
Works perfectly. I'll have to try again but flashing a rom on the virtual slot over the copied system didn't go so well. So I had to jump back on my stock slot.
I like that it keeps system data but there is a downside to this too. It would be nice if it didn't and it separated them between the slots. So when I suggest a full wipe for people to update or for me to test things if I wipe system I won't have to go back through the setup on the old system slot. This is rather annoying. I read that it used the same system data between them but I guess I didn't think it the whole way through. Some things need a good system wipe between updates. Anyway that you can change it to be setup separately?
talkingmonkeys said:
Works perfectly. I'll have to try again but flashing a rom on the virtual slot over the copied system didn't go so well. So I had to jump back on my stock slot.
I like that it keeps system data but there is a downside to this too. It would be nice if it didn't and it separated them between the slots. So when I suggest a full wipe for people to update or for me to test things if I wipe system I won't have to go back through the setup on the old system slot. This is rather annoying. I read that it used the same system data between them but I guess I didn't think it the whole way through. Some things need a good system wipe between updates. Anyway that you can change it to be setup separately?
Click to expand...
Click to collapse
Ok, it's at very early development stage, I'll consider this & more other features with updates.
Simple One-Click Installation
I've fixed the installation script by setting the required symlinks (this makes it a very simple one-click installation for future versions), but I'll keep it a bit complicated for everyone to go through the Q&A thread (posts #1-6) to learn more before being able to use it.
On a side Note, I'd recommend to backup your data via TitaniumBackup & only wipe system data before rebooting to a completely different ROM.
Good luck!

[TOOL] [MultiSystem] MultiROM and Recovery Replacement for Android

​
MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices.
★ Disclaimer:
This service is FREE of charge, use it at your own risk, take it or leave it !
Click to expand...
Click to collapse
THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USE AT YOUR OWN RISK!
Click to expand...
Click to collapse
MultiSystem is a powerful tool and can perform potentially dangerous and/or destructive operations on your device and data that may affect your life. While it is unlikely to do irreversable damage to your device, it is not impossible, and you should proceed with caution. Loss of data and/or the need to re-flash a full stock (manufacturer-supplied) firmware IMGs (usually requiring a computer) is always a possibility, and is increasingly likely if you do not know what you are doing. It is possible to lose root access when using MultiSystem on locked-bootloader devices running unexpoitable (bu rooted) Android firmware, without careful reading of documentation or following the instructions. Please consult with expert users before performing actions you do not comprehend.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Notes:
To devs: Please do not use/port MultiSystem to any other device. If you'd like to add support for your device, please contact me!
Click to expand...
Click to collapse
To users: This thread is only for DEVELOPMENT. If you need a place for general discussions, go to MultiSystem Q&A thread.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Features:
Keeps stock system partition safe/rooted
Permenant root survival with proper use
MultiROM support via virtual ROMs
Unlimited number of virtual ROMs
Booting options to choose stock, primary, or secondary virtual ROM
Any of the virtual ROMs can work as a recovery replacement
Flashing multiple ROMs at the same time without a reboot
Ability to create/install ROMs on Linux to microSD card
Great performance & battery life on virtual ROMs
Recovery solution to install ROMs or Mods
Easy upgrade to newer versions of Android
Ability to safely apply OTA updates to virtual system
Permissive SELinux and other kernel tweaks
Safe flashing that doesn't trip KNOX flag on Samsung devices
Wrapper script runs via ADB or a Terminal Emulator on device
APK to manage all MultiSystem functions with a nice UI and extra options
Management for the best performance & user experience
Support for all Android devices with microSD card
Portability to almost all devices
Compatibility with all Android versions
Click to expand...
Click to collapse
★ ChangeLog:
Check the updated changelog in the main development thread!
Click to expand...
Click to collapse
★ Instructions:
Check the updated instructions in the main development thread!
Click to expand...
Click to collapse
★ Downloads:
Download the latest version from the main development thread!
Click to expand...
Click to collapse
★ Credits:
@ChainFire - for SuperSU & FlashFire
@Hashcode - for Safestrap Recovery
@[NUT] - for XZDualRecovery
@Androguide.fr - for APKreator & various libraries/apps
Jack Palevich - for Terminal Emulator for Android
@osm0sis - for Android Image Kitchen
All authors of binaries/libraries, source codes, or tutorials...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'd like to thank everyone who made a donation just to show appreciation.
It's fine to just click Thanks! or enjoy my work without saying anything.
A donation is to show appreciation of the work I have done already.
A donation is not by any means in expectation of future work.
A donation doesn't entitle for preferred/private support/requests.
A donation is meant as a gift - always appreciated, never required.
Click to expand...
Click to collapse
Verizon Samsung Galaxy Note 4 (N910V), Note 3 (N900V) & LG G3 (VS985)
Hit thanks, follow thread & add 5-star rating/review... Donations are always appreciated!
​
XDA:DevDB Information
MultiSystem, Tool/Utility for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr
Source Code: https://github.com/hsbadr/MultiSystem
Version Information
Status: Testing
Current Stable Version: 1.3.1
Stable Release Date: 2015-05-09
Current Beta Version: 1.1.1
Beta Release Date: 2015-05-02
Created 2015-05-07
Last Updated 2015-05-10
Supported Devices
Samsung Devices​
Samsung Galaxy Note 3​
Samsung Galaxy Note 3 - Verizon Variant [Retail Edition]
Samsung Galaxy Note 3 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 3 - AT&T Variant
Samsung Galaxy Note 3 - T-Mobile Variant
Samsung Galaxy Note 3 - Sprint Variant
Samsung Galaxy Note 3 - International Variant
Samsung Galaxy Note 4​
Samsung Galaxy Note 4 - Verizon Variant [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 4 - AT&T Variant (ROOT Required!)
Samsung Galaxy Note 4 - T-Mobile Variant
Samsung Galaxy Note 4 - Sprint Variant
Samsung Galaxy Note 4 - International Variant
Samsung Galaxy S4​
Samsung Galaxy S4 - Verizon Variant
Samsung Galaxy S4 - AT&T Variant
Samsung Galaxy S4 - T-Mobile Variant
Samsung Galaxy S4 - Sprint Variant
Samsung Galaxy S4 - International Variant
Samsung Galaxy S5​
Samsung Galaxy S5 - Verizon Variant
Samsung Galaxy S5 - AT&T Variant
Samsung Galaxy S5 - T-Mobile Variant
Samsung Galaxy S5 - Sprint Variant
Samsung Galaxy S5 - International Variant
Click to expand...
Click to collapse
LG Devices​
LG G3​
LG G3 VS985 - Verizon Variant (Under Testing + more features utilizing Bump!)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+++
Reserved #2
Reserved #3
Reserved #4
Reserved #5
Awesome, thanks for your work.
how do we?
PARTITION your microSD card into two (FAT32/ExFAT & EXT4) partitions?
anticloud said:
PARTITION your microSD card into two (FAT32/ExFAT & EXT4) partitions?
Click to expand...
Click to collapse
It's in the instructions when you go to the Q/A section.
Cool. I'll try this as soon as a rom that I really want to try comes along.
Sent from my SM-N910V DE
Remember: Read twice flash once
Simple One-Click Installation
I've fixed the installation script by setting the required symlinks (this makes it a very simple one-click installation for future versions), but I'll keep it a bit complicated for everyone to go through the Q&A thread (posts #1-6) to learn more before being able to use it.
On a side Note, I'd recommend to backup your data via TitaniumBackup & only wipe system data before rebooting to a completely different ROM.
Good luck!
hsbadr said:
I've fixed the installation script by setting the required symlinks (this makes it a very simple one-click installation for future versions), but I'll keep it a bit complicated for everyone to go through the Q&A thread (posts #1-6) to learn more before being able to use it.
On a side Note, I'd recommend to backup your data via TitaniumBackup & only wipe system data before rebooting to a completely different ROM.
Good luck!
Click to expand...
Click to collapse
Any chance you can get this working for the S6 so we can install a custom ROM? We now have root.
Misterxtc said:
Any chance you can get this working for the S6 so we can install a custom ROM? We now have root.
Click to expand...
Click to collapse
You can use FlashFire? I could work on it by storing virtual ROMs on the internal storage, but this has drawbacks; for instance:
Factory Reset = complete loss
Loop devices on vFAT are less powerful compared to EXT4
...
This can be resolved if we could make a separate partition for MultiSystem, but I'm not sure if it'd work & I don't own that device.
If FlashFire works, it'll be a better solution for flashing regardless the MultiROM option. That's why I hate Samsung decision of removing microSD slot & I hope they won't ruin the Note line.
hsbadr said:
You can use FlashFire? I could work on it by storing virtual ROMs on the internal storage, but this has drawbacks; for instance:
Factory Reset = complete loss
Loop devices on vFAT are less powerful compared to EXT4
...
This can be resolved if we could make a separate partition for MultiSystem, but I'm not sure if it'd work & I don't own that device.
If FlashFire works, it'll be a better solution for flashing regardless the MultiROM option. That's why I hate Samsung decision of removing microSD slot & I hope they won't ruin the Note line.
Click to expand...
Click to collapse
Thanks, I totally forgot about FlashFire. I'll have to give that a try tomorrow. Either way I'm happy to finally be able to delete the bloat.
Misterxtc said:
Any chance you can get this working for the S6 so we can install a custom ROM? We now have root.
Click to expand...
Click to collapse
Is there any chance the root method would work for the Note 4?
Update: Cool!! KingRoot + MultiSystem = Rooted Note 4 Retail Edition.
Sent from my SM-N910V DE
Remember: Read twice flash once
MultiSystem v1.3.1 [May 9, 2015]
★ ChangeLog:
Simple one-click installation
Added log for installallation
Fixed LED indicator for Note 4
Click to expand...
Click to collapse
stueycaster said:
Is there any chance the root method would work for the Note 4?
Update: Cool!! KingRoot + MultiSystem = Rooted Note 4 Retail Edition.
Sent from my SM-N910V DE
Remember: Read twice flash once
Click to expand...
Click to collapse
I'm not sure but here is the thread to submit your info to.
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
MultiSystem Video Tutorial
Thanks To: @Tomsgt , aka RootJunky
Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:
Amazing!!! Been waiting a LONG WHILE for a tool like this to come back around. Thanks guy!
Any chances this will work for the Note Edge?

(BootAnimation) Android 6.0 Marshmallow for Samsung devices

This is the Android 6.0 Marshmallow Bootanimation for ALL SAMSUNG devices. This will work on ANY Samsung device that is at least Rooted and uses QMG bootanimation files. Keep in mind that this is not a flashable zip, if unfamiliar with how to manually install these files and set permissions see my instructions gif. Also, keep in mind that this QMG format system that Samsung uses is old school, it has not been updated or supported in over 3 years, so please do not ask me to make this bootanimation more fluid. Instead ask Samsung to update their design tools, so we can have more fun.
Android 6.0 Marshmallow QMG files for any Samsung device. (included are bootsamsung.qmg, bootsamsungloop.qmg, and my version of the shutdown.qmg.)
Latest Updated Version Download
Original Large version Download
​
If you would like to use this in your ROM, just leave a mention.
Instructions
​
For access to my [Bootanimation] MASSIVE QMG BootAnimation LiBRaRy KoLLecTioN GALORE click here.
Reserved
Reserved this one too!
Who knows..
thanks for sharing such amazing boot animation...
KachowPow said:
This is the Android 6.0 Marshmallow Bootanimation for ALL SAMSUNG devices. This will work on ANY Samsung device that is at least Rooted and uses QMG bootanimation files. Keep in mind that this is not a flashable zip, if unfamiliar with how to manually install these files and set permissions see my instructions gif. Also, keep in mind that this QMG format system that Samsung uses is old school, it has not been updated or supported in over 3 years, so please do not ask me to make this bootanimation more fluid. Instead ask Samsung to update their design tools, so we can have more fun.
Android 6.0 Marshmallow QMG files for any Samsung device. (included are bootsamsung.qmg, bootsamsungloop.qmg, and my version of the shutdown.qmg.)
​
If you would like to use this in your ROM, just leave a mention.
Instructions
​
For access to my [Bootanimation] MASSIVE QMG BootAnimation LiBRaRy KoLLecTioN GALORE click here.
Click to expand...
Click to collapse
Nice work! Just some feedback... animation frames are way too low (if you are aiming for the stock smooth looking one). On the S6 the bootanimation looks blurry and overwhelmingly big IMO.
EDIT: Sorry, I read the OP more carefully, I didn't know this can't be changed. But I've seen some S6 roms with the Samsung bootanimation running with modified and smoother frames.. hmm
@KachowPow Great job on this!
Thanks for the feedback! I've added a 2nd version to the OP. This one is not as large, it does play all the way through, you should notice a quick Android bleep at the end of the playback as a result of the bootsamsungloop.qmg file. None-the-less this one should present better.
https://www.androidfilehost.com/?fid=24052804347817349
Thank you buddy. Made a flashable for the S4 leaving a mention here and wherever i post it in the S4 section :good:
thank mate ?
Not working, both versions. I've got black screen. G920F.
Harthouse said:
Not working, both versions. I've got black screen. G920F.
Click to expand...
Click to collapse
Both are working, I hope you didn't flash them as they are non-flashashable. In case re-read the op and take a look at the instructions to make sure all steps are correct.
Nice work
It's working now. Problem with permissions.
hi... thanks for thw efford, but could you made it run a bit faster?
because it run very slow and i just bootup before it finish. thanks in advance...
Read the OP. Jesh
Dear friends,
I made a new Android 6 bootanimation from the work of @stangdriver44 and LGG4 bootanimation.zip file.
All infos here :
http://forum.xda-developers.com/showpost.php?p=62926825&postcount=7
Thank you
Sent from my SM-G920F using Tapatalk
Code124Y said:
hi... thanks for thw efford, but could you made it run a bit faster?
because it run very slow and i just bootup before it finish. thanks in advance...
Click to expand...
Click to collapse
For me too.
Any chance to get it finished bedore boot is finish?
Gesendet von meinem SM-G925F mit Tapatalk
here is a zip file for the android m boot animation. flash in recovery. it also has the original android m boot animation with the correct fps and you get the android name at the end of boot up. i use it on my tmobile gs6 all the time when i install a new rom. works every time.
http://d-h.st/sR2i

[ROM] [5.1.1] Emotion Revolution Note 5 Port R3 [N910VVRU2BPA1] [5/15/16]

Read this whole OP before doing anything!
** I am excited to announce that TeamEmotroid's Emotion Revolution Note 5 Port R3 (INTERNATIONAL NOTE 4 BASED ROM) works for the Verizon Note 4 ! I am not a developer and do not take credit for this ROM. Enjoy!!
Give many thanks and donate to Team Emotroid: http://forum.xda-developers.com/note-4/snapdragon-dev/twrom-emotion-revolution-note-iv-t2976107
Give @Battlehero a thanks and donate to him for his time and effort for creating the data fix for our Verizon Note 4 http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
Give @hsbadr a big thanks and donate to him for making this possible with his 5.1.1 Jasmine ROM and multi-system kernel!! http://forum.xda-developers.com/note-4-verizon/development/rom-jasminerom-v1-0-t3113771
Without them, this would not have been possible!
Remember that.
DISCLAIMER: Your warranty is now void. Please be careful make a full TWRP backup of your current Verizon ROM. I am not responsible if you break your phone or lose data on your device!
*A clean flash is a must if you are coming from another ROM or you will run into problems.* Do not post issues if you dirty flashed.
**Note only the Note 5 port version of Emotion Revolution works for our phone with the datafix **
Big NOTE: (Puns intended) There are OG Developer's Editions and Converted Retail Editions. OG's, including me, have an aged KitKat 4.4.4 unlocked bootloader and we need to use multi-system kernel that @hsbadr patched to fix the brightness issue that was present during the Lollipop upgrade. We are forever in his debt. Converted Retail Editions have a newer Lollipop 5.1.1 unlocked bootloader meaning they can try other Verizon specific kernels without the brightness issue (You might come across other issues trying other kernels so please state what kernel you're using if you experience an issue). I'm also believing that it is possible that converts can experience issues that OG's don't experience due to the difference in bootloaders, and vice versa. It would be nice to know your build, including xposed mods, if you experience any issues. Thanks!
Instructions:
1.) Make sure you are on a 5.1.1 modem.
(N910VVRU2BOK3) or (N910VVRU2BPA1)
2.) Download the ROM and Fix to your SD
3.) Download the DataFix to your SD
4.) Wipe /system /data /cache /dalvik-cache (/InternalStorage Optional, you will lose your files on the device)*
5.) Flash the ROM
6.) Flash Fix
7.) Flash the DataFix.
8.) Wipe Dalvik and Cache
9.) Reboot. (Will take about 10-15 mins to boot)
Do not log into Samsung account or Google account during initial setup..
10.) Navigate to Settings > Mobile Networks > Network Mode > Verify Network Mode is LTE/CDMA
11.) Enjoy!
*If you use the stock Samsung keyboard just change the language to English it is on Spanish by default*
*The Google Playstore needs to eventually update so if you run into issues with it, it is probably in the process of updating so give it some time to install. You will see the new Playstore splash screen when it is finished*
*Use kernel auditor at your own risk I experienced a crash with the OnDemand governor. I turned it off and had no issues since*
*Use xposed and flash any mods at your own risk*
Downloads:
Download Emotion Revolution Note 5 port ROM and 3.1 Fix here: http://emotroid.com (Click the menu button > Note 4 ROMs(Click the plus sign) > TouchWiz > Click on N910F/G Note 5 port ROM and V3.1 Fix)
then
Download @Battlehero's 4/18/16 Data Fix V3.3 here (Go to the third post and expand "US Variants", look for N910V datafix): http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
**READ ME**
Bugs:
Along with the bugs from the OP (No GearVR support) :
- *MMS does not work correctly on the stock Messaging app (group chats come in and send as individual messages, and unable to send picture messages)
**(Workaround: Use Textra as default messaging app, MMS works like it should)**
- Unable to perform a factory reset within the settings because you will get non-stop FC's once booted up. So make a TWRP backup after you go through a battery cycle.
- If you do not wipe internal storage any old Note 2 files in you SNote data folder will kill the SNote app. So remove them from that folder and you'll be able to use SNote.
- System update in settings force closes the Settings
- Simultaneous data works at 4G speeds when talking on the phone but it shows it as a 1X connection. (Must have a 4G connection to work)
- To get My Verizon to work:
1. Navigate to /system/priv_app and delete the VzwSilentSSOEngine folder.
2. Edit the system/buid.prop file. Change the model value to SM-N920V and save.
3. Reboot.
4. You need to log into My Verizon using your user name your number will not work
Thanks @stueycaster and @rayjr13
- Verizon Visual Voicemail does not work and may never work
- Screen mirroring may not work (Haven't tested)
- All apps on homescreen option does not work on stock launcher
- Ink in water lockscreen effect does not work
- If you change the model value in the build.prop to Verizon Note 4 model value (SM-N910V) it will break the theme store. Switch it back to SM-N920F or SM-N920V to get theme store working again.
- Google Play Movies does not work
- I have noticed that the hour of the current time may ghost behind whatever you have to right of the status bar. For me I have the center aligned clock so it is behind the stock battery. (Little eye sore but there's no fix at the moment). If you use 3mint battery there are some battery options that cover it.
- Show SFinder in the quick panel settings in custom Emotion app does not work and will force reboot your phone.
Read/search through the original OP thread for any non-Verizon specific issues first.
Credits:
Thank you so much TeamEmotriod for developing Emotion Revolution Note 5 Port !!
Thank you @Battlehero for creating a data fix for our phone!!
Thank you @hsbadr for your constant development and support for the Verizon Note 4, and of course for Jasmine ROM and multi-system kernel !!!
Reserved
jcip17 said:
Read this whole OP before doing anything!
** I am excited to announce that TeamEmotroid's Emotion Revolution Note 5 Port R3 (INTERNATIONAL NOTE 4 BASED ROM) works for the Verizon Note 4 ! I am not a developer and do not take credit for this ROM. Enjoy!!
Give many thanks and donate to Team Emotroid: http://forum.xda-developers.com/note-4/snapdragon-dev/twrom-emotion-revolution-note-iv-t2976107
Give @Battlehero a thanks and donate to him for his time and effort for creating the data fix for our Verizon Note 4 http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
Give @hsbadr a big thanks and donate to him for making this possible with his 5.1.1 Jasmine ROM and multi-system kernel!! http://forum.xda-developers.com/note-4-verizon/development/rom-jasminerom-v1-0-t3113771
Without them, this would not have been possible!
Remember that.
DISCLAIMER: Your warranty is now void. Please be careful make a full TWRP backup of your current Verizon ROM. I am not responsible if you break your phone or lose data on your device!
*A clean flash is a must if you are coming from another ROM or you will run into problems.* Do not post issues if you dirty flashed.
**Note only the Note 5 port version of Emotion Revolution works for our phone with the datafix **
Big NOTE: (Puns intended) There are OG Developer's Editions and Converted Retail Editions. OG's, including me, have an aged KitKat 4.4.4 unlocked bootloader and we need to use multi-system kernel that @hsbadr patched to fix the brightness issue that was present during the Lollipop upgrade. We are forever in his debt. Converted Retail Editions have a newer Lollipop 5.1.1 unlocked bootloader meaning they can try other Verizon specific kernels without the brightness issue (You might come across other issues trying other kernels so please state what kernel you're using if you experience an issue). I'm also believing that it is possible that converts can experience issues that OG's don't experience due to the difference in bootloaders, and vice versa. It would be nice to know your build, including xposed mods, if you experience any issues. Thanks!
Instructions:
1.) Make sure you are on a 5.1.1 modem.
(N910VVRU2BOK3) or (N910VVRU2BPA1)
2.) Download the ROM and Fix to your SD
3.) Download the DataFix to your SD
4.) Wipe /system /data /cache /dalvik-cache (/InternalStorage Optional, you will lose your files on the device)*
5.) Flash the ROM
6.) Flash Fix
7.) Flash the DataFix.
8.) Wipe Dalvik and Cache
9.) Reboot. (Will take about 10-15 mins to boot)
Do not log into Samsung account or Google account during initial setup..
10.) Navigate to Settings > Mobile Networks > Network Mode > Verify Network Mode is LTE/CDMA
11.) Enjoy!
*If you use the stock Samsung keyboard just change the language to English it is on Spanish by default*
*The Google Playstore needs to eventually update so if you run into issues with it, it is probably in the process of updating so give it some time to install. You will see the new Playstore splash screen when it is finished*
*Use kernel auditor at your own risk I experienced a crash with the OnDemand governor, before and after I turned it off I had no issues*
*Use xposed and flash any mods at your own risk*
Downloads:
Download Emotion Revolution Note 5 port ROM and 3.1 Fix here: http://emotroid.com (Click the menu button > Note 4 ROMs > TouchWiz > Click on N910F/G Note 5 port ROM and V3.1 Fix)
then
Download @Battlehero's 4/18/16 Data Fix V3.3 here (Go to the third post and expand "US Variants", look for N910V datafix): http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
**READ ME**
Bugs:
Along with the bugs from the OP (No GearVR support) :
- *MMS does not work correctly on the stock Messaging app (group chats come in and send as individual messages, and unable to send picture messages)
**(Workaround: Use Textra as default messaging app, MMS works like it should)**
- Unable to perform a factory reset within the settings because you will get non-stop FC's once booted up. So make a TWRP backup after you go through a battery cycle.
- If you do not wipe internal storage any old Note 2 files in you SNote data folder will kill the SNote app. So remove them from that folder and you'll be able to use SNote.
- System update in settings force closes the Settings
- Simultaneous data works at 4G speeds when talking on the phone but it shows it as a 1X connection. (Must have a 4G connection to work)
- To get My Verizon to work:
1. Navigate to /system/priv_app and delete the VzwSilentSSOEngine folder.
2. Edit the system/buid.prop file. Change the model value to SM-N920V and save.
3. Reboot.
4. You need to log into My Verizon using your user name your number will not work
Thanks @stueycaster and @rayjr13
- Verizon Visual Voicemail does not work and may never work
- Screen mirroring may not work (Haven't tested)
- All apps on homescreen option does not work on stock launcher
- Ink in water lockscreen effect does not work
- If you change the model value in the build.prop to Verizon Note 4 model value (SM-N910V) it will break the theme store. Switch it back to SM-N920F or SM-N920V to get theme store working again.
- Google Play Movies does not work
- I have noticed that the first digit of the current time may ghost behind the stock battery at times.
Read/search through the original OP thread for any non-Verizon specific issues first.
Credits:
Thank you so much TeamEmotriod for developing Emotion Revolution Note 5 Port !!
Thank you @Battlehero for creating a data fix for our phone!!
Thank you @hsbadr for your constant development and support for the Verizon Note 4, and of course for Jasmine ROM and multi-system kernel !!!
Click to expand...
Click to collapse
Awesome...again, thank you for all you do to keep us entertained!
Sent from my SM-N920V using XDA-Developers mobile app
gcounts said:
Awesome...again, thank you for all you do to keep us entertained!
Sent from my SM-N920V using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't do anything lol all credit goes to the developers. I just do the write ups and I guess initial testing to make sure they can be used as daily drivers ?
Sent from my SM-N920F using Tapatalk
jcip17 said:
I don't do anything lol all credit goes to the developers. I just do the write ups and I guess initial testing to make sure they can be used as daily drivers ?
Sent from my SM-N920F using Tapatalk
Click to expand...
Click to collapse
I know, but that's a LOT more than the 99.9% of us that do nothing. And you are maintaining 3-4 threads now, and having to deal with all that entails. So, thanks again!
Sent from my SM-N920V using XDA-Developers mobile app
gcounts said:
I know, but that's a LOT more than the 99.9% of us that do nothing. And you are maintaining 3-4 threads now, and having to deal with all that entails. So, thanks again!
Sent from my SM-N920V using XDA-Developers mobile app
Click to expand...
Click to collapse
Np brother!
Sent from my SM-N920F using Tapatalk
Emotion control sounds dope :silly:
Thanks for keep testing.. By any chance have you tried marshmallow ones?
@jcip17
Sent from my Samsung Galaxy Note5 using XDA Labs
EdrickMG said:
Emotion control sounds dope :silly:
Thanks for keep testing.. By any chance have you tried marshmallow ones?
@jcip17
Sent from my Samsung Galaxy Note5 using XDA Labs
Click to expand...
Click to collapse
No I haven't but I doubt we will be able to get data without a MM kernel and modem.
Sent from my SM-N920F using Tapatalk
jcip17 said:
No I haven't but I doubt we will be able to get data without a MM kernel and modem.
Click to expand...
Click to collapse
Well you are right we better be patience and wait for Verizon... Hopefully is before September becausr typically they are the last ones
Sent from my Samsung Galaxy Note5 using XDA Labs
Awesome job man... is the battery life better with this than the Kyubi rom?
First off I wanna say I'm loving this ROM. Thank you VERY much. Just installed it about 2 hours ago and everything seems great. love all the customizations and it's a very nice change. The only thing so far is I can't send picture messages even with Textra. Any ideas? I'm on the multisystem kernel. Other than that I love it. Don't know about battery life yet but hopefully it'll be as good as Jasmine, my other favorite.
dhplap said:
First off I wanna say I'm loving this ROM. Thank you VERY much. Just installed it about 2 hours ago and everything seems great. love all the customizations and it's a very nice change. The only thing so far is I can't send picture messages even with Textra. Any ideas? I'm on the multisystem kernel. Other than that I love it. Don't know about battery life yet but hopefully it'll be as good as Jasmine, my other favorite.
Click to expand...
Click to collapse
thats great. thanks for the feedback. please do mention about the battery life whenever you get a chance. i had terrible battery with Kyubi. thanks.
Where's the MD5 checksum?
gcounts said:
I know, but that's a LOT more than the 99.9% of us that do nothing. And you are maintaining 3-4 threads now, and having to deal with all that entails. So, thanks again!
Sent from my SM-N920V using XDA-Developers mobile app
Click to expand...
Click to collapse
I'll second that!!!
?If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
I can't get the rom downloaded, I get an error page every time.....I think all you guys crashed the server from so much traffic!
Sent from my SM-N920V using XDA-Developers mobile app
Data fix was removed by administration
Sent from my SM-N910V using XDA-Developers mobile app
After reading comments here I am sure about one thing that i will get good battery life other n5 port roms
Edit #1
bugs or whatever you called this thing
- after adding google accounts phone stuck on reboot loop (boot successfully after that >starting and reboot same thing happen again and again)
- they have some customization app if i open that app and enable S finder my phone reboot automatically
more will be discovered
This rom is really snappy! Also, so far everything I've tried works, even screen mirroring through roku stick. Thanks @jcip17!
Sent from my SM-N920F using XDA-Developers mobile app
I just keep seeing 404 error.
?If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
stajam said:
I just keep seeing 404 error.
?If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
1st click the menu button and then when you see the note 4Roms press the + symbol and then Touchwiz..

Categories

Resources