I unlocked the device bootloader thanks to Narender, and tried to flash Lineage OS 18.1. After flashing the ROM and vendor zip files, I switched the current slot and restarted to fastboot mode. Then I flashed the vbmeta image. Then I rebooted to recovery to check the current slot. Slot was as expected, so I rebooted the system.
Then, TWRP gave me an alert saying "No OS is installed" before rebooting. I was unsure what was the reason for it because the ROM was just installed, so I rebooted the system.
After that, device went straight into fastboot mode after "Android One" screen. No matter which option I choose from there, it keeps restarting the bootloader. I tried using "fastboot reboot recovery" but that did not work either. Then I tried to change the active slot of the device using fastboot commands. That did not help either.
Now I'm stuck with a Nokia 7.2 that can only be turned off or start in fastboot mode. Is it bricked beyond saving? I just want to install TWRP in any of the slots and install any usable ROM. Any help is deeply appreciated.
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Chevindu said:
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Click to expand...
Click to collapse
Follow this and DM if you have doubts
Edit: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
Follow this and DM if you have doubts
Click to expand...
Click to collapse
I actually installed few ROMs after my previous reply. But none of them had working WiFi, which is a deal breaker. Went back to stock ROM.
If you are interested I could help you
Ujwal2000 said:
If you are interested I could help you
Click to expand...
Click to collapse
Hey, thanks. But I thought it's not possible due how the signatures in security patches work. So I gave up. Maybe I misunderstood. Linking to Raghu's reply below.
Post in thread '[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |'
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Ujwal2000 said:
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Click to expand...
Click to collapse
Yup, pretty much what I experienced too.
I haven't tried extracting boot image and flashing it manually. At this point to be honest, I'm reluctant to put my hands on it again without having a clear step-by-step guide about it.
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I realize I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I relaise I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Click to expand...
Click to collapse
Thanks Ujwal, appreciate it. I'll have a look.
Related
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Go to fastboot and boot into stock recovery, don't install. Just boot to recovery, command should be something like below.
fastboot boot recovery-name.img
If you can go to opx recovery, flash stock rom and see
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Have you tried going through the steps for unlocking bootloader again?
Exodusche said:
Have you tried going through the steps for unlocking bootloader again?
Click to expand...
Click to collapse
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
tech_master said:
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
Click to expand...
Click to collapse
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
Ah no. You'll probably need to find someone who can re-sign CM so that it'll flash.
Thanks for the answer, I have no idea how to do this, how is this done? I don't seem to find much info online...
Sent from my HUAWEI TAG-L21 using Tapatalk
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
yuv93 said:
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
Click to expand...
Click to collapse
Thank you. I had tried this procedure previosuly, and didn't work. This time, since you insisted, I tried again, on another computer, and the phone was correctly detected, drivers installed and factory image installed on phone. I am happy again
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
Pixel 3:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/
Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/
Reserved.
You are the man! Cant believe we have TWRP this early! Just in time for the next OTA!
Thank you for this! Great work, it feels like an early Christmas!
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Thanks you!
Is anyone having the touchscreen not work after a reboot?
Archangel said:
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Click to expand...
Click to collapse
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
On the Pixel 2 XL touch was broken unless you used a custom kernel. I guess it's the same on 3. If you boot TWRP using fastboot it should allow touchscreen.
You would think after buying the Pixel 1, 2 and 3 I would have this whole A/B slot thing down pat but I dont LOL. That did the same thing for me too. I just rebooted into recovery and flashed TWRP again and it has been fine since. I think sometimes it switches slots and that causes the bootloop. I messed around with changing slots and I think I am on slot A and all if fine for me.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
I had that happen I think once and I just rebooted back into TWRP and it was fine.
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
ktdt00 said:
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
Click to expand...
Click to collapse
No, only the current slot needs to be rooted.
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Is root
To Pixel 3 owners that succesfully rooted, can you share the build.prop here? /system/build.prop
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Carmenlove said:
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Click to expand...
Click to collapse
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
jsauder2 said:
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks! I will give it a try this morning after some coffee. I learned a cool trick last night to get my hotspot to work un-rooted, so I am less desperate than I was last night.
Carm
freebordjunky said:
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Click to expand...
Click to collapse
Just enter your PIN at the TWRP prompt and it will work.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
I have a similar problem. After installing twrp, I can boot to the OS, but Magisk isn't installed and I don't have root. After going back to Twrp and flashing the magisk zip, i can't get past the bootloader screen with a error saying something about failed to load boot.img.
Re-fastboot flashing the patched boot img to both slots brings me back to a rooted state with all magisk modules loaded and applied, but no more twrp. I technically don't need twrp for anything except for nandroid backups, but I guess i could just backup using the adb backup commands and get similar results, right?
Either way, I'm open to suggestions for how to get twrp and magisk working at the same time.
The device is a Xiaomi Redmi Note 4 (codename: mido)(4/64 GB variant)
So I had this problem yesterday where I was stuck in a bootloop and was unable to get into recovery, so I asked for help in a few subs and XDA, and some good people suggested various suggestions. What worked for me was going back to stock by flashing a stock fastboot ROM via MiFlash Tool.
After getting back to stock, I tried installing TWRP recovery again and everything went smooth, except the fact that it did not get installed at all and I am still on the default Mi-recovery. I have tried numerous versions of the TWRP image, double checked whether USB debugging is switched on or not, but I still can't seem to install TWRP.
Here's a video of the entire process I followed to install TWRP and the issue I am facing:
Apologies for the long video. It is difficult to hold a film with one hand while trying to do stuff on the PC with the other.
Any help is greatly appreciated. Thank you.
laneofmagic said:
The device is a Xiaomi Redmi Note 4 (codename: mido)(4/64 GB variant)
So I had this problem yesterday where I was stuck in a bootloop and was unable to get into recovery, so I asked for help in a few subs and XDA, and some good people suggested various suggestions. What worked for me was going back to stock by flashing a stock fastboot ROM via MiFlash Tool.
After getting back to stock, I tried installing TWRP recovery again and everything went smooth, except the fact that it did not get installed at all and I am still on the default Mi-recovery. I have tried numerous versions of the TWRP image, double checked whether USB debugging is switched on or not, but I still can't seem to install TWRP.
Here's a video of the entire process I followed to install TWRP and the issue I am facing:
Apologies for the long video. It is difficult to hold a film with one hand while trying to do stuff on the PC with the other.
Any help is greatly appreciated. Thank you.
Click to expand...
Click to collapse
First, I noticed that your TWRP version is old. You said you have tried different versions, but are you sure you tried the latest one? You can download it from here: Download TWRP for mido
Alternatively, you can try with OrangeFox recovery, which is well-recognized as well and personally I use this one: Xiaomi Redmi Note 4 (mido) build releases | OrangeFox Recovery Downloads
Anyway, after the command...
fastboot flash recovery recovery.img
...try this one:
fastboot boot recovery.img
If doesn't work try...
fastboot reboot
..and right after you push Enter button, hold Power and Volume+ buttons.
When you enter the TWRP/OrangeFox finally, you should wipe stock system and format data partition, then flash your custom rom.
Lord Sithek said:
First, I noticed that your TWRP version is old. You said you have tried different versions, but are you sure you tried the latest one? You can download it from here: Download TWRP for mido
Alternatively, you can try with OrangeFox recovery, which is well-recognized as well and personally I use this one: Xiaomi Redmi Note 4 (mido) build releases | OrangeFox Recovery Downloads
Anyway, after the command...
fastboot flash recovery recovery.img
...try this one:
fastboot boot recovery.img
If doesn't work try...
fastboot reboot
..and right after you push Enter button, hold Power and Volume+ buttons.
When you enter the TWRP/OrangeFox finally, you should wipe stock system and format data partition, then flash your custom rom.
Click to expand...
Click to collapse
That worked.
I just realized you are the same person who helped me on reddit as well. Thanks mate, you're awesome.
laneofmagic said:
That worked.
I just realized you are the same person who helped me on reddit as well. Thanks mate, you're awesome.
Click to expand...
Click to collapse
You're welcome, I like to help people if I am able to Enjoy!
So I just rooted my pixel 6 using the correct original img from google and Magisk. This worked great and I got root access (active boot partition was a if it’s somehow relevant). Now I wanted to use all the functions of nethunter (which I downloaded and installed from nethunter store or something like that), so I wanted to install the nethunter Kernel for my device. Pixel 6 is not officialy supported by kali or not leaked yet so I found pre build nethunter kernel for pixel 6 on xda developers.: https://forum.xda-developers.com/t/...o-oriole-raven-kernel-kali-nethunter.4461589/
So I went in to the mega folder and into the mad-kali-maxhunter-kernel folder. Then into the p6_p6pro folder. Then I just downloaded the maxhunter zip thing for oriole because it stands for p6 ig. Then I flashed this zip file using the Franco kernel manager as recommended in the thread. My device restart and didn’t start up again. So I just tried getting in fast boot and I got it. Now I thought i would just flash the patched magisk img I made for rooting the device previousl. So I did that using fastboot flash boot and so on. Next my device was in an bootloop still, so then I flashed the very original google official img for the device. Still boot loop, so then I wanted to do recovery from fastboot on the phone when I started factory reset mode the phone was just stuck in the google logo. Then I wiped all data using the fast boot tools from my computer. It wiped it but said stuff like the file system is not formatted or not the right format or so but still wiped the data. Still boot loop. So now I switched the active boot partition from a to b. This time the phone said like waiting for command and so on. So I watched a tutorial and got further, now I was able to get to the factory reset mode did. a reset and started. Nothing realy happened and it jumped back to fastboot mode. I thought maybe because in boot b is no img to boot. So I flashed the official google img again but on b. Still bootloop. Now I have a problem. Pls help me.
You should consider trying Google's official Android Flash Tool, it might succeed where your manual flashing failed -- especially considering it was set up by Google and might have better/further checks and such...
Yes, I would recommend Android Flash Tool also. Its helped me a couple times to recover when I couldn't boot. It gives you options for boot.img right before flashing your phone so everything you'll need should be there
@simplepinoi177 i would really like to use it but its using adb and adb is not passible only fastboot so my device isnt available. EDIT: Nvermind i didnt read correctly.
Thank y'all so much it worked!!!
Great. Android Flash tool ftw again