Recovery Mode Stuck On One+ Logo... - OnePlus X Q&A, Help & Troubleshooting

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...

Related

Flashed wrong rom - How screwed am I?

Here is what went down--
I installed TWRP - the official one, everything up to this step went great. Then I flashed a rom for Huawei Ascend Mate 1, not 2, by mistake.
Don't flame me for this plz, I feel bad enough already. Anyways, the phone is now stuck in a boot loop and there is no way for me to open up TWRP anymore. Is there any way I can salvage this phone yet?
Maybe try to fast boot and flash a stock .img. I think volume down +power is for fastboot, it is opposite volume+power for recovery.
Don't give up yet
Misleadingg said:
Here is what went down--
I installed TWRP - the official one, everything up to this step went great. Then I flashed a rom for Huawei Ascend Mate 1, not 2, by mistake.
Don't flame me for this plz, I feel bad enough already. Anyways, the phone is now stuck in a boot loop and there is no way for me to open up TWRP anymore. Is there any way I can salvage this phone yet?
Click to expand...
Click to collapse
Hi there,
Try to Fastboot and install TWRP recovery img again . When in TWRP wipe EVERYTHING but ext-sd!
After that (as I learned from experience) all is possible.
Here is what I had to do with my MT2-L05:
Installed original recovery.img via Fastboot,
auto updated (already had b607 update files in ext sd),
reinstalled TWRP via Fastboot and after asking me if I wanted to, twrp installed su for me!
Back in the game with b607 - rooted!
Had a problem with busybox because system was still locked,
installed in xbin with Stericson.zip via twrp and that did it.
Hope that's helping!

[Q] Unable to boot on TWRP

My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac

TWRP + CM13 Error 7 ?

Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!

[SOLVED]HELP! can't get TWRP to boot up on Z7 (NX506j)

Problem seems to be solved. it just did work magically. idk how and why but it works and boots up after some time.
as mentioned in the title, i cant get any twrp recovery to boot up.
i got my phone yesterday and succeeded updating it to the latest official version (V3.88 which is android 5.1.1 with nubia ui 4.0)
now i want to get a custom recovery
problem here is, i tried several versions that i found here and everyone doesn't boot up (just stays at the nubia logo)
i tried to flash it via fastboot of course. it gets flashed (command prompt returns "OKAY")
in fact everytime i reboot to android the recovery gets replaced automatically by the original one (at least thats how i think it happens). that means if i try to enter the recovery after i rebooted to android, the old original nubia recovery got restored.
am i missing a step or am i doing something wrong?
pls help
thanks in advance
where did you get v3.88 file?
not_noober_than_me... said:
where did you get v3.88 file?
Click to expand...
Click to collapse
From the official nubia site

Nokia 7.2 stuck in fastboot mode and cannot install TWRP

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.

Categories

Resources