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.
Related
Help Me!! How to delete cupcake from g1???????
or
Reset phone to factory settings like i just got it from t-mobile.
today i updated and tried the cupcake.
now i wanna go back to my previous status.
i had root access, auto rotate, multi touch, custom splash n boot image amd a theme.
right now i have the custom splash n boot image and cupcake.
Can someone help me.
i have tried to go through fastboot and use fastboot to update <update.zip> but no matter what file i use it says it's unable to load it.
also in fast boot i tried to
commands(after cd-ing to your folder):
fastboot erase boot
fastboot erase recovery
fastboot boot kernel ramdisk.img
fastboot reboot (or press send menu end)
fastboot flash:raw boot kernel ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
that worked to install cupcake but when i use
fastboot flash:raw boot kernel ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
it gets stuck at
fastboot flash system system.img
or
fastboot flash userdata userdata.img.
can someone help me
just install the rc29 DREAMIMG.nbh in fastboot... then just update your phone with regular updates......
btw here is a link for the rc29
i tried .....
i made sure my dream was in fastboot
i than wrote in cmd
C:\Documents and Settings\*****>fastboot update DREAIMG.nbh
error: failed to load 'DREAIMG.nbh'
**
maybe the DREAIMG.nbh which is 89,419 kb is a bad file???
or i'm just doing something wrong
i think its working now ...
its updatting in progress now
yeay
sorry i didnt explain myself correctly.... download the DREAIMG.nbh... copy the file to your sdcard (make sure its formatted to fat32).... then boot your phone to the bootloader... (turn it off and turn it back on by pressing camera+power).... then install the file....
Make sure you rename it to DREAIMG.NBH
soloxp said:
Make sure you rename it to DREAIMG.NBH
Click to expand...
Click to collapse
right now i,m just trying to get mt g1 to the way i had it
but know its acting up...
i had a similiar issue and i just went to here:
http://forum.xda-developers.com/showthread.php?t=442480
and followed the first part of the instructions to get the phone back down to rc29 and then everything worked fine
imponfire said:
i had a similiar issue and i just went to here:
http://forum.xda-developers.com/showthread.php?t=442480
and followed the first part of the instructions to get the phone back down to rc29 and then everything worked fine
Click to expand...
Click to collapse
ty ty but i already fixed it
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
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?
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
vorsprungtechnik said:
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
Click to expand...
Click to collapse
Doesn't work yet, don't think it will for a while because fastboot has changed apparently.
The guy who makes the OP7 port has it baked in, but it's not encrypted
brashmadcap said:
Doesn't work yet, don't think it will for a while because fastboot has changed apparently.
The guy who makes the OP7 port has it baked in, but it's not encrypted
Click to expand...
Click to collapse
Ok thanks. So there's no way to possibly root the new ROM at the moment?
Flash patched boot.img via fastboot. Just becarful with magisk modules at the moment.
Bradl79 said:
Flash patched boot.img via fastboot. Just becarful with magisk modules at the moment.
Click to expand...
Click to collapse
Can you elaborate on this? The part about being careful with modules? I got magisk working, and I'm using 2 modules, YT Vanced and Google Dialer framework.
When should I be careful? When there is a new update for the A10 beta? Or just on how many modules you install, or which ones?
Thanks
Meaning if u go into a bootloop u r pretty much screwed without a twrp, there is no way to remove the module.
Deleted, wrong post
ArkAngel06 said:
Can you elaborate on this? The part about being careful with modules? I got magisk working, and I'm using 2 modules, YT Vanced and Google Dialer framework.
When should I be careful? When there is a new update for the A10 beta? Or just on how many modules you install, or which ones?
Thanks
Click to expand...
Click to collapse
Just be smart. Use stuff that doesn't fundementally alter things (framework mods, etc.). FDE is updated, Vanced works, stuff like call recorder, fonts etc. should be fine. I'd avoid audio mods (directories might have changed idk) and things like auto brightness fix (framework mods).
---------- Post added at 02:22 AM ---------- Previous post was at 02:20 AM ----------
vorsprungtechnik said:
Ok thanks. So there's no way to possibly root the new ROM at the moment?
Click to expand...
Click to collapse
Updating from rooted OOS Pie, flash magisk through manager to inactive slot before reboot after OTA finished. Worked for me.
Of course I don't have any recovery at all so we will see how that goes three days from now when I install something crazy
vorsprungtechnik said:
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
Click to expand...
Click to collapse
I fixed this on the op6 by doing this:
Note: On Windows systems, thanks to a bug in fastboot, you must first swap to slot a with fastboot set_active a, then specify slot a when flashing images, e.g. fastboot flash boot_a <recovery_filename>.img
(from lineageos install site)
however after this was a success i'm now stuck on the 1+ fastboot splash screen and it never actually goes to recovery. Hopefully you've figured it out by now but I came across your post a few times while I was looking for the solution myself
So, i bumped into this the other day, what i did was, flash the full Android 10 fastboot rom using the op6 aio tool, then, using fastboot I flashed twrp the one from mauronofrio, then from twrp without wiping anything, I flashed the stock boot.img, then the twrp installer again from mauronofrio and voila, twrp working, I also flashed magisk after the first boot, this is all in the fool proof guide in the guides subforum
any update on this? just updated to OOS 10.3.2 and cant boot into twrp anymore. All I want is to have twrp...any way to roll back to android 9?
I have been using this method to flash new stock update every month to my rooted pixel 4a.
Steps I follow:
- Download the factory image of the last month
- Extract the boot.img. And patch it using magisk canary build
- Move the boot.img to the computer and flash it in fastboot mode
- flash the complete image
- Reroot the phone using magisk
This time with January update, I am getting stuck on step 3. Everytime I try to flash the bootloader image using the command:
C:\platform-tools>fastboot flash bootloader "C:\platform-tools\magisk_boot.img.img"
I get the following error:
Sending 'bootloader' (65536 KB) OKAY [ 1.609s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
No, It isn't booted in fastbootd mode. I am using correct Fastboot mode using the hotkeys
Kindly assist. Thank you
Your fastboot may be old... Upgrading it might help.
Or you might be able to use fastboot boot patched.img to get temporary root and use Magisk manager to install (direct) to make it permanent. That's what I do, and it's always worked.
Absarock said:
I have been using this method to flash new stock update every month to my rooted pixel 4a.
Steps I follow:
- Download the factory image of the last month
- Extract the boot.img. And patch it using magisk canary build
- Move the boot.img to the computer and flash it in fastboot mode
- flash the complete image
- Reroot the phone using magisk
This time with January update, I am getting stuck on step 3. Everytime I try to flash the bootloader image using the command:
C:\platform-tools>fastboot flash bootloader "C:\platform-tools\magisk_boot.img.img"
I get the following error:
Sending 'bootloader' (65536 KB) OKAY [ 1.609s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
No, It isn't booted in fastbootd mode. I am using correct Fastboot mode using the hotkeys
Kindly assist. Thank you
Click to expand...
Click to collapse
fastboot flash boot
And not
fastboot flash bootloader
Cheers!
Typhus_ said:
fastboot flash boot
And not
fastboot flash bootloader
Cheers!
Click to expand...
Click to collapse
Thank you, sir. It helped
a1291762 said:
Your fastboot may be old... Upgrading it might help.
Or you might be able to use fastboot boot patched.img to get temporary root and use Magisk manager to install (direct) to make it permanent. That's what I do, and it's always worked.
Click to expand...
Click to collapse
I tried updating fastboot. Didn't work.
Either way I was able to solve by using the command boot_b instead of bootloader. B being the partition