Hello everyone,
I attempted to unroot my phone by uninstalling Magisk; however, my phone is not able to go to the home screen anymore. The phone is only able to cycle through a few pages such as fastboot mode, or the page, which indicates "The boot loader is unlocked and software integrity cannot be guaranteed... The third option is recovery mode, but that leads me to nowhere. I looked up many tutorials and tried to use the MSM tool, but I did not have any luck. When I used the MSM tool, my phone showed up as COM3, but the tool said "Waiting for device."
Can someone link me to a step-by-step guide, or assist me? My phone is a One Plus 7 Pro (unlocked T-Mobile version).
I attached a few images of the only options that I can see. Also, does this indicate that my phone is soft bricked, or hard bricked?
Thank you!
First, can you access fastboot commands from your computer ?
If so, can you boot the latest TWRP (https://twrp.me/oneplus/oneplus7pro.html) with the command : fastboot boot twrp.img (assuming you've put the TWRP IMG file in the same folder as the ADB tools)
Related
Hi everyone,
I'm quite new to unlocking and rooted phone, but I've read many many post on this forum but nothing worked....
Here what's happening;
Few days ago I wanted to Recover from TWRP a backup that I've made. I launch the recovery from TWRP (important details, it was a backup that I made from slot B in twrp....) in slot A.
So yes I indeed restore a slot B recovery into the slot A in TWRP.....
And I tried to reboot after that..... and the problems begins !!
I just have a blackscreen with a blue light, nothing happened..... Same thing If i try to boot into recovery mode.....
Since I tried many many things but nothing worked...... I can't boot into TWRP from fastboot.
When I'm trying that:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
The phone just reboot and got stucked on the screen with one plus logo and the text "fastboot mode" below the logo.....
I read all these post below and everything I tried (erase all data, change the active slot on fastboot mode......)didn't work:
https://forum.xda-developers.com/oneplus-6/help/oneplus-6-os-twrp-stuck-fastboot-screen-t3870989
https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-rooted-help-please-t3851802
This one I didn't really understand exactly what needed to be done but I guess I need to boot into a custom recovery as well:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Even tried that but it didn't unbrick the phone:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I tried to boot into another recovery, but same thing not working/booting;
Code:
fastboot boot blu_spark_r65-oos-pie_op6_9a5f932e4.zip
So I'm desesperate and really really need help !!:crying::crying:
Does anyone can help me step by step or has a solution please?
I can access to fastboot mode that is the only think I can do and the bootloader is unlocked.
Go and see there :
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
You'll get your phone like it comes out of the box.
yep, do this:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
I had the same problem with my OP3. i cant get past the fastboot screen. after i tried the tool everything was back to normal. but i had to oem lock after it to boot up.
Also use the official twrp for a fully functional backup and restore
Thank you all for your reply !
I've tried to follow the process from the link but the MSMTool is not finding my OP6 and I've uninstall in the Device Manager as indicated:
HTML:
plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug
But When I go into safe mode and re-plug, I can't do this part because I don't have this information....
HTML:
Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process
I tried on 2 different PC (Windows 10 and 7) but nothing worked so I can't used the MSMTool
You have to use it in safe mode to install the unsigned drivers. It only works when you see the device as something like 9800 in your device manager.
Dont worry if it fails a few times. I had to do this 8 times on my OP3 till it was successful.
You can also use this guide:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
The steps are the same
basically this is my first time trying to flash a custom recovery and after a while of trying multiple methods, none worked
i have firstly install adb,unlocked the bootloader and enabled usb debbuging
the first approach was from xda site following the tutorial, the adb reboot bootloader command just normally restarted the phone and wouldnt put me into bootloader mode, then after manually going to bootloader mode i tried to flash the img with no luck at all and the phone wasnt showing up on adb devices aswell on bootloader mode
then i tried using odin and gave it the tar file but never completed the flashing so im kind of stuck not being able to flash twrp and root the phone aswell so id appreciate your help
thanks for your time
edit: after trying again today and looking at the log, whenever i use odin it will either stop at setupConnection or recovery.img, the phone is also a galaxy j3 SM320FN
check the drivers while in download mode. fastboot devices shows you the phone while in download mode, adb devices shows you the phone while in system mode. these are different drivers. from fastboot you can boot the recovery.img without flashing for testing purposes
I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?
Hi guys,
I think I've tried it all at this point so I'm in need of some help.
I've got the T-Mobile IN2017 version of the OP8. I wanted to get rid of the T-Mobile junk and get access to the "regular" updates.
I started with this guide: [Guide] Convert to Global [WIP]
I got my unlock token today and gave 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT a shot. When it booted into Rescue Mode I assumed something had gone wrong so I told it to wipe everything and I figured I'd start over. I realized this was probably a good thing because I had neglected to backup anything.
I used instantnoodlet_15_O.16_201001 to reset. I couldn't get the volume up + volume down combination to work at all so used adb to reboot in edl. All went well.
I then re-unlocked the bootloader, flash booted into twrp-3.3.1-test10-instantnoodle-unified-mauronofrio.img and made some backups.
I installed the latest Magisk (changing .apk to .zip) within TWRP, and used adb shell to make a backup of my persist.img
I went back to 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT and ran the flash-all.bat but this time it failed and I've found myself bricked: CrashDump Mode.
I've only been able to switch betwen CrashDump Mode, off, and Fastboot. When I'm in Fastboot if I try to start or boot in recovery it just ends up back at CrashDump. If I do a hard power off and try holding volume up + down to get into edl I end up at Fastboot again as soon as I plug the usb in. The commands fastboot reboot edl, fastboot oem edl, and fastboot reboot-edl all give me errors. I can no longer flash boot into TWRP. I've tried flashing the 11.0.0 Global again but I get "Flashing is not allowed for critical partitions" and "partition not found" errors before I end up back at the CrashDump screen.
When in CrashDump it shows up in my device manager as Qualcomm HS-USB Diagnostics 900E (COM13). When I'm in fastboot it appears as OnePlus Android Bootloader Interace. I have uninstalled the drivers and reinstalled the drivers (OnePlus_USB_Drivers_Setup, QDLoader HS-USB Driver_64Bit, androidwinusb). I'm using the latest Platform Tools. I am in test mode and I have turned off driver signature.
I only have two USB 3.0 ports and I don't have access to another Windows PC. I have used three different USB cables, including the OnePlus original, in both ports. I have taken off my phone case to make sure nothing is interfering with me pushing volume up + down. My thumb hurts from pressing it so much. I've done this dozens of times now. No EDL.
I'm at a loss. Someone please help me!
Edit: I've tried using the All-In-One-Tool but it says reboot to EDL doesn't work because I'm in fastboot and trying to boot into the latest twrp still just sends me back to CrashDump.
Solved!
I came across this twrp guide: [TWRP][3.6.0-11-b7][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA] and unlike the other I had used, this one didn't warn against flashing and only booting. I flashed the img for twrp-op8-3.6.0_11-infected-b4 to recovery_a and recovery_b and booted into recovery. At first it just said I was in fastboot, it didn't give me all the usual twrp options, and the only buttons were to reboot and to switch between fastboot and adb (which did nothing, it stayed in fastboot). I tried to reboot to edl and ended up back at the fastboot screen. From here I tried again to boot into recovery and this time I got all the usual twrp options. I rebooted into edl and was able to successfully unbrick with the 10.5.7 MSM. Flashed the global 10.5.7 MSM and I'm set. Updated to A11 and everything is groovy!
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Try fastboot getvar all then do fastboot set_active to either a or b depending on which partion you are on you want to change it also pretty sure USB debugging doesn't matter in bootloader you can also try fastboot oem unlock to unlock bootloader to boot twrp unless you updated to oos twrp doesn't work yet
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
JonasHS said:
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
Click to expand...
Click to collapse
With MSM he will get everything wiped on his device. This is not he is intending to do.
AK138 said:
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Click to expand...
Click to collapse
Run fastboot flash recovery twrp.img ... And then fastboot reboot recovery or choose recovery on your phone.
Sometimes holding volume up and power to do a soft reset boots back into system worth a try.