Develop Bugs

Trouble Flashing Custom ROM

So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.

Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later

Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)

slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew

Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.

peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew

Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew

Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!

First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs

Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]

Phone bricks when trying to flash new ROM?!

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Does anyone know what the problem could be?

I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk

Wrong forum.

danecr7 said:
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong

RazorBlade123 said:
Wrong forum.
Click to expand...
Click to collapse
Yeah I thought it seemed a little out of place but I don't know where to post it? Is there a general questions forum?

evilkitty69 said:
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
Click to expand...
Click to collapse
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.

danecr7 said:
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
Click to expand...
Click to collapse
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly

evilkitty69 said:
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
Click to expand...
Click to collapse
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.

danecr7 said:
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
Click to expand...
Click to collapse
All of the ROMs I tried with were android 6.0.1, I'm avoiding touching android 7 because I'm not a fan
The strange thing is that in TWRP under "mount", system is unchecked and it won't stay checked when I reboot or try to flash something and then the flash fails. Strangely however, I can flash RR afresh and it will work but nothing else works
Therefore I don't think OOS would work either

Upgrading from S7 to Pixel XL 2 - Few Questions

Getting the phone tomorrow and wanted to ask a few questions. The phone is on the latest update.
First thing I want to do is unlock the bootloader and root the device, can someone point me to where I can find the latest information for a device that's up to date? I have already found the method I am familiar with, using fastboot to unlock bootloader, running TWRP, flashing TWRP & magisk, etc. Not sure if that would work on the latest Android as the guide is from last year.
Second thing I am looking for a ROM that allows me to theme. Allows me to install the minimal Google APPS, as I do not want Assistant, Photos, etc. Only Google Apps I use, I will download via Play Store. And more importantly allow me to use custom Kernels. I would prefer if the ROM comes already pre-installed with Viper4Android & has audio tweaks made to it.
Third, can I use Xposed Framework with Pixel XL 2? And if yes, is there a ROM that already has Xposed Framework pre-installed?
Finally, one of the most important features I used on the Galaxy S7 is scrolling screenshot, if this is available pre-built into a ROM as a feature that would be brilliant. If not, what is the best APP people use for this feature?
Thank you for all your help in return. Really excited for the Pixel XL 2. Probably do need to buy a USB Type-C DAC or DAC/AMP combo to get the best out of my Sennheiser Momentum 2.0 over-ears though, as I've read sound quality is very disappointing using the adaptor that comes with it.

The link below is a good start:
https://forum.xda-developers.com/pi...unlock-flash-root-pixel-2-xl-t3702418/page202
I believe the guide should still work even with the latest updates!
CarbonROM has full OMS, which means you can use the theming engine Substratum to its full capability. As for minimal apps, I think you can get away with not installing the recommended GApps package in the CarbonROM thread for a minimal setup, but don't hold me to that lol.
Yes you can use Xposed, I have it installed on my 2 XL right now! I don't think there are any ROMs that have it pre-installed, however, getting Xposed is as easy as flashing a zip file in TWRP.
Not sure about scrolling screenshots, maybe there's an app on the Play Store.
Hope at least some of this helps:silly:

Thank you for the reply. I don't get the installation instructions in Carbon ROM are different to what I am used to, once I've unlocked, rooted, and installed TWRP. Shouldn't I be able to just install ROMS and GAPPS via TWRP?
Their install instructions start with "Flash the newest factory images on both slots".
What's both slots? I checked a few others ROMS, can't find people talking about slots or having to flash things to two different slots. Does this imply there's two different system partitions and I have to flash the factory image first to both of them, their installation instructions are confusing me.
So from what I managed to understand flash newest factory image to both slots (don't know how to do that, I have to research it, I didn't know there was 2 system partitions with Pixel 2 XL), then flash TWRP, then flash ROM to slot 1, then flash gapps to slot 2 after rebooting back to recovery? And if i want xposed for example that goes in slot 2 with gapps as well, or anything that I need to flash that isn't the ROM goes into the opposite slot as the rom?

Blackfyre said:
Thank you for the reply. I don't get the installation instructions in Carbon ROM are different to what I am used to, once I've unlocked, rooted, and installed TWRP. Shouldn't I be able to just install ROMS and GAPPS via TWRP?
Their install instructions start with "Flash the newest factory images on both slots".
What's both slots? I checked a few others ROMS, can't find people talking about slots or having to flash things to two different slots. Does this imply there's two different system partitions and I have to flash the factory image first to both of them, their installation instructions are confusing me.
So from what I managed to understand flash newest factory image to both slots (don't know how to do that, I have to research it, I didn't know there was 2 system partitions with Pixel 2 XL), then flash TWRP, then flash ROM to slot 1, then flash gapps to slot 2 after rebooting back to recovery? And if i want xposed for example that goes in slot 2 with gapps as well, or anything that I need to flash that isn't the ROM goes into the opposite slot as the rom?
Click to expand...
Click to collapse
Here is a script that will flash the stock factory images to both slots......https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Yes, we have an a/b partitioned storage on the P2XL, which is why things are a little bit different when it comes to flashing roms.

Another's S7 to Pixel XL 2 experience for some good info here

You should have went with Huawei P20 Pro

Switch to another custom rom

Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.

oceliome said:
Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.
Click to expand...
Click to collapse
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.

sliding_billy said:
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.
Click to expand...
Click to collapse
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.

wangdaning said:
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.
Click to expand...
Click to collapse
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.

sliding_billy said:
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.
Click to expand...
Click to collapse
True, but lots of people have extra time nowadays. I would say just always make sure you back up somehow before any switch. Be ready to wipe your device clean.

Thank you for your replys.
I'm not an english speaking personn, so if i understand:
The normal way to switch two customs roms is to "transit" by the stock rom and clear all data and then install rhe new custom rom.
The other way, would be dirty flash the new custom rom above the previous custom rom (with loss data possible so a bachup is needed).

Question Is it possible to have bricked a partition slot on Poco F3?

You may have noticed in my other threads i've had a lot of trouble flashing crDroid. On my first attempt I flashed an incompatible Gapps addon which made the phone hang on the crDroid logo, it simply wouldn't get passed it and boot in to the phone. This was all on Slot A.
I fixed the problem by flashing the ROM again and everything seems ok. When I flashed the ROM again it flashed it to Slot B and i'd like to know what would happen if were to update crDroid by flashing the latest version or if i did a clean flash of a different ROM altogether?
My concern is that anything i flash again will flash to Slot A and then wont boot.
Thanks

Did you flash NikGapps?
Unfortunately I don't have much experience with Gapps. Most Custom ROMs don't require Gapps anymore..
But I used to use OpenGApps. Don't know of the differences between these Gapps projects. Neither do I know if flashing GApps requires a Data-Wipe..
I used ArrowOS and Xiaomi.eu a lot, and I never worried about where it flashes. Though, ArrowOS have their own Recovery.

cyanGalaxy said:
Did you flash NikGapps?
Unfortunately I don't have much experience with Gapps. Most Custom ROMs don't require Gapps anymore..
But I used to use OpenGApps. Don't know of the differences between these Gapps projects. Neither do I know if flashing GApps requires a Data-Wipe..
I used ArrowOS and Xiaomi.eu a lot, and I never worried about where it flashes. Though, ArrowOS have their own Recovery.
Click to expand...
Click to collapse
I flash NikGapps yes but i also flashed the Pixel Launcher which apparently is what caused the problem. Everything is working OK at the moment and i'm just trying to find out what would happen if i flashed a different ROM and it flashes it in the Slot A (where it wont boot) instead of Slot B (which works fine).