I have a rooted Oneplus 7 pro with android 11, but it has been lagging a lot lately, so I thought I might just unroot it and see if it helps. But, I don't have any access to a windows pc, I have a Mac.. So, I went searching the internet for a tutorial but I couldn't find any for Mac, but many guys mentioned that it could be done via Magisk by just uninstalling it. After doing so, my phone is now booting into fastboot mode only, showing the following :
Fastboot Mode
Product_Name - msmnile
Variant - SDM UFS
Bootloader Version -
Basband Version -
Serial Number - ********
Secure Boot - yes
Device State - unlocked
I have downloaded a stock android 11 version for 7 pro on my Mac, so all I need is to flash it if it is possible.
It is the only phone that I have, so any help would be appreciated.
Related
I tried to update my phone by going to Cyanogenmod's Mirror network and updating to the newest version (crespo full 118 zip) but once I had "successfully" installed it, it got stuck on the google logo lock screen, so I took the battery out, and tried again with no luck.
On Fastboot mode, I tried all options, but cannot get past this logo/lock screen. I am using a Mac and am having a really hard time finding any information on step by step (got lost in a unzip/zip file explanation video) and really need help turning it back on and making sure I don't mess it up permanently!
Anyone? I would really appreciate it!
ANYbody? Please I'm starting to get desperate and I have continued trying to find a solution for the past 4 hours with no luck whatsoever! I don't understand, and would really be super grateful if someone could help me out!
QUICK UPDATE: I'm using a Mac and my computer doesn't seem to pick up any sign of the phone when I connect it with the USB cable.
When I get to the Fastboot mode page this is what I see:
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOODLOADER VERSION - I9020XXJK1
BOOTLADER BUILD - NOV 4 2010
BASEBAND VERSION - I9020XXJK8
SERIAL NUMBER - (my serial number)
LOCK STATE - UNLOCKED
.......please please please help!
selenag said:
QUICK UPDATE: I'm using a Mac and my computer doesn't seem to pick up any sign of the phone when I connect it with the USB cable.
When I get to the Fastboot mode page this is what I see:
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOODLOADER VERSION - I9020XXJK1
BOOTLADER BUILD - NOV 4 2010
BASEBAND VERSION - I9020XXJK8
SERIAL NUMBER - (my serial number)
LOCK STATE - UNLOCKED
.......please please please help!
Click to expand...
Click to collapse
Ok, don't panic
So, you're unlocked - that's good.
Verify that fastboot sees your device when connected in the boot loader (fastboot devices should list a serial)
If it does then reflash the appropriate recovery for your device
NS:http://mirror.sea.tdrevolution.net/cm/recoveries/recovery-clockwork-3.0.2.4-crespo.img
NS4G: http://mirror.sea.tdrevolution.net/cm/recoveries/recovery-clockwork-3.1.0.1-crespo4g.img
Download the image, put it in the same folder as fastboot (unless you've added it to your $PATH) and then run
Code:
fastboot flash recovery recovery-image-name-here.img
This is going to reflash the recovery image. At this point you should be able to reboot into recovery.
Once you are in recovery go ahead and reflash the CM7 build if you'd like or flash any other package (a full stock rom for example).
Thanks!! Got it
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.
So i recently did some sh*t with my 7 Pro and bricked it :
- Once it has started, it successively displays the TWRP logo and a black screen
- I can only boot into fastboot mode
In order to resolve this I tried two different solutions :
- The Mega Unbrick Guide for A Hard Bricked OnePlus 7 Pro : https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
- The Tool all in one
For the first solution, MSM Tool doesn't work. I'm stuck in Param preload, even though I have the QC and OP drivers installed (I see Qualcomm HS USB ...... under COMs and Ports)
For the second one, the tool can see the phone when it boots indefinitely with TWRP logo but when I want to restore the phone, it goes in fastboot mode and from this moment the phone is no longer detected by the PC (the terminal displays "waiting for device") making it impossible for my computer to interact with my phone.
Anyone have a suggestion / solution ?
Lots of time there a driver conflict ,causing there peram preload error, make sure there are no other Qualcomm drivers active at this time. Also sence u can get into fastboot or TWRP, this still leave lots of flashing options. Just find a fastboot pack with a all.bat to flash. Also lots of the boot ishues are to do with the a and b slot not matching up. What works the best is a format reboot flash a reboot them flash b. To make both slot match up.
I've just got Realme GT2 PRO (RMX3300) (China ROM) and I need to flash the global ROM on it. but with all of my knowledge and hours and days wasted trying to flash the global ROM I am still unable to.
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
here are some of the things i tried:
1- turning off the phone then holding the VOLUME DOWN and POWER BUTTON (AS SHOWN IN THE PICTURE) only puts me in recovery mode
2- using commands such adb reboot bootloader just restart the phone and shows a weird Chinese text for a split second (AS SHOWN IN THE VIDEO)
3- tried installing DEEP TESTING app but it gives me this error (AS SHOWN IN THE PICTURE)
I am honestly very desperate at this point and I am willing to pay anyone who manages to fix this issue
Tl;dr : can't go into bootloader/fastboot
Mr.pizza said:
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
Click to expand...
Click to collapse
Each computer so also every Android phone ( regardless of brand / model ) has a bootloader. Whether Google's Fastboot tool is supported or not on Android phone depends on brand / model: e.g. Samsung does NOT support it whereas Realme does.
See also here:
How to Unlock Bootloader of Realme GT2 Pro? – (Easy Method)
Do you want to Unlock the Bootloader of Realme GT2 Pro? We have shared the Easiest Method.
androidcatch.com
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.