What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
asad510 said:
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
Click to expand...
Click to collapse
And not a verizon phone
asad510 said:
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
Click to expand...
Click to collapse
On step one. After you wipe system, data, and cache, your wiping the system to your active slot.the one your on. So I would say you would want to switch slots right here. So your new rom goes on clean slot.
In my experience so far after your step 5 you will have to fastboot boot TWRP again, because you just flashed a rom now and it's not signed anymore. So TWRP will not boot. Unless you have April bootloader in that slot, if you have may in both slots you will have to fastboot boot twrp. So far this is what I have had to do. I would like to know if someone has figured out how to flash a rom on may bootloader's without having to use fastboot.
mac796 said:
On step one. After you wipe system, data, and cache, your wiping the system to your active slot.the one your on. So I would say you would want to switch slots right here. So your new rom goes on clean slot.
In my experience so far after your step 5 you will have to fastboot boot TWRP again, because you just flashed a rom now and it's not signed anymore. So TWRP will not boot. Unless you have April bootloader in that slot, if you have may in both slots you will have to fastboot boot twrp. So far this is what I have had to do. I would like to know if someone has figured out how to flash a rom on may bootloader's without having to use fastboot.
Click to expand...
Click to collapse
Mac your right mate. I'm not sure you can do it but what I have noticed is that twrp rc1 is needed for may bootloader
Hi,
Does a thorough guide exist on how to flash custom ROM on this phone?
I have done quite a lot of flashing in my life but can't a ROM flashed for the love of God.
Got TWRP installed, ADB works, cables are good.
Thanks!
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Waancho said:
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Click to expand...
Click to collapse
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
AndroidDevices said:
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
Click to expand...
Click to collapse
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Waancho said:
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Click to expand...
Click to collapse
It does have Magisk installed, it should if its one of the newer builds and all you need to do is install Magisk Manager which in turn activates Magisk
Installing Magisk manager was one of the first things I did, but unfortunately, the latest version A/B Havoc at the aforementioned link did not have Magisk.
There's about 6 or 7 and probably a bunch of YouTube's
Sent from my PH-1 using XDA Labs
Flashing for Dummies
In this guide we'll go over how to flash custom ROMs with root and TWRP in addition to updating
this guide will always be updated
Read the ENTIRE guide before you start
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
things to keep in mind:
1- when you flash a ROM through TWRP, it will flash to your inactive slot, that's why you need to switch slot after flashing it and then flash everything else, think of it like an OTA update except you need to switch active slot yourself
2- when you change your active slot in TWRP, it will only change after you reboot, your active slot will always be the one you're currently booted on
3- the order of flashing anything that modifies boot is
1) TWRP
2) custom kernel
3) noverity
4)Magisk
if you're not sure, flash stock boot of your rom and do it again, flashing TWRP will break Magisk, flashing a custom kernel will break magisk, flashing TWRP after flashing a custom kernel will most likely get you a bootloop
Before you begin
you need to unlock your bootloader first https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
It is no longer required to be on stock Oreo before flashing, but I currently still recommend you do so as there might be some minor bugs on some custom roms, but otherwise everything will work just fine.
get latest platform-tools if you haven't already, using an older one WILL result in errors
platform-tools
extract it and open the folder
hold shift then right click on an empty space then click "open command window here"
if you're on windows 10, doing that will open power shell instead, inside power shell, type "cmd" and press enter, use cmd for everything below
if you're coming from stock, you need to do this first
type the following command (data and files will be wiped)
Code:
fastboot -w
fastboot set_active b
Notes:
Pixel Experience includes Gapps, do not flash them after the rom
many roms include TWRP, such as Havoc, AICP and many others, check ROM thread first, if it includes it then don't flash TWRP.
Flashing custom ROMs and other stuff
download latest TWRP img and zip from https://twrp.me/xiaomi/xiaomimia2.html and place it in the same folder you extracted platform-tools to
NOTE: if you are on stock then use TWRP 3.2.3 img, not 3.3
note: if you're having issues with official TWRP, I've built an unofficial one with F2FS support which you can try here
be careful if you switch to F2FS, it will only work with a recovery that supports it and a ROM that supports it, no stock.
rename the img to twrp.img
in cmd, type
Code:
fastboot boot twrp.img
if you get a bootloop, force shutdown (power + volume down) and try again
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
after you got the files on your phone, it's time to flash
remember that when flashing a ROM, it will flash to your inactive slot, in this guide I'll assume your active slot is B, use "fastboot set_active b" in fastboot if you'd like to follow along
First go to wipe > advanced and select System and Data then wipe, then you can start flashing
1- flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC (ONLY if the ROM doesn't include it already)
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
5- flash Gapps if required by the ROM you're flashing, Opengapps nano is recommended, you can get it here http://Opengapps.org
6- (optional) flash a custom kernel if desired/needed
7- (optional) flash DM-VERITY & FORCEENCRYPT DISABLER zip , this will disable DM verity and encryption in vendor, this is not required by most custom ROMs as they will disable encryption anyway, it is most useful on stock, and in the possibility that the ROM you're flashing does not disable encryption
8- flash Magisk
9- reboot to system
IMPORTANT, if you get an error while flashing ROM zip, do the following
use latest official TWRP, if you're already using it, then the ROM you're flashing is one of the older ROMs
previously, ROMs and TWRP used Jasmine as a codename for our device, while the real codename is Jasmine_sprout, this caused some issues, newer ROMs and TWRP now use the correct codename, but that means new TWRP can not flash older ROMs, and so you will need some simple modifications to the ROM zip:
1- open the ZIP using WinRAR on PC or X-plore on phone
2- go to META-INF/com/android/metadata and open it as text
3- on the last line, edit 'pre-device=jasmine' to 'pre-device=jasmine_sprout'
4- save it and try flashing again
Switching between custom ROMs
follow the same flashing instructions, you can boot directly to TWRP by holding power + volume up, wipe data and system first then flash ROM and the rest.
Updating Custom ROMs
For OFFICIAL ROMs which support A/B OTA it's very easy
1- once you get a notification that an update is available, download and install with the system updater but don't reboot (If the ROM includes TWRP then don't do any of the following steps, just reboot)
2- go to Magisk, Downloads, search for "TWRP A/B Retention Script" and install it
3- on the main Magisk page, click install > install > Install to Inactive Slot (After OTA)
4- once Magisk finishes, reboot, you will now be on the opposite slot with both Magisk and TWRP installed.
for Unofficial ROMs with no OTA or Official ROMs that don't support A/B OTA, you'll need to use TWRP, do not wipe anything:
1- boot to TWRP
2- flash the ROM zip
3- flash TWRP zip (ONLY IF the ROM doesn't include TWRP)
4- switch your active slot (to A if you are on B and to B if you were on A)
5- reboot recovery
6- flash Gapps if required by the ROM you're flashing, Opengapps nano is recommended, you can get it here http://Opengapps.org
7- (optional) flash a custom kernel if desired/needed
8- (optional) flash DM-VERITY & FORCEENCRYPT DISABLER zip , this will disable DM verity and encryption in vendor, this is not required by most custom ROMs as they will disable encryption anyway, it is most useful on stock, and in the possibility that the ROM you're flashing does not disable encryption
9- flash Magisk
10- reboot to system
Very good and very well detailed guide. This guide will be useful to those who are not so familiar with Flashing ROMs especially in our device with partitions.
Thank you for making this, as many users were asking this thing. Keep it up!
does rebooting to twrp gets stuck on twrp logo after flashing twrp zip?
its been an issue on stock or maybe i have been doing to wrong...
after wipe commands and setting active slot b,
i reboot into fastboot boot twrp.img and flash the rom and Im getting mount failed /system
is that normal?
Edit: NVM, it is normal. I successfully flashed Carbon ROM in my device. Thanks for this awesome guide.
This is great thank you. Going to try it once I get bored of stock rom.
@AxL said:
after wipe commands and setting active slot b,
i reboot into fastboot boot twrp.img and flash the rom and Im getting mount failed /system
is that normal?
Edit: NVM, it is normal. I successfully flashed Carbon ROM in my device. Thanks for this awesome guide.
Click to expand...
Click to collapse
Yes it's normal because you wiped system
levai_spencer said:
does rebooting to twrp gets stuck on twrp logo after flashing twrp zip?
its been an issue on stock or maybe i have been doing to wrong...
Click to expand...
Click to collapse
twrp.zip has a bootloop for TWRP when it is flash
Candy_Pineapple said:
twrp.zip has a bootloop for TWRP when it is flash
Click to expand...
Click to collapse
No, if you follow the instructions it works
coming from stock to pE I followed exacty the steps.
then flash CR. Here what Ive done
i-wipe cache,data,system for both partition using twrp
ii- set partition to B in twrp and flash zip
iii- set partition to A in twrp and reboot into bootloop
iv- set partition to B in twrp and reboot successfully
so what partition is my CR now?
which partition should i install gapps,kernel and magisk?
Thanks.
notJimz said:
coming from stock to pE I followed exacty the steps.
then flash CR. Here what Ive done
i-wipe cache,data,system for both partition using twrp
ii- set partition to B in twrp and flash zip
iii- set partition to A in twrp and reboot into bootloop
iv- set partition to B in twrp and reboot successfully
so what partition is my CR now?
which partition should i install gapps,kernel and magisk?
Thanks.
Click to expand...
Click to collapse
It's in B, because you didn't reboot after switching slot initially in twrp, stay in B and boot recovery then flash Gapps and the rest
Nebrassy said:
It's in B, because you didn't reboot after switching slot initially in twrp, stay in B and boot recovery then flash Gapps and the rest
Click to expand...
Click to collapse
You are right. I miss the first bl reboot.
I follow the step back and reboot after switch partition.
Only now i got the concept for A/B flashing. And my os in A now.
Thanks for the guide. Really helpful.
notJimz said:
You are right. I miss the first bl reboot.
I follow the step back and reboot after switch partition.
Only now i got the concept for A/B flashing. And my os in A now.
Thanks for the guide. Really helpful.
Click to expand...
Click to collapse
No prob, keep connected and click the tx button
Matteo (AIO Project Founder)
Hello,
after make adb push file.zip /data/media/0
I receive the next message
adb: error: failed to get feature set: no devices/emulators found
Please advice.
Thanks
Roviva said:
Hello,
after make adb push file.zip /data/media/0
I receive the next message
adb: error: failed to get feature set: no devices/emulators found
Please advice.
Thanks
Click to expand...
Click to collapse
What's the output of adb devices?
Nebrassy said:
What's the output of adb devices?
Click to expand...
Click to collapse
I entered in fastboot mode,:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>.\adb devices
List of devices attached
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>
If I enter the command "adb devices" in normal mode (no fastboot) appear:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
a341410 device
Roviva said:
I entered in fastboot mode,:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>.\adb devices
List of devices attached
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>
Click to expand...
Click to collapse
Adb devices
While in twrp, adb won't work while in fastboot, follow the guide carefully
Nebrassy said:
Adb devices
While in twrp, adb won't work while in fastboot, follow the guide carefully
Click to expand...
Click to collapse
Hello,
In your guide I dont understand the next part:
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
If I made the step 1 above: I enter in the TWRP, select wipe, then, select wipe, advance wipe, select data and then swipe to wipe. After this reboot system, the telephone start but in normal mode, like restored.
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
I follow the step 2, in data/media appear a folder TWRP then i dont created a folder called 0
Then I go to advanced >> adb sideload and in the pc i wrote "adb sideload twrp.zip.
You write file.zip, I dont understand what is this file?
I dont understand what do you mean in the step 3: "try using PBRP for MTP, then go back to TWRP PBRP"
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
Roviva said:
Hello,
In your guide I dont understand the next part:
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
I follow the step 2, in data/media appear a folder TWRP then i dont created a folder called 0
Then I go to advanced >> adb sideload and in the pc i wrote "adb sideload twrp.zip.
You write file.zip, I dont understand what is this file?
I dont understand what do you mean in the step 3: "try using PBRP for MTP, then go back to TWRP PBRP"
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
Click to expand...
Click to collapse
File.zip, as in the file you want to copy, you change that to the name of the file you want to copy
PBRP is another recovery, you can try booting it if twrp doesn't work to copy
Nebrassy said:
File.zip, as in the file you want to copy, you change that to the name of the file you want to copy
PBRP is another recovery, you can try booting it if twrp doesn't work to copy
Click to expand...
Click to collapse
hello,
I dont know how to follow:
flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
I wiped data and storage then I press back.
I flashed the PBRP that I pushed to data/media/TWRP
After flash I returned to the menu of PBRP
I switched to A
When I reboot, a warning message that "NO OS SYSTEM IS INSTALLED" appear.
I reboot to recovery but after this, the telephone does not restart. the screen "androidone" appear and dont advance...
How can I install the PBRP and magisk?
I succesfull push the files to the telephone but when flash the PBRP I cannot follow......
Roviva said:
hello,
I dont know how to follow:
flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
I wiped data and storage then I press back.
I flashed the PBRP that I pushed to data/media/TWRP
After flash I returned to the menu of PBRP
I switched to A
When I reboot, a warning message that "NO OS SYSTEM IS INSTALLED" appear.
I reboot to recovery but after this, the telephone does not restart. the screen "androidone" appear and dont advance...
How can I install the PBRP and magisk?
I succesfull push the files to the telephone but when flash the PBRP I cannot follow......
Click to expand...
Click to collapse
You didn't flash a rom, obviously it won't boot
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
You made sure you have latest OOS11 on BOTH slots?
xtcislove said:
You made sure you have latest OOS11 on BOTH slots?
Click to expand...
Click to collapse
Thanks for the response! How do i check that? Both slots of what?
Infraviored said:
Thanks for the response! How do i check that? Both slots of what?
Click to expand...
Click to collapse
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Infraviored said:
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
Click to expand...
Click to collapse
U don't need the command fastboot reboot recovery. U can just use the volume buttons to select recovery and press power button to boot to recovery
Nimueh said:
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Click to expand...
Click to collapse
Another way to set your phone up for a custom rom can be found here. https://wiki.lineageos.org/devices/instantnoodlep/install
Just make sure your booting from a good 00S11 install when you do this.
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
king_xerxes said:
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
Click to expand...
Click to collapse
Sorted it out by this. Thank you!