I initially had installed oxygenOS 12, then rollbacked to oxygenOS 11 without ADB, using the system update method. Then I unlocked the bootloader and enabled USB debugging. Then rebooted into fastboot mode and according to the guide here, I used the command "fastboot update aospa-sapphire-2-oneplus8-alpha-20220118-image.zip" to try to flash Paranoid Android in my phone...and here's where the problem occurs: it gets stuck at "<waiting for device>" till I reboot the phone into fastboot again and when I do it throws the error: "fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable." (I have also attached the error message in this post), and ultimately my phone gets bricked. I am able to unbrick it into OxygenOS again but this error keeps happening again when I tried it for the second time. Please help.
Related
Solved.
AL10, NXT-C900B133, rescue0.3, NEXT
I unlocked bootloader, installed TWRP, and rooted using SuperSU with no problem by following these directions:
http://forum.xda-developers.com/mate-8/general/guide-unlock-bootloader-root-install-t3301371
I then formatted data using TWRP wipe, then tried to install Stock Rooted No Encrypted Boot from
http://forum.xda-developers.com/mate-8/development/rom-stock-rooted-encrypted-boot-t3303606
The phone never gets past "...unlocked...booting now...." (I did not install insecure_boot because I had trouble finding it---it is not in Mate 8 Android Development, only in Mate 8 Original Android Development.)
I can get to fastboot and to the Huawei recovery in Chinese (which doesn't work---wifi downloading stops with an exclamation point), but TWRP is gone, and I can't get it back by reflashing it. I've tried HiSuite recovery, unbricking using the Italian knife following these instructions:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
with various roms, and I've tried force flashing an UPDATE.APP from /sdcard/dload. No joy.
I caused the problem by installing a B331 rom when I was at B133—dyslexic much? Once I got TWRP back, flashing a B180 rom worked fine.
The difficulty was getting TWRP back. To do that, I flashed the following files using fastboot—it may be overkill:
TWRP-2.8.7.0-ENG.img,
insecure_boot_b331.img,
and the files in
L29Fastboot.rar.
TWRP
Hey ho!
I had exactly the same problem yesterday.
I figured out my system only was able to boot when I hold down [vol-]&[power].
Then the "not trusted message" had a few more lines and the phone booted up.
When it's up again, you can use adb to reboot to fastboot: adb reboot bootloader
You can also try to go directly to recovery if you alrteady flashed it: adb reboot recovery
From threre you can try again.
btw: I had to use a complete different TWRP version. 3.x somewhat. I think it was from here: http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
Info: I was NOT able to use [vol+]&[power] for Recovery, eRecovery or anything else. I was just stuck.
I hope it helps.
I recommend after getting your device back on track to use twrp to make a recovery on your microsd card. That way u have a sure chance of getting bwck to working order
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
iAngus said:
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
Click to expand...
Click to collapse
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Click to expand...
Click to collapse
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
iAngus said:
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
Click to expand...
Click to collapse
you could fix the same problem I have is not to do help me
Hello everyone,
after unlocking my bootloader (on a Realme 5 Pro) to install TWRP and custom ROM, I am now stuck at trying to make fastboot do anything.
No matter which fastboot command I try, the phone won't execute it. I instantly get a "FAILED" and "(No error)" returned and the phone exits fastboot, showing some logo with a chinese message, as well as "press any key to shutdown" in the top left corner.
The only excpetions to that behaviour:
1. "fastboot devices" works as expected and recognizes the phone.
2. "fastboot boot [path to TWRP .img file]" sometimes gets stuck at "downloading boot.img..." indefinitely, sometimes it fails like all the other commands
3. "fastboot flash recovery [path to TWRP .img file]" gives an instant "FAILED", but the error message is "requested download size is more than max allowed"
I've tried re-locking and unlocking the bootloader, when unlocked both colorOS and fastboot recognize the bootloader as being unlocked.
I have no clue what to try at this point, hopefully someone can help me out?
Same problem here.
Mine is Realme 3 pro with the new version of realme UI, RMX1851, C.04, I have unlocked bootloader without downgrading it to color os 6, but now I cannot flash twrp in my device. After going into fastboot mode, after applying the commands, it says "FAILED" (remote: GetVar variable not found) and sometimes directly "ERROR"
The fix was an incredibly easy one, but I only found it/got the idea through a lot of googling... simply used a different PC (that I never used adb and fastboot with before), let windows search for drivers online, and BAM, it works!
Hopefully this will help someone in the future.
If you don't have more than one PC, I guess the best bet would be uninstalling all adb and fastboot related drivers.
OnePlus 7 Pro was running 10.3 . Was rooted with Magisk, bootloader is currently unlocked (though it locked after an attempt with MSM Download Tool.)
Through a series of increasingly unfortunate choices, my phone will only go to the bootloader screen. While it receives commands from adb or Tool-in-One, those always result in a reboot and back to the bootloader. I was able at one point to use the MSMDownload Tool on it, even though I'm not clear at all what the various choices on that tool mean. It did appear to successfully clear the phone, but I was unable to install TWRP and a stock rom. (I do have a TWRP backup but we're not even close to being able to use it.)
Right now I can't get the MSM tool to recognize the phone; the phone will not turn off. As soon as it is "off", it boots right back to bootloader screen. I've held every combo of buttons and I can get it to go off for a second, then immediately reboot. So far I have been unsuccessful getting the tool to be useable again.
EDIT: Further info. Used flashall with a fastboot rom, all appeared to go successfully, but still only boots to fastboot. I used the Tool in One to flash a TWRP recovery, and each time get the error: Booting TWRP...
Sending 'boot.img' (31440 KB) OKAY [ 0.679s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Waiting the TWRP boots...
And I remain stuck at Fastboot . Thanks again for any help
Any suggestions for help would be much appreciated.. Without a phone, this quarantine stuff (I'm in NYC) is 100X worse.
Thank you.
Further edit: Appears to me that perhaps when I used the MSM tool, it took me back to an OOS earlier than OOS 9.5.4 GM21AA , which apparently will not accept the "fastboot boot" command. Now what? (Apparently OOS 9.5.4 GM21AA is where OnePlus fixed this bug.)
BeachNYC said:
OnePlus 7 Pro was running 10.3 . Was rooted with Magisk, bootloader is currently unlocked (though it locked after an attempt with MSM Download Tool.)
Through a series of increasingly unfortunate choices, my phone will only go to the bootloader screen. While it receives commands from adb or Tool-in-One, those always result in a reboot and back to the bootloader. I was able at one point to use the MSMDownload Tool on it, even though I'm not clear at all what the various choices on that tool mean. It did appear to successfully clear the phone, but I was unable to install TWRP and a stock rom. (I do have a TWRP backup but we're not even close to being able to use it.)
Right now I can't get the MSM tool to recognize the phone; the phone will not turn off. As soon as it is "off", it boots right back to bootloader screen. I've held every combo of buttons and I can get it to go off for a second, then immediately reboot. So far I have been unsuccessful getting the tool to be useable again.
EDIT: Further info. Used flashall with a fastboot rom, all appeared to go successfully, but still only boots to fastboot. I used the Tool in One to flash a TWRP recovery, and each time get the error: Booting TWRP...
Sending 'boot.img' (31440 KB) OKAY [ 0.679s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Waiting the TWRP boots...
Will MSM detect your phone if you try this fastboot command?
Code:
fastboot reboot edl
And I remain stuck at Fastboot . Thanks again for any help
Any suggestions for help would be much appreciated.. Without a phone, this quarantine stuff (I'm in NYC) is 100X worse.
Thank you.
Click to expand...
Click to collapse
Will MSM detect your phone if you try this command?
Code:
fastboot reboot edl
Turn off your Phone.
Hold volume up (and down) sumultanious while connecting your Phone to a computer.
Settup the right drivers and use the msm tool to flash stock firmware. EVERYTHING WILL BE RESET!
than update to latest Version 10.x and try rooting again if you like.
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Otherwise... to me it looks like you have you dont have the right recovery installed. Try flashing the right Version for you current bootloader https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943 and try flashing the latest firmware via adb
I hope this helps.
Goodluck!
I will provide as much information as possible.
The last time my phone was working, it was had build number FRD-L04C567B402.
I wanted to install the Oreo update, so I unlocked my bootloader and install TWRP for honor 8. Everything was working at this point.
I attempted to update my phone using the rom L04C567B560 and the methods provided in the thread below (HuRUpdater method)
https://forum.xda-developers.com/honor-8/how-to/guide-how-to-install-oreo-update-t3825078
It was when I attempted to install oreo my phone bricked. When I turned it on, it would attempt to boot multiple times, and then go into recovery mode.
I used the dload method to try to reflash stock rom. The installation would stop and 5% then give an error. This method failed.
I used the Huawei Extractor and multi Tool to flash a stock rom. I got the error "the size or path does not match the file system markup." This method failed.
I used adb and bootloader to flash boot.img and recovery.img directly on the device. I got the error "FAILED (remote: partition length get error)". This method failed.
After some browsing I found the following thread and attempted to used it.
https://forum.xda-developers.com/honor-8/how-to/guide-comprehensive-method-to-unbrick-t3632998
I completed up to step 8, and that package installed. Notice how the guide mentions the phone is still bricked.
After that update.app got installed, the phone went into a endless boot loop.
Now when device bootloops to this default screen
ERROR Mode
Func NO: 8 (hifi image)
Error NO: 1(security verify failed)
When I press vol+ and power, I see on my device
ERROR Mode
Func NO: 8 (hifi image)
Error NO: 1(security verify failed)
When I press vol+, vol- and power, I see on my device
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
I can still enter fastboot mode, but erecovery is no longer available. TWRP is also not available.
When I attempt to flash anything (recovery.img, system.img, boot.img) in fastboot mode. I get the error "FAILED (remote: partition length get error)".
Currently unsure what to do next. Any suggestions?
Hi, this is my first post in XDA, so sorry if I'm posting in the wrong section.
I recently got a Redmi Note 11 and today I was going to install KomodoOS in it. I did as follows:
First thing I did was to unlock the bootloader, which seems to have worked fine (I can see the open lock icon alongside the Mi logo when it powers on).
I then flashed TWRP (from here https://www.getdroidtips.com/twrp-recovery-redmi-note-11/). When I first tried the command fastboot flash recovery_a twrp.img, I got an error telling me that recovery_a_a doesn't exist, same for recovery_b (which gave me error that partition recovery_b_a didn't exist). I found on Google I could boot into twrp (fastboot boot twrp.img) and then flash twrp itself (Advanced->Flash recovery), which I did and got no error messages. I booted up the system just normal, rebooted into recovery by issuing adb reboot recovery and it got me back into TWRP. So it seems it was installed successfully.
Lastly, while the phone was on TWRP I copied the rom file into the root directory with adb push komodo-version.zip komodo.zip, clicked on Install, selected komodo.zip then confirmed the installation. It took a few minutes (file is 1.3GB) and it completed with a few errors, but at the top there was the message Install successful.
Then I wiped Dalvik and rebooted the system, but now I'm stuck at a bootloop where it goes to the "No command" screen and reboots. I tried holding volume up+power and volume up while reconnecting the USB but to no avail, can't seem to get out of the loop. Also tried spamming adb devices and fastboot devices on pc but can't connect to the phone.
I'm now a bit desperate, since there's (surprisingly?) not much about this phone out there, and I don't know anything that could be done. Is there still hope?
Links/tutorials I used:
Download and Install AOSP Android 12 on Xiaomi Redmi Note 11
Xiaomi Redmi Note 11 launched in January 2022. The handset came with Android 11. In this tutorial, we will guide you to install Android 12 Custom ROM on
www.getdroidtips.com
Download TWRP Recovery for Xiaomi Redmi Note 11 | Root Using It
On this page, we will guide you to install the TWRP Recovery on Xiaomi Redmi Note 11 (spes). This guide contains both the written instruction and a video
www.getdroidtips.com
[4 Methods] How to Fix TWRP Error: FAILED (remote: No such partition)
In this guide, we will show you four different methods to fix the FAILED (remote: No such partition) error while flashing the TWRP Recovery.
www.droidwin.com
Draining battery and directly going into fastboot as soon as plugging in works or not?
.
dont trust getdroidtip , search rom on xda instead
In Shaomi "No Command" error means system partition has been destroyed. You most likely need to Reflash MIUI using >Mi Flash Tool<.
So your issue is that you cant boot into TWRP? Also, have you tried Power + Vol(-) to get into Fastboot mode. You can also try PC softwares like >Reiboot-For-Android.exe< to boot to recovery or bootloader.
>If you have TWRP no need to use ADB push, just use USB OTG to flash ZIP<