Welcome everyone,
Last week I got second hand Asus Tf201. I was disappointed with the stock rom that was installed on it and I decided to do something with that. I have unlocked bootloader, unlocked root, installed twrp recovery and finally installed AndroWook rom. Then I made a full system backup with twrp. After all, I made a decision to install KatKiss. I have read that to do this I need newer recovery than I had before so I installed the newest version of twrp. Then the problem appeared. When I wanted to get into the recovery twrp asked me for password I had never set. I've read loads of many topic on many different forums about it but unfortunately I was unable to connect my Tf201 to PC because of the broken USB cabel. I have opened android terminal and changed the version of twrp to another but the problem didn't dissappear. By mistake I got into recovery and pushed the "wipe data" button, I even didn't know that it will erase all my data with OS from the device. Right now I'm stuck on twrp asking me for password, when I tap on cancel and get into the menu, then into "restore" it says that it's unable to mount external storage, on which I have my backup files. I bought a new USB cabel, PC sees it in adb, but actually I don't have the faintest idea what can I do more with it. I have already tried some different unbrick methods but some of them need nvflash installed, which I don't have. Could anyone please help me with my problem?
Jackobtone said:
Welcome everyone,
Last week I got second hand Asus Tf201. I was disappointed with the stock rom that was installed on it and I decided to do something with that. I have unlocked bootloader, unlocked root, installed twrp recovery and finally installed AndroWook rom. Then I made a full system backup with twrp. After all, I made a decision to install KatKiss. I have read that to do this I need newer recovery than I had before so I installed the newest version of twrp. Then the problem appeared. When I wanted to get into the recovery twrp asked me for password I had never set. I've read loads of many topic on many different forums about it but unfortunately I was unable to connect my Tf201 to PC because of the broken USB cabel. I have opened android terminal and changed the version of twrp to another but the problem didn't dissappear. By mistake I got into recovery and pushed the "wipe data" button, I even didn't know that it will erase all my data with OS from the device. Right now I'm stuck on twrp asking me for password, when I tap on cancel and get into the menu, then into "restore" it says that it's unable to mount external storage, on which I have my backup files. I bought a new USB cabel, PC sees it in adb, but actually I don't have the faintest idea what can I do more with it. I have already tried some different unbrick methods but some of them need nvflash installed, which I don't have. Could anyone please help me with my problem?
Click to expand...
Click to collapse
Give this command a try
Code:
adb reboot-bootloader
Does it boot to the bootloader screen ?
Thx Josh
bootloader tf201
lj50036 said:
Give this command a try
Code:
adb reboot-bootloader
Does it boot to the bootloader screen ?
Thx Josh
Click to expand...
Click to collapse
Yes it did!
okey, OS is installed, and what is more it works properly. Many Thanks to You!
Now I have a little problem. I can`t remove twrp recovery. I have installed rom manager and installed cwm recovery, but when i reboot tablet to recovery menu the twrp starts as it did before.. What now?
Update:
I did everything mentioned in this post http://forum.xda-developers.com/showthread.php?t=2459711&highlight=twrp+mount&page=4 and have restored my backup. All works fine now. Thanks again!
Jackobtone said:
Now I have a little problem. I can`t remove twrp recovery. I have installed rom manager and installed cwm recovery, but when i reboot tablet to recovery menu the twrp starts as it did before.. What now?
Update:
I did everything mentioned in this post http://forum.xda-developers.com/showthread.php?t=2459711&highlight=twrp+mount&page=4 and have restored my backup. All works fine now. Thanks again!
Click to expand...
Click to collapse
Great to see you up and running ...... :good:
Can you add 'SOLVED' to the thread tittle ....
Thx Josh
Related
I rooted my Nook using the method here. I then downloaded Goo Manager though the app store and installed TWRP recovery. If I choose "reboot recovery" in Goo Manager, it will grant SU access and reboot, however it will not boot in to TWRP. it will just reboot the Nook normally. Then I powered down normally and now my Nook won't boot at all! It just shows the splash screen and shuts off or bootloops if i plug it in. What's up?
Edit: I tried doing the root method over again to unbrick it. I could boot in to recovery but the tablet still won't boot after I flash.
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
asawi said:
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
Click to expand...
Click to collapse
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Back when I origianlly did it I did it like I outline in this post (under C): http://forum.xda-developers.com/showthread.php?t=2081981
Nowadays I do it differently though, but that process should still work.
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
alevineman said:
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
Click to expand...
Click to collapse
Where did you get the TWRP to flash and what is fastboot?
Snakebear said:
Where did you get the TWRP to flash and what is fastboot?
Click to expand...
Click to collapse
Fastboot is a tool in the Android SDK that can do a lot, including flashing a recovery.
Steps to use
Make a Ubuntu 13.04 virtual machine
Open Terminal
Put in : "sudo apt-get install android-tools-fastboot"
Install CyanoBoot if not already
When booting Press n in cyanoboot
Choose start fastboot using buttons
Plug into computer and hook up to VM
Download TWRP internal 2.4.3.0 from iamafanof.wordpress.com
Open terminal
Type cd Downloads
Type ls
Look for a file that starts with twrp
Type fastboot flash recovery then type the file name of the twrp file
Done
Snakebear said:
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=40998406&postcount=3.
my nook tablet stopped in read forever.
my nook tablet stopped in read forever.
volume buttons not working
needs twrp recovery
any help?
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Thank you for the reply mate, sorry to hear you are in the same situation more or less.
Further reading over at Stack overflow help forums seems to lead me to believe the tablet is bricked. Loss of su/root privileges means no r/w access via adb to put the required files where they need to be, or install or TRWP.
I'm not giving up on this... well not yet. I have a ton of other work related things going on right now that I need to clear down so I can look into this a bit more seriously. I'm away till the 17th April but will check in here when I can. And, if I find a solution I will post it here.
smirnofred ;0)
smirnofred said:
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Click to expand...
Click to collapse
You need to select fastboot protocol in the menu after booting with pwr/vol buttons. Then install fastboot driver, then install TWRP. From that point the thread you linked will work.
scotia_rfc said:
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Click to expand...
Click to collapse
Doesn't matter if you flash the original recovery, you need to flash the original system. TWRP can do the OTA but it will fail because there are a couple of system files that were changed that fail SHA-1 checks. Don't know what version you are on or if it's a UK or US or Disney/Nick version.
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
smirnofred said:
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
Click to expand...
Click to collapse
Somewhere in that post you linked I put a pretty good procedure for getting a UK Nabi to the latest OS, hopefully you will be up and running in no time.
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
smirnofred said:
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
Click to expand...
Click to collapse
Hi Smirnofred, I have similiar issues to you, and i'm wondering of you can help. The 2.2 file from dropbox is no longer available, have you still got it? and would you kindly upload it somewhere for me if you have time. It would be much appreciated. :good:
James
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!
I just rooted my phone lenovo k4 note using golden twrp and flashed resurrection remix with open gapps. Unfortunately the gapps zip file was corrupted and I wasn't able to fix that.
So I booted my phone to the new os , took the new feeling but later realised the gapps are mandatory.
So I downloaded a new file and tried to go to twrp recovery mode. But I wasn't able to. I thought the bootloader must've locked itself up so I unlocked it again, flashed the twrp recovery IMG file with adb and booted my phone to recovery. But still twrp didn't start.
BUT THEN I SAW THAT I HAD NO INTERNAL STORAGE
Just the SD card
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
ParagTheGre8 said:
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
Click to expand...
Click to collapse
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Andrew_Geo said:
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
Click to expand...
Click to collapse
Settings>Storage just shows the is size that's is roughly around 7gb
It says 7.11gb used of 7.15gb.
It should have been 16gb
I usually have around 10 GB free internal storage
DevALT said:
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Click to expand...
Click to collapse
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
ParagTheGre8 said:
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
Click to expand...
Click to collapse
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
Thanks for the help but I found what was the concern (my problem is not fully solved)
The recovery was very stubborn to just start up.
So I used the official twrp app and flash booted through my phone.
Fortunately it worked.
I wiped everything including internal storage and the storage just showed up in my pc.
I flashed the ROM and Gapps again and the problem got solved.
There just one thing now, the internal storage is there when I go to Settings>Storage but cant access through File Explorer or pc.
The apps got downloaded to the internal storage only so its not much of a problem though.
I am having the same issue.
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
I have a huawei Gr5 KII-L21 / kiwi mobile. Initially there was 16GB internal memory now it is just showing 2GB internal memory. I flashed stock rom yet the problem is there. I tried to flash stock rom in bootloader mode from window command prompt. Is there any method to get bak my internal memory?
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.