Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.
If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.
thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:
Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.
Related
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
you didnt search very well...
there's a return to stock thread in the general section.
Just use this: http://forum.xda-developers.com/showthread.php?t=1766475
Read last 3-4 pages.
AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
search again... and in short if u are flashing your rom with stock image u dont have to install the bootloader and radio img again... search how to flash stock image using adb..
Sent from my Galaxy Nexus using xda premium
AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
Hi, let me try to help you
Galaxy Nexus is my first smartphone. So i'm pretty new at flashing things. I did some research last year to learn how to flash stuff in it and that's how i learned to make a fresh install:
-Make sure you have the SDK platform-tools and the Galaxy Nexus driver properly installed on your PC. Also, make sure you have USB debuging enabled on your device.
-Download the factory image that fits your phone at https://developers.google.com/android/nexus/images
-Open up the tgz file you just downloaded and extract the files:
-boot.img
-bootloader-maguro-primemd04.img
-radio-maguro-i9250xxlj1.img
-recovery.img
-system.img
-userdata.img
Extract the files in the platform-tools folder to make things easier.
-Connect your Nexus to your PC, open the command prompt, go to the platform-tools folder and type
(Do not turn off, disconnect or close the cmd prompt windows until everything is done. Again, make sure you have the nexus driver properly installed on your Windows)
Code:
adb reboot-bootloader
(this command will reboot your device to recovery mode)
With your device on recovery mode, type the following commands to erase your device:
Code:
fastboot erase boot
Hit enter, then:
fastboot erase cache
Hit enter, then:
fastboot erase recovery
Hit enter, then:
fastboot erase system
Hit enter, then:
fastboot erase userdata
-Now you're going to flash the new files you have downloaded and extracted steps before:
Code:
fastboot flash bootloader bootloader-maguro-primemd04.img
(or whatever name your bootloader img file has. In this case the bootloader file is "bootloader-maguro-primemd04.img")
Code:
fastboot reboot-bootloader
(you'll need to reboot after flashing the bootloader)
Code:
fastboot flash radio radio-maguro-i9250xxlj1.img
Flash the radio
Code:
fastboot reboot-bootloader
Reboot again
Code:
fastboot flash system system.img
Flash system
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
We are almost done!
Code:
fastboot erase cache
Code:
fastboot reboot
Done! Reboot to Android. The first boot may take some more time than the usual. Don't worry!
-
If you want to flash a custom recovery, download it from their website, go into fastboot mode and flash it using the command to flash the recovery.
Code:
fastboot flash recovery [recovery filename].img
The same command used when flashing the recovery on the fresh install above
That's the way i learned how to do it from scratch. In case someone more experienced has any thoughts about it, i'd like to hear as i'm not an expert and learned by researching it on my own...
This is how it's done, PROPER. Well done, mnoguti.
a maguro wrote this.
@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?
AbhishekS said:
@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?
Click to expand...
Click to collapse
you don't have to go into the recovery mode to flash recovery, just boot into fastboot mode and flash recovery using command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
obviously replace the recovery.img with the name of the custom recovery file you downloaded, make sure the custom recovery file is in the same folder as fastboot/adb otherwise you'll have to do it like:
fastboot flash recovery C:\Downloads\recovery.img
Click to expand...
Click to collapse
Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.
Obviously he meant fastboot mode..
a manta wrote this.
AbhishekS said:
Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.
Click to expand...
Click to collapse
It's "fastboot mode". Sorry for the mistake!
I've updated my post and now it's right
Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
I've been following this guide:
https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591
to try and root my Pixel C. I was initially following a different guide, but I believe I now have:
bootloader-dragon-google_smaug.7900.50.0.img and TWRP_dragon_3.1.0-2.img, loaded through fastboot
I was then able to push
Update.ZIP_PixelC_Ryu_system-vendor-boot_OPP1.zip and SuperSU-v2.79-201612051815.zip to /sdcard/ via adb in TWRP. I then tried to install both, as per the guide.
I was a bit confused when the "flashing system.img... this will take some time" part took no time at all, but it had taken a while to get to that point so I figured maybe the messages were in the wrong order or something. Both said they were successful.
Tried booting to system - just came back to TWRP.
So I thought I'd try to flash the system image back on. But I can't push any files now. Everytime I try, it creates the files then fails and I start getting read-only file system errors
If I try to install update.zip again (the one above), I now get "failed to mount '/data-full' (Device or resource busy)"
So I'm quite stuck at this point. Can't revert to stock image, can't install the new image... any help would be much appreciated!
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
peter73 said:
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
Click to expand...
Click to collapse
I second this ^ except for the fastboot boot twrp.img part. Why do you do that? The first line should be enough.
Hi guys,
I've just updated to newest OOS firmware wich is 5.1.2 and I'm facing a weird problem.
Every time I flash codeworks TWRP and reboot to system, the next time i try to boot to recovery it boots to the original recovery.
It's like when I flash TWRP it doesn't remain persistent. When i flash it through fastboot and straightly boot from fastboot to recoverry I succeed to get in TWRP but as soon as I reboot to system and try to boot to recovery I reach the original OnePlus recovery.
Is anyone facing the same problem ?
And also do you have any idea about what i could do to solve this problem ?
Thanks in advance for your answers !
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Adnan008 said:
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Click to expand...
Click to collapse
Indeed, I just needed to flash magisk to get it persistent. I'll try blu spark's one as you suggested.
Thank you very much for your answer !
Cheers !
Nothing to do with recoveries or kernel. After you do the fastboot flash recovery TWRP in fastboot, do this: "fastboot boot TWRP". I believe that's the right command. Basically after you flash it, manually boot to recovery through fastboot one time. After that it'll work from inside the phone or with the button combination with the phone off.
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
pinnekeshaar said:
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
Click to expand...
Click to collapse
Actually not that lazy because I used to do what you mentionned.
The thing is that a flash of Magik is needed to patch twrp. That's the step I forgot in the procedure and explained here.
So before being unpleasant, please know what you're talking about...
Cheers !
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Aserar said:
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Click to expand...
Click to collapse
What is the code name of your device?
NOSS8 said:
What is the code name of your device?
Click to expand...
Click to collapse
Its alioth poco f3
Aserar said:
Its alioth poco f3
Click to expand...
Click to collapse
Seems that in official no TWRP A13
https://androidfilehost.com/?w=files&flid=322193
Here boot version A12(more recent).
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v5.6_A12
https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4272625/
Aserar said:
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Click to expand...
Click to collapse
It is because flashing rom also flash the recovery packed along with the rom, and it will replace your old recovery. To prevent it you need to also tick on the reflash ofox option when you flash a rom, which is too late in your case.
So, if you want to reflash ofox recovery, download and extract the zip file, locate the recovery.img in the extracted folder, reboot to bootloader and issue this command:
Code:
fastboot boot /path/to/recovery.img
then reboot to recovery with the command:
Code:
fastboot reboot recovery
and your device will temporarily boot into ofox recovery
The last step is to flash the recovery to ramdisk to make it permanently, you can find this option in ofox settings.
NOSS8 said:
Seems that in official no TWRP A13
https://androidfilehost.com/?w=files&flid=322193
Here boot version A12(more recent).
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v5.6_A12
https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4272625/
Click to expand...
Click to collapse
This is what I did befor posting but but TWRP wouldnt boot through fastboot. it just gives me blackscreen for a few seconds then it boots to system. but the problem was solved with ofx. thank you for your help
disconmair said:
It is because flashing rom also flash the recovery packed along with the rom, and it will replace your old recovery. To prevent it you need to also tick on the reflash ofox option when you flash a rom, which is too late in your case.
So, if you want to reflash ofox recovery, download and extract the zip file, locate the recovery.img in the extracted folder, reboot to bootloader and issue this command:
Code:
fastboot boot /path/to/recovery.img
then reboot to recovery with the command:
Code:
fastboot reboot recovery
and your device will temporarily boot into ofox recovery
The last step is to flash the recovery to ramdisk to make it permanently, you can find this option in ofox settings.
Click to expand...
Click to collapse
Thank you mf this worked! Booting twrp through fastbood just gave me black screen so I didnt think that booting Ofox would be any different but it actually booted Ofox recovery and I flashed it no problem. If anyone's going to attempt this make sure to backup your data before cause you'll need to format data