Related
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.
I am not a programmer and have little knowledge about flashing the ROM so to make sure I understand what I need to do and the order it needs to be done.
My Nexus 10 works great still, I have not had a security update for 2 some years and am concerned about this. Last October I tried to upgrade to 6.0 but it would not recognize the new rom and I ended up going back to the original 5.1 rom.
What I need to know is how to do it in a way I can understand. I have seen a utube video of someone that has been able to do it. So I know it can be done. Just need to know how.
Thanks,
Mike B.
Assuming you have a PC use this tool to unlock then root and install a custom recovery
Next download a Nougat rom like Lineage
Also download gapps and SuperSU
Copy the rom, gapps, and supersu into a folder on your tablet
Now reboot the tablet into recovery and do a full wipe then from recovery
Flash the rom
Flash gapps
Flash SuperSu
Reboot to system and give it a few minutes on the first boot
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload
MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!
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
Hi,
I have a Nexus 6P that has Android 7.1.2 (N2G47W) installed. I've just unlocked the bootloader, installed TWRP then installed Magisk 16.0 for root.
I'd like to next downgrade from Nougat to Marshmallow. Are there any steps to do so? Can I just boot to TWRP, and immediately install the factory image from https://developers.google.com/android/images#angler?
Or are there any additional steps I need to take?
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Exodusche said:
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Click to expand...
Click to collapse
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
goister said:
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
Click to expand...
Click to collapse
That's exactly what I'm saying unless you want to flash a marshmallow ROM. Then you can use TWRP but would still need 6.0 gapps and a computer to fastboot flash MM bootloader of that months build. MM vendor could be flashed by either fastboot or TWRP. Your best to download a MM build from Google site. Then unzip that folder and inside unzip again. You will get all the bootloader, vendor (radio optional) you will need for that months MM build. Then follow the guide from hiesenberg for returning to stock . Best to put all the images files and fastboot in the folder that is suggested in the guide . That way you can copy and paste the commands as written on the guide. There might be a flash all bat file you can use in the stock folder but not sure if MM had that I never used. If you have any more questions feel free to ask.
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
goister said:
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
Click to expand...
Click to collapse
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Exodusche said:
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Click to expand...
Click to collapse
Thanks. I've no issues wiping the phone as this is pretty much a fresh phone. There's nothing to even back up. The only thing I've done so far beyond rooting, was to import a certificate into /system. I suppose a factory reset would delete this certificate and bring it back to stock (but rooted)? Or should I wipe with TWRP instead?
Looking at the zip file of the stock ROM, here's what I see
bootloader-angler-angler-03.54.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mtc20l
radio-angler-angler-03.61.img
After wiping with TWRP, would I be able to run flash-all?
Edit: I've just TWRP wiped everything, and rebooted. However, the device is stuck at the initial "Google" screen with the lock icon at the button. How long is it supposed to take to boot up after a full TWRP wipe?
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.