Related
Hello,
I have followed a tutorial for solving the problem of "Fastboot mode started
udc_start()" from this thread http://forum.xda-developers.com/showthread.php?t=2131247 and something was go wrong.
I have done this steps in the sdk platform tools folder:
1- fastboot erase recovery
2- fastboot flash recovery recovery.img ( here i've got an error)
3- fastboot reboot
Everyting was ok until I have tried to write the .img file on the phone. I've got an error that I don't have enough space. I think I have deleted the recovery file and now it's stuck, because it's not booting. The 4 leds from the bottom it's flashing continuously and the screen remains to the LG logo. I have tried to connect the phone to the PC but the device it's not recognized anymore. I get this message in the adb tool "Waiting for device"
I really appreciate if it's someone that can help me
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Logan_M said:
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Click to expand...
Click to collapse
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
catalin11 said:
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
Click to expand...
Click to collapse
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Logan_M said:
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Click to expand...
Click to collapse
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
catalin11 said:
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
Click to expand...
Click to collapse
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
catalin11 said:
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
Click to expand...
Click to collapse
now i'm in the emergency mode
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
some1 pls help me
catalin11 said:
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
Click to expand...
Click to collapse
can u plz elaborate...i too have the same problem....plz..
Logan_M said:
If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located.
Click to expand...
Click to collapse
That is incorrect. The recovery does NOT have to be named recovery to use fastboot to flash it, although it does make life simpler
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, then hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Final reboot:
Code:
fastboot reboot
7. If everything worked your phone should now boot into OxygenOS.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To check current slot:
Code:
fastboot getvar current-slot
To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. This will wipe your device! Reboot to the bootloader and run:
Code:
fastboot -w
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Edit: script attached. I've (unfortunately) had the opportunity to test it and fix all the bugs. So it works. You will need to have fastboot.exe accessible in your system PATH to run it.
Slikkster2k said:
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. Reboot to the bootloader and run:
Code:
fastboot -w
This will wipe your device!
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot bootloader
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Click to expand...
Click to collapse
That would be helpful indeed. Would this script run on mac as well?
Not unless there's a version of PowerShell for macs (there is for Linux, but I don't know if it's compatible).
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
AxelM said:
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
Click to expand...
Click to collapse
I used 11.2.2.2.LE25AA as I said in the original post (this is the global variant, which matches my device). I am not sure if this works for cross-flashing, or if it's possible to cross-flash an Indian phone to EU. Have you tried restoring the Indian ROM? Does that work?
You're getting an actual boot loop? The error I was getting (and the reason I had to restore) was the phone booting to the bootloader or fastbootd (depending on the slot I tried) instead of Oxygen, because it couldn't mount the user partition due to encryption. In fastbootd an error was reported (I forget the exact one) which made me suspect it was a partition mounting issue. At no point was my phone actually boot looping, even during partial/failed flashes.
I've never encountered the error with fastboot -w, but I only did that on my phone once. From some searching online, it can be caused by an old version of the platform tools, so did you download the latest version?
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
AxelM said:
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
Click to expand...
Click to collapse
Glad to hear you got it working!
PowerShell script added to second post. Totally untested, but I tried to make it as idiot proof as possible.
Slikkster2k said:
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Reboot back into the bootloader:
Code:
fastboot reboot bootloader
7. You should now be able to continue booting normally by pressing the power button.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
Click to expand...
Click to collapse
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
toyanucci said:
That would be helpful indeed. Would this script run on mac as well?
Click to expand...
Click to collapse
Windows offered now to add to MAC - https://support.apple.com/en-us/HT201468
toyanucci said:
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
Click to expand...
Click to collapse
Thanks, updated OP.
ok i kind of bricked my phone using this and i need a little help PLEASE?
Ok i tried the fist 2 steps 1. fastboot -w than the first list of commands using cmd with admin rights it worked...i think but it did load everything without issues...now i go to do the "fastboot reboot fastboot"
and now my phone is stuck on a black screen with nothing and i just hear the chime windows makes when you disconnect and reconnect a device..... and in the Device manager this comes up for 10 seconds than goes away for 5 than comes back NON STOP
i cant adb i cant do anything please help !
I'm not sure if this will help you, but I had a lot of issues initially running this. First off you need to use the Oneplus drivers, I don't think the qualcom driver will work the same way. I could be wrong, but that's what I did. Secondly, you need to force install the driver because Windows doesn't like it.
Here are the steps I took.
1. Uninstall any old drivers.
2. Install the newest Oneplus Drivers from here https://oneplususbdrivers.com/
3. Extract the zip file and run the installer like normal
4. Once the installer finishes, you'll need to reboot your machine and bring up the Startup settings (hold down shift and reboot (keep holding down shift until you get a screen with options)) Then click advanced and startup settings and hit restart after that. Once the machines starts up, on the first boot you will have a bunch of options. Choose option 7 "disabling driver signature enforcement" mode.
5. Once Windows launches and you login, go back into the device manager and follow these steps:
right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.
----------------------------------------
The above should get your drivers working properly in all modes (adb, fastbootd, bootloader, normal)
One other issue that I ran into when I was using the powershell script was that I was seeing intermittent errors. After trial and error I realized that Windows was picking up a different version of fastboot. I was initially using the minimal adb/fastboot files, but if you compare those to the ones listed in the first post in the "SDK Platform Tools", they are very different from each other, so you need to make sure you use the SDK Platform Tools version. The minimal ADB/Fastboot version will NOT work.
After I got those 2 things ironed out, the powershell script ran without a hiccup and my phone is stock and booting without an issue.
I know I'm late to respond to this thread, but I hope someone finds this information helpful!
Mine keeps trying this and it isn't running and or rebooting into Fastbootd when the script is ran. Should I just try and invoke this manually? I've tried that as well an I'm seeming to get errors left and right with no resolve.
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Good work
toyanucci said:
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Click to expand...
Click to collapse
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
ilikepie___ said:
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
Click to expand...
Click to collapse
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
toyanucci said:
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
Click to expand...
Click to collapse
I’ll give it a shot, yeah it doesn’t do anything. Can’t see a display or anything on the screen.
Hello, friends. So I am here following this exact tutorial :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards
krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.
Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards
SOLVED
krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.
Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)
I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.
If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.
Hello there.
I have a Redmi pad running on mediatek helio g99(Treble A/B partition)
I have recently compiled orangefox recovery for my device and trying to boot from the image so that i can make my recovery permanent. But i get the following error:
Code:
fastboot boot OrangeFox-Unofficial-yunluo.img
Sending 'boot.img' (65536 KB) OKAY [ 1.826s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any solutions?
Obviously the Fastboot command "boot" isn't supported on your
XIAOMI REDMI PAD ( Android 12, MIUI 13.1 ).
ghostranger047 said:
Hello there.
I have a Redmi pad running on mediatek helio g99(Treble A/B partition)
I have recently compiled orangefox recovery for my device and trying to boot from the image so that i can make my recovery permanent. But i get the following error:
Code:
fastboot boot OrangeFox-Unofficial-yunluo.img
Sending 'boot.img' (65536 KB) OKAY [ 1.826s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any solutions?
Click to expand...
Click to collapse
Try
fastboot boot recovery OrangeFox-Unofficial-yunluo.img
ghostranger047 said:
Hello there.
I have a Redmi pad running on mediatek helio g99(Treble A/B partition)
I have recently compiled orangefox recovery for my device and trying to boot from the image so that i can make my recovery permanent. But i get the following error:
Code:
fastboot boot OrangeFox-Unofficial-yunluo.img
Sending 'boot.img' (65536 KB) OKAY [ 1.826s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any solutions?
Click to expand...
Click to collapse
Also on devices that have a neutered version of fastboot (or none at all) you can use mtkclient which can also unlock bootloader, etc on the pesky ones.
You can find mtkclient on github.com :
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
If you're not really familiar with Linux, there's a gui for windows they were nice enough to include so it's not all terminal command line.
Droidriven said:
Try
fastboot boot recovery OrangeFox-Unofficial-yunluo.img
Click to expand...
Click to collapse
Didn't work.
Code:
fastboot: error: cannot load 'recovery': No such file or directory
ghostranger047 said:
Didn't work.
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
Do you have the recovery .img in the folder where fastboot.exe is located on your PC? If not, you will have to include a <path to flie> in your command line.
Droidriven said:
Do you have the recovery .img in the folder where fastboot.exe is located on your PC? If not, you will have to include a <path to flie> in your command line.
Click to expand...
Click to collapse
I dont have a recovery image for my device, its A/B partition with only boot image. And yes OrangeFox-Unofficial-yunluo.img is inside the same folder as fastboot.exe.
ghostranger047 said:
I dont have a recovery image for my device, its A/B partition with only boot image. And yes OrangeFox-Unofficial-yunluo.img is inside the same folder as fastboot.exe.
Click to expand...
Click to collapse
If you are trying to fastboot boot a TWRP or Orangefox recovery, you need a TWRP or Orangefox recovery.img to do it. There is a difference between a boot.img and a recovery.img.
Your posts are confusing and contradicting each other. To clarify, what exactly are you trying to boot? A boot.img or a recovery.img? The Orangefox .img you have is a boot.img or a recovery.img? Are you trying to boot a temporary TWRP session in order to install Orangefox recovery, or what? If you are using a boot.img, you should be trying to flash that boot.img instead of fastboot booting a TWRP or Orangefox recovery session. Typically, "fastboot boot" command is used to boot a temporary recovery session(usually on devices that have locked bootloader) and then use that temporary recovery session to flash a custom file or modify something on the device. Is your bootloader locked or unlocked? If it is unlocked, you should be able to flash your modified boot.img instead of having to fastboot boot TWRP or Orangefox.
Either you don't understand what you are doing or you are not wording yourself correctly and I'm misunderstanding your intent. Help me make sense of what you are trying to do and what you want your end result to be.
@Droidriven you are the noob here..
aIecxs said:
@Droidriven you are the noob here..
Click to expand...
Click to collapse
No. 10+ years is far from noob. I'm just trying to make sense of what they are after. In their first post, they said they had just compiled Orangefox recovery and the title says ("fastboot boot TWRP.img failed", this command is used to boot a recovery.img, not a boot.img) of which, both are recoveries but then they say they don't have a recovery.img and their original failed command says "boot.img". In my experience, to "fastboot boot TWRP.img" means to boot a temporary TWRP recovery session and then flashing/modifying from within that temporary recovery session, fastboot booting a boot.img is something completely different. I'm just trying to establish which of these is their actual goal. Now, do you see the convolutedness of what the title says and what their posts say and how the wording conflicts?
I've personally used fastboot boot TWRP.img command to boot a temporary TWRP recovery session, not a "boot.img". What they are describing is something different from that process but they are trying to use the same command that boots a temporary TWRP recovery session.
If they are trying to boot a "boot.img" then they should be using a "fastboot boot boot.img" command, not a "fastboot boot TWRP.img" command, correct? Again, conflicting information. Do you understand why I'm trying to clarify now?
see post #1 ghostranger047 for right usage.
the phone answered with FAILED (remote: 'unknown command')
the correct answer is in post #2. on SAR devices, init is in / rootdir of system partition. in case boot.img/recovery.img itself contains no kernel/ramdisk, booting straight from fastboot no longer works (might be the reason why Xiaomi disabled that cmd, or he's simply in fastbootd).
fastboot boot accepts 1 argument (file). you are giving advise to pass 2 arguments. 1st argument 'recovery': No such file or directory, 2nd argument is ignored.
you with 10+ years experience for sure know that fastboot boot cmd always state Sending 'boot.img' (65536 KB) regardless of the file name provided, be it recovery.img or boot.img
OP is very clear in what he said. He wants to boot in his own compiled (orangefox, based on twrp) recovery.img, nothing else.
you are confusing yourself.
edit: btw fastboot boot is forbidden on locked bootloader, otherwise anyone could just boot into magisk patched boot.img
found another possible reason why fastboot boot won't work when it should.
Exelios said:
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
Click to expand...
Click to collapse
Worth a try checking which slot is flagged bootable and set as active (the one with yes)
Code:
fastboot getvar current-slot
fastboot getvar slot-bootable
fastboot getvar slot-successful
fastboot --set-active=other
aIecxs said:
see post #1 ghostranger047 for right usage.
the phone answered with FAILED (remote: 'unknown command')
the correct answer is in post #2. on SAR devices, init is in / rootdir of system partition. in case boot.img/recovery.img itself contains no kernel/ramdisk, booting straight from fastboot no longer works (might be the reason why Xiaomi disabled that cmd, or he's simply in fastbootd).
fastboot boot accepts 1 argument (file). you are giving advise to pass 2 arguments. 1st argument 'recovery': No such file or directory, 2nd argument is ignored.
you with 10+ years experience for sure know that fastboot boot cmd always state Sending 'boot.img' (65536 KB) regardless of the file name provided, be it recovery.img or boot.img
OP is very clear in what he said. He wants to boot in his own compiled (orangefox, based on twrp) recovery.img, nothing else.
you are confusing yourself.
edit: btw fastboot boot is forbidden on locked bootloader, otherwise anyone could just boot into magisk patched boot.img
Click to expand...
Click to collapse
I used a tool that used a script with the fastboot boot command to boot a temporary TWRP img while in fastboot mode on a locked bootloader Intel Atom device. With A/B devices, partitions and where everything is at changed but the basic function of the commands changed very little.
As for the part you said about I should know that the command returns "sending boot.img", that has nothing to do with I said or why I said it, it has to do with the fact that the OP themselves stated that they didn't have a recovery .img, that they had a A/B device, that they were using a boot.img(not a recovery .img). See the confusion? You are confused by what I'm saying about being confused about what they are saying.
I think you got it
ghostranger047 said:
Hello there.
I have a Redmi pad running on mediatek helio g99(Treble A/B partition)
I have recently compiled orangefox recovery for my device and trying to boot from the image so that i can make my recovery permanent. But i get the following error:
Code:
fastboot boot OrangeFox-Unofficial-yunluo.img
Sending 'boot.img' (65536 KB) OKAY [ 1.826s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any solutions?
Click to expand...
Click to collapse
did you manage to run this on your device?
I've recently switched to FerenOS(Unbuntu) tried flashing a spare device but I've run into a block. I've searched extensively but can't find what I need.
Whenever I flashed a stock image on Windows 10, I followed these commands:
fastboot --slot=all flash bootloader bootloader.img
fastboot reboot bootloader
fastboot --slot=all flash radio radio.img
fastboot reboot bootloader
fastboot --slot=(current) --skip-reboot update image.zip
Everything goes good up until flashing the image. The phone stays in fastboot and fails to reboot into fastbootd and start the update with the error "FAILED (remote: Partition system not found)"
I'm able to get to fastbootd by going into recovery and typing adb reboot fastboot. But even trying to sideload from adb doesn't work. It says "adb: command failed to read: success"
My adb is up to date but I can't figure this out. Maybe I'm using the wrong commands? Any help would be appreciated.
Nevermind, it's been solved and the phone unbricked