Related
Hi All,
I am working on a custom RoM with specific focus.
So basically i will be taking a standard rom and will be adding some softwares some binaries some terminal related shortcuts and stuff.
Now i had two apporaches for it
1) create a custom ROM for each device.
2) create / user a mod manager which allows for mods which are not incremental in nature and can coexisit independently.
example i release m1 m2 and m3 as 3 Mod packs.
person A might want m1 m3 but not m2
person B might want just m3
person C is happy with just m2
and m1 m2 m3 are completely inependent packages.
Can any one suggest if such a solution exist in the wild I have tried to look at various rom managers but they all work on update mode and not mod mode.
Also using such a system i would like to create zip's which i can install in simmilar fashion to the recovery based update.zip flashing. but in running environment. (considering they are not hurting any running code)
Thanks in advance for help
Check out the AROMA Installer thread...see if it does what you are looking for...
-BMFC
bmfc187 said:
Check out the AROMA Installer thread...see if it does what you are looking for...
-BMFC
Click to expand...
Click to collapse
Interesting project will check it out.
however as far as i can understand it right now its running in recovery mode, I am looking for something which can work when device is running.
If i was not clear before i will give some examples.
I have some apk's and some system mod's
now i want some software which a person can install on his machine and he can securely see the list of items on my server,
he selects i want to install apk.
apk gets downloaded and installed
he selects a system mod
zip file will be downloaded and it will be extracted on /system or / as required and permissions to be setted as listed in a update script on file.
Basically what i am trying to do is to put my mod's and apk's in generalized manner so i don't have to deal with the nittygritties of the android system's on each device. i can directly work on my stuff.
I hope i am clear this time
Now real question ? Is there any such thing in wild?
or am i looking at building something from scratch and if yes what's the cost.
[Guide] Multi Boot Note 3 (Updated 24/07/2015)
*** Hi Guys i no longer have a note 3 so i cant do any testing but our team member is here to give support for you all and even im here to give support except testing. please contact @[email protected] and @djnim for support.***
I am using this on SM-N9005 Snapdragon Variant of the Note 3; I believe this will work with other Note 3 Variants as well. Few of them are already tested and you can find them below. Others who have different variants which are not tested can try this and update us, and we will be here to help you out if you are ready to try this out.
@chenxiaolong is the one who made this happen to our beloved Note 3
Main advantage of this is you can try any new rom with out loosing or having any kind of trouble with your existing rom. This mod will not change anything in your primary rom, so any time you can go back to your normal state.
Disclaimer
1.I am not responsible for bricked devices, dead SD cards,etc.
2.Before going further! YOU are choosing to make these modifications.
supported Devices: ( Tested and confirmed working)
SM-N9005 (International Qualcomm): hlte (Tested by me )
SM-N900T (T-Mobile US): hltetmo (Tested by @MistaEast ) confirmation post
SM-N900R4 (US Cellular): hlteusc (Tested by @harshal10398 ) confirmation post
SM-N900 (International Exynos): ha3g (Tested by @mohnishkat ) confirmation post
SM-N900P (Sprint): hltespr (Tested by @lord dredd ) confirmation post
SM-N900K(Korean): (Tested by @Premananda_laishram) confirmation post
Requirements
* Read the full guide before Starting.
* Backup your phone if you are doing this first time. (Full Nandroid backup recommended for the new comers and it’s also recommended to others who don’t know what they are doing exactly even if they have multi booted several times)
* Rooted Note 3 with custom recovery (preferred TWRP or philz).
* free space in your internal SD (for example a Cm based roms take up to 2.5GB to 3.5GB and a TW roms take up to 5GB or more.)
* If you face any trouble please read the FAQ before doing something or asking for help. And if you want help please provide as much as details(device, roms, etc.) you can.
*
Instruction:
1.Download your desired Rom which you want to use for multi booting and the mods, addons, gapps, Kernel etc for the same. Keep the files in your internal memory.
2. Download the most recent snapshot release of Dual Boot Patcher and install it on your Note 3.
3. Open Dual Boot Patcher and grant SU permission. Then go to ROMS and you will see your Primary rom, press the 3dotmenu key and click "set kernel". If it fail to set kernal please read the FAQ.
4. Then In Dual Boot Patcher go to Patch Zip File and Choose hlte for snapdragon variant and ha3g for Exynos veriant (Samsung Galaxy Note 3) from the drop down menu.
5. In the second drop down menu select "Data Slot".
6. Below that you have to enter the ID of the secondary rom.(Example 1, 2, 3, etc. - it will take it as /data/multiboot/data-slot-1)
7.Now tap on the below button to choose the ROM's, Gapps, Kernel and mods to patch them and make them perfect for Multi booting.
8. Always remember to keep same slot ID for the Gapps, kernels and mods same as the rom. (Example: if you want to flash the gapps/kernel to the data-slot-1 rom then you have to select the same ID that’s 1 or if you want to flash the gapps/kernel to the data-slot-2 rom then you have to select the same ID that’s 2.)
9. When selecting the files except cm rom zip there will be a “preset” drop down menu, from that you have to select according to the file you are going to patch. (Examp: for roms, kernels, mods, addons – custom; for gapps – Google_Apps; for Su zip – other/SuperSu; For xposed-Other/Xposed)
10. Now press the tap to begin patching button to patch the file. And you will get a new patched zip file in the same location.
11. Now Boot into custom recovery and flash the new patched file and reboot.
12. And your device will boot into New Rom.
13.Install the Dual Boot Patcher app and set the kernel for your second ROM as well.
14. To switch between roms
•Open Dual Boot Patcher app/roms and click on primary or secondary rom as you like and reboot.
•Or Use Swap Roms to switch between Roms.
* Important things to keep in mind: while installing a rom or mod with Aroma installer don't reboot directly from the aroma.
You have to always uncheck the last option to reboot in aroma and click finish. So it can finish the final steps for multi booting.
And if you miss that it will only reboot to recovery. To boot back you have to flash your primary rom kernel or re-flash the patched rom.
Never update a secondary rom through OTA Update.
*. For other devices:
1. You have to download and install X-plore File Manager (which I am using) from play store.
2. Open X-plore File Manager from app drawer and navigate to the patched zip file and open it.
3. Now you will see a folder named multiboot inside that you will find info.prop, now open info.prop with the text editor which comes with the x-plore file manager.
• And then find and change mbtool.installer.ignore-codename=false to mbtool.installer.ignore-codename=true
Revert
To revert back or if you face any problem just flash my Multi Boot cleaner.zip which will wipe all the installation files from \system and restore the primary rom kernel.
As a backup keep a copy of your kernel flashable zip file.
FAQ
1. I can't set the primary rom kernel in xyz rom. And I can’t switch to other rom in primary rom.
Ans. Just download the set kernel fix as per your model and flash it in the recovery.
The above fix only work for primary rom. If you have trouble with any other roms just add ro.patcher.device=hlte(for other models add your model instead of hlte) to the bottom of build.prop of that rom and you are good to go.
If you don’t know how to do that just pm me and I will make a flash able zip to add it to your secondary rom.
if the above didnt work Read this post please
2. App sharing?
Ans. Until now no luck. (Still under testing)
3. This rom can’t be patched.
Ans. some roms are not supported its known, if the Dev have time may be he will consider including them.
Also read this
Credits/ Thanks:
@chenxiaolong
Original Thread: http://forum.xda-developers.com/showpost.php?p=45659284
Don't forget to thank him and if you can please consider a small donation for him because he really deserve it.
@aukhan & Team Emotroid
His Thread (Where I got the idea and help to make this guide): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
@rlorange for the help and support.
His thread for Dual boot backup and restore app. http://forum.xda-developers.com/showthread.php?t=2491299, http://forum.xda-developers.com/not...-4-15-multi-boot-backup-restore-v1-0-t3087187
@AholicCert for helping me with some scripts
@ other XDAmembers
Video Guide
https://www.youtube.com/watch?v=upeSC65t5XQ
Going to try it mate tnx
a_prabhu7 said:
Going to try it mate tnx
Click to expand...
Click to collapse
Welcome try it and let us know.
Sent from my SM-N9005 using XDA Free mobile app
Has anyone tried this out on N900????
thetitanium said:
Has anyone tried this out on N900????
Click to expand...
Click to collapse
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
54NJ41 said:
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
Click to expand...
Click to collapse
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
vagenrider said:
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
Click to expand...
Click to collapse
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
54NJ41 said:
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
Click to expand...
Click to collapse
tried all mate but nothing..
vagenrider said:
tried all mate but nothing..
Click to expand...
Click to collapse
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
54NJ41 said:
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
Click to expand...
Click to collapse
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
vagenrider said:
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
Click to expand...
Click to collapse
Which version 7.2 or other
54NJ41 said:
Which version 7.2 or other
Click to expand...
Click to collapse
7.2
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Rogers Note 3
Anyone can tell me if I can install it for the Canadian Rogers Galaxy Note 3 ?
Thank you
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
vagenrider said:
7.2
Click to expand...
Click to collapse
I have tried the rom but same result as yours. But don’t worry I have an alternative way to set the kernel for your primary rom.
First make folders in your SDCard, “MultiBoot” in it “Primary” it should be like: Sdcard/MultiBoot/Primary
Then extract the boot.img from your rom zip and copy it to Sdcard/MultiBoot/Primary
So the result will be Sdcard/MultiBoot/Primary/boot.img
It’s done.
NightForce said:
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
Click to expand...
Click to collapse
Welcome bro
dream_catcher79 said:
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Click to expand...
Click to collapse
To make space in your system partition.
1. Delete what ever apps you are not using from system/app and syatem/priv-app (Don’t delete if you don’t know what it is or what your are doing.)
Example: shealth, etc.
2. Move some google apps from /system/app to /data/app to make them user app using root explorer.
Example: maps, gmail, chrome, etc.
thermax04 said:
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
Click to expand...
Click to collapse
To dual boot two TW roms is very hard. Because there is not enough space to fit both system file in your system partition. Other wise you have to deboalt the primary rom and you have to deboalt secondary rom zip before flashing. And by doing so you will lose most of the features of your TW roms.
And if you want to use CM as primary and TW rom as secondary its possible but not recommended. Because you will have trouble with flashing mods etc for your TW rom.
The better option at the moment is to keep the TW rom as Primary and others a secondary.
This ROM has some FCs on third party apps (such as Facebook, some Bank apps, etc.), so I deleted all the ROM files because they are useless at this time. Due te fact I have no more time to spend on this project, a moderator can close this thread!
Thank you!
Very well done! I just have one question: what does the CellBroadcastReceiver package do, and why is it installed if we don't need it?
gvlfm78 said:
Very well done! I just have one question: what does the CellBroadcastReceiver package do, and why is it installed if we don't need it?
Click to expand...
Click to collapse
In many Countries they use it to broadcast anything useful/vital to people life. In Italy it's used by Vodafone to broadcast the Province/CellID in GSM, channel 50, and TIM for the "Arancione" plans (does it exist anymore?) to bill by Province/CellID (I don't remember the channel ID).
The -> real <- thing, in Italy, is the battery drain!
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
Melkor_98 said:
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
Click to expand...
Click to collapse
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!
The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).
These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!
If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).
Lastly, have you clicked on the "d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
@Melkor_98 @sun75 When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
gvlfm78 said:
@Melkor_98 @sun75 When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
Click to expand...
Click to collapse
Yes, it can be true, but the problem is Wiko and Canvas have different partition schemes: Wiko has one partition more (Apedata) and different partition sizes and entrypoints vs. Canvas. (refer scatter file...). If you change your phone to Canvas, make sure to FIRST, make a *complete* ROM backup of all 26 partitions to files with SP Flash Tool!
Then you can format all the flash eprom, and restore the Canvas Rom. So you will need the SN Write Tools to restore IMEI/WIFI/BAR Code/BT mac addr using the Canvas mddb database.
Then you have to restore all the Wiko hidden partitions except the system, boot and recovery, but from now on, you have to use the Canvas scatter file, because you changed the partition scheme!
Hidden partitions are important because they contain calibration data, security keys, crts, etc... For sure they are used on Stock Roms, ... I don't know if custom Roms use them...
So, be careful on mixing the correct scatter file being on Canvas or on Wiko type Rom...
sun75 said:
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!
The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).
These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!
If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).
Lastly, have you clicked on the "://d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
Click to expand...
Click to collapse
I thank you for the answer, yes that link after some ads bring me to a page that do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status? ps on the last version of MM for fever (the one that i have) if i flash a different version of twrp that is not the 3.0.something the recovery do not start, the phone remain on the "wiko" screen and stop here...
Melkor_98 said:
I thank you for the answer, yes that link after some ads bring me to a page than do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status?
Click to expand...
Click to collapse
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.
What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!
For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
sun75 said:
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.
What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!
For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
Click to expand...
Click to collapse
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7? (the reason of why i was using adb fastboot is becouse fever has not the removable battery and sp flash tool have difficulty do detect him)
Melkor_98 said:
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7?
Click to expand...
Click to collapse
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool!
sun75 said:
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool!
Click to expand...
Click to collapse
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help
Melkor_98 said:
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help
Click to expand...
Click to collapse
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!
Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash! The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
sun75 said:
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!
Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash! The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
Click to expand...
Click to collapse
It worked perfectly, thank you for everything
I've got huge battery drain especialy when the phone is used (I think it's correct on sleep mode) and I already set up kernel audiutor to 1040 max CPU speed...
Is it normal ?
Two others minor bugs :
Settings app crash at first boot, need to force stop it and re-launch the app to get it to work (I'm in France if it's matter).
Mobile data on LTE can't connect directly at phone boot, I have to switch to 3G then set it back to LTE and it's good.
Also, I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
pakrett-bm said:
I've got huge battery drain, only 8 hours and I already set up kernel audiutor to 1040 max CPU speed...
Is it normal ?
Also Settings app crash at first boot, need to kill it and re-launch the app to get it to work.
Mobile data on LTE can't connect directly, I have to switch to 3G then set it back to LTE but this is minor.
Click to expand...
Click to collapse
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?
If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!
The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!
For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
sun75 said:
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?
If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!
The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!
For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
Click to expand...
Click to collapse
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)
I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
Also why we need superSU ? Can't we use lineage/cm integrated root ?
Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.
Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?
The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.
Another thing, why there is two camera app exactly ?
pakrett-bm said:
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)
I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
Also why we need superSU ? Can't we use lineage/cm integrated root ?
Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.
Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?
The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.
Another thing, why there is two camera app exactly ?
Click to expand...
Click to collapse
It's not a problem what version of LL or MM did you came from...: the problem, maybe is the Region you are for the Baseband. I "statically linked" the SE Baseband (in the Stock MM Rom it is chosen by reading the NVRAM for the suffix _XX and then it loads the right files from /etc/firmware and ../mddb directories). Now, with the custom ROM, all the scripts reading the NVRAM for the suffix are gone, so it loads everytime the _n modem and mddb databases, whatever they are! So I overvritten the generic _n modem and mddb databases with the _SE ones. For your region to work correctly, I suggest you to upgrade to MM Stock, go in Factory Mode Menu and select Version Info -> check your Region Zone! If it's SE, ok, otherwise you have to copy/paste the zone modem/mddb _XX files to _n overwriting it for each group!
I don't know magisk and the other software you mentioned... so I can not help you for the battery drain with them!
For SuperSu... I tried to use /xbin/su but it doesn't work for all apps... Something works, most not! So, because are years I used SuperSu for all, I installed it solving the rooting problems for all apps requesting it!
Idem with Settings: it's requesting SuperSu with Root Permissions from the first start... maybe not installing SuperSu breaked something. You can check it by logging the boot process "adb shell logcat > log.txt" and looking for the cause of the crash! I can not replicate the problem...
For LTE,... in Italy I'm attaching LTE with no problems with two distinct network operators... it switchs automatically from H+ to 4G and viceversa without any interaction from me! I suspect you are on the wrong Baseband Zone... By the way, I got the Baseband from the MM V.34 ROM (the latest!).
Two cameras? Yes... only because every app has some nice features the other app does not have! Feel free to delete the one you don't like/don't use!
Some Bugs...
Hi,
I found some bugs in this Rom and/or port on Wiko Fever. I'll describe them so you can confirm them!
- In these days I'm working in a DataCenter at floor -1. Well, there is no GSM/data available here. The problem is that when coming back on ground or upper floors, the phone correctly reattach itself to H+/LTE data connection, but it never establishes an ip connection to the Internet, with the "x" in the LTE signal fixed as no ip was negotiated. This is true until a reboot is done! Once a reboot is done, the problem is solved: data connection and ip connection to the Internet are established automatically! I think it's the MM baseband that is not fully compatible with this Nougat Rom based on LL...: I'll try to substitute the Baseband with the LL V39 one and test it!
- FM radio module: I fixed it. BUT... : it's complaining about a "Alsasound: no defined handler specified for .... " forever (draining battery) and info on radio stations and RDS is not working (but radio and audio is working ok!). I'll investigate more on this!
- AudioFX mixer: apparently working,... but ... it's making no difference on sound, no matter on settings you select on its panel! So it's useless! I'll investigate to correct it, to change it, or the like. There is something wrong on the mixer config.
- As someone suggested me, I found that flashing TWRP 2.8.x and the Rom from MM results in some screen glitches and flickering on kernel boot, on charge and on TWRP operation. These can be annoying! To solve them, flash the Fever LL V39 Stock Rom before flashing anything else. Then flash the TWRP 2.8.x, and then the Rom. Doing so, you will never experience screen glitches and flickering on boot and TWRP operation. I think the big difference from the two versions (LL and MM) is the bootloader.bin that is different from the two releases.
- I added some MTK Engineer Mode Modules... someone asked me to do so....: some modules are crashing, e.g. the audio interface test suite, maybe for the Alsasound interface.
- I updated the OpenGLES driver library with the Fever V39 one: more stability.
- I updated all the audio/mixer interface to make FM Radio module work. Maybe this breaks AudioFX, maybe not...
- I updated the installer scripts to look for /gapps/gapps.zip and for /supersu/supersu.zip, so you can download them separately (the version you want) and integrate them yourself. Zip the Rom, and flash!
- Settings -> Backup & Restore -> Factory Reset : is NOT working (if you press "restore", it does NOTHING!!). Ok ok...you can hard reset by TWRP... I Know!
I think it's all... for now!
I'll update the Rom .zip once I'll solve the major issues here explained.
I finally saw someone interested in making a rom for wiko fever and here i am. I would like to know if i can install this rom in the wiko fever 16gb/2g ram version. I noyticed by the stock systems version that this is for wiko fever with 3gb ram. Anyways thank you for your goooooooood work!!
Edit: i have an hanuna twrp already installed in my phone, will it work or i have to install the version metion in the rom description??
Few days ago as expected, official users (who is using CN-EN official ROMs) of Le Pro 3 AI (further mentioned "x7") got an OTA update to the latest release of EUI 6.0.030S.
The miracle that expected was not appeared. It is still based on Android 6.0.1 (Marshmallow).
The ROM is still not localized for other countries, it contains only CN and EN languages.
And there still many bloatware of LeEco services that is very annoyance.
But first of all, the apps inside are now more optimized and as I see, they starting and function faster then previously.
Ok, let's go to the main part - links =)
The Official Site where you can download the ROM based on OTA update scheme is HERE. Also you can download a copy of OTA package from HERE.
But if you want to download faster, you can use my clouds where I'm continuously holding the most of Official ROMs for x7.
---> MEGA (follow into the folder called "original_stock")
---> FEX
Inside my clouds you can find that the ROM filenames contains not only a version but also an appropriate suffix (_OTA or _FASTBOOT). It's used to separate the ROMs by the installation method.
The FASTBOOT prepared ROMs contains an installation scripts (.BAT for Windows and .SH for Linux/Mac) for not only full installation (with clearing of User Storage), but also for update (without clearing of User Storage).
Please be careful, don't even try to install via FASTBOOT without clearing of User Storage, if you currently have functioning non Official multilingual EUI like 5.9.027S (faked as 028S in menu "About phone") or other non official!!! If you'll do this you will get many conflicts in settings and apps.
I expect that the FASTBOOT updating instructions are widely known, but remind them once more:
1) Enable the "Developer options" menu by clicking on "Build number" 7 times in the "About phone"
2) In the "Developer options" menu, turn on "OEM unlocking" and "USB debugging"
3) Connect the phone to the computer with a USB cable
4) Run one of the installation scripts from the folder of the unpacked firmware
5) Immediately upon startup, allow on the phone screen the "USB debugging" permission for your computer, preferably within the checkbox "always trust this device"
6) Wait until the installation process finishes (15-20 mins), calmly referring to the fact that the phone itself will reboot into FASTBOOT mode, and also please ignore the Sparse format error message (it's normal)
7) The phone itself will reboot into a new OS ... the first launch will be very long
Please feel free to ask anything here about the installation process, cloud links etc.
But be ready that I'm not fast answering.
Any other questions including the comparison of EUI versions performance and functionality will be ignored by me.
We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =|
thank you
I should have researched before buying the device kk was already "lost" trying to find a customized rom for him. this part of the text: "We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =| " , clarified me a lot
I istalled it but it does not have google play store?
azizo07 said:
I istalled it but it does not have google play store?
Click to expand...
Click to collapse
ROM does not have Google applications. You need install it. I think this still working in this version: https://forum.xda-developers.com/le-pro3/leeco-le-pro3-a1-model-x651-guides-development--and-mods/automated-installer-gapps-morelocale2-t3752576
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
azizo07 said:
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
Click to expand...
Click to collapse
030S mod is based on APKs of 030S with few modifications... but it also runs the old Boot from version 027S... so it may have some unexpected behavior...
yes, all of these ROMs have no root... but with mods based on Boot of 027S version you can use a temporary root (one time booting into TWRP) for further system modifications and then back to boot with native stock kernel and modified system will run good (expect the problems with apps you may cause by modifications)
hi, how i can install this ROM if I use a non official Rom? I mean, I recived this phone yesterday with a 028s (stable) that is non official, and I want to install this official ROM.
Help please
My cell phone has brick
You have some rom to fix it?
Does the NFC work on this rom? I had 028s before but the NFC was disabled.
Hi im install rom eui 6.0.030s "https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634"]https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634 But me phone have in antutu 50000 . Ealier was 100000. What is wrong i see Stock-thermal.zip but i cant dowload . plise help
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
cyzarine said:
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
Click to expand...
Click to collapse
What you can't see? The scripts?
You need to look at the contains of unpacked ROM zip that have suffix "FASTBOOT" in filename. There must be files with names like "x7_fastboot_tool.bat" and "x7_fastboot_tool_noUser.bat" and also same files with ".sh" extensions for Linux.
For installation to start you need to run one of this scripts. To run from CLI (CMD), not by double-clicking on it.
what's the score in antutu in new rom ? I have 50000....
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
cyzarine said:
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
Click to expand...
Click to collapse
This is an OTA package. But it's buggy, my try to make a direct update from 028S to this 030S with OTA way was failed, and I heart many reviews about same behavior.
So I think the best way to update is to use Fastboot with scripts and executable provided in my package that contains "_FASTBOOT" suffix in filename.
From there you can use script "x7_fastboot_tool_noUser.bat" (or .sh option in Linux) to make update to 030S (only from clean stock 025S, 026S or 028S, not from fake 027S or any mod) without clearing of Userdata Storage.
Or you can use script "x7_fastboot_tool.bat" (or .sh option in Linux) to make a new installation of 030S with clearing of Userdata Storage (from any other previous ROM).
If you can't download by my links provided in topic, please write here and I'll try to solve this.
grzegorzkuc said:
what's the score in antutu in new rom ? I have 50000....
Click to expand...
Click to collapse
My x650 shows 87000 in antutu on 030S. I can't know what is reason you having less.
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
I think that is 027s custom rom better than this 028s. I recommend you to not change anything.
Sent from my LEX657 using Tapatalk
AmanS99 said:
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
Click to expand...
Click to collapse
As an example of this way how to move into stock 028S with flashing first 025S and then just update to 028S (or 030S if you want) I prepared a video half of year ago. HERE
I understand that not all processes there are perfect... for example I used ADB to push ROM instead of MTP that is much faster =)
But if you have experience and you sure in other option of processing the steps explained in this video - enjoy and good luck.
Hope it will help somebody.
P.S.: Now I have some trouble with focus (can't focus larger then 120 cm) in stock Camera on EUI 030S and have a plan to get 028S back just for testing of Camera and focus processing.
P.S.2.: If you will have desire to get back into custom 027S you had earlier, you always can make it. It's available on both forums (XDA & 4pda). But you need to know, that changing of using between clean stock and custom ROMs is always requires you to clean a Userspace too.
Thanks for your reply . But I want to ask is there is risk of getting brick if anything goes wrong.
I'm proud to present the first dual boot project for the Samsung Galaxy S9+ Snapdragon version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
NOTE
Treble-based ROMs are NOT supported(yet)! In-app ROM changing may not work on stock ROM (maybe it works, maybe not) so you have to use utilities.zip or flash the boot.img of every ROM! I do not own a S9+ so I rely on you guys!
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Patcher: Download
Utilities: Download
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy S9+ Snapdragon/Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Epic htc 1 said:
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Click to expand...
Click to collapse
Yes root is needed, but the patcher does not support treble ROMs at this point. Maybe in the future.
Im not a programmer, I just add support for devices and compile it. The real programming is made by the official devs
please support for exynos
Joad said:
please support for exynos
Click to expand...
Click to collapse
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
simon151102 said:
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
Click to expand...
Click to collapse
Thanks .
View attachment 20190225.101831.tar.gz
Joad said:
Thanks .
Click to expand...
Click to collapse
Will compile a new version with S9+ Exynos support in the next few days
Update
Support for S9+ Exynos version
Patcher: Download
Utilities: Download
Does anyone have a root for s9 plus (snapdragon)
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Epic htc 1 said:
Does anyone have a root for s9 plus (snapdragon)
Click to expand...
Click to collapse
Use magisks built-in root, works perfect on most devices
Joad said:
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Click to expand...
Click to collapse
I will look into this.
But I cant guarantee for a fix because I have no skills in programming
Thank you very much,if anyone has any information about this plz let me know I'm really interested in this program
Does this work for anyone? and if so, using which roms.
Thanks
cvamoose said:
Does this work for anyone? and if so, using which roms.
Thanks
Click to expand...
Click to collapse
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
simon151102 said:
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
Click to expand...
Click to collapse
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
cvamoose said:
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Click to expand...
Click to collapse
Yes, treble devices arent supported (yet?).
I dont know if the S9+ is treble based, but it seems like this version of DBP works for most S9+ users
kykint said:
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
Click to expand...
Click to collapse
Sorry, Im not a "real" dev.
All I did was following the instructions from the DBP wiki.
Is there anyone that can make a modded version of this that will work on non rooted phones and it doesn't have to be a dual boot patcher but just to get a different ROM running on top or VNC into and use. Maybe like a dual ROM runner.