This is exactly what I was afraid was going to start happening. People should use Fastboot Enhance instead of fastboot scripts because it's already booted into fastbootd!```Failed to boot into userspace fastboot; one or more components might be unbootable.```
Try reaching out to support and see if you can get them to remote flash. Apparently they were saying that they won't but someone else who messed his up with the Android 13 beta said that he had gotten them to agree but he managed to fix it himself.
Gotcha, I'll make a service request for it.Try reaching out to support and see if you can get them to remote flash. Apparently they were saying that they won't but someone else who messed his up with the Android 13 beta said that he had gotten them to agree but he managed to fix it himself.
What firmware were you on and what were you trying to flash? Had you ever been in fastbootd before? Was your phone bootable before the script?```Failed to boot into userspace fastboot; one or more components might be unbootable.```
Dude. STOP TROLLING MY THREADS!!! Anyone who has ever booted into fastbootd knows that it waits for the device and the script won't be able to continue without it. Everything below it FAILS because it wasn't booted into fastbootd and NOTHING was flashed. This is so easy to show...This is exactly what I was afraid was going to start happening. People should use Fastboot Enhance instead of fastboot scripts because it's already booted into fastbootd!
I'm not trolling. The fact is that this wouldn't have happened with Fastboot Enhance because it starts and finishes with fastbootd. It doesn't need to reboot during the process which is the point when things go south with fastboot scripts. Exactly what I was concerned was going to happen has happened, I point it out, and now I'm trolling? I should have dropped a post about it here too to begin with when I saw you posted it on both forums and I would have saved this person but I was trying to be respectful of your wish not to be negative in your thread. My only intent was to save people from bricking their phones, that's quite different from a troll.Dude. STOP TROLLING MY THREADS!!! Anyone who has ever booted into fastbootd knows that it waits for the device and the script won't be able to continue without it. Everything below it FAILS because it wasn't booted into fastbootd and NOTHING was flashed. This is so easy to show...
The point is that the script is NOT the reason he bricked. NOTHING flashed after the first failure. He doesn't show that in his screenshot does he? He shows the end, but not the beginning of the failures.I'm not trolling. The fact is that this wouldn't have happened with Fastboot Enhance because it starts and finishes with fastbootd. It doesn't need to reboot during the process which is the point when things go south with fastboot scripts. Exactly what I was concerned was going to happen has happened, I point it out, and now I'm trolling? I should have dropped a post about it here too to begin with when I saw you posted it on both forums and I would have saved this person but I was trying to be respectful of your wish not to be negative in your thread. My only intent was to save people from bricking their phones, that's quite different from a troll.
fastboot enhanced did *not* get me into fastbootdI'm not trolling. The fact is that this wouldn't have happened with Fastboot Enhance because it starts and finishes with fastbootd. It doesn't need to reboot during the process which is the point when things go south with fastboot scripts. Exactly what I was concerned was going to happen has happened, I point it out, and now I'm trolling? I should have dropped a post about it here too to begin with when I saw you posted it on both forums and I would have saved this person but I was trying to be respectful of your wish not to be negative in your thread. My only intent was to save people from bricking their phones, that's quite different from a troll.
A10 NE2215, No. And yes! It was on A10.What firmware were you on and what were you trying to flash? Had you ever been in fastbootd before? Was your phone bootable before the script?
Did you try to boot into fastbootd with FBE before or after the script?
It flashed my boot in slot a, which made it not boot, fastbootd fails later down the script, unfortunately, i do NOT mean to be negative.Here is the beginning of errors sent by someone else. Notice it errors out. NO FLASHING IS DONE. Brick is NOT caused by the script.
You can, but you'd have to build it yourself with the A13 firmware and then use upgrade.bat even though it's a downgrade.Any idea if we can downgrade with this? Like I'm on a14 but wanna be on a13
Install.bat will wipe the device. Upgrade.bat will not. I suggest you use Install.bat since you're switching regions. You should start in regular fastboot/bootloader mode to flash some partitions. The script will then automatically boot you into fastbootd to flash the rest. This is why It's VITAL to make sure you can get into fastbootd before running the script.Thanks! I should be good to run install.bat right I don't need to change anything before flash? Should I start flash in bootloader? Or fastbootd?
You need to update your OnePlus and Windows drivers:Thanks,
but when i tried.
In cmd it says that "device not fund"
So do cant i go into fastboot?
You will have to send it to OnePlus, the tools haven't been cracked.
Yes, it will. Ensure that you can get into fastbootd mode before running the script though.Could I use this fastboot rom to flash on NE2217 device? Bootloader unlocked ,this should flash on needed files to convert to global firmware right?
@zelma83 there you go buddy.. Do thisYes, it will. Ensure that you can get into fastbootd mode before running the script though.
Thanks,
Do you know of anywhere I can get A10 for Global to flash those? :O
Extract all contents to same folder. Open command prompt in that directory. If you want phone/data wiped, run install.bat. If you want data preserved, run upgrade.bat.