Database Info

Stuck in bootloop

hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated

yunghunter said:
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
Click to expand...
Click to collapse
Are you sure you are running the latest version of platform tools - here?
If you are using the latest version, you could try the Deuces script to try to fix your issue. I have heard good things about it, but have never actually used it, just follow the instructions in the thread.
HTH!

Try flashing 8.0 then flashing 8.1.

yunghunter said:
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
Click to expand...
Click to collapse
What was you trying to do before bootloop?

Daandofreak said:
What was you trying to do before bootloop?
Click to expand...
Click to collapse
root

Duhman72 said:
Are you sure you are running the latest version of platform tools - here?
If you are using the latest version, you could try the Deuces script to try to fix your issue. I have heard good things about it, but have never actually used it, just follow the instructions in the thread.
HTH!
Click to expand...
Click to collapse
Tried the Deuces and updated the platform tools now after the deuces it reboots to bootloader with a error highlighted in yellow saying LoaImageAndAuth Failed: Load Error

yunghunter said:
Tried the Deuces and updated the platform tools now after the deuces it reboots to bootloader with a error highlighted in yellow saying LoaImageAndAuth Failed: Load Error
Click to expand...
Click to collapse
I ran into this error recently which seemed to be fixed by updating my not-new-enough platform tools and reflashing.

cntryby429 said:
I ran into this error recently which seemed to be fixed by updating my not-new-enough platform tools and reflashing.
Click to expand...
Click to collapse
how would I go about doing that what would my next step be I'm sorry just dont where to go next

yunghunter said:
how would I go about doing that what would my next step be I'm sorry just dont where to go next
Click to expand...
Click to collapse
what do you get when you type the below commands?:
adb --version
fastboot --version

Duhman72 said:
what do you get when you type the below commands?:
adb --version
fastboot --version
Click to expand...
Click to collapse
with adb command it gives me all the commands I can do and with the fastboot command it says unreconized option

yunghunter said:
with adb command it gives me all the commands I can do and with the fastboot command it says unreconized option
Click to expand...
Click to collapse
I believe you said you are on Linux.. those work on windows. look thru the adb commands and you should see the proper syntax.. same for fastboot if you maybe just type fastboot help or fastboot -h.
There should be an option for getting the versions. It will return something like this (except not windows paths):
C:\Users\UserName>adb --version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\platform-tools\adb.exe
C:\Users\UserName>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\adb\platform-tools\fastboot.exe

Duhman72 said:
I believe you said you are on Linux.. those work on windows. look thru the adb commands and you should see the proper syntax.. same for fastboot if you maybe just type fastboot help or fastboot -h.
There should be an option for getting the versions. It will return something like this (except not windows paths):
C:\Users\UserName>adb --version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\platform-tools\adb.exe
C:\Users\UserName>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\adb\platform-tools\fastboot.exe
Click to expand...
Click to collapse
adb version is 1.0.32 fastboot I cannot find the fastboot version

yunghunter said:
adb version is 1.0.32 fastboot I cannot find the fastboot version
Click to expand...
Click to collapse
I don't think you are using the latest version.
Download the latest versions for Windows/Mac/Linux here.
Run the adb version command again to see if it has updated.

Duhman72 said:
I don't think you are using the latest version.
Download the latest versions for Windows/Mac/Linux here.
Run the adb version command again to see if it has updated.
Click to expand...
Click to collapse
downloaded from the file posted for latest version still came up same version tried using dueces toolkit runs everything ok until the end then it says fastboot unrecognized option set active=a

yunghunter said:
downloaded from the file posted for latest version still came up same version tried using dueces toolkit runs everything ok until the end then it says fastboot unrecognized option set active=a
Click to expand...
Click to collapse
are you sure you don't have an old installation of the tools somewhere else on you computer? That error sounds to me like it is an old version of fastboot.
can you run the adb version by pointing it to that actual path you have installed the new one you downloaded? I am not real familiar w/ Linux, but in windows it would be something like this - straight from my computer where i have adb.exe installed in 2 different paths:
--OLD VERSION OF TOOLS
C:\Users\UserName>c:\adb\adb.exe version
Android Debug Bridge version 1.0.26
--CURRENT VERSION OF TOOLS
C:\Users\UserName>c:\adb\platform-tools\adb.exe version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as c:\adb\platform-tools\adb.exe
I made sure to set environment variable to always reference the one in path c:\adb\platform-tools\, so i get the newer version and don't have the errors you are seeing. (again I use windows, so I have very little Linux knowledge)
It really sounds like you are using old version of the tools.

yunghunter said:
adb version is 1.0.32 fastboot I cannot find the fastboot version
Click to expand...
Click to collapse
Saw that you mentioned you were using Linux; it appears that the latest Ubuntu binaries are not up to date. After I finally tracked down the version number installed on my laptop I realized I wasn't on the latest version and downloaded them from Google. You should ultimately end up with fastboot version 0.0.1-4500957. As it turns out this is the only version of fastboot that actually returned a valid version number for me.

[Guide] Installing Blu_spark TWRP | Magisk 20.1 On Stable Oxygen OS 10

Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
 @eng.stk for the Blu_Spark TWRP
 @mauronofrio for the initial TWRP Image
 @Akhil701 for the stock boot.img
 @remewer for inspiration to build this guide.​

Patched boot.img or why we need the boot image after flashing OOS10 via local update?

Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide

Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.

no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system

I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching

Functionally on OOS 10.0.1 OP6 ?

So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.

Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand

magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.

Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?

WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works

After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine

Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail

As above. No wifi, no sound. What's going on?

Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...

ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.

Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?

dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.​
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!

loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes

Can't update my Pixel 3 manually

I downloaded the latest January Update. I did my reboot to bootloader, flash bootloader/radio, did update image.zip.
This failed with: failed (remote: variable not found).
Google says it's because not updated fastboot. I updated now i'm getting:
error: failed to load 'image-blueline-qq1a.200105.003.zip': Not enough space
When I google this error, it mentions doing a complete manual install of a and b slots, but fastboot flash system system.img doesn't work anymore. Anyone know how I can update?

Welp 1 computer I tried it on, gave the above problems. Tried it on my main home computer, worked. Don't know what's different TBH.

dardack said:
Welp 1 computer I tried it on, gave the above problems. Tried it on my main home computer, worked. Don't know what's different TBH.
Click to expand...
Click to collapse
Different driver versions perhaps?

dcarvil said:
Different driver versions perhaps?
Click to expand...
Click to collapse
Think fastboot. I have no clue where i got the adb/fastboot i use on the computer that worked.

dardack said:
Think fastboot. I have no clue where i got the adb/fastboot i use on the computer that worked.
Click to expand...
Click to collapse
The official source for fastboot is platform tools at https://developer.android.com/studio/releases/platform-tools
You should always check for a new version if you run into problems. Actually, I always check for a new version before I try to do an update.

And never use the version from the Linux apt repository for anything but setting permissions. After that, use a ./ to run the current version downloaded (or installed with SDK tools or Studio) separately with the folder opened directly in terminal. Probably off topic, but that version of fastboot is old AF and there have been a handful of new commands like "fastboo reboot fastboot" to get to fastbootd.

System partition not found

This is just a quick post to document an issue & solution I had when updating my Pixel 5 to the latest OTA and trying to re-root.
I had installed the latest OTA via system update, then downloaded the matching image from the Factory Images Page, pulled the boot.img out of there, transferred it to my Pixel, and used Magisk to patch it.
I then transferred it back to my computer and tried to flash it to the phone using fastboot flash boot boot_patched.img. At this point the phone entered a bootloop.
I booted into the bootloader menu and tried to flash the latest clean system image (without wiping data), when I ran into the following system errors causing the flash to fail when trying to flash the system partition:
Code:
FAILED (remote: Partition system not found)
(and later...)
FAILED (remote: Partition should be flashed in fastbootd)
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.

CarteNoir said:
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
Click to expand...
Click to collapse
Just wanted to say thanks. I had this issue with my Pixel 6, and updating my ancient ADB/fastboot binaries resolved it!

It's always important to ensure your platform tools are updated! Glad you figured this out!

Thank you!
I had the latest universal ADB/Fastboot drivers installed... but this didn't make a difference
I downloaded latest platform tools, ran the flash-all.bat from there and BOOM, sorted
Thank you so much

Thank you so much. Can't believe the solution is so simple lol

Question Pixel 7 Pro Fastboot "device requires partition vendor_kernel_boot"???

HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....

Update: tried again via PixelFlasher and did not encounter the error so I guess if anyone else hits this issue and sees this post.... just use PixelFlasher(?????) No idea the why or how but seems to be good now.

Sounds like you were trying to flash in Fastboot mode rather than FastbootD.

Tomadock said:
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
Click to expand...
Click to collapse
Negative. I also thought that might be the issue and attempted it (the actual command it was running, not the entire script again since that would reboot to bootloader again) in FastbootD as well to the same result.

Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
i tried the latest version of "SDK Platform Tools"; it worked for me

Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
Literally error says everything....
You need latest platform tools that supports vendor _kernel_boot partition
Google added vendor kernel boot partition on P7 series that's been supported only on latest platform tools