Coolpad Note 3 and lite are now officially supported by DualBootPatcher
Steps to use DualBootPatcher :-
# Downlad and install latest DualBootPatcher
apk from here
https://dbp.noobdev.io/
# Open it -> Go to roms in option
Grant all the permission,set the kernal
and update the ramdisk in primary rom.
# Go to settings and install boot ui.
# Now go to patch zip file -> Add flashable zip
# Select the rom.zip , googleapps.zip ,
patches.zip , addons.zip which you want to
use as secondary rom.
Select your device , data slot , (ext sd slot not
tested).
And apply patch.
# After patch completes install all the zip files
you have patched from twrp.
# If u want to use inapp flasher of
DualBootPatcher,
flash this zip before u use the app.
https://mega.nz/#!xhgQERbL!5UEPeMbbHU9kxLBmWLpUpsosRk4lGmtr0S3pWgkbdeU
#Note : works only if your rom supports init.d or su.d
# After the flash completes, hit reboot ==>> u
will be in the second rom.
# To switch rom :- Methods(any one works )
1. Using boot ui :u get option to switch rom during reboot
2. Select the rom in the App and reboot.
3. Install the boot.img in internal -> mutiboot folder from recovery and reboot
# If something goes wrong :-
Go to recovery -> install boot.img of primary
rom.
Note : 1. Not all the roms are tested.
Do At Your Own Risk
2. Note 3 plus also added but not tested
those who are interested can test and
coment here
CREDITS:-
#Chenxialong : For the incredible app
@Uday Hegde (For this Guide)
@kuberrocks96 (personally tested on Coolpad Note 3 Lite)
UPDATE : WORKING ON COOLPAD NOTE 3 , LITE AND PLUS
Working On Coolpad Note 3 as well
Note 3 plus try..
Well got interested...did the steps all...
And given all permissions...
When I try to install ROM as secondary (tried cm 12.1) while installing rom I got error saying unable to symblink and other as failed to extract data file to /data...any idea how to fix this...
Thanks in advance
File uploaded for reference crash log and a screenshot..
RaghuStar said:
Well got interested...did the steps all...
And given all permissions...
When I try to install ROM as secondary (tried cm 12.1) while installing rom I got error saying unable to symblink and other as failed to extract data file to /data...any idea how to fix this...
Thanks in advance
File uploaded for reference crash log and a screenshot..
Click to expand...
Click to collapse
did u tried to flash from recovery..?
Uday Hegde said:
did u tried to flash from recovery..?
Click to expand...
Click to collapse
Oh well no..flashed it from the app...as secondary ROM..
And I was able successfully boot android lollipop stockrom and Nougat Resurrection remix custom ROM as dual..I had no problem with that...and for RR ROM I selected extsd slot...so basically I could install in SD card...but failed in other slots..(slot 1.2.3 or secondary did not work for me.) And I did not try in data...
RaghuStar said:
Oh well no..flashed it from the app...as secondary ROM..
And I was able successfully boot android lollipop stockrom and Nougat Resurrection remix custom ROM as dual..I had no problem with that...and for RR ROM I selected extsd slot...so basically I could install in SD card...but failed in other slots..(slot 1.2.3 or secondary did not work for me.) And I did not try in data...
Click to expand...
Click to collapse
It is bcoz
Secondary slot is of system partition
and other 3 slots are of cache partition
as there is not enough space in all these 4 slots,it wont work.
And data slot is working for all roms.Extsd slot is working only for some roms as I tested.
And it is better to use twrp to flash.
no probleam if ur rom supports init.d (just flash the fix)otherwise u may face an assue of in switching rom,need to flash boot image of secondary rom manually.
Uday Hegde said:
It is bcoz
Secondary slot is of system partition
and other 3 slots are of cache partition
as there is not enough space in all these 4 slots,it wont work.
And data slot is working for all roms.Extsd slot is working only for some roms as I tested.
And it is better to use twrp to flash.
no probleam if ur rom supports init.d (just flash the fix)otherwise u may face an assue of in switching rom,need to flash boot image of secondary rom manually.
Click to expand...
Click to collapse
Well twarp is for primary ROM right!! How can I flash it for secondary ROM??? Is their any option for that...because if I want to flash gapps for my second ROM..all I did was first patching the ROM selecting same slot in which my RR ROM is present and then flashing the file by logging into the primary ROM..
RaghuStar said:
Well twarp is for primary ROM right!! How can I flash it for secondary ROM??? Is their any option for that...because if I want to flash gapps for my second ROM..all I did was first patching the ROM selecting same slot in which my RR ROM is present and then flashing the file by logging into the primary ROM..
Click to expand...
Click to collapse
what the app does is it inserts some binary to handle the process of flashing into the zip files.
patch the zip files such as gapps or patches to the rom and give the same id as the rom,it will be flashed to ur rom(to which ro has that id).
and flashing the patched zip files from recovery will not touch the primary rom.binary will create create a chroot environment at /data/local/multiboot/slot-id/ and everything will be flashed into it...
Uday Hegde said:
what the app does is it inserts some binary to handle the process of flashing into the zip files.
patch the zip files such as gapps or patches to the rom and give the same id as the rom,it will be flashed to ur rom(to which ro has that id).
and flashing the patched zip files from recovery will not touch the primary rom.binary will create create a chroot environment at /data/local/multiboot/slot-id/ and everything will be flashed into it...
Click to expand...
Click to collapse
Thanks a lot bro...
It works in coolpad note 3 plus..so u can edit ur blog saying it is tested in cpn3+ also...all the best...
If I get any qustn I will post it...thank u very much bro
RaghuStar said:
Thanks a lot bro...
It works in coolpad note 3 plus..so u can edit ur blog saying it is tested in cpn3+ also...all the best...
If I get any qustn I will post it...thank u very much bro
Click to expand...
Click to collapse
sure bro
Thanks sir for the guide
yadavdharmendar said:
Thanks sir for the guide
Click to expand...
Click to collapse
All thanks to @Uday Hegde
Unable to dual boot RR with MIUI 8.1
Am trying to dual boot RR with MIUI 8 but its showing same error that was posted by RaghuStar. Even tried by TWRP recovery, but it showing same error, what should I do?
What exactly going wrong?
Am using Coolpad Note 3 Lite
unable to update ramdisk on cpn3. why?
ripon_b said:
unable to update ramdisk on cpn3. why?
Click to expand...
Click to collapse
may be ur using nougat rom.
its bcoz of special characters in board name.
to solve
backup your boot.img
unpack it using any boot.img unpack tool
edit boot.img-board using text editor
clear all the lines in that file
repack boot.img and flash
now it will not fail to update
abhishek_patil said:
Am trying to dual boot RR with MIUI 8 but its showing same error that was posted by RaghuStar. Even tried by TWRP recovery, but it showing same error, what should I do?
What exactly going wrong?
Am using Coolpad Note 3 Lite
Click to expand...
Click to collapse
use data slot or external sd card
I have tried that also..
abhishek_patil said:
I have tried that also..
Click to expand...
Click to collapse
u have log file of the error..??
Uday Hegde said:
u have log file of the error..??
Click to expand...
Click to collapse
Actually it was deleted, but according to my research, for dual boot, ram disk should be updated in both ROMs, but I noticed a problem with nougat ROM, I am unable to update RAMDisk in Nougat ROM, so when I dual boot it with MIUI, it goes in Boot Loop. But how can I update RAMDisk in Nougat?
abhishek_patil said:
Actually it was deleted, but according to my research, for dual boot, ram disk should be updated in both ROMs, but I noticed a problem with nougat ROM, I am unable to update RAMDisk in Nougat ROM, so when I dual boot it with MIUI, it goes in Boot Loop. But how can I update RAMDisk in Nougat?
Click to expand...
Click to collapse
check above comnts for update ramdisk in nougat roms.
but its not necessary to update ramdisk,it is required only to use boot ui.
Uday Hegde said:
check above comnts for update ramdisk in nougat roms.
but its not necessary to update ramdisk,it is required only to use boot ui.
Click to expand...
Click to collapse
Okay, i have following Questions.
1) Which software should I use to unzip img file.
2) I am unable to dual boot it with MM V010 on CN3L,
It showing same error posted by @RaghuStar.
3) Avoiding use of BootUI will prevent BootLoop?
4) Is there any effect of kernel version?
Related
Hello all galaxy note 4 910C users...below is the guide to multiboot different ROMs on your galaxy note 4 910c model.
1. Install the dual boot patcher app from the following link and also download the zip file which can be used while in recovery when needed........https://snapshots.noobdev.io/
2. Select patch zip...select the note 4 exynos model and select the data slot and write any name in id field...this id would be used later to flash any zip to the Rom on data slot.... Then select the tw/aosp ROM and tap to patch. The touchwiz ROM can be installed only on the data slot since the system memory will not allow it to install as secondary ROM. For eg. If u r using sweet ROM and you want to install simpl ROM ...you have patch it with data slot.
3. Once the patch is successful ...select ROM and click on the bottom right corner with a pink icon. ..and select the patched file and flash the zip.
4. After successful flash, the ROM section in the menu will show two roms. Select the new ROM and reboot. That's it.
Note
1. The secondary ROM can not be flashed if you are using glamor ROM because there is some system mouting error and you can not also flash the glamor ROM as secondary or data slot due to permission fix requirement after the first boot.
2. If you want to install the glamor rom.....there is a workaround..will write in detail later.
3. To flash any zip like xposed to the ROM on data slot patch the zip uaing the id assigned to the Rom and flash the zip.
A big thanks to @chenxiaolong ..original thread ....http://forum.xda-developers.com/showthread.php?t=2447534 by @chenxiaolong.
For using dual rom having glamor as primary please follow the below steps:
1. You should be on note 4 touchwiz rom such as sweet rom , ketan rom , simpl rom , etc
2. Install the dual boot apk and flash the aosp rom to the secondary slot as mentioned in the OP.
3. Reboot to the secondary rom and install the dual boot apk. Go to patch zip and patch the glamor rom with primary upgrade slot. After sucessfull patch flash the glamor rom. After sucessfull flash go the rom section and in it will show the primary rom as glamor.
4. Click on the 3 dot menu and select wipe rom and delete cache, dalvik and data only. Then select glamor rom and it will switch to glamor rom and then reboot and after 5 min go to recovery and fix the permission. Wait for a solid 15 to 20 min and you would reboot in to glamor rom.
5. Once you set your rom go to system and open the build.prop and paste the following at the end and save and reboot the phone
ro.patcher.device=treltexx
6. Open the dual boot app and switch to secondary rom and you would be able to boot in to the secondary rom.
7. Patch any rom with data slot and flash it. To flash anything to glamor or rom on data slot you need to reboot in to secondary rom. This rom will act only for flashing the stuff and you can not flash anything to secondary rom.
You can use end number of roms on data slot till your memory is out of space.
Hi! Can you please explain how to backup the secondary rom? Also, is it safe to delete a rom inside the app?
Thanks, and congratulations for the great work!
Regards!
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.
WELCOME
Dual Boot Patcher
I am proud to present to you, Dual Boot Patcher for j510!
Code:
Disclaimer:
I am not responsible for any bricked devices lost data or national disasters. Use at your own risk
Features:
Run two or more roms on your device at the same time!
Able to patch rom zips, custom kernels, gapps, supersu zips etc
Clean Material UI
Boot UI which allows you to select ROM at boot
App Sharing between Roms
Backup and Restore roms
Note: If the app is saying that this device is not supported and you have j510, edit your build.prop to set ro.build.product and ro.product.device to "j5xnlte". Then reboot. The app should be working. Do this only if you have j510. If you set the values improperly, installing a dual boot zip will hard brick your device.
TUTORIAL:
NOTE:Make a full nandroid backup before proceeding!!
Install your first ROM normally(from TWRP). It is recommended that if you want to multiboot an AROMA ROM, you should install it first(as primary). If you want to make your current rom as primary, skip this step.
Download and install the apk provided in the attachments.
Download the second rom.
Open the Dual Boot Patcher app, in the left swipe-in menu, select ROM section
It will ask you to set the kernel for Primary Rom. press Ok
Then go to "Patch zip file" menu, and click on the red "add" button
Then select "Add flashable zip". It will ask you to select a rom zip. Browse to your downloaded ROM and long-press to select it.
It will then ask you where to install it. You can Either Install it in "Secondary" which will install the Rom in system partition(use this if you have enough space on your system partition( at least 1.1 GB for AOSP roms and 1.8 GB for Touchwiz Roms). If you dont have enough space on your system partition, install it in Data or ext sd slot.(Note that installing in Data will take up space from your internal memory. DO not select the "multi slots"! they are for other devices
Click on OK. it will ask you the location of target file, just click on select to use defaults.
if you have any additional zips(such as gapps or supersu) patch them all using the above method. Select the same setting you used for the ROM!
After you have added all your zips, Click on the tick in the upper right corner and the patching will begin!
After Patching is done, reboot to recovery. DO NOT WIPE ANYTHING. Just install the zips you just patched(they will have "Dual" or "Data slot" written in front of their names.
After installation is complete, click reboot, and it will reboot to your newly installed ROM. Set up the rom normally. After setup is complete, install the DualBootPatcher apk.
Now you can select whichever ROM you want in the app. Just select it and restart!
From now onwards patch every zip with dual boot patcher before installing!
Boot UI
If you want Boot ui, follow these steps:
Go to roms section of the app. Press the 3 dots next to your first rom then scroll down and select update ramdisk. then press ok. It will ask you to reboot. just press reboot later
Repeat the same with other roms
Then go to settings and select install Boot ui.
Download Apk
DualBootUtilities
If anything goes wrong with the DualBoot keep the utilities zip in your sdcard. You can flash it in recovery(AROMA only). It allows you to wipe any rom installed on your device or switch to any rom.
Download Utilities
UPDATES
Update1:
Performance Improvements
Now you can restore backup to primary and secondary locations too(previously gave error)
Update2:
Added j5xnltexx to supported device codenames
Performance improvements
This app is not mine. I added support for dual boot on J5 2016.
This app is licensed under GPL. As per its requirements, here is the source code:
https://github.com/RIPT1DE/DualBootPatcher
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Boot ui not supported ?
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
This not work either
Moshifan100 said:
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Click to expand...
Click to collapse
No changes to the master branch as I am keeping it in sync with the original developer's master. The changes are in branch j510fn_support.
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
Bro change ro.build.product and ro.product.device in build. Prop to j5xnlte.
Wizardlysense said:
This not work either
Click to expand...
Click to collapse
Also if the above doesn't work send me the update.log
__riptide__ said:
Also if the above doesn't work send me the update.log
Click to expand...
Click to collapse
Here
Wizardlysense said:
Here
Click to expand...
Click to collapse
Did you give storage and root permission?
__riptide__ said:
Did you give storage and root permission?
Click to expand...
Click to collapse
Yup
Wizardlysense said:
Yup
Click to expand...
Click to collapse
Ok. Then can you send me a copy of your build. Prop?
Guyz, this is perfectly working for me.
Just follow the instructions.
@Wizardlysense I have edited my post with further instructions. Try those. If it's still not working, we will and figure it out.
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Incredible! Just incredible! Works fine with a5ux and lineage os!
GlitchWolf said:
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Click to expand...
Click to collapse
What is the error?
doc_elias said:
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Click to expand...
Click to collapse
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
gzdc said:
Incredible! Just incredible! Works fine with a5ux and lineage os!
Click to expand...
Click to collapse
Same here.. Great Work! Amazing!
__riptide__ said:
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
Click to expand...
Click to collapse
Everything working fine.
OK, so guys some of us have been facing problems in flashing the MIUI modded roms, and the error “ur device is Raphaelin and this Rom is for Raphael” sorry I don't remember the exact statement but u got me right.
Well...below are the steps u can do to fix this error.
Prerequisite:
1. Your system must have 7zip installed
2. You should have a modded MIUI Rom
3. Little Attention
1. Download Your Modded ROM (eu, MIUIMIX, MASIK, MIUI MOD, MIUI PRO) and all other MIUI modded roms.
2. Right Click on the .zip file which u have downloaded.
3. Follow now....
Right Click on zip file > 7zip > Open Archive > META INF > com > google > android > right click on updater-script and choose Edit or F4
4. A text file will open up with some code stuff….
5. Now change raphael to raphaelin thats it. (in begaining, u have to change around 4 names in most of the Roms)
6. After changing the name, when You Close the Text File window, a pop will ask u to SAVE the file
7. Choose Save , then agan it will ask “Do you want to update it in the archive?” Choose OK
8. 7zip will automatically repack the zip file
9. Now u can flash this ROM without problems
Please help
I have unlocked my bootloader and flashed the twrp successfully but every time I try to flash a rom (tried to flash evolutionx 4.0 rom ) the twrp says “E unhandled flag wrapped key” and after flashing the rom it directly boots into fast recovery.
RandomStha said:
I have unlocked my bootloader and flashed the twrp successfully but every time I try to flash a rom (tried to flash evolutionx 4.0 rom ) the twrp says “E unhandled flag wrapped key” and after flashing the rom it directly boots into fast recovery.
Click to expand...
Click to collapse
yeah do not worry abt it.
right after flashing the ROM, kindly flash dm variety zip file
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
and reboot to system.
FOD not working after flashing MIUI EU stable
leosinfinity said:
OK, so guys some of us have been facing problems in flashing the MIUI modded roms, and the error “ur device is Raphaelin and this Rom is for Raphael” sorry I don't remember the exact statement but u got me right.
Well...below are the steps u can do to fix this error.
Prerequisite:
1. Your system must have 7zip installed
2. You should have a modded MIUI Rom
3. Little Attention
1. Download Your Modded ROM (eu, MIUIMIX, MASIK, MIUI MOD, MIUI PRO) and all other MIUI modded roms.
2. Right Click on the .zip file which u have downloaded.
3. Follow now....
Right Click on zip file > 7zip > Open Archive > META INF > com > google > android > right click on updater-script and choose Edit or F4
4. A text file will open up with some code stuff….
5. Now change raphael to raphaelin thats it. (in begaining, u have to change around 4 names in most of the Roms)
6. After changing the name, when You Close the Text File window, a pop will ask u to SAVE the file
7. Choose Save , then agan it will ask “Do you want to update it in the archive?” Choose OK
8. 7zip will automatically repack the zip file
9. Now u can flash this ROM without problems
Click to expand...
Click to collapse
Thanks for the guide. I have flashed stable Miui EU rom on Raphaelin but i am not able to fingerprint FoD to work. Is there a solution?
diwakar2030 said:
Thanks for the guide. I have flashed stable Miui EU rom on Raphaelin but i am not able to fingerprint FoD to work. Is there a solution?
Click to expand...
Click to collapse
It is working on my side bro im also on MIUI EU stable.(k20 pro indian)
Kindly clean flash the ROM.
WIPE CACHE, DALVIK CACHE, SYSTEM, VENDOR, DATA
Then flash the ROM right after that flash DM variety zip file.
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
boot into system.
Any other way to edit that file not in PC but in phone....?
abhimukesh25 said:
Any other way to edit that file not in PC but in phone....?
Click to expand...
Click to collapse
Use MIxplorer
GSI ROM: PixelExperience-10.0-20200328-GSI-ARM64-AB. Take it at Your Own Risk!
It works on Android 9 and 10 stock rom
INSTALLATION :
Enter TWRP Recovery
Select Wipe - Format Data - type "yes" and confirm
Select Reboot - Power off and Enter TWRP again
Copy GSI ROM and GAPPS to your phone
Install - Install Image - select PixelExperience-10.0-20200328-GSI-ARM64-AB.img - select System Image and Confirm to flash.
Select Reboot - Power off and Enter TWRP again
Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize
Select Mount - select "System" & "Vendor"
Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
Reboot - Recovery
Setup the phone - Done!
DOWNLOAD:
GSI ROM PixelExperience-10.0-20200328-GSI-ARM64-AB.img.xz
Open GAPPS open_gapps-arm64-10.0-nano-20200408.zip
ISSUE:
MTP does not work
other by your self
Credits
Thanks to ExpressLukeGSI
Watch this video how to flash it:
help pla i am a gamer and want to play pubg smooth plz help
can u please share the backup file of twrp of this rom
when i flashed and reboot ita says no os installed and
cant repair or resize the partion error 9 showed in twrp pls help i am a gamer and want smooth game play plz plzzzz
coolro121 said:
can u please share the backup file of twrp of this rom
when i flashed and reboot ita says no os installed and
cant repair or resize the partion error 9 showed in twrp pls help i am a gamer and want smooth game play plz plzzzz
Click to expand...
Click to collapse
I don't backup it, just follow the instructions correctly, don't miss a step and It should work, make sure you download ARM64-AB. On resize partition you must select system.
tried with these all gsi roms same error on all
i did all the things according to the video bro but
same error on resize and repair partion
twrp 8 error and no os installed can u tell me which firmware u flashed exactly name plz
coolro121 said:
i did all the things according to the video bro but
same error on resize and repair partion
twrp 8 error and no os installed can u tell me which firmware u flashed exactly name plz
Click to expand...
Click to collapse
I think I know what happened with you. After download the ROM PixelExperience-10.0-20200328-GSI-ARM64-AB.img.xz, you must extract it and you will get PixelExperience-10.0-20200328-GSI-ARM64-AB.img. You can extract it using winrar or 7-zip
hmm
i rename the pixel file to zip i should extract it okay i will try
How we can fix issue with mtp because mtp is important to connect phone with computer.and I use USB tethering often
Volte issue no call going
In pixel rom volte issue unable to call plz help
coolro121 said:
In pixel rom volte issue unable to call plz help
Click to expand...
Click to collapse
volte, mtp are does not work...
Thanks for the effort , but could magisk and xposed work well on this ROM ?
lfk0000 said:
Thanks for the effort , but could magisk and xposed work well on this ROM ?
Click to expand...
Click to collapse
Yes, it work
Device automatically restarts
Flashed custom ROM, as show in the video but after setting the account, device automatically restarts at particular time intervals unexpectedly. How do i fix it?