Nokia x6.1 bootloops to twrp. - Nokia 6.1 Plus (X6) Questions & Answers

So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: 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.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.

Related

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

Can't flash ROM's or use USB to ADB to flash/restore original Android OS.

HI all,
I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.
Here's the situation.
I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.
I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.
I did a nandroid backup before I did this, knowing something might go wrong.
I think my camera wasn't working so I tried a nandroid recovery to get it back.
Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.
Anyway after that I can only get to TWRP.
I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.
I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.
I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.
I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.
Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.
Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.

Download Mode Recovery on H918

After installing twrp using the one click root method, it restarted my V20 and I ended up in recovery mode (TWRP) and unable to boot into the OS. It seems I only have access to fastboot, download mode, and TWRP at this moment. I tried flashing the partitions with twrp, but twrp isn't realing my SD card for some odd reason, and I don't believe theres another way to move the file directly to the phone. I've been trying to work with "LG FlashTool" for hours, and keep getting the same error. Is there a reliable way to flash the OS through download mode? Thanks!
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
slayerh4x said:
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
Click to expand...
Click to collapse
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
KingofPineCones said:
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
Click to expand...
Click to collapse
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
crazyc78 said:
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
Click to expand...
Click to collapse
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
Thanks I appreciate the response, I was able to get my phone up and running by flashing a deodexed rom.
What are the commands to flash the stock system, boot image and recovery through fastboot? Is that what you used?
KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
andrewjt19 said:
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
Click to expand...
Click to collapse
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
DarkestSpawn said:
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
Click to expand...
Click to collapse
I'm running the latest version of TWRP not the RC8.
andrewjt19 said:
I'm running the latest version of TWRP not the RC8.
Click to expand...
Click to collapse
ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!!
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.
Will definitely give a shot. Thanks. I'll report back when I get to do it...
what are commands to flash the sys files

Upgrading from Build N4F26J (7.1.1) to OPR6.170623.017 (8.0.0). Bricked?

Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
You don't flash a factory image in TWRP. Unzip the file and flash the individual images: boot, system, and vendor. Try that method or use ADB sideload to install the full OTA image. Full OTA images can be downloaded from the same site.
Sent from my Nexus 5X using Tapatalk
I'm assuming you have ADB / fastboot in place (if not, google it): unzip your factory image to a given folder. Navigate to this folder using prompt / terminal. Turn on your phone with vol down pressed and leave it at that screen. Plug it onto your computer and type fastboot devices - you should see a line with a bunch of numbers. If Windows, run flash-all.bat. If Mac / Linux, run flash-all.sh. Your phone should get back to life in a few, sit back and relax.
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
wizardwiz said:
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
Click to expand...
Click to collapse
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
ultyrunner said:
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
Click to expand...
Click to collapse
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked.
I wasn't talking about using a manual fastboot option to flash an indevidual image.
wizardwiz said:
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked. I wasn't talking about using a manual fastboot option to flash an indevidual image.
Click to expand...
Click to collapse
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
ultyrunner said:
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
Click to expand...
Click to collapse
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
wizardwiz said:
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
Click to expand...
Click to collapse
No we're not in competition. My point was you gave him one option with the least control and not remotely the best option to get his device up and running, particularly making an assumption he has a locked bootloader, when you never asked. If he is able to use a command line to run a flash command, then pointing him to the guide is the best bet. If something goes wrong with flash-all scripts then he's probably going to be really lost.

One Plus 8 Pro features (Wifi / Camera) stopped working after root

I rooted my OP8-Pro. I followed the instructions in this video:
https://www.youtube.com/watch?v=UVABAEGRgew.
To summarize, his steps were as follows:
1. Unlock the bootloader
2. Extract boot.img file from payload bin file (on Windows)
3. Install Magisk Canary 2020 app on the phone
4. Install the boot.img file through Magisk
5. Download Fastboot.zip in Windows and extract files
6. Download and place magisk.patched file in Fastboot folder
7. Connect the phone to Windows, use cmd to boot into bootloader
8. Flash the magisk.patched file on the device and reboot
This is a new method to me. In the past rooting always involved TWRP. Root checker shows that the phone is rooted but other features have stopped working.
WiFi no longer works. Even if I turn it on, it turns itself off. Camera keeps crashing and I can't even change the camera mode once I launch the app. My phone also rebooted itself a couple of times while I was testing it after root.
I also rooted my One Plus 6 in 2019 but had to use a custom TWRP (Bluspark) for it to be stable.
I rather start over with a factory reset than try to repair the device in it's current state (but will try to repair it if it's easier). I prefer to stick with the factory ROM and only need root for one app.
Try latest stable magisk instead of canary. Mine works perfectly with regular magisk
I used the all in one tool by mauronafrio here. Worked flawlessly.
shagexpert said:
I rooted my OP8-Pro. I followed the instructions in this video:
https://www.youtube.com/watch?v=UVABAEGRgew.
To summarize, his steps were as follows:
1. Unlock the bootloader
2. Extract boot.img file from payload bin file (on Windows)
3. Install Magisk Canary 2020 app on the phone
4. Install the boot.img file through Magisk
5. Download Fastboot.zip in Windows and extract files
6. Download and place magisk.patched file in Fastboot folder
7. Connect the phone to Windows, use cmd to boot into bootloader
8. Flash the magisk.patched file on the device and reboot
This is a new method to me. In the past rooting always involved TWRP. Root checker shows that the phone is rooted but other features have stopped working.
WiFi no longer works. Even if I turn it on, it turns itself off. Camera keeps crashing and I can't even change the camera mode once I launch the app. My phone also rebooted itself a couple of times while I was testing it after root.
I also rooted my One Plus 6 in 2019 but had to use a custom TWRP (Bluspark) for it to be stable.
I rather start over with a factory reset than try to repair the device in it's current state (but will try to repair it if it's easier). I prefer to stick with the factory ROM and only need root for one app.
Click to expand...
Click to collapse
I used the all in one tool by mauronafrio here. Worked flawlessly.
Click to expand...
Click to collapse
So I tried that tool. I tried to flash factory image downloaded directly from One Plus website and kept getting the following error message:
"Error: flash-all.exe or flash-all.bat or flash_all.bat or flashall.bat not found!!!"
I think this has to do with the fact that I am using a secondary hard drive on my computer to store all the downloaded files and the bat file is supposed to be in the same folder as the zip file.
I also reset it to factory settings from the recovery mode but that didn't fix the WiFi issue.
Then I ran TWRP from the All in one Tool and installed the factory firmware from phone's internal memory. This soft bricked my phone.
After getting soft-bricked I installed Magisk through the tool but that didn't fix the issue.
Now it is stuck in a boot loop and keeps going into recovery mode. I can also boot into Fastboot mode and install zips through there but I would like to unbrick it first. Is there an alternative ROM that can unbrick it?
I think I am going to try and use the unbrick tool first and if that doesn't work I will try the Fastboot ROM, that already comes with the bat file.
I am a little confused as to which version goes on my phone though. They have Indian, Global and European versions but I live in the U.S. Global seems to be the most appropriate for my phone but I don't want to install the wrong ROM on it.
I remember reading that you can run into WiFi issues if you flashed the wrong version (from a different region) for your phone
I've rooted for many years and this is the first time I didn't go through TWRP as well.
If you use the unbrick tool you'll probably get issues with the fingerprint reader. But that's fixable, after you've rooted.
The easiest way to get root is to just unlock the bootloader, fastboot boot twrp (not flash), and then flash magisk 20.4 stable.
Before TWRP you had to patch the boot.img and fastboot flash it, but with twrp there is no need for it.
If you use the unbrick tool you'll probably get issues with the fingerprint reader. But that's fixable, after you've rooted.
The easiest way to get root is to just unlock the bootloader, fastboot boot twrp (not flash), and then flash magisk 20.4 stable.
Before TWRP you had to patch the boot.img and fastboot flash it, but with twrp there is no need for it.]
Click to expand...
Click to collapse
Thanks for letting me know. I attempted to use the unbrick tool but it had problems connecting to the phone. And I also didn't want to run into finger print issues.
I downloaded the patched Rom (with flash-all.bat file included) and installed it via All in one tool. That unbricked the phone and I reset the system to start from scratch. I used the global / international version for my North American phone.
After setting up the phone, I rebooted into Fastboot and loaded TWRP via All in one tool and installed Magisk 20.4 and got the phone rooted.
Root checker shows the phone is now rooted. WiFi and camera also work. I am ready to transfer data from the old phone.
This would have gone smoother if I had just used the correct version of Magisk from the start.

Categories

Resources