Hello, i have tried to update to the latest crdroid "april 23" zip and it has made my phone unbootable. After i have finished flashing rom and recovery flasher, i have not been able to decrypt my phone after the reboot to recovery to try and install gapps and magisk. I've also tried to boot to the rom and it has only showed a black screen, and after that it reboot to recovery. The decryption message has appeared again when i did that and after i decrypted and flashed the other stuff i have not been successful to boot to the rom. I have then once again tried wiping and flashing rom and recovery and reboot to recovery again, and again the decryption promt did not appear. After that i've tried booting to system once again and it appeared and after flasshing the stuff again it still has not booted. I've tried downgrading to the previous version when i wiped instead of the newest one and reboot to recovery again and then it didnt show the prompt. I tried rebooting to system again to get the prompt to decrypt but now it doesn't appear even then. I've also tried using the command "twrp decrypt (my pin)" and it gave me an error. I am now in school and cannot do anything untill i get home but even then my computer monitor has been hit and now doesnt function so i cant even do anything via ADB. I have another computer and monitor and im thinking about using it instead. Can i get a step by step on how i can get my phone to boot once again? Even if i lose all my data im fine with it but i prefer not to since i have alot of pictures that i really wanna keep. All help is appreciated. Now that i cant boot to the rom i cant use telegram on the web either so im completely ****ed. Cheers!
An update .zip is always installed to the inactive slot. Start TWRP and open the reboot menu. Change the slot back to your running system. From there you can try to find the reason why your update fails. You don't need a decrypted TWRP for this.
You can also change the boot slot via fastboot command
Code:
fastboot --set-active=a (slot a)
fastboot --set-active=b (slot b)
-or short-
fastboot -aa (slot a)
fastboot -ab (slot b)
Related
I reset my Oneplus one and installed the COS13.1 update.... But now after installing I'm not able to flash twrp through fastboot... Even tho it shows successful on the PC, it wing boot into TWRP
Go to the developer options (tapping on the build number first ofcourse) and then go to the option: "update Cyanogen-recovery". set it to off.
I think that should do it. Haven't installed the update yet, but there is an option like that in the normal CM-13.
edit:
If that doesn't work you can try to flash it through flashify (requires root). If that still doesn't work you can also boot TWRP through fastboot and then install the IMG through TWRP itself (like updating your recovery)
You can boot TWRP via fastboot with using the boot command instead of the flash command:
fastboot boot "image.img"
Still showing that it's failed
Could you boot TWRP without flashing via fastboot? Because if you can do that it means that the system is automatically reflashing the stock recovery at startup.
How did you installed (tried to install) the recovery?
fastboot?
Follow this. TWRP 3.0.2 can be installed this way. 2.8.6 sometimes doesn't.
1. Turn off option to Update Cyanogen Recovery from Developer Options.
2. Flash Recovery via fastboot, the put command to clear cache from fastboot only. DONT REBOOT NOW.
3. Disconnect phone and turn it off.
4. Try booting to recovery. If it fails, dont worry let the phone boot normally then try again. It should work.
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.
Hi everyone,
I have tried to get root priviledges following a guide from Droidwin.com to flash Magisk throught TWRP. At the very last step, after flashing Magisk 19.3 throught TWRP when I tried to reboot my phone, it gets stuck on the "unlocked bootloader warning message", which is supposed to disappear after a few seconds and move on to the boot animation.
It seems like I can go to the stock recovery, which shows fastboot and wipe actions. At this point, I can acces the fastboot screen, but the device is not listed using the ADB command "adb devices", nothing is find.
I'm wondering, what can I try to restore the phone ? I thank you in advance for any suggestions.
Here are some additionnal informations:
---Device---
Oneplus nord running OxygenOS 10.5.5, european version.
---What I've done to get in this situation---
Unlock bootloader using ADB
Launch an TWRP image file using ADB
"Try" to root using Magisk 19.3 zip throught TWRP
Power off from recovery (using TWRP touch interface), but the guide tells to click reboot at this step ...
Get stuck on the warning message, not having any boot animation.
Try to boot in Fastboot.
Turn the Nord Off and start it with plus minus and Power.
Boot TWRP with "Fastboot boot "TWRP File name.img" and flash magisk 20.4
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Search forum....
Msm tool oneplus nord wipes phone but fixes any issues
thibdur said:
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Click to expand...
Click to collapse
Plug your phone to your PC while in TWRP, then you can use adb to push files to your phone, for example with adb push magisk.zip /sdcard. Then, flash Magisk in TWRP.
How about flashing stock boot to see if your OPN boots to system again and then simply load Magisk zip to your internal storage and then flash via TWRP?
Thank you a lot for your suggestions !
Here is the solution in my case :
Because fastboot was working, I was able to flash stock oxygen rom, and get every working, but it needs to erase all your data.
You can find a guide on the XDA topic "[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord". The rom list have the lastest roms version (09/2020), and the process is super automated.
Have a good week-end XDA !
Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.
If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.
Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?
MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.
Boot into twrp. Then format data. Phone will boot then.
I've decided to upgrade to OOS11 stable and patch the boot before going into the rom. What I did was:
1. Flash latest TWRP (3.5.2_9-0)
2. Reboot to recovery
3. Flash ONLY OOS11 boot.img
4. Flash TWRP again
5. Install Magisk and Kirisakura-R 1.1.1 kernal (for f2fs support)
6. Reboot to recovery
Here I was going to do the same on other partition but TWRP failed to boot and screen kept flashing but I noticed that ADB was connected so I rebooted to fastboot and flash stock boot I've previously extracted from stock ROM. Now I face another problem, phone doesn't boot anywhere else but fastboot.
I've tried a few stuff to get it back.
# There were some cases where the phone won't boot with bootloader unlocked and stock boot so I managed to patch boot.img with Magisk using an emulator and then flash it.
# Tried booting into TWRP but phone phone would get stuck in "Fastboot mode" screen with fastboot still connected (And taking commands from PC).
# Tried flashing TWRP to boot partition which worked previously but this time the problem stayed and kept booting into fastboot.
A few more points that I should mention,
# I've backed up my entire phone using TWRP so I can unbrick it if I somehow manage to get into TWRP
# I don't have the backup on my computer. It's on the phone.
I absolutely can't lose those data. Yeah, mistake on my side for not backing up on my computer but to my defense, this never happened before so I let my guard down this time.
What options do I have left? Any hint would be appreciated. Thanks for reading