Related
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
tpbklake said:
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
Click to expand...
Click to collapse
Tried option 1 and when I go to select install zip from sd card after booting to cwm the phone restarts. Trying option 2 now...
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Kayak83 said:
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Click to expand...
Click to collapse
How did you try to reboot into bootloader from recovery once the ROM was flashed. Once I get into recovery I connect the phone with a USB cable and then type
Adb reboot bootloader
This will boot you into HBOOT straight from recovery and should prevent the hang at the HTC.
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Kayak83 said:
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Click to expand...
Click to collapse
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
Then Fastboot reboot
tpbklake said:
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
The Fastboot reboot
Click to expand...
Click to collapse
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Kayak83 said:
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Click to expand...
Click to collapse
Which version of CWM are ou using. I use CWM 5.0.2 and it works fine.
SUCCESS. Thanks for your help!
Glad you got it goin!
Sent from my ADR6350 using xda premium
Kayak83 said:
SUCCESS. Thanks for your help!
Click to expand...
Click to collapse
Which option did you have success with?
dumb question but...
how do you find the path to your custom recovery?
mza929 said:
dumb question but...
how do you find the path to your custom recovery?
Click to expand...
Click to collapse
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
tpbklake said:
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
Click to expand...
Click to collapse
great thank you... i was thinking i had to use a path to the recovery on my phone's storage not my PC's...
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
mza929 said:
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
Click to expand...
Click to collapse
You should look for and use CWM 5.0.2
Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
mza929 said:
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
Click to expand...
Click to collapse
Yes good job. The last part is the key to getting a custom ROM installed. Glad it worked for you.
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
hackweed said:
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Click to expand...
Click to collapse
After you have an unlocked HBOOT, you need to flash CWM recovery image in FASTBOOT mode. Once you have CWM installed, you can install the latest SU-3.0.xx.zip to root your current ROM and then you can installl and use root programs like ROM Manager, Busybox, Titianium Backup, etc. or you can install a rooted custom ROM.
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.
Hello!
I unlock the bootloader, installed TWRP (several versions) but it doesn't work.
I enter in recovery, select YES in both options, the green android shows up and the phone just boot normally. TWRP options never displayed.
Any help on this? Plz...
Thank you!
Download: https://dl.twrp.me/h815/
1. fastboot boot recovery your_recovery_image.img
2. flash twrp image from booted twrp
Or fastboot flash recovery twrp.img
No ! This doesnt work. Read the official twrp xda thread.
Hi!
I tried all that, flashed all TWRP versions, all available versions of european rom for LG G4 H815, nothibg... the damn thing just don't work on my phone
Have you followed the right steps?
First use fastboot boot twrp.img (boot not flash)
Then within twrp copy the twrp image from your pc by adb or mtp then use the button to flash an image and then choose the copied twrp to flash to recovery
Now I think you got me... I followed the tutorial how to install twrp but, in the beggining I was having problems with the drivers. Win10 was changing them on every command, and after so much time (I went to sleep at 5 AM ) trying everything that it could work, maybe I just mess on that step....
Thanks for your help. As soon as I have time again, I'll check that step.
Thank you very much @steadfasterX !!!
It works
I followed this tutorial: http://www.technobuzz.net/install-twrp-recovery-on-lg-g4/
Thats why I got mistaken... Thanks once again
First use fastboot boot twrp.img (boot not flash)
Then within twrp copy the twrp image from your pc by adb or mtp then use the button to flash an image and then choose the copied twrp to flash to recovery
Click to expand...
Click to collapse
You're welcome
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 !
Hello, on any custom roms we see recovery as img, so whats the ultimate good process to actually flash it?
img to tar bootloop
any other recovery bootloop
only one thats working is "twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5" BUT i have x1s, so pain to flash some rom.
Im currently on beyond rom 3.1, because i cant flash anything else.
Any help here?
Try flashing vbmeta.img after flashing recovery
like download mode -> recovery, then download mode again and only vbmeta?
didnt try that, ill try it right away
edit:
1) download mode -> AP EXYNOS-G98X-LINEAGE-RECOVERY-20200709
2) booted up rom
3) turned off -> download mode -> USERDATA vbmeta.tar from beyond rom
4) bootloop, up button and power same thing
i dont know if i should try stock and then go for root again or what exactly do.. i dont want to lose any data now. It got really complicated, since i go from root apk clockworkmod era.
maybe magisk is the issue? since i have it installed
Go to fastboot
Flash recovery
Flash vbmeta
Reboot
If fastboot doesn't like extensions of your images, change them to .img
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
b30wu1f said:
how can i get to that? on TWRP if i do reboot -> fastboot, im still in TWRP and "fastboot devices" shows completely nothing (not even list of devices or whatever)
when i go to bootloader mode from magisk i just see "entering fastboot mode.." and thats about it, no fastboot commands work
Click to expand...
Click to collapse
Move vbmeta.img to your phone and go to Install section. Install it and reboot.
Also, TWRP offers an option to reboot to bootloader. You can try it too
well, i flashed lineage recovery img and then vbmeta, phone booted up, but got probably original recovery. its really frustrating. Do you have any valid and working "tutorial" to get the recovery working ?
i just need recovery thats x1s, so it should be probably lineage recovery, but cant install it. Im starting to hate these new phones.
I'm sorry, I don't have any specific tutorial, but in general:
adb reboot-fastboot
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot-recovery
If this doesn't work, search for your specific device on XDA. You shouldn't hate new phones, you should hate people who sell them, because they make everything hard so you won't switch from their software, which spies on you.
tried TWRP that works, installed as img lineage-18.1-20210224-recovery-x1s.img and now it suddenly worked. Thank you for help, after 6 hours =)