Hi, I am currently on Stock android 12 and there is nothing I can do to reboot to Bootloader.
I tried all combinations of keys and adb reboot bootloader with differents drivers, usb ports, and adb versions.
Every time it boot into something with tiny letters for 1 sec and then instanly boot the system.
Any ideas ?
This is the tiny message I have
serial doesn't match
fastboot verify fail
Try searching. You're not the first one :]
Serial is not match fastboot unlock verify fail??
I am not able to open fastboot mode there is no fastboot mode available and showing this error in OnePlus Nord 2 5g
forum.xda-developers.com
Hey found THE solution to have fastboot and BROM. There is a rollback package to OOS 11 here. It works for all versions after C.05
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
follow instructions from this video but use package from oneplus community
you need to have enabled developer options to see the local update button
Related
I have previously unlocked and modded several Xiaomi phones. However recently I got a MI8 and what I thought would be simple was quite problematic. Its solved now which is why I am writing this guide to help someone else in a similar situation. I'm not an expert but the issues I had could be relevant to other USB-C Xiaomi Qualcomm based phones from mid 2018 and later:
NOTES:
1) AMD Ryzen PC with B350 chipset would not connect in any fastboot mode procedure at all with Mi8 in my case. It could not unlock the phone or flash anything with fastboot. Go with Intel.
2) Use a good USB-C cable. One of mine worked for MTP transfers but did not work with fastboot stuff
3) If you get a request in TWRP to provide your password for decryption, this refers to the PIN used in Android security
4) If you have not unlocked your Xiaomi phone you must do this first before trying any of the steps below. There are many guides for this.
5) Follow the steps EXACTLY to avoid boot loops etc.
Issue 1: The commonly used ADB and Fastboot tools fail to flash TWRP recovery (Thanks to khanhdx https://forum.xda-developers.com/member.php?u=7791242)
1) It is necessary to use Xiaomi's specific version of fastboot in their miflash_unlock tool.
2) Put phone in fastboot mode and connect to PC.
3) Go into the miflash_unlock directory which was used to successfully unlock the phone
4) Put your TWRP image file in that miflash_unlock directory
5) While mouse cursor is in the directory, Right click while holding down SHIFT and select 'Open PowerShell session here'
6) Type 'cmd' then Enter
7) Type 'fastboot devices' to see if fastboot sees your device.
8) If a device code is displayed then USB drivers could be adequate so try 'fastboot flash recovery twrp.img' (insert actual name of img file)
9) If either no device code shows up or the recovery flash fails you will need to update USB drivers
10) First uninstall any other previously installed ADB USB drivers
11) Download Xiaomi MiFlash tool at https://www.xiaomiflash.com/ which contains drivers which work
11) Before installing the drivers with the MIFlash tool, it is recommended to boot with 'Disable Signed Driver Enforcement' enabled first. Google that if needed
12) The driver installer in MiFlash is wonky but it works. Continue to say 'Yes' to all the weird driver install warnings and long latency delays. It gets there slowly and confirms successful installation one driver at a time
13) Repeat Steps 5 through 8
14) If the above doesn't work, take a look at the driver in Windows Device Manager under Android ADB Device. It should be signed by Xiaomi not Microsoft. Also try different USB ports and/or remove other USB devices.
Issue 2: Custom ROM such as LineageOS or Pixel Experience will fail to flash in TWRP with "Error 7" stating that you don't meet the minimal Xiaomi developer firmware version requirement
1) In my case starting out with the latest Xiaomi global developer ROM and flashing the latest developer Xiaomi firmware from https://xiaomifirmwareupdater.com/#stable did not help meet the requirement and Error #7 would not go away. According to some sources such things do happen with official Xiaomi ROM's.
2) You can do the solution mentioned here https://forum.xda-developers.com/mi-8/how-to/guide-how-to-flash-poco-f1-roms-t3911336 but this is a hack and not a true solution as you will have to do this every time you update the ROM, and the phone might not work right as the dev's at LineageOS and others know what they are doing when they put in those insist lines.
3) A real solution is to meet the firmware requirement by flashing the latest Xiaomi EU weekly/developer ROM (i.e. NOT official Xiaomi) from https://xiaomi.eu/community/ before flashing the custom ROM of choice (Thanks to Xiaomi EU forums)
4) Go to TWRP and wipe everything except USB OTG option. Format data! Reboot to Recovery!
5) Transfer downloaded xiaomi.eu ROM zip file to phone via MTP and install it with TWRP. Reboot to System!
6) Allow phone to initialize it's first Xiaomi boot fully. When the MiUI welcome screen comes you can stop there. Boot into fastboot mode
7) Repeat steps in 'Issue 1' above to re-flash TWRP recovery back to the phone
8) Repeat Step 4
9) Transfer custom ROM zip and optional GAPPS zip files to phone via MTP and install with TWRP.
any reasons why this flashing and fastboot doesnt work properly with amd based pc/laptop.it is really hard for me..
I have a Moto Z4 XT1980-3 (Unlocked retail version with RETUS channel) with bootloader locked - no modifications from official state so far. When I got the December 2019 security patch upgrade, something network-related got corrupted - I have not been able to connect to any WiFi at all! This was the origin of all the desaster.
I read through the internet and found the information that it could happen that an OTA upgrade may not have been got on the device properly and if there are any hassles afterwards, it is required to do a full flash of the recent firmware. Okay, no problem, I thought. I am really familiar with ADB, fastboot and so on, and so I did. Took the recent firmware from here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/ (the one uploaded on 6th of December 2019).
The result was that I could flash all parts of the firmware, except of boot, vbmeta and dspso - for these parts I got a "(bootloader) Preflash validation failed" error. So now I am with an inconsistent firmware state and can only access fastboot mode (not even recovery). Plus sometimes when booting it, I get errors of unbootable A/B slots in the bootloader log. After having flashed gpt again, these errors disappear and I simply get the message that my device won't boot because of an invalid operating system.
What I have already tried to do:
- flash a full factory image (see above)
- use RSD lite (this tool detects my device as connected, but with no device information at all (only "?") and says it can not be switched to fastboot mode - but I am in fastboot mode already ???)
- use LSMA Smart Repair Assistant (this tool says my device is not compatible)
- Blankflash (I have not found out yet how to get my device in edl mode from fastboot)
As bricked devices are a more general Android issue and Moto Z4 is not very spread (the corresponding device forum is almost dead), I try to ask my question here in the general Android troubleshooting section. I hope, somebody can give me any advice how to reanimate my device. Maybe, anybody with special Motorola experience who can tell me why I can not flash the full factory image or explain how I can get boot, vbmeta and dspso back to the device. Any help appreciated.
The TL;DR is, I bricked my phone (TMo Nord N200 5G, SIM unlocked, Bootloader unlocked). I'm trying to use the MSM to recover it. I can't boot to EDL (hold down volume up and volume down at the same time, while pressing power or plugging a USB cable into my PC). It just boots to Fastboot when I follow that procedure. I can't get to a place where I can use ADB commands (ADB shows device "unauthorized").
Longer version, my stock phone was upgraded to the June patch level, I think.
I did the SIM unlock, unlocked the bootloader, and installed the drivers.
I successfully flashed the latest PHH squeak FOSS by following this guide but it had some quirks that I wasn't completely satisfied with.
I flashed a SparkOS GSI linked from somewhere else, but it constantly beeped at me after I disabled Google Play Services, so I decided to move on.
I think the next OS I tried was CRdroid from the same place, but I also replaced the boot.img with a stock one that was patched for Magisk. I can't remember why I thought this was a good idea. There was also a thread that said Magisk doesn't like having nothing in system_a so flash this blank partition using these commands. It always errored out, but I tried it before rebooting.
At this point, my phone would either boot to Qualcomm CrashDump on its own, or Fastboot if I held volume down.
Using the latest Fastboot Enhance I was able to get into fastbootd by switching to "A" active, then rebooting to fastbootd. Have to remember to switch back to "B" active to get anything else to work.
I've tried flashing a few different things since I can get to fastbootd now. I'm no longer booting into the Qualcomm CrashDump, it reliably boots to fastboot as long as I'm "B" active. I just can't get anything resembling a working OS.
I've tried flashing the OTA TMo with Fastboot Enhance a few different times, and a few different GSIs through fastboot, and I really want to get back to stock now so I can start all over.
I've also tried a couple different MSM tool versions, but since my phone is never in EDL, it's never recognized.
Thank you for any assistance.
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
scanman0 said:
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
Click to expand...
Click to collapse
Thank you for responding!
The command fastboot oem edl is returning either:
FAILED (remote: 'Command not supported in default implementation')
FAILED (remote: 'unknown command')
I'm running fastboot version 33.0.2-8557947, it's not in my system path.
From a full power off, holding the buttons and plugging in the USB cable, it's about 5 seconds until I see the OnePlus logo, then 2 more seconds before I drop into Fastboot. I'm not sure what I'm looking for, to confirm EDL mode. I'm not seeing my Device Manager update in that time, and the MSM tool isn't displaying anything, either.
try insert cable then volume + and - and power. keep it holding for 10-15 seconds or till you see qualcomm device in device manager
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
try holding both volume buttons (make sure its off!) then plugging your phone in to the computer with msm tool open (you can pre-press the start button) (make sure you have all the drivers installed)
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
yrrebeulB said:
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
Click to expand...
Click to collapse
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Same issue as OP, won't boot into edl
edit: use USB 2.0
You can try enumusb.exe here: http://www.temblast.com/windows.htm
Code:
C:\>enumusb.exe /l /v05c6 /p9008
It will list the first time that a QUSB_BULK was plugged into a port, even if there was no driver found/loaded.
If you want, you can clear past connections by (needs to be admin command line):
This does no harm. I clear everything out occasionally, it just means that next boot will take 5 seconds longer while it discovers "new" devices and installs the same drivers.
Code:
C:\>enumusb.exe /d /v05c6 /p9008
Or, if you don't like that, just plug your device into a different port and see if another port is listed in enumusb.exe /l
On that same page you can find usblog.exe
You just run it and it will show you what pops up and down.
But, this only shows devices that Windows has loaded drivers for.
swee08315 said:
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Click to expand...
Click to collapse
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
I re-installed the Qualcomm driver bundle while my phone was plugged in and in EDL mode, and MSM finally worked! Thank you kind stranger! I'm back to factory now.
Thank you Strangers ,
yrrebeulB , all of you​
Ytube21 said:
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
Click to expand...
Click to collapse
thank you
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
this line literally saved me hours
yrrebeulB said:
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
Try my native Windows EDL client. It uses the same Firehose loader as your stock tool does.
At the very least this will give you a second opinion.
http://www.temblast.com/edl.htm
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?
N200 on OOS 12, can't seem to possibly ever enter fastboot mode. Whenever I try I get some screen with the only options as wipe device, reboot, power off and 'fastboot devices' on my computer no longer shows the phone. Also there is no longer an 'advanced reboot' option in OOS12 so I can't go that route either. Please help so I don't have to bin this thing
Looks like you're in recovery mode. Remember that you have to shut down your phone and hold both volume buttons and the power button while it's unplugged to enter fastboot mode. Alternatively, you can use the "adb reboot bootloader" command while your phone's booted up.
Also, you can't install LineageOS from OxygenOS 12 right now. You need to downgrade to the last version of OxygenOS 11 before installing a custom rom.
Hi, thank you for responding! I've dug in further and what's going on is the driver doesn't work in Windows in fastboot mode, only in ADB does the driver work so I am sort of stuck. I downloaded the OOS 11 zip but I can't figure out how to install it now, I don't have a 'System Update' area in settings that will let me apply the local zip. My update screen just says 'you are up to date' and gives no option to apply a local update. Any idea how to get to the local update setting to apply the OOS 11 zip? Thanks again!
EDIT: I've found a couple of applications that restore the 'local update' feature but now it either says verification failed (My Application2 app) or else the local update file is not shown (OPLocalUpdate_For_Android12.apk). I downloaded this file and put it in the root of the internal storage but it's not working:
NordOxygen_14.I.25_OTA_0250_all_2201171943_downgrade_347e133266814951.zip
Is this the right downgrade file? I have an N200 global. Thanks!
Edit 2: I'm now back on OOS 11! Yahoo! I used the guide here:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Back to my original issue though, I seem to be having driver issues with fastboot mode. I've tried a few USB ports & cords to no avail, do you have any thoughts on troubleshooting a fastboot problem? The device shows normally when plugged into Windows but when I do 'adb reboot bootloader' and the handset enters fastboot mode then I lose the driver and instead the device shows up under 'Other devices' as 'Android' with a yellow exclamation point. I tried installing OnePlus_USB_Drivers_Setup.exe but that didn't do anything, do you think I should boot Windows with driver signing disabled and try again?
You can usually force the OnePlus fastboot driver to install. I don't remember the exact steps, but I think that you have to right click on "Android" in Other devices, select Update Driver, select "Browse my computer for driver software", select "Let me pick from a list of device drivers on my computer", select the Android related category, and select Android Bootloader Interface. Accept all warnings.
If that doesn't work, you could also try the universal ADB driver, as that's what LineageOS recommends.
You probably don't need to disable driver signing.
Thank you for the replies, I was able to get the driver installed and I installed lineageOS per the offficial doc. Unfortunately I seem to have bricked the phone as it's stuck in fastboot mode and won't boot into recovery anymore
What I did was from here:
Install LineageOS on dre | LineageOS Wiki
wiki.lineageos.org
a) fastboot oem unlock
b) boot into custom lineageos recovery via fastboot - fastboot flash boot lineage-19.1-20221116-recovery-dre.img
c) sideload in copy-partitions-20220613-signed.zip
d) install lineageos
Any idea how to get recovery working again?
EDIT: I think I should specify this is an UNLOCKED N200 not a T-mobile one so I think the MSM tool doesn't apply
EDIT 2: I got it booted into LineageOS but now Wifi won't turn on, oh what a night of drama!!!
EDIT 3: I fixed that now too, I'm all set! Thank you!!!