So I was trying to install magisk using fastboot and it installed successfully however when I tried rebooting it it just kept booting into fastboot. I tried installing TWRP but I got an error = (FAILED (remote: Error verifying the received boot.img: Invalid Parameter) My bootloader is unlocked and any help will be great.
well twrp won't work if you are on 10, if 9 then it should. i'd flash the stock kernel first. make sure it is the boot.img from the firmware image you have installed. if that does not help then try to flash the most recent complete firmware image. you could edit out "-w" in the flash-all.bat or flash-all.sh look for the line fastboot -w update image-xxxxxx.zip and take out the -w to keep the update from wiping your data.
Google Pixel 3a Stuck In Fastboot
dkryder said:
well twrp won't work if you are on 10, if 9 then it should. i'd flash the stock kernel first. make sure it is the boot.img from the firmware image you have installed. if that does not help then try to flash the most recent complete firmware image. you could edit out "-w" in the flash-all.bat or flash-all.sh look for the line fastboot -w update image-xxxxxx.zip and take out the -w to keep the update from wiping your data.
Click to expand...
Click to collapse
So I attempted to flash the boot.img file and got this error: FAILED (remote: Failed to write to partition Not Found)
And I tried the system.img file too and got a different error: FAILED (remote: Partition boot not found)
So finally I clicked the 'flash all' file and got this error: FAILED (remote: Failed to write to partition Not Found)
I installed the firmware from the google website.
have you tried a factory restore/reset from the bootloader menu?
fastbootでslot a,b手動でflashを試しましたか?
fastboot flash boot_a boot.img
Related
Hi I've Installed Chainfire(dumbest idea ever) -I had GLTools with only default plugin- ,too check whenever It would be possible to run Portal-So memory is almost full ,so I couldn't do neither full CWM backup ,and Advanced Backup didn't worked for me.
So What I did was flash 4.4.2(and I was on 4.4.4 europe rom -XT1032)
I have Fastboot Reason: UTAG *flashfail* configured as fastboot(no not after installing chainfire)
I was flashing with my premade /.sh file (fastboot flash partition gpt.bin etc.) and it seems like what have been flasheed is:
wirting 'partition'...
(bootloader) Preflash validation failed
FAILED(remote failure)
wirting 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
witing 'boot'...
OKAY
'system' -sparechunk.0
FAILED (data transfer failure (No such file or directory)) - lol? ,I've actually modified VM to have 512 mb of ram instead of 1536mb and cores from 2 to 1.
*fastboot resets*
Fastboot Reason: UTAG *flashfail* configured as fastboot
'system'-sparechunk.1
OKAY
and the rest wasn't flashed ,What can I do ,...I've just clicked factory(up button-congrats idiot-I wanted to go into recovery to say that I can go there and do something from there *facepalm* and clicked Up button ,because I was on factory option).
Okay ,so know I have no UTAG error recovery still works ,phone gets stuck on unlocked bootloader disclamer.
Btw before I started to install chainfire I've followed some instructions:
Code:
Backup
[B] * boot into recovery
* adb backup -f boot.img boot
* adb backup -f system.img system[/B]
Restore
[B] * boot into recovery[/B]
* adb shell echo -n boot > /tmp/ro.bu.restore
* adb restore boot.img
[I][B] * adb shell echo -n system > /tmp/ro.bu.restore
* adb restore system.img[/B][/I]
I've followed ,Failed
As boot.img from 4.4.2 have flashed can I actually flash that( * adb backup -f boot.img boot) boot.img and I don't magic will help me. Or can Actually someone who Have XT1032 falcon_umts do like CWM Backup without any personal stuff and I would try to flash it(Preloader/boot is not corrupted- device unlocked etc.-) ,when I used Used factory then everything seems to be working(expect for the android of course... and I don't know whenever VM will work If I don't have everything flashed).
Btw I can't Flash System.img from before I've destroyed it with Chainfire ,because the size is more than 600/700 mb and it just out numbers max number for sending system partition to fastboot.
Not saying this will definitely work, but if you get the gpt.bin and emmc_appsboot.mbn files from the 4.4.4 OTA zip (probably floating around here) and overwrite the originals from 4.4.2 in your factory image (delete the old ones or rename them to something else), then do the following:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Then flash as normal according to the guide that's floating around here, but leave out the gpt.bin and emmc_appsboot.mbn (you already flashed these) and the motoboot.img or it will brick it!
I just installed Paranoid Android ontop of it(adb sideload-I couldn't get into CWM ,and by accidently clicking factory in fastboot I could then go to CWM) and it works-then I launch PA install minimal gapps then factory reset it in cwm delete all data and slowly update pa update by update(installing 4.4RC2 into 4.45 is an bad idea for overall performance and stability) -I just kinda paniced.And I think ,because I was using generic fastboot instead of provided in guide ,preloadder didn't get corrupted(when to look at It only boot have been flashed correctly , and PA have boot.img in package).
So far so good.
This error has been associated with locked bootloader.
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Shuttwind215 said:
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Click to expand...
Click to collapse
My moto's bootloader is unlocked too, but it still gives the error...
Found an article:
https://giorgiosadventures.wordpres...rom-gpe-4-4-4-to-stock-and-recover-softbrick/
Try this... Lets see if it helps...
BTW, I got this error after converting xt1033 to gpe, then OTA'ing it to 5.0.1, then downgrading to 4.4.2.
@layman806 My moto g allready work look at post #3 this is what I did it[it looks extremly confusing]. It mightn't work for you through
,but if yours moto g have unlocked bootloader then you can do a lot ,and your situation isn't that bad.
lost101 said:
This error has been associated with locked bootloader.
Click to expand...
Click to collapse
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
khiladi_786 said:
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
Click to expand...
Click to collapse
I have the exact same problem on my xt1031 motog. I cant get any roms to boot and I cant figure out what version of gpt.bin i need to use. I get the same error.
Driving me crazy.
not solved
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
heisenberg1546 said:
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
Click to expand...
Click to collapse
This subforum is not for your phone. https://forum.xda-developers.com/2015-moto-g is the place for you.
If you are getting a 'pre-flash validation' error - even with the latest available firmware image - then you have to either wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.
help me plseeeeeeeeeeeeee i m getting preflash validation failed error on gpt.bin and sparsechunk plseee help me anyone i m using moto g3 xt1550 and trying to flash marshmallow.
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
gardeimasei said:
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
Click to expand...
Click to collapse
Flash factory image with fastboot.
wangdaning said:
Flash factory image with fastboot.
Click to expand...
Click to collapse
Where can I get the factory image? And how do I use fastboot to flash the device? Like so?:
Code:
fastboot boot <image name>.img
I am able to fastboot boot into the blueline TWRP image. Selecting the "Fix bootloop" didn't work however
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
gardeimasei said:
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
Click to expand...
Click to collapse
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Also, the boot partition is not the bootloader partition. Just run the flash-all script that google provides with the factory image download.
dcarvil said:
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
I was using Android 9. I tried running the flash-all script (i.e., follow the official instructions) but the fastboot commands would hang. Maybe I just didn't wait for long enough.
I wiped system,data,cache using TWRP following some online guide and now I can't boot into recovery mode. I can get into the bootloader menu though. When I try to boot into TWRP using:
Code:
fastboot boot twrp-3.3.0-0-blueline.img
I get the following error on the PC: Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
When I try to enter recovery mode the screen turns black indefinitely.
I still have the TWRP .win files from my backup on my PC. Is there a way out of this?
EDIT:
Weirdly, after trying the flash-all.sh script again it worked basically instantly. Possibly it took so long the first time i ran it because it was wiping data (which i then did manually).
Was able to get the factory image on there. Thanks a lot!
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.
So i goofed up and wiped everything under advanced when I was switching Roms. I was able to get the original recovery image installed (nv-recovery-st-wx-na-wf-5.2.0.zip) but if i reinstall TWRP and attempt to install any rom, the device name is still "" instead of "ShieldTablet". Is there anyway to restore the device name? I have been digging around on the forums (Including other device forums) but installing recovery is all I have been able to find. (Note: There was some guides advising removal of the device name check from the script within the image file, then re-zipping it. But this seems to always fail with a bad image error.)
Recovery was installed manually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Recovery image pulled from https://developer.nvidia.com/shield-open-source
More info to issue.
Boot into bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Boot into OS. (everything works.)
EnableUSB debug
adb shell settings get global device_name (Gives back "SHIELD Tablet")
Reboot into bootloader
fastboot flash recovery twrp-3.5.1_9-0-shieldtablet.img
Reboot into twrp
Copy on Rom and attempt to install.
Error text:
E3004: This package is for device: shieldtablet; this device is .
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Lineage-14.1-20210312-unofficial-shieldtablet.zip'
Note: above error text occurs when trying to install any ROM.
I am trying to figure out where "E3004: This package is for device: shieldtablet; this device is ." is pulling the device name. That is the part that I need to fix somehow.
Hi did you try to use a older version of twrp ? I also had my issues with the 9.5.1 version as it doesnt recognize my sdcard so i reflashed the version 9.5.0
You beautiful person! Downgrading from twrp-3.5.1_9-0-shieldtablet.img to twrp-3.5.0_9-0-shieldtablet.img allowed the img to install!
Checking in with the same problem. Thank you for the solution listed of downgrading to 3.5.0_9-0.
Currently flashing!
Hello,
I've been trying to flash a recovery image from the unofficial LineageOS for OP9 files, but when I try to flash it using the fastboot flash boot <recovery image name>.img command, it gives this error (as stated in the title): fastboot: error: boot partition is smaller than boot image. Can someone help me? What do I do in this case? I've seen others in that thread saying they got it to work and it installed. My bootloader is already unlocked, and my OP9 version is the 128GB/8GB-RAM one. Is there any way to clean the boot partition? I've been following the guide on the LineageOS wiki for the OnePlus 9 Pro, but using the files from the thread I linked above (since that is what it said to do). What do I do?
Because with your command your trying to flash a recovery partition into a boot partition. Fastboot flash recovery.img