I unlocked the bootloader and rooted with Magisk following this guide: https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Since than my phone is stuck on the Google boot screen.
I'm able to get the phone into fastboot mode and initiate 'fastboot update image' or 'flash-all.bat' unfortunately the restore fails every time on this step: Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
I'm out of options and pretty desperate, please help!
I'm using a Pixel 3 64GB (unlocked EU edition), Laptop is on Windows 10. The phone and laptop are connected with the stock USB-C cable.
luzero said:
I unlocked the bootloader and rooted with Magisk following this guide: https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Since than my phone is stuck on the Google boot screen.
I'm able to get the phone into fastboot mode and initiate 'fastboot update image' or 'flash-all.bat' unfortunately the restore fails every time on this step: Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
I'm out of options and pretty desperate, please help!
I'm using a Pixel 3 64GB (unlocked EU edition), Laptop is on Windows 10. The phone and laptop are connected with the stock USB-C cable.
Click to expand...
Click to collapse
Flash the stock boot image to both slots with fastboot. You can extract it from the factory image you downloaded.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
robocuff said:
Flash the stock boot image to both slots with fastboot. You can extract it from the factory image you downloaded.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Hi Robocuff,
Thank you for your suggestion.
I successfully managed to perform the boot_a and boot_b flash. Afterwards I restarted my device and retried to fastboot the original image and again the process fails with the same error. (Vendor_A FAILED (Error reading sparse file).
Any suggestions how to restore the device? And safe my day ?
luzero said:
Hi Robocuff,
Thank you for your suggestion.
I successfully managed to perform the boot_a and boot_b flash. Afterwards I restarted my device and retried to fastboot the original image and again the process fails with the same error. (Vendor_A FAILED (Error reading sparse file).
Any suggestions how to restore the device? And safe my day [emoji4]
Click to expand...
Click to collapse
Do you have the latest sdk tools, fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
luzero said:
Hi Robocuff,
Thank you for your suggestion.
I successfully managed to perform the boot_a and boot_b flash. Afterwards I restarted my device and retried to fastboot the original image and again the process fails with the same error. (Vendor_A FAILED (Error reading sparse file).
Any suggestions how to restore the device? And safe my day ?
Click to expand...
Click to collapse
Did the boot flashes complete successfully? If so, did you allow the phone to attempt to boot to the OS after you restarted it or did you just reboot directly to fastboot mode? Flashing the stock bootloader should have fixed the issue of the phone not booting. That said, if it still won't boot after flashing the stock bootloader, make sure your fastboot files are up to date. Outdated files can cause issues like you're having while flashing the factory image. You can get the latest files here. If that doesn't do it, try a different usb port. Also cables can sometimes be a problem so you might want to try another cable also.
Flashing the stock boot image to both slots, boot_a and boot_b should solve the problem. I don't think it's a bootloader issue. The boot image includes the stock recovery as well as the kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Yes the boot flashes where performed successfully and I tried to start the device. I just redid the boot flashes and waited longer to double check if I was too impatient.
Yesterday I downloaded the latest files of everything as linked in the above referred to Magisk flash guide on xda developers.
Later tonight I will try to redonwload all the latest files and double check everything.
I only have one usb type c port on my laptop. I will also try the regular USB port to.
Thank you all for your contributions. Really appreciated!
jd1639 said:
Flashing the stock boot image to both slots, boot_a and boot_b should solve the problem. I don't think it's a bootloader issue. The boot image includes the stock recovery as well as the kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You mean:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
I tried and although successful unfortunately still stuck at the google logo.
luzero said:
You mean:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
I tried and although successful unfortunately still stuck at the google logo.
Click to expand...
Click to collapse
Try flashing the system image. Again, to both slots like you did for the boot image, which you did correctly.
Sent from my [device_name] using XDA-Developers Legacy app
It's working again! Thank you so much guys.
In the end I managed to run flash-all using an USB type a to c cable.
Really appreciated your advise!
luzero said:
It's working again! Thank you so much guys.
In the end I managed to run flash-all using an USB type a to c cable.
Really appreciated your advise!
Click to expand...
Click to collapse
Glad to hear you got it up and running again.
What's "flash all?"
BrickMe?Naw said:
What's "flash all?"
Click to expand...
Click to collapse
flash-all is the batch file included with the full image .zip. Ran from a command prompt it reinstalls the image. Deleting the -w (for wipe) from the text file and saving/running will keep the user files, apps etc. intact while installing.
BrickMe?Naw said:
What's "flash all?"
Click to expand...
Click to collapse
Here you find an easy guide to explain the appropriate steps:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
luzero said:
It's working again! Thank you so much guys.
In the end I managed to run flash-all using an USB type a to c cable.
Really appreciated your advise!
Click to expand...
Click to collapse
I am experiencing this same issue and unfortunately this did not work for me.
I am using the latest SDK tools, have tried two different cables in two different USB ports and always have a flash-all fail at the exact same step as the OP.
Anyone have any other suggestions I can try?
BluhmJA said:
I am experiencing this same issue and unfortunately this did not work for me.
I am using the latest SDK tools, have tried two different cables in two different USB ports and always have a flash-all fail at the exact same step as the OP.
Anyone have any other suggestions I can try?
Click to expand...
Click to collapse
I had the same problem and fixed it specifically by switching to a slower USB 2 port. I guess the USB 3 was exposing a timing bug?
Related
So I had an old Nexus 5 running a custom KK rom. I tried getting it back to stock using Wugs Toolkit. I've been playing with it for hours trying to get it to work. I ended up making it worse and it gets stuck on Google Logo now. I tried using the revert to stock option on the toolkit. It looks like everything is working.. Here is the log..
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: hammerhead
finished. total time: 0.001s
Launching flashstock.bat
and then it just stops.. I tried downloaded two seperate .tgz images from Google. They both do the same thing. It doesn't go out of the bootloader screen or anything. It writes the radios and that's about it.
This is a *very* high-level suggestion - there are many tutorials that take you through drivers/ADB, etc. I just want to give you the script I followed for the manual procedure, which turned out to be extremely quick and simple.
After suggesting Wugfresh's NRT to several people in these forums (I'm a very big fan) I decided to refresh my Nexus 6 with the latest image and make it unencrypted - a problem that doesn't exist on the N5. I wasn't sure that NRT would do this for me, since the script automatically restarts the device and I wanted to be sure that it didn't start before I had flashed a modified no-encrypt boot image, since it would just encrypt itself again. So I downloaded the factory image, a no-encrypt boot image (thanks, doitright ) and TWRP - naturally being very careful to get the right ones. I unzipped the TGZ and the image files down to their final *.img components. To make things simple I renamed the various images to one-word names (e.g. radio.img). I put all of them in the same directory as ADB & fastboot.
Since all Nexus devices are updated the same, this should also work for you. Since you've used NRT I'm guessing that you have the PC drivers already installed. You'll also need ADB/Fastboot. Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Some of these may be overkill (I believe the -w wipe command erases userdata anyway), but it worked for me.
I would say take a TWRP image first as well so that you can recover, but it sounds as if you have nothing to recover anyway.
If the more expert member want to suggest amendments to the script, I won't be insulted...
dahawthorne said:
Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
USB debugging means nothing if you're trying to use fastboot.
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
gregs1213, stop using a toolkit, since you don't know what you're doing. read the above link and the following one as well:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
dahawthorne said:
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
Click to expand...
Click to collapse
Hey, sure, I didn't mean to "attack" you. I noticed that you wanted to help. Really. Thanked you for that.
No worries, beekay. Posts don't allways mean what they look like, which is why we have smilies.
And I did read the articles. I tried with my N6 to attach it in bootloader mode with no USB debugging, and you're absolutely right. I suppose I just read "Remember to switch on USB debugging" so often that I assumed it was needed for any sort of work. Thanks for the tip. It's things like this that encourage all of us to try new things - like flashing a ROM manually instead of with NRT...
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
mraramesh said:
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
Click to expand...
Click to collapse
Toolkits don't teach people stuff, they just hide it from them
mraramesh said:
The problem is Wugfresh NRT
Click to expand...
Click to collapse
I edited your post to show you the error of your ways
Sent from my Xperia z5 using Tapatalk
While replying to another thread asking for help in installing a ROM, I linked to this, and I notice that the OP never did tell us if he managed to get his device working. Feedback is not only helpful to the forum, it's also polite.
So bump for gregs1213's attention...
boys please can u write me steps to flash patched boot. img with fastboot? thank you (european model)
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
flas patched boot image
Slok 00 said:
boys please can u write me steps to flash patched boot. img with fastboot? thank you (european model)
Click to expand...
Click to collapse
If you flash Magisk from your sd-card, the boot.img is automatically patched by magisk.
Root HTC U11+ European model software number 1.10.401.23
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2) boot.img is automatically patched
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
milesd said:
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
Click to expand...
Click to collapse
I have unlocked my U11+ via htcdev.com
I have extracted the boot.img from my RUU
I have installed MagiskManager and patched boot.img
I am having problems flashing the patched_boot.img file ..
I boot to download mode and fastboot flash fails .. see below..
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
Can anyone help please!!
I am presently on 2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_India_SEA_1.24.400.2_Radio_8998-002772-1712011153_release_519104_signed_2_4
I boot to download mode and fastboot flash fails .. see below..
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
Can anyone help please!!
Click to expand...
Click to collapse
Try to get a newer htc-fastboot
milesd said:
Try to get a newer htc-fastboot
Click to expand...
Click to collapse
I have tried the fastboot bundled with HTC Sync Manager v3.1.88.3 as well as using the fastboot from platform-tools-v27.0.1-windows but no joy
AFIK there are the latest of the HTC one and the SDK one.
Should also point out I cannot flash the twrp recovery image either.. same error
---------- Post added at 10:56 PM ---------- Previous post was at 10:11 PM ----------
Another thing to mention is that I can erase the partitions without problem using fastboot erase but cannot flash any partitions. The only way I can restore the partitions is to reflash the RUU by putting the RUU zip o the SD card.
I wonder if there is an issue having the 128G sd card in the phone. Will try again tomorrow without the SD card inserted.
The CID's are HTC__060.
You are enable oem unlock in developer option?
Test the connectivity using the following command (provided your phone screen is unlocked)
adb devices
--------------------------------------------------------------------------------------------------------------------------
I think you must rename file patch_boot.img to boot.img
cmd: fastboot flash boot boot.img
newyesor said:
You are enable oem unlock in developer option?
Test the connectivity using the following command (provided your phone screen is unlocked)
adb devices
--------------------------------------------------------------------------------------------------------------------------
I think you must rename file patch_boot.img to boot.img
cmd: fastboot flash boot boot.img
Click to expand...
Click to collapse
I am not new to unlocking and rooting HTC phones I have been doing this since the beginning .. I had an original O2 XDA phone
The phone bootloader is unlocked 100% did it via htcdev and the bootloader screen on both phones says unlocked. There is no issue with connectivity either, adb devices shows the connected phone and other adb commands work fine .. as I said I can even fastboot erase partitions, but am unable to flash them...
I am now thinking it might be my drivers as I am using the windows drivers that came with the latest HTC Sync manager. Later today or tomorrow I might try uninstalling them and using the Universal Naked or the Universal ADB drivers..
Sidewindr said:
I am not new to unlocking and rooting HTC phones I have been doing this since the beginning .. I had an original O2 XDA phone
The phone bootloader is unlocked 100% did it via htcdev and the bootloader screen on both phones says unlocked. There is no issue with connectivity either, adb devices shows the connected phone and other adb commands work fine .. as I said I can even fastboot erase partitions, but am unable to flash them...
I am now thinking it might be my drivers as I am using the windows drivers that came with the latest HTC Sync manager. Later today or tomorrow I might try uninstalling them and using the Universal Naked or the Universal ADB drivers..
Click to expand...
Click to collapse
Have you tried flashing with
fastboot flash boot YOUR_DIRECTORY / patched_boot.img
Just an idea....
Yes tried absolute and relative paths.
Sent from my HTC One M8 using Tapatalk
Switch to another usb port and/or try with another usb cable
https://plus.google.com/+ArtemRussakovskii/posts/RwJ28EdYgCb
https://www.youtube.com/watch?v=5Omhpv7oYdc
Problem solved ... Tried it again after reboot and on a different USB port and it worked .. odd ..
Patched
milesd said:
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
Click to expand...
Click to collapse
HI I would just like to clarify before I try the download mode.
I have been trying to patch the magisk patched_boot.img in bootloader mode on a HTC U11 with no joy.
This is the error I receive
PS E:\HTC\ADB tools with latest twrp.img Use this one 2019\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boot' (37589 KB)...
OKAY [ 0.915s]
writing 'boot'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.924s
Is it safe to patch in the download mode as stated?
Thanks
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
i allways getting this massage when i try to flash the magisk boot img via fastboot.
what is wrong?
hyundai2010 said:
i allways getting this massage when i try to flash the magisk boot img via fastboot.
what is wrong?
Click to expand...
Click to collapse
Make sure you have the latest fastboot driver's installed.
Did this work?
Hi, did you find a resolve?
I have the latest drivers and nothing seams to work. Tried 5 windows 10 computers with the same result. No partition.
It has to be something with fastboot or the boot image. Well, I guess your phone could be toasted as well. What happens with "fastboot flash boot boot.img" if you use the stock image?
wangdaning said:
It has to be something with fastboot or the boot image. Well, I guess your phone could be toasted as well. What happens with "fastboot flash boot boot.img" if you use the stock image?
Click to expand...
Click to collapse
Any solution to this? Stock boot.img returns error: cannot load 'boot.img'
I just updated to the latest Pixel 3 image (blueline-qq2a.200405.005). Removed the -w from the .bat file and had no issue with the update. Now trying to root and I can't boot TWRP from the bootloader. See below output.
C:\adb>adb reboot bootloader
C:\adb>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.551s]
Booting FAILED (Status read failed (Too many open files in system))
fastboot: error: Command failed
I have updated google drivers, downloaded latest fastboot and adb files. Any idea's what I am doing wrong?
I don't think TWRP is working for our phone right now. You have to extract the boot.img from the factory image you downloaded and patch it with Magisk. Then flash the patched boot.img using fastboot.
robocuff said:
I don't think TWRP is working for our phone right now. You have to extract the boot.img from the factory image you downloaded and patch it with Magisk. Then flash the patched boot.img using fastboot.
Click to expand...
Click to collapse
Thank you for that, so I opened Magisk app and downloaded the latest. I copied boot.img from inside image-blueline-qq2a.200405.005.zip and copied it to the phones storage. I used the app to patch the boot.img then copied that to the phones storage. adb reboot bootloader then ran the command fastboot flash boot boot.img. My phone then wouldn't boot . I reran the flash-all.bat to get back in. What did I do wrong?
Nevermind, I got it. It's always an adventure when I update my phone for some reason . Thank you so much for your input!
Shawn haz root said:
Nevermind, I got it. It's always an adventure when I update my phone for some reason . Thank you so much for your input!
Click to expand...
Click to collapse
Not sure what you did wrong but the next time you flash a patched boot image and it won't boot, there's no need to flash the whole system image again. All you need to do is flash the boot.img that comes with the system image using fastboot. I've run into the same problem a couple times in the past and flashing the factory boot.img always got me going again.