So, at first, I thought it was my computer because I was running the leaked Windows 11, but now its doing it with windows 10 as well. I was trying to install GrapheneOS (bootloader unlocked, done this countless times, tried different cables) but for some reason whenever it gets to
Code:
Writing sparse 'system_b' 4/10 FAILED (remote: 'Operation not permitted')
I get this with google's Flash-All for flashing to stock, I get this on GrapheneOS, I get it with GSI images. Seems like its always step 4 on the ROM. Not sure what's going on here. Stuck at bootloader currently. Recovery states android 11.
I'm about to attempt to flash with Chrome via google's online flash tool
Update: Flashed GrapheneOS "successfully" with chrome through their online flasher... but then start up error is "error setup km". Fresh install of win10
Update2: Fixed. Flashed the OTA image from google via stock recovery with adb sideload
Related
Hi guys,
I'll tell you the story first, so you can see the whole picture and answer me based on it.
A few days ago I was trying to flash twrp and magisk on my op6 oos 9.0.3. I failed a lot and went into a lot of bootloops and crashdump and black screen but got out of these situations somehow. eventually, I found a way to root using patched magisk and it worked, but I didn't have twrp. So I uninstalled magisc from the app itself and rebooted, but that caused my op6 to get into a bootloop. Luckily I was able to get to the fastboot mode but after trying to flash different twrp imgs, and failing becasue I was just trying without any previous experience and that's stupid, I know. Anyway, fastboot started to give me this error "downloading 'boot.img'... OKAY [ 0.769s] booting... FAILED (remote: Failed to load/authenticate boot image: Load Error) finished. total time: 0.784s " so I used this command "fastboot --set-active=B" to switch to slot b and it worked, then I flashed twrp and magisk successfully because I learned a lot from those failures.
So, idk what happened to slot a, so when I recieve an update in the future for op6, can I update normally from updates in settings or do I have to do it manually or what? I really have no idea and I would like to have an expectation to what may happen.
olik2000 said:
Hi guys,
I'll tell you the story first, so you can see the whole picture and answer me based on it.
A few days ago I was trying to flash twrp and magisk on my op6 oos 9.0.3. I failed a lot and went into a lot of bootloops and crashdump and black screen but got out of these situations somehow. eventually, I found a way to root using patched magisk and it worked, but I didn't have twrp. So I uninstalled magisc from the app itself and rebooted, but that caused my op6 to get into a bootloop. Luckily I was able to get to the fastboot mode but after trying to flash different twrp imgs, and failing becasue I was just trying without any previous experience and that's stupid, I know. Anyway, fastboot started to give me this error "downloading 'boot.img'... OKAY [ 0.769s] booting... FAILED (remote: Failed to load/authenticate boot image: Load Error) finished. total time: 0.784s " so I used this command "fastboot --set-active=B" to switch to slot b and it worked, then I flashed twrp and magisk successfully because I learned a lot from those failures.
So, idk what happened to slot a, so when I recieve an update in the future for op6, can I update normally from updates in settings or do I have to do it manually or what? I really have no idea and I would like to have an expectation to what may happen.
Click to expand...
Click to collapse
As per my knowledge, since you already have your bootloader unlocked and have custom recovery, you might no lt be able to install updates directly. You will have to download them from oneplus' official website and then manually flash the updates. This has to be followed with the normal twrp recovery or unlocked bootloader.
I am not too sure about slot a and b, but I hope the procedure will be same. If you want to directly get updates, you will have to flash original recovery and OOS from oneplus' website.
Download and flash manually using twrp. Should be just fine.
happiy91 said:
As per my knowledge, since you already have your bootloader unlocked and have custom recovery, you might no lt be able to install updates directly. You will have to download them from oneplus' official website and then manually flash the updates. This has to be followed with the normal twrp recovery or unlocked bootloader.
I am not too sure about slot a and b, but I hope the procedure will be same. If you want to directly get updates, you will have to flash original recovery and OOS from oneplus' website.
Click to expand...
Click to collapse
That's really helpful, thanks :highfive:
Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.
Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.
I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.
I actually resolved the first challenge I had by getting some good assistance in this thread:
https://forum.xda-developers.com/oneplus-6/help/oneplus-6-twrp-boot-img-return-qualcomm-t4047773
But after everything was working fine with the TWRP, then I realized that I needed to downgrade from Oneplus 6 stock ROM for Android 10 to a new custom ROM with Android 8...
So I wanted to format whatever was on the phone, in order to do a clean install of everything.
But unfortunately I messed up, as I thought I could do it the same way as I did with my old rooted Oneplus One... and I went into TWRP and checkmarked all I could to format all I could, including SD card etc.
I am used to Oneplus One, and here the TWRP would still stay on the phone, no matter how much I formatted, meaning that I always had a totally empty phone... as I am used to format everything and connect the empty phone to my PC and copy the custom ROM ZIP on to the phone and then boot into TWRP and install it, in order to have a new fresh installation...
But now the format on this Oneplus 6 also removed the TWRP, so I only have recovery mode now, but fastboot devices command does show the serial number, so I do have some kind of connection, but also I have an empty phone with nothing at all.
I tried to do a boot with TWRP and a push with a random ROM, but this doesn't work now:
*******************************
PS C:\adb> fastboot devices
195ce6aa fastboot
PS C:\adb> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
Sending 'boot.img' (28376 KB) OKAY [ 0.612s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
PS C:\adb> adb push lineage-15.1-20181011_085513-UNOFFICIAL-enchilada.zip /data/media/
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
PS C:\adb> fastboot devices
195ce6aa fastboot
*******************************
It seems that I found a custom ROM which is Android 8 = lineage-15.1-20181011_085513-UNOFFICIAL-enchilada.zip - but maybe not the best out there...
The mauronofrios TWRP that I got in version Q 3.3.1-17 might not be useful anymore if I want to install a custom ROM being Android 8.
So again, I am a novice and a fool here, and I need some kind of help now to get TWRP and a Custom ROM up and running now.
Thanks in advance guys!
Anyone who have a good advise here?
Easiest thing to do in your situation would be to use the unbrick tool from this thread.
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
This will completely format the phone back to Android 8 if you choose that version of the tool, and only requires 1 click after you install the proper drivers on your computer. Then you can start from the beginning and unlock the bootloader, then install twrp, and finally flash the Android 8 custom rom you want.
Hm, I am just curious, why Android 8? Lineageos 17.1 should come out in a few month, which probably means that they will end support for 15.1. Why not 16.0?
Also, do not wipe random partitions. Follow the instructions for your rom. For example, for lineageos 16 you only format data and system
I'm trying to downgrade my Pixel back to 9. Few reasons - unimportant.
I have the latest platform tools, adb and fastboot both find the phone fine.
I've downloaded the latest stock image from the Google site.
But I get a very odd error
Sending 'bootloader' (8493 KB) OKAY [ 0.199s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Everything is in the same folder, I've tried using the full path and not relative paths. Tried different cables and even different stock images. I've also got older versions of platform tools so tried earlier versions of fastboot.
I'm lost. What else is there to try/do?!
teapea said:
I'm trying to downgrade my Pixel back to 9. Few reasons - unimportant.
I have the latest platform tools, adb and fastboot both find the phone fine.
I've downloaded the latest stock image from the Google site.
But I get a very odd error
Sending 'bootloader' (8493 KB) OKAY [ 0.199s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Everything is in the same folder, I've tried using the full path and not relative paths. Tried different cables and even different stock images. I've also got older versions of platform tools so tried earlier versions of fastboot.
I'm lost. What else is there to try/do?!
Click to expand...
Click to collapse
Out of curiosity, which variant is this? Vzw? Google? Have you done updates in this way before? Or maybe only OTA updates?
cheers
Google stock image, using Google drivers, platform tools from full SDK. Done many many flashes this way - although never "downgraded" before. I stupidly hit update on my Pie stock image and it went to 10 so trying to go back.
I did read it needed have no "pending installs" in order to flash - but that doesn't make much sense, but currently OTAing to latest 11 version.
I did have Magisk root on my original 9, and the OTA to 10 obviously killed this.
Happy to kill all data and start again, I just need 9 back on this phone!
Only thing I've not tried is a different computer - will need to wait until I get back from the office to try another one though, but I've used my own laptop many times before which is why it's so confusing!
And to confirm - another laptop, totally fresh image - same problem...
teapea said:
And to confirm - another laptop, totally fresh image - same problem...
Click to expand...
Click to collapse
I know it seems simple but bootloader is unlocked and usb debugging is enabled? Also, are file extensions visible? That could cause problems too
Here's how I downgrade once in fastboot:
fastboot --slot=all flash bootloader bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after
Yeah - well I found the problem.
I was launching fastboot via "adb reboot fastboot" - which then put the phone in a screen which said "fastbootd" in red at the top. I'd never seen it before, but said fastboot so thought it was OK.
As soon as I remembered to reboot into fastboot with the volume down key - we're all good!
Never seen the fastbootd screen before - no idea what that was all about - I assume after installing Android 10/11 this was the new fastboot screen but clearly not!
Either way - I'm back on 9 and getting things back to normal. Systemless hosts is causing my grief with adblocker at the moment, but not investigated that too much.
So I guess the error message wasn't the right one, but just a generic one based on me not being in the right fastboot mode!
Thanks all for looking and offering advice, appreciate it - but I guess you'd never guess the issue with that error message!
the adb command is adb reboot bootloader. There may be others not sure, but that's the one I've used if the phone was on and booted.
Hi, up until recently I had crDroid on my phone, after not touching for a while and the rom being a bit corrupt, I decided to rollback to OOS.
To do this, I used some files I had of the OOS version that was on the phone before crDroid, went into fastbootd mode through the custom recovery of the crDroid ROM and became flashing images, it's a bit janky but I only wanted to get OOS working and booting to install a fresh OTA version of OOS through the settings. I ended up using the Oxygen updater app (or something like that, got it off the playstore) to have the OOS file to copy it to my PC where I would dump the payload into a folder to get the boot image and patch it with magisk.
Everything worked perfectly, I had root, OOS was running with no apparent big problems, but I wanted to try and flash TWRP, that's when crap hit the fan.
I was a bit worried about the process because I know TWRP can behave unpredictably but after I saw some posts of users who have android 12 OOS and TWRP I decided to try.
I downloaded the TWRP image from the official website on Oneplus 7 pro, chose the version for stock rom, Europe (I am from Israel, pretty sure I need EU image), opened up fastboot, typed:
Code:
fastboot boot <image file location>
, it was sending, the phone began booting, and nothing, it didnt boot up, stuck on the loading LOGO of Oneplus, so I tried a different version.
I tried the American version, still didnt work, and then tried the custom ROM > Europe version, and the phone booted to twrp, I wanted to check everything was alright, so I rebooted from the custom recovery to system, it reboot to recovery. I wasnt so surprised, had a few issues with TWRP in the past, so I went into TWRP and did the "flash current TWRP image" thing, and the phone still wouldnt boot to system, only the custom recovery. At that point, I gave up on a custom recovery, and tried to flash the boot image again, as from what I remember usually this fixes the custom recovery problems, got a bootloop, tried flashing the Magisk patched boot image, got a bootloop, tried flashing all the images I could (not critical partitions), of the OOS I had installed on the phone and still got a bootloop.
thought that maybe I need to flash everything, flashed all the images I could of crDroid to get to its custom recovery and enter fastbootd, flashed all of the OOS images except "reserve.img" which gave me:
"fastboot flash reserve '/run/media/android/2E5CD91E5CD8E21F/Utilities/notroot/payload_dumper-win64/payload_output/reserve.img'
Invalid sparse file format at header magic
Sending sparse 'reserve' 1/11 (262124 KB) OKAY [ 8.115s]
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed"
and Im still in a bootloop, never had a problem like this before, and I would love some help.
PS: Sorry for the long story, thought it would be essential for a real pro who would like to help me understand my poor phones situation.
Also, English isn't my first language so forgive me for a painful read.
Thanks in advance for any help.
Forgot to add, while trying to get to fastbootd, I read on the forum that you can do that with running in fastboot the following command:
fastboot reboot fastboot
after doing it the phone bootlooped again, and I got this message:
Code:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Hello,
I think you need to use the MSMDownloadTool to entirely reset your phone and restart from a fresh phone.
You will find informations here : https://forum.xda-developers.com/t/...a-gm21ba-collection-of-unbrick-tools.3956595/
Shalom and Happy Rosh Chodesh. Hebrew is not my first language, I believe you are better at inglet than I am at ivrit.
I agree with the above post, probably your only way out now. I think it started with your usage of the custom crDroid features as I am always wary of those 'custom' features on such a finicky device (as you found) as this. Compounded when trying to flash TWRP. So many have luck, but . . . . I have flashed more phones than I can count and for me the One Plus 7 Pro just does not like not being stock.