Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
***EDIT - FIXED, NOT SOLVED***: I'm still unsure what caused it in the first place, but I was able to regain root by flashing the October update, patching a new boot.img from that update, and then flashing. I was previously using the latest November update. I think that when I tried to flash the ROM something went wrong and it left things behind, and I don't think my original flash back to stock worked completely because flashing the October update took about 4 times as long. I used Pixel 5 unlocked stock images from Google's website for both attempts so im not sure why one worked and the other didn't, but I am rooted. If anyone else is experiencing similar issues, try flashing to a previous software update and rooting that.
this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/
grisly grizzly said:
Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
Click to expand...
Click to collapse
And you have usb debugging on
swangjang said:
this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/
Click to expand...
Click to collapse
Hey, Yes OEM Unlocking is on and greyed out. It was giving me the option to turn it off again before, not sure why it isn't now.
jaythenut said:
And you have usb debugging on
Click to expand...
Click to collapse
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.
grisly grizzly said:
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.
Click to expand...
Click to collapse
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img
jaythenut said:
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
I think I tried that last night, but I tried again just now with a new patched.img just in case. Flashed successfully but same problem. Here's my exact powershell input/output. For powershell I gotta use ./fastboot but its the same as running 'fastboot' in cmd. And I've using powershell with and without admin access.
HTML:
PS C:\platform-tools> ./fastboot flash boot_a ".\patched.img"
Sending 'boot_a' (98304 KB) OKAY [ 0.469s]
Writing 'boot_a' OKAY [ 1.993s]
Finished. Total time: 2.725s
PS C:\platform-tools> ./fastboot flash boot_b ".\patched.img"
Sending 'boot_b' (98304 KB) OKAY [ 0.469s]
Writing 'boot_b' OKAY [ 1.981s]
Finished. Total time: 2.713s
Just gets me back to the fast boot menu saying boot partition not found, just flashed the stock boot.img and I'm back at my home screen again. If its of any importance, I only had to flash the stock boot.img to slot a in order to get back to my home screen. Slot B should still be flashed with the patched.img, no root access on slot a though.
Edit: Do you think it would be helpful to relock the bootloader (since it returns everything to stock) and then re-unlock and re-root? Nevermind I forgot that re-locking makes it so you can't re-unlock. Won't do that.
how exactly did you flash the stock rom bc im lost on this process.... Heres where im at bc i cant get any help from the ProtonAOSP thread or anywhere. ive never flashed a rom without twrp and im lost now:
BC This is what ive been getting:
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot flash C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip
unknown partition 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
fastboot: error: cannot determine image filename for 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
and now this fof Fastboot boot ZipFile
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot boot C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1-gapps.zip
creating boot image...
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
but what im not understanding is do u unzip it to platform-tools and use flash-all, like reverting back to stock? bc this is what i get when i dont unzip it and just copy it to platform-tools directory from my downloads folder. this is my first time flashing a custom rom and i just cant seem to get anyone to tell me exactly what i need to do or what im doing wrong. PLEASE HELP
Related
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
CyrodiilSavior said:
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
Click to expand...
Click to collapse
First, you need to Relock your bootloader, Unroot, then S-ON your devide , Then flash RUU rom via Command in PC ( fastboot , ADB )
Finaly : if you want Flash a custom Rom , you should unlock bootloader , Root your HTC ONE , Flash recovery and then Flash custom Rom
Hope this can help you , sorry for my bad in english , I'm VietNamese
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
CyrodiilSavior said:
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
Click to expand...
Click to collapse
Make sure you're running it on a Windows 7 PC.
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
I'm sorry for not being more descriptive, I have a pretty strong background in linux and android but this issue has really stumped me.
CyrodiilSavior said:
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
Click to expand...
Click to collapse
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
StormyNight said:
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
Click to expand...
Click to collapse
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
CyrodiilSavior said:
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
Click to expand...
Click to collapse
Flash the latest radio/baseband founf HERE
BD619 said:
Flash the latest radio/baseband founf HERE
Click to expand...
Click to collapse
I didn't notice this till now but the sdcard is not mounting. I have the ability to mount it in recovery but when booted into system no luck. I am thinking reflashing a new boot.IMG would correct the issue.
Good news, I did an adb push and flashed the radio and that fixed it, I now can connect to sprint and my Sdcard is now mounting.
Thanks so much to everyone for the help. I really appreciate it!
I'm sure I'm going to get grilled about posting this, either posting it in the wrong area or about something that's "already been answered 1000 times." Don't care at this point because I've spent too much time googling and searching the forums and can't find an answer to my exact question.
Background: I have a Nexus 6 (obviously) with the stock firmware(encrypted) and stock recovery (I like it like this).
I maintain the latest updates by extracting the google factory image and flashing them individually (ie. fastboot flash bootloader bootloader.img, etc) and usually I end up booting up, then restarting into bootloader and using CF autoroot, extract the files and grab the root.img file, run fastboot boot root.img and I'm good to go. A while back (when marshmallow first came out) I couldn't get a CF autoroot (wasn't around yet) so I gave up on rooting for a while, which was very inconvenient but I a new father and just didn't have time to mess around with the chance I could lose my data.
Now... every month I update my nexus version to the latest the day after it's posted and I've noticed that chainfire is on top of things. I want to root my device (still OEM unlocked and stock firmware). I went to the autoroot website and the only version available is for N developer (which I'm not willing to chance yet since it's only alpha 1). My question is, I want to run fastboot boot root.img but I don't know if I can use the version posted for 6.01 or if I have to scour for an older version, any help would be greatly appreciated and if you've read this far I probably took up about 4 minutes of your time so thanks for that as well.
you need the newest version. google supersu beta, you'll find it right away. it think its like version 2.71 or 2.72 now. BTW, that one will also work on N. your alpha find is kinda old now
SuperSU doesn't help me as I can't extract an (.img)file from it. I've tried the newest beta of supersu running fastboot boot supersu.zip and it just locks the bootloader.
I am going to give you the steps, and stay short on details. So you will know what you need to do and can research the details.
You clearly know how to flash, you are 99 percent there.
Flash TWRP. You want custom recovery in case you muck it up plus having it will make step two easier. They are 3.02 I believe.
After TWRP is flashed copy Chainfires root over. Not the one step click to root stuff, you want his systemless root.
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Copy the zip to the phone, flash it with twrp.
Done.
Let me just start off by saying thank you for responding so fast. So I thought about twrp (and have used it a bunch in the past with my nexus 5 and 7)but I don't really need it for my every day and I believe it has to format userdata after its installed correct?
If you don't want to install TWRP you can run it using "fastboot boot [image.img]". From there you can install the SuperSU beta. I'm however not aware of userdata needing to be formatted after installing TWRP.
I agree with Strephon, since I've done exactly that myself. Download the latest TWRP for your device, copy it to the ADB/fastboot folder, rename it to twrp.img, and then fastboot boot twrp.img. You'll have TWRP for that session only, allowing you to install SuperSU. When you reboot, you'll be back to normal recovery. Since this works purely on the recovery, (I guess it doesn't even touch the recovery partition?) it doesn't affect user data.
Though I don't know why you wouldn't want to keep TWRP...? I'm sure there's a reason I haven't thought of - maybe for taking OTAs?
firestarter44 said:
Let me just start off by saying thank you for responding so fast. So I thought about twrp (and have used it a bunch in the past with my nexus 5 and 7)but I don't really need it for my every day and I believe it has to format userdata after its installed correct?
Click to expand...
Click to collapse
TWRP does not erase user data.
fastboot flash recovery recoveryname.img replaces your recovery
fastboot boot recovery recoveryname.img lets you use twrp recovery until you reboot, wont replace stock recovery
and twrp doesnt erase nor format user data, unless you do it yourself, manually.
simms22, you spooked me enough to make me check with my Nexus in a CMD window.
D:\ADB>fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
D:\ADB>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
OKAY [ 0.116s]
finished. total time: 0.701s
But the flash command does need the keyword "recovery".
dahawthorne said:
simms22, you spooked me enough to make me check with my Nexus in a CMD window.
D:\ADB>fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
D:\ADB>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
OKAY [ 0.116s]
finished. total time: 0.701s
But the flash command does need the keyword "recovery".
Click to expand...
Click to collapse
oddness! with the version of fastboot im using on my work computer, i need to use recovery with boot or it doesnt work.
Hey guys, I've decided I'm going to root my Moto X Unlocked Edition. I've been following this guide: http://www.theandroidsoul.com/2014-moto-x-2nd-gen-marshmallow-root-86348/ (as well as many others) and I'm running into issue after issue.
I've managed to unlock my bootloader. I'm on step 8: "fastboot flash boot boot.img" and have tried with so many techniques but keep getting this "mismatched partition size (boot)" error after each attempt. I've tried using .img files from CMod, from the guide that I'm following, etc. I've googled the error with no useful result coming up. I'm at a loss here and really hoping someone is able to help me out. Searching is turning up nothing and I'm about to start tugging at my hair. If anyone has a one click installer that would work, please pass it along!
Thank you all very much!
Edit 4/29/16 13:01 ET: I've switched from trying to use the 'fastboot flash boot' command and started trying to use 'fastboot update <romname.zip >' with various different ROMs. I'm getting this error.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I'm not sure what to do now. I feel like I'm getting reckless in trying an overwhelming amount of solutions to no avail. I'm going to wait, now. I'm starting to think that these phones can't be rooted or flashed with a new ROM.
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Thank you for the help @viper74656!
I'm struggling to even get the TWRP installed. When I try to install TWRP-3.0.0-0-victara.img, I get
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:0096c000
cmd: flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I was having this problem earlier too when I was trying to work around that. I'm going to try an alternate way of installing TWRP.
Really, all I want to do is get CMod. When I rooted my HTC Inspire 4G, it was a cakewalk... I didn't expect all this LOL
viper74656 said:
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Click to expand...
Click to collapse
Yeah, btw, I have an xXT1095
So I managed to get TWRP installed on my XT1095 using the "WinDroid" toolkit I found somewhere on XDA. It seems to push the right fastboot commands, but I had to manually download and select an older TWRP version. Read something about our recovery partition not working with the newer versions. I still got the mismatch error, but when I rebooted into recovery TWRP was there.
I haven't ventured back to try it again after having to wipe and start over...bleh.
Twrp manager (from the playstore) is what I had to use to install recovery. Windroid wouldn't push it for some reason.
Sent from my XT1096 using XDA-Developers mobile app
Hey everyone,
I rooted with the Magisk guide and patched the boot.img etc.... but it was annoying every time there is an OTA so I flashed all the stock firmware via ADB and everything went well, I rebooted and no longer have root. This is with the December image. So now I'm stock and I tried to apply OTA via 'settings' but I am STILL getting the error of "Couldn't Update: Installation Problem".
Any ideas what to do?
CheatingOutlaw said:
Hey everyone,
I rooted with the Magisk guide and patched the boot.img etc.... but it was annoying every time there is an OTA so I flashed all the stock firmware via ADB and everything went well, I rebooted and no longer have root. This is with the December image. So now I'm stock and I tried to apply OTA via 'settings' but I am STILL getting the error of "Couldn't Update: Installation Problem".
Any ideas what to do?
Click to expand...
Click to collapse
If you flashed stock December, why didn't you just flash stock January?
Since OTA isn't working, you would just need to flash stock January anyway...
ilal2ielli said:
If you flashed stock December, why didn't you just flash stock January?
Since OTA isn't working, you would just need to flash stock January anyway...
Click to expand...
Click to collapse
You're absolutely right. I was just thinking that now. But I was also wondering how I can get OTA working again because I travel for work and don't always have access to a PC. Thank you for the response.
CheatingOutlaw said:
You're absolutely right. I was just thinking that now. But I was also wondering how I can get OTA working again because I travel for work and don't always have access to a PC. Thank you for the response.
Click to expand...
Click to collapse
I haven't seen too many people successfully do the OTA method. I tried it and couldn't get it to work properly either. Someone said you need to have stock dtbo too (for those that flash custom kernels), but since you can't flash the dtbo through an app (like FKM or EXKM), then there's no point to the OTA method.
ilal2ielli said:
I haven't seen too many people successfully do the OTA method. I tried it and couldn't get it to work properly either. Someone said you need to have stock dtbo too (for those that flash custom kernels), but since you can't flash the dtbo through an app (like FKM or EXKM), then there's no point to the OTA method.
Click to expand...
Click to collapse
I flashed the whole January firmware but after rebooting the phone the build number is still showing as December?!
CheatingOutlaw said:
I flashed the whole January firmware but after rebooting the phone the build number is still showing as December?!
Click to expand...
Click to collapse
Probably a long shot, but did you use the correct version per your carrier?
I'm sure you did, so I would change slots and fastboot it again. fastboot --set-active=a or b
Depending on which slot your on of course :good:
CheatingOutlaw said:
I flashed the whole January firmware but after rebooting the phone the build number is still showing as December?!
Click to expand...
Click to collapse
What he said!
Badger50 said:
Probably a long shot, but did you use the correct version per your carrier?
I'm sure you did, so I would change slots and fastboot it again. fastboot --set-active=a or b
Depending on which slot your on of course :good:
Click to expand...
Click to collapse
writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.933s
Press any key to exit...
This is the error I receive after trying to flash-all. Really weird.
Every time I had to go back to stock I used the sideload method.
Best way IMO to fresh start, best way to relock bootloader though.
Good luck
CheatingOutlaw said:
writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.933s
Press any key to exit...
This is the error I receive after trying to flash-all. Really weird.
Click to expand...
Click to collapse
Try different cable and USB ports :good:
open the flashall.bat and remove the -w from the command. the flash factory resets the device.
It's still failing to flash the firmware via Minimal ADB and Fastboot. I've been trying to flash the factory image, not the OTA, from here:
https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
After extracting the stock firmware from the ZIP, I have a few files but also another ZIP which I did not extract. Maybe I must extract that too? I kept them in the root installation of ADB where you run the cmd from.
I've tried using another cable and USB port, doesn't work. I tried flashing to partition B not A, but I just get a bootloop until I switch back to A. But no matter what, I keep getting the error of:
"writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.914s
Press any key to exit..."
CheatingOutlaw said:
It's still failing to flash the firmware via Minimal ADB and Fastboot. I've been trying to flash the factory image, not the OTA, from here:
https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
After extracting the stock firmware from the ZIP, I have a few files but also another ZIP which I did not extract. Maybe I must extract that too? I kept them in the root installation of ADB where you run the cmd from.
I've tried using another cable and USB port, doesn't work. I tried flashing to partition B not A, but I just get a bootloop until I switch back to A. But no matter what, I keep getting the error of:
"writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.914s
Press any key to exit..."
Click to expand...
Click to collapse
Get rid of minimal adb and just use platform-tools :good:
Badger50 said:
Get rid of minimal adb and just use platform-tools :good:
Click to expand...
Click to collapse
No refernce to minimal adb in the guide he posted.
Badger50 said:
Get rid of minimal adb and just use platform-tools :good:
Click to expand...
Click to collapse
SUCCESS!!! I will explain the simple and easily overlooked stupidity that got me into this situation, so others can read:
Minimal ADB and Fastboot DID work previously for the December stock firmware (if i can recall?). I don't think it was working for January in this case.
Also, I tried using the platform tools previously today and after opening windows powershell within the root folder, I just got red text and absolutely nothing worked. After a few hours today, somehow the powershell opened and did NOT show all red text this time. Input commands responded when I typed "adb devices" and I was like AHAAA!! For me, there was no need to download Android SDK or any of that. Only Platform Tools was required.
CheatingOutlaw said:
SUCCESS!!! I will explain the simple and easily overlooked stupidity that got me into this situation, so others can read:
Minimal ADB and Fastboot DID work previously for the December stock firmware (if i can recall?). I don't think it was working for January in this case.
Also, I tried using the platform tools previously today and after opening windows powershell within the root folder, I just got red text and absolutely nothing worked. After a few hours today, somehow the powershell opened and did NOT show all red text this time. Input commands responded when I typed "adb devices" and I was like AHAAA!! For me, there was no need to download Android SDK or any of that. Only Platform Tools was required.
Click to expand...
Click to collapse
Glad you got it working.
CheatingOutlaw said:
SUCCESS!!! I will explain the simple and easily overlooked stupidity that got me into this situation, so others can read:
Minimal ADB and Fastboot DID work previously for the December stock firmware (if i can recall?). I don't think it was working for January in this case.
Also, I tried using the platform tools previously today and after opening windows powershell within the root folder, I just got red text and absolutely nothing worked. After a few hours today, somehow the powershell opened and did NOT show all red text this time. Input commands responded when I typed "adb devices" and I was like AHAAA!! For me, there was no need to download Android SDK or any of that. Only Platform Tools was required.
Click to expand...
Click to collapse
The IDE (Android Studio) is just nice to have for easyish updating (open Android studio, hit update notification, done!) and it's emulator, otherwise if not using at least 2 out of those 3 it's probably not worth the extra disk space, platform tools and manually checking for updates is the other official (directly handed out by Google) option.
Phoenix591 said:
The IDE (Android Studio) is just nice to have for easyish updating (open Android studio, hit update notification, done!) and it's emulator, otherwise if not using at least 2 out of those 3 it's probably not worth the extra disk space, platform tools and manually checking for updates is the other official (directly handed out by Google) option.
Click to expand...
Click to collapse
Or, he can check the thread he posted for all the latest updates.
CheatingOutlaw said:
writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.933s
Press any key to exit...
This is the error I receive after trying to flash-all. Really weird.
Click to expand...
Click to collapse
Your ADB files are outdated, you must update to the latest version. I initially ran into the same issue when I got my P4 XL back in November.
I've tried flashing 3 different roms.
1)A different version of the stock Android 11 from Google Image Libary. (I got an unlocked phone, and haven't been able to get 5g on it as I should. I was trying to download the verizon version of the rom to see if this may help).
2)Android 12 Dev Preview
3)Lineage 18.1
I have all the prerequisites --
-bootloader unlocked
-latest adb/fastboot
-latest drivers
I've tried flashing with the Flash-All command. It flashes the bootloader, then the radio, but then when it gets to the meat of the it... it starts throwing "archive does not contain dbto.sig" and all the images within. When it gets to the system sparse, it says something about unable to find the partition. Then fails and closes out.
I realized I was using plain fastboot, so I switched to fastbootd. (which by the way, fastboot reboot fastboot doesn't work either).
Switching to fastbootd, everything begins as normal just like the other method I tried. And then after it flashes the bootloader, it reboots to plain fastboot. Not D. And once again, all the errors are present.
I searched and found that I should just bypass the flash-all script and flash it manually line by line, image by image. So I tried that. Boot.img flashes successfully. But when I flash anything else I get a FAILED: No such file or directory. This is true whether I'm in fastboot or fastbootd.
This pretty much holds true, no matter what version of the rom I'm installing.
With lineage 18.1, when I try to flash the recovery --
sending 'recovery' (98304 KB)...
OKAY [ 2.500s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Again, happens in fastbootd and fastboot.
What am I doing wrong? I know its something so simple here. Its been a while since I did anything like this, so please take it easy on me. lol
flashing unlock returns "bootloader is already unlocked". unlock_critical returns failed: invalid argument. And at this point, thats exactly what I'm doing -- arguing with it. So far, its winning.
Help me please.
bubbyj said:
I've tried flashing 3 different roms.
1)A different version of the stock Android 11 from Google Image Libary. (I got an unlocked phone, and haven't been able to get 5g on it as I should. I was trying to download the verizon version of the rom to see if this may help).
2)Android 12 Dev Preview
3)Lineage 18.1
I have all the prerequisites --
-bootloader unlocked
-latest adb/fastboot
-latest drivers
I've tried flashing with the Flash-All command. It flashes the bootloader, then the radio, but then when it gets to the meat of the it... it starts throwing "archive does not contain dbto.sig" and all the images within. When it gets to the system sparse, it says something about unable to find the partition. Then fails and closes out.
I realized I was using plain fastboot, so I switched to fastbootd. (which by the way, fastboot reboot fastboot doesn't work either).
Switching to fastbootd, everything begins as normal just like the other method I tried. And then after it flashes the bootloader, it reboots to plain fastboot. Not D. And once again, all the errors are present.
I searched and found that I should just bypass the flash-all script and flash it manually line by line, image by image. So I tried that. Boot.img flashes successfully. But when I flash anything else I get a FAILED: No such file or directory. This is true whether I'm in fastboot or fastbootd.
This pretty much holds true, no matter what version of the rom I'm installing.
With lineage 18.1, when I try to flash the recovery --
sending 'recovery' (98304 KB)...
OKAY [ 2.500s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Again, happens in fastbootd and fastboot.
What am I doing wrong? I know its something so simple here. Its been a while since I did anything like this, so please take it easy on me. lol
flashing unlock returns "bootloader is already unlocked". unlock_critical returns failed: invalid argument. And at this point, thats exactly what I'm doing -- arguing with it. So far, its winning.
Help me please.
Click to expand...
Click to collapse
Odd things like this are almost always related to the adb/fastboot version. Where did you get the ones you're using?
If you can't simply do
Code:
adb reboot bootloader
fastboot flash <destination> <source.img>
Your bootloader is locked or adb/fastboot is likely incorrect/old. What does:
Code:
fastboot --version
report?
If you're just trying to get something flashed and you can get adb to respond you could use the website flashing tool from Google. It's the "flash" link next to download when selecting the firmware. I've used it when in crisis and it's changed up my issues nicely, even when I flashed a magisk module that was for a newer os version than what I had installed. Took a bit but it did eventually flash the latest monthly update and disabled magisk in the process.
Thanks for the replies. I had the 'latest ADB/Fastboot" -- but it was the minimal adb/fastboot. And while I confirmed its the 'latest' update -- it was still from 2018! haha. I used it recently to flash my G Stylus/Pro, no issues at all. However, the Pixel 4a 5g (I know this is the Pixel 5 forum, please forgive me), simply wouldn't utilize it.
I downloaded a build from summer 2020 that I found, and it cleared it up. However, I still got the dtso.sig (xxxxx.sig missing). But it still yet installed and worked perfectly.
I appreciate your alls help, truly.
bubbyj said:
Thanks for the replies. I had the 'latest ADB/Fastboot" -- but it was the minimal adb/fastboot. And while I confirmed its the 'latest' update -- it was still from 2018! haha. I used it recently to flash my G Stylus/Pro, no issues at all. However, the Pixel 4a 5g (I know this is the Pixel 5 forum, please forgive me), simply wouldn't utilize it.
I downloaded a build from summer 2020 that I found, and it cleared it up. However, I still got the dtso.sig (xxxxx.sig missing). But it still yet installed and worked perfectly.
I appreciate your alls help, truly.
Click to expand...
Click to collapse
Here you can download the latest SDK Platform-Tools. The latest release was in April 2021. Use this instead:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Thanks again to everyone who chimed in. You all solved my problems, and I'm super grateful. Have a blessed day! I'm sure I'll be back for more help in the future lol