I tried aosp extended, pixel experience and several other pie treble roms. They don't even enter the boot screen. They are stuck in the screen where it says your device has been unlocked. I used the arm64 a only images. The openkirin roms work otherwise. Help regarding this will be appreciated. BTW I used twrp to flash. I even tried using magisk but it didn't work. Can you guys check and let me know your results. Guidance regarding this issue will also be helpful.
Edit- only LOS16 unofficial treble boots.
you've got to flash using fastboot and then right after, without booting to the OS, flash GApps if the ROM doesn't already have it.
steven360 said:
you've got to flash using fastboot and then right after, without booting to the OS, flash GApps if the ROM doesn't already have it.
Click to expand...
Click to collapse
What if the entire reason we're using an AOSP/etc ROM is to avoid Google integration (to use MicroG, etc)?
Is there a way to use this phone without Gapps? If not, what is the bare minimum to let it boot successfully, and can they be disabled/removed later?
UPDATE: This AOSP ROM w/ MicroG integrated boots and runs successfully on the Honor 7X. Stock recovery, flashed via fastboot. (I did fastboot format system & fastboot -w to be safe).
awoolf said:
What if the entire reason we're using an AOSP/etc ROM is to avoid Google integration (to use MicroG, etc)?
Is there a way to use this phone without Gapps? If not, what is the bare minimum to let it boot successfully, and can they be disabled/removed later?
UPDATE: This AOSP ROM w/ MicroG integrated boots and runs successfully on the Honor 7X. Stock recovery, flashed via fastboot. (I did fastboot format system & fastboot -w to be safe).
Click to expand...
Click to collapse
I see. My apologies for not knowing that you do not want Gogole applications on your system. If that is the case, then you would definitely 100% want to use fastboot to flash the ROM. Then, you can just boot it up after doing a factory reset from the stock EMUI recovery. No need to do anything else since you want to avoid GApps. Again, sorry for not reading thoroughly.
Related
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?
Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot
So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565
wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!
if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
If you only want to use TWRP when you have a fastboot-ready PC available, there is no need to install it. The reason why that is there is because since TWRP is embedded in the kernel (not flashed to a recovery partition like older devices), it will be overwritten whenever you flash a custom rom that includes a kernel, and I'm fairly certain they all do.
Returning the stock recovery menu is as easy as flashing the stock boot.img. There are no downsides that I know of of having TWRP on your device. And yes, returning to the stock rom and recovery is as easy as fastboot flashing the factory image.
myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
I dont install it anymore.
I run rooted stock and have no need really for a nand backup.
When I need it I just fastboot it and honestly I cant recall the last time I needed to do that.
On other deivces I have it installed for ease of updates for LineageOS.
My Pixel XL 2 swings both ways! I use TWRP on board and Fastboot!
I run stock rooted with flash kernel. I use my Nexus 6p terminal to fastboot boot TWRP on my Pixel when flash kernel pushes an update. I don't really see any reason to run a custom rom on this device as it runs great as is and there is an app for pretty much any custom rom feature you'd want.
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
UKWZ7 said:
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
Click to expand...
Click to collapse
For aex issue did you flash factory2vendor zip before flashing rom?
You will have to install twrp image using PC. Like the first time you did when you were unlocking bootloader
Flash zui using qfil or miflash.
If bootloader is unlocked still. You can directly flash twrp.
If not first unlock your bootloader and then flash twrp.
For treble rom like aex5.5 you need to flash factory2vendor.zip and then flash twrp with treble support.
For info on flashing and link visit aex5.5 rom page.
Hey guys,
I have recently bought my "Whyred" (4/64 global) and have already unlocked the bootloader.
After switching to Miui 10 global developer rom (with official MiFlash Tool) I wanted to test some custom roms. Therefore I have enabled the developer options, USB-Debugging and OEM Unlock. After this I have booted TWRP 3.2.2.0 with fastboot and flashed the TWRP image to the phone via the booted recovery. Followed by the no-verity-opt-zip (6.0) and Magisk v16.7 to root the phone.
On this basis I went back to the recovery and did a factory reset, followed by an advanced wipe of dalvik, cache, data, system and vendor. Afterwards I have moved the whyred-treble-vendor (zip-file) and the PixelExperience GSI to my phone. First I have flashed the vendor-zip and then switched to image and flashed the GSI as system-image.
And now comes the problem: when I try to reboot to the system it always states "No Os installed". By wiping the cache and data again, I am able to boot to the system, but the phone is stucked on the Mi-Logo
After recovering my phone with the MiFlash Tool (Miui 10 global developer rom), I have tried to flash the GSI in different ways according to a lot of guides I have found in the net, but nothing is working. All methods are leading to the same result: my phone stucks on Mi-Logo
Could anyone of you give me a hint about what I am doing wrong?
Thank you!
Best regards,
nkl
At a guess with wiping system and data. Your also removing changes done by "no-verity-opt-zip (6.0)", and since your still using the MIUI Bootloader the device won't boot the associated GSI.
Maybe try flashing/booting a Treble enabled custom rom, first and then install your GSI. Or avoid the whole Treble thing and just use a custom rom.
You may get more assistance in Treble specific threads/forums.
corkiejp said:
At a guess with wiping system and data. Your also removing changes done by "no-verity-opt-zip (6.0)", and since your still using the MIUI Bootloader the device won't boot the associated GSI.
Maybe try flashing/booting a Treble enabled custom rom, first and then install your GSI. Or avoid the whole Treble thing and just use a custom rom.
You may get more assistance in Treble specific threads/forums.
Click to expand...
Click to collapse
Hey,
Thank you for your quick reaction!
But did I get something wrong? Doing a factory reset and then doing an advanced wipe of dalvik, cache, data, system and vendor is more or less an essential part of all the guides out there?
So you think, I should try to flash for example LineageOS first and then take an approach on the GSI? And which steps should I take? Should I flash no-verity-opt and Magisk under Miui 10 global dev first and then flash custom, i.e. LineageOS? Or should I flash LineageOS first (on a fresh Miui dev rom) and then no-verity-opt and Magisk?
Thanks!
@nkl0806 After installing the GSI while using MIUI as the base you could try flashing no-verity-opt before trying to boot.
no-verity-opt is only required on MIUI based roms (or in your case with a GSI).
Flash a custom rom and boot it. Don't worry about magisk etc.
Then install your GSI and boot it, avoid flashing magisk or gapps.
Once it boots, go back and install magisk and gapps etc and wipe data.
Hopefully then boot and setup your GSI rom.
Also make sure your using a Treble enabled TWRP!
Noob guide to install GSI on whyred
Again look for support in Treble Threads/Forums, I haven't experiment with it, so only going by what I have read.
corkiejp said:
@nkl0806 After installing the GSI while using MIUI as the base you could try flashing no-verity-opt before trying to boot.
no-verity-opt is only required on MIUI based roms (or in your case with a GSI).
Flash a custom rom and boot it. Don't worry about magisk etc.
Then install your GSI and boot it, avoid flashing magisk or gapps.
Once it boots, go back and install magisk and gapps etc and wipe data.
Hopefully then boot and setup your GSI rom.
Also make sure your using a Treble enabled TWRP!
Noob guide to install GSI on whyred
Again look for support in Treble Threads/Forums, I haven't experiment with it, so only going by what I have read.
Click to expand...
Click to collapse
Thank you!
I have also followed this noob guide to flash the GSI, but it did not work out. Maybe I should really skip the Treble stuff and just use the normal custom rom!
I will try to flash the PixelExperience rom and not the GSI - or maybe follow another Guide and flash the Mokee rom first as a base for the GSI.
Thanks again!