Related
Hello community
I am able to get as far as unlocking the bootloader but I'm not sure as what to do next. I am on a fresh clean 4.3 stock upgrade Can some one suggest the best rooting method and possibly a very good ROM and kernel for this device please...
jgentry151 said:
Hello community
I am able to get as far as unlocking the bootloader but I'm not sure as what to do next. I am on a fresh clean 4.3 stock upgrade Can some one suggest the best rooting method and possibly a very good ROM and kernel for this device please...
Click to expand...
Click to collapse
I recommend backing up your data before making any changes then follow the Nexus 4 Root Guide at http://forum.xda-developers.com/showthread.php?t=2266654 to install your preferred recovery utility, either Clockworkmod or TWRP.
If you plan to install a custom ROM and kernel anyway, there really isn't much point in gaining root on the stock 4.3 ROM. If you must gain root on the stock 4.3 ROM, you will need to download Chainfire's experimental SuperSU v1.41 (available at http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip) and transfer the file to the root folder of the Nexus internal storage. Start your phone's bootloader by powering down the Nexus and simultaneously holding the volume down and power buttons approximately 5 seconds until the bootloader screen appears. Next use the volume up/volume down buttons to highlight Recovery and press the power button to start the custom recovery. In recovery press Install, then highlight the file SuperSU-JWR66N-S005-130625-1.41.zip and move the button slider to the right to install root. Reboot the phone and update SuperSU from the Play Store.
There is a wide selection of custom ROMs and kernels available in Nexus 4 Android Development and Nexus 4 Original Android Development. Every custom ROM already includes a kernel, so you only need to download and flash a kernel if you need specific features inlcuded in the custom kernel. I recommend taking some time to review the ROMs listed in these two forums, look at the screen shots, and read some of the user comments regarding the ROMs that look appealing to you. Once you identify the ROM(s) you would like to try, download the ROM(s) and tranfer the zip file to the root folder of the Nexus internal storage.
Before flashing any ROM make sure your battery is charged at least 50%, then boot into recovery and make a nandroid backup of your existing setup. Next wipe data, cache, and Dalvik cache and install the custom ROM from the associated zip file. Bear in mind that the first boot after flashing a new ROM will take a few (5 to 10) minutes. After booting the phone configure your Google account, update your Play Store apps, and configure the phone settings to suit your preference then reboot your phone. Be patient: Try out the new ROM for a couple of days before making a decision to move to a different ROM.
Here is my Note 4 Guide. I did one for the note 3 so figured i will throw one up for note 4 so it might look familiar to it! Sorry this one is a little late but here it is!
I TAKE NO CREDIT I AM NO DEVELOPER! THIS IS MERELY A GUIDE!!
UNDERSTAND ROOT/RECOVERY WILL VOID YOUR WARRANTY
Part 1: Flashing TWRP onto Developer Note 3
Step 1- Download and install Odin onto Windows PC http://uploaded.net/file/o2xcp01n
Step 2- Download Verzion TWRP Tar File (openrecovery-twrp-2.8.1.1-trltevzw.img.tar) http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.1.1-trltevzw.img.tar
Step 3- Flash your Verizon TWRP Tar File your just downloaded in Odin under the AP Slot ONLY!
BE CAREFUL IF YOU PLACE IN WRONG SLOT DEVICE WILL BE A BRICK!
Side note phone will now say Set Warranty Bit: Recovery when booting into recovery. Don't worry this is normal. This is showing you what tripped warranty. More about this below later in guide.
Step 4- Flash Superuser if TWRP doesn't ask you to root http://download.chainfire.eu/589/Sup...erSU-v2.16.zip
Step 5- Make a complete backup of EVERYTHING in TWRP. Boot, Recovery, System, Data, Cache ALL OF THEM I have backed up to internal sdcard & external sdcard & even throw a backup on your pc just in case something catastrophic happens since we have no Odin stock files still!
Step 6- (optional) Flash a rom/kernel.
Rom Section: Only one stock rooted, deodexed, Knox-Free rom so far
Thanks @EMSpilot!!
http://forum.xda-developers.com/not...rom-stock-root-odex-deodex-knox-free-t2949569
Kernel Section: While there is no verizon specific kernels there are ones that will work. I have flashed ktoonsez's kernel over in the T-Mobile side of things and it does work. Haven't been on long but it will flash. I am testing now how much better it is then stock. Always have your boot.img ready to go and/or your stock backup in TWRP ready to restore the boot if required. Some other carrier kernels will not play nice with it but from what i have expereienced with Note 4 so far and the Note 3 T-Mobile kernels will work without any hassle. So continue to check back here for updates!
Thanks @ktoonsez!
http://forum.xda-developers.com/not...lopment/kernel-kt-note4-nih-ktweaker-t2936809
Step 7- Enjoy!
Part 2: Restoring Boot.img if phone will not boot after rom or kernel install
If you get a kernel that won't run properly or boot loop or a rom that will not boot on the developer edition without proper boot.img here is how you fix.
Step 1- Boot into TWRP. From phone being off use three finger method of vol up, power and home button to boot into TWRP.
Step 2- Restore boot.img from the very important backup in step 5 from part one! This is why you have to have a backup of everything! Restore the boot.img only and reboot!
Step 3- Back to enjoy!!
I do not take any credit for roms/kernel/recovery just sharing links and what I have done. Hope this guide helps!! Please continue to check back here for updates on roms/kernels or other helpful Developer Edition info!
Thanks for the instructions!
After your suggestion I also flashed KToonez kernel and it makes the phone a WHOLE lot snapier. The only issue is that sometime it'll randomly go into a boot-loop. I was wondering if you also had encountered this.
There's other kernels from t-mobile development which work on the DE, such as the N4 Kernel from Echo Rom. I'm running that and it's the smoothest my device has ever been.
keithce said:
Thanks for the instructions!
After your suggestion I also flashed KToonez kernel and it makes the phone a WHOLE lot snapier. The only issue is that sometime it'll randomly go into a boot-loop. I was wondering if you also had encountered this.
Click to expand...
Click to collapse
yes it does and oh i havent experienced that. i actually flashed stock kernel again to get a good baseline for battery life and such for a week or so before i start going off the deep end with kernels! haha what settings did you change?
bobbarker2 said:
There's other kernels from t-mobile development which work on the DE, such as the N4 Kernel from Echo Rom. I'm running that and it's the smoothest my device has ever been.
Click to expand...
Click to collapse
there wasnt when i looked but i will have to check them out! any special settings you are using!?
I've read pretty much every source I can find on getting a custom ROM up on my LG G2, which I haven't even rooted in the past 2 and a half years. My warranty ran out a while back and I'm getting a bit bored with stock now, and I want to start flashing, but the last time I did this was with my old HTC Desire HD.
As you can see I'm on 20d on my LG G2. It's a Hong Kong version for some reason, lol. What I considered doing was the following: update to the latest Lollipop official ROM using the LG Flash Tool (it gives me an available update to 30d); root using the rooting app, install a recovery with AutoRec Lollipop, flash a thermal recovery from the installed recovery (very scared of my phone overheating, I'm even considering putting it on a large, fast-running fan while doing anything, read too much about the phone overheating and making the screen yellow); back up my phone's IMEI data; use the recovery to install a brand new (I'm hoping a Marshmallow) ROM. I also understood that I need to flash a bootstack to change my bootloader to a KitKat, because it can be "fooled" using the BUMP thing. Is that correct? Do I even have to update my phone to Lollipop in this case? Also, how likely is it to overheat while doing all of these procedures?
Thanks in advance!
Sorry for the necroing my old thread, but I have yet to do anything with my phone. I am also still on KK. I saw that I can start rooting and install TWRP from it straight away. After that I need to flash a bootstack, right? How likely is it that I can brick myself? By that I mean what could get mixed up to get a brick while flashing. Also, has anyone had overheating issues while doing root, recovery installation and flashing things (newer TWRP, bootstacks, new ROM)?
Hi, i can understand your situation as i was in same till today, g2 with stock kitkat.
i finally installed cm13 after rooting it and the phone feels fresh.
you have understood most things right and ready now.
you dont need to upgrade to lollipop if youdont want to, you can start from kitkat itself.
few things i can tell you to begin here,
Root your G2,
for kitkat i found few good methods. Either do it via ioRoot using pc. or you can use towelroot or kingoroot apps to do it from phone itself. I used kingoroot since i didnt have a system with me. You can find these apps by searching at google, jst tyoe kingoroot. At first i was skeptical but it worked nice.
after root, you download autorec app, this is to install a custom recovery(twrp) for kitkat. you just have to install the app and run it and press install recovery/twrp and it'll do the rest.
after you have twrp installed, you need to upgrade it to latest version. For that download blastgator's twrp for your model and flash it through your recovery.
oh and dont forget to learn, how to enter into recovery yourself, since each G2 model has different method.
once you have these things you can start flahing roms. Most of the instructions on how to flash certain rom with what bootloader and bootstack etc. is written in its own thread, so you can learn that from that rom's thread that you will flash.
but basically, you need kk bootloader and lp bootstack for cm13 and above. usually both these things come in one zip. (if not you check for hybrid bootstacks)
Just make sure you are downloading things For your Model, if you try to flash different models stuff into yours, itll brick.
The autorec app, blastgator's twrp and ioroot can be found in a sticky thread in G2 general section, along with many other files and guides in that thread, theres complete index in that thread of all thing for all g2 models .
here : http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
also usually the phone doesnt heat up while flashing, just make sure your battery is more than 80% before you start and itll be ok. Even if it does a little, after a custom rom itll be fixed. I suggest you try cm13 for starters as your first custom rom.
hope this helps you :good:
Good Luck ::highfive:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
hitmancho said:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
Click to expand...
Click to collapse
to upgrade from kitkat you need lp or hybrid bootstacks. they have images (. img files) that are needed for your phone to function properly., like aboot, modem, radios etc. Hybrid bootstack contains aboot from kk and everyhing else from Lp. So when youll flash a bootstack, youll need to wipe everything, except internal storage(or external if you have one) , before you can flash it. that wipe will include, cache, dalvik cache, system, data. so basically all the old system stuff will be gone before you can flash this bootstack. i hope after reading that youll know that you cant access your old kk installation since itll be wiped, therell be nothing to boot to. if youll try, it will give you errors on lg logo.
understand it like this, to install new 21 inches tyres to your car, you need to upgrade the rims to hold a 21 inch tyre right? what will happen if you just put the 21' tyres on old 15' rim or old 15' tyres on new 21' rims?
the cm 13 devs dont recommend you to flash bootstacks because most of the models took the official lollipop update, which put everything in their phone to lolipop level. since there is no official marshmallow(MM) bootstack for our phone (because no official update), everyone developed ways to utilize lollipop bootstack to function on a custom MM Rom. Since most models are already on lollipop, theres no need to flash lollipop bootstack while flashing custom rom. That step is mostly for those who are still on stock or custom kitkat based rom. So they say to get official lollipop through kdz method, instead of flashing Lp bootstack before gettig their rom. But remember if a rom developer asks to install a bootstack for their rom, you should consider it if you dont have much knowledge about it, cause if you dont follow instructions, you can soft brick, in that case youll need hybrid bootstack.
see if you are using everyhing proper for your phone then your phone wont brick. only thing that can go wrong with that condition is your execution, your steps. As long as you dont make a mistake in these steps everything will go fine.
ill explain it what you should do.
1. first root your phone.
2. when done rooting, install "root checker" from google play. itll confirm if you have root or not.
3.Then you come back here and find autorec app from the link i gave you in my previous reply. download that, install the autorec app. and follow on screen instructions and itll install twrp recovery for you.
4. then come back here again, and find blastgator's twrp, from the same link in previous post. itll be the one whih says "twrp with f2fs". download it and remember where you put it.
5. turn off phone, boot into recovery (i hope you've learned by now how to get into recovery of your g2 model). Now youll be in recovery, hit install button there and find where you put that file, flash it, then reboot recovery, youll have new recovery after that. then you reboot into system.
now upto this point, you can play along in your kk, have fun with features, say last goodbyes and all lol. Because everything stock kk related will be gone, past this point, including all the apps you have installed.
[IMPORTANT] : after rooting and installing recovery, get bootstack zip, rom zip and gapps zip files downloaded and placed together in a folder on your phone, before you start with flashing bootstack. Because you wont be able to boot back into system after flashing just bootstack.
now you prepare for MM, boot into recovery, now since you are in kk, you need to install LP bootstack, and for that you need to wipe everything using your recovery's wipe feature.
6. in recovery, hit wipe, hit advanced, select cache, dalvik cache, system, data. [ Dont select internal storage otherwise all flashing files will be gone and youll be left with a brick.] and wipe.
7. Now hit the back button to go back to main recovery screen once wiping is finished. hit install, flash the bootstack zip.
8. now your phone has new bootloader but its still empty, like you got a body but no soul . so hit back button, hit install and flash the rom zip you downloaded.
9. now flash gApps same way.
10. once its done, just hit reboot system. no other steps needed.
11. be patient, first boot takes longer than normal boot.
12.enjoy MM :highfive:
you probably know these steps from all the reading but its for your reference, so you dont screw up at all and be safe from bricking.
you can get google apps from opengapps website. you need to get ARM-> 6.0 -> (your prefered ones) pico/nano/micro/etc.. pico has the least amount of gapps, all important ones are there in pico, then extra will increase as you go up from pico to stock. stock has all the gapps. size will also increase as you go up. so choose as you prefer.
now once you have a cm13 /MM based rom, you wont need to flash bootstacks for other roms from next time unless the developer instructs to do so.
good luck
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
andrew2432 said:
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
Click to expand...
Click to collapse
cwm is clockworkmod, its a custom recovery. i think you meant CM 13, mm rom.
yes, the Cyanogenmod team have placed root access into the rom, so once youll be finished wih installing cm 13 rom, you can just go to settings, Tap build number repeatedly until a message will show "congrats you are a developer now". that'll open developer options in main setting screen Go into that and youll see root access. turn it on. youll have root.
you can check in root checker app to confirm root access for confirmation. you wont need super su app in any of these roms anymore.
your steps :
stock
1. root
2.autorec (for installing twrp on your phone) for kitkat its on forums, for lollipop its in google play. just get the one for your model, search for autorec in google play.
- blastgator's twrp requires you to have any version of twrp beforehand in order to install his version.
3. download and save blastgator's latest twrp, when youll go to download his twrp, itll be written there which one's is the latest version, just download that one and flash it through recovery.
4. Yes place all files in your phone, you can get gapps from opengapps.org/
select arm- 6.0- whatever size you like(, pico is lightest contains all essential gapps, stock contains every gapps)
5. wipe yes.
6. flash bootstack
7. flash rom
8. flash gapps
9. once gapps done, just hit reboot system.
10. enjoy
yes go for it when you have more than 80% battery, this is to ensure that all flashing steps go through without any issue, you dont want your phone to run out of juice while flashing rom do you that could cause soft bricks. so always keep battery more before flashing.
[IMPORTANT] : remember to read instructions of the rom you're installing and adjust the steps as instructed in there.
Goodluck :highfive:
Awesome, I forgot to.flash gapps prior to something I just did, not sure if it will cause increased global warming or thermonuclear war...update soon
@MarshisnotMellow
Gapps installed!! No Internet connection on the d800 and something sinister has happened to my unlocked WiFi Hotspot so I'll have to check for play store capabilities later!! Thanks for the help!!
I decided to go with the latest 29.10.2016 nightly of CM13 for my first run on this phone. Everything went through, no one died, lol. I'm going to start installing and restoring stuff now, get Xposed on, like I have on my TF701T tablet and trick out my phone's appearance. Just a note - after you install new bootstacks your phone's MAC address will change, so if you have a WiFi network with a MAC filter you might want to add your new address.
Hello everyone,
last night I was toying with my Note 3 (SM-N9005) European Edition and I succesfully rooted the phone and installed Super SU.
Super SU was upgraded automatically via TWPR.
Tried to Flash Darkwolf Note7 rom for Note3.
Installation starts, but once it begines I get an error about wrong footer and the progress bar stops.
So I went back, used Odin again, changed from TWRP to CWM tried to flash again the same Rom got verification of zip file failed.
Downloaded RessurectionRom with 6.0.1 for note 3, same issue.
Went back again, changed from CWM to TWRP once more, same issue.
Installation fails
Ultimately had to recover the ROM that I had backed up.
Not sure what the problem is?
Can someone help me?
Thank you in advance.
Read the roms OP a guess is you are using the wrong version of TWRP .
TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
Ι don't think that the issue mate.
I downloaded exactly what I should have according to their site and the tutorial I follow.
Furthermore CWM has a dedicated CWM for note 9005 which again was unable to complete the installation.
So any other thoughts?
This is most likely due to the unsupported version of twrp you are using as darkwolf ported roms uses aroma/pico installer. Use below v3 like 2.8 you should be able to launch aroma installer.
REMEMBER TO FLASH A CUSTOM KERNEL OR IT WILL NOT BOOT ONCE YOU FINISH FLASHING THE DARKWOLF ROM AS DARKWOLF ROMS DONT HAVE ANY KERNEL INCLUDED.
I recommend using SKYNET GENESIS as your custom kernel. You will know how good it is after you install it:laugh:
I highly recommend you not to use note 7 darkwolf rom as your daily driver... features are really good but in actuall fact heats up like mad and drains battery very well
If there's still problems after trying my methods out please let me know i will give a full tutorial on how to install the DARKWOLF ROM on youtube
Cheers!
<<I recommend using SKYNET GENESIS as your custom kernel. You will know how good it is after you install it >>
That by the way is a closed thread by the mods on xda .
Hi guys, thank you for your replies.
But to b honest I am a bit of a novice. I just checked some tutorial videos and I though FUN let's sprush up the NOTE 3....
So I do not know how to proceed??
Let's see if I can help you with at least installing a CM12.1 on the n9005. Once you can successfully install CM12.1, you'll have a basic working knowledge of flashing.
Download the latest tar version of TWRP for the n9005 from here: https://twrp.me/devices/samsunggalaxynote3internationalqualcomm.html
Download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.133178914,d.amc
Download the latest cm12.1 for the n9005 from here and save it to either a micro SD card which you will put into the phone or the phone's internal memory: https://download.cyanogenmod.org/?device=hlte
Download the latest ARM version of gapps for the n9005 from here and save it to either a micro SD card which you will put into the phone or the phone's internal memory: http://opengapps.org/
Open Odin, uncheck everything except f.reset time.
Make sure CM12.1 and gapps are either on a micro SD card or the phone's internal memory. If CM12.1 and gapps are on a micro SD card, insert the card into the phone.
Put the phone into download mode, connect the phone to the computer, flash TWRP in the PDA slot. When you see the word "reset" in the status window remove the USB cable from the phone, remove the battery, replace the battery, use the button combination (home, volume up, power) to boot into recovery which should now be TWRP.
Once you are in TWRP, wipe system, data, cache, install CM12.1, install gapps, and reboot.
JJEgan said:
<<I recommend using SKYNET GENESIS as your custom kernel. You will know how good it is after you install it >>
That by the way is a closed thread by the mods on xda .
Click to expand...
Click to collapse
It IS a closed thread but you sill can get it somewhere else from a mirror. I will provide the link once i finish hosting somewhere. I have the kernel...
---------- Post added at 12:48 AM ---------- Previous post was at 12:47 AM ----------
JJEgan said:
<<I recommend using SKYNET GENESIS as your custom kernel. You will know how good it is after you install it >>
That by the way is a closed thread by the mods on xda .
Click to expand...
Click to collapse
It IS a closed thread but you sill can
get it somewhere else from a mirror. I will provide the link once i finish hosting somewhere. I have the kernel...
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Got now rr as primary rom and will try later on to flash some roms on the second space... Let you know if that works out.
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
superior8888 said:
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
Click to expand...
Click to collapse
I have also rr as primary but second rom install ended in error 1 in twrp. Maybe you can try to reset data of second rom with the dualboot patcher zip.
It might be helpful to read the Dual Boot Patcher thread for the OP5, as there may be some important info there that is relevant for getting it to work on the 5T.
I tried rr as primary, no problem. Tried adding 2nd rom as secondary, as data slot 1, and no dice. Even tried removing assert lines in the updater script as suggested in op5 with rr as 2nd rom but that didn't work either; either booted back to twrp or booted to a black screen. If anyone makes it work please document and share your work. I'm encrypted by the way, even though you're "supposed" to be decrypted I was able to switch between primary and the non-booting rom just fine.
Anyone having any luck with this?
matteosaeed said:
Anyone having any luck with this?
Click to expand...
Click to collapse
Nope primary install goes good with a oos rom not stock. But when you try to install a second rom it gives error 1 in twrp and rom don't boot up.
That's great! Old MultiROM user here!
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
superior888 said:
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Click to expand...
Click to collapse
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN ?
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
cubandanger05 said:
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
Click to expand...
Click to collapse
Thanks for updating us, I'm an old multirom user as well and I'm going to keep my eye on this.
cubandanger05 said:
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
Click to expand...
Click to collapse
Thanks! I'll try this next days.
Thanks. Nothing works with Oreo as of yet i suppose :/
superior888 said:
Thanks. Nothing works with Oreo as of yet i suppose :/
Click to expand...
Click to collapse
It may be possible to have oreo as primary and flash Nougat as data slot roms. I tried with Phoenix as primary and I could boot into rr Nougat in data slot but Phoenix wouldnt boot. If someone can try rr oreo as primary and report back. I'm tempted to try with otg and see if I can install secondary roms using extsd option
*Quick update*
I was able to keep latest Phoenix oreo ROM as primary and install and boot Nougat RR as data-slot and as secondary using the latest dualbootpatcher app which may have fixed the "failed to update mbtool" error I was getting on Phoenix ROM. Also I used Magisk 14.0 for root as the latest version 16.0 kept booting back to recovery on non primary ROMs.
I'm still unable to flash Oreo ROMs as data-slot or secondary. At least we're able to keep Oreo as primary and test Nougat ROMs until dualbootpatcher app is compatible with Oreo or until some other fix is released.
Internal storage/data is still encrypted and unreadable on all non-primary ROMs; you must be decrypted prior to installing additional ROMs to have access to it, which I haven't tested yet.
See screenshots
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
es0tericcha0s said:
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
Click to expand...
Click to collapse
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Edit: Now that it's working almost as intended we should make an official "how to" thread
cubandanger05 said:
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Click to expand...
Click to collapse
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
es0tericcha0s said:
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
Click to expand...
Click to collapse
? understandable