Related
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?
sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250
efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.
efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.
sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.
would running terminal in windows with admin privileges help?
sent from my i9250
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".
bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?
I have same problem to...
sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250
My ZE551ML was rooted and I decided to update it being unaware that I was supposed to unroot it before updating. Once I got to the recovery menu, I attempted to sideload the newest firmware but the device was not found despite being able to be found during the bootloop. I then performed a factory reset and now it is stuck on a bootloop and cannot be detected by adb at any point.
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
But how do I fastboot to flash? Every tutorial I found told me to use adb sideload which I never found possible.
Edit:
I solved my problem by copying the firmware I downloaded into an external sd card under the name MOFD_SDUPDATE.zip and going to recovery mode.
download full firmware according to ur device from here https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw give Thanks @shakalaca for this
download (Z00A)2.19.40.18 if u want to unlock ur bootloader cause latest one cause problems with unlocking bootloader
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
loganj said:
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
Click to expand...
Click to collapse
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
ultramag69 said:
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
loganj said:
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
Click to expand...
Click to collapse
System.img is the entire firmware except for boot, droidboot and recovery... These can be flashed separately BUT make sure you use the right commands...
If you get to the usb symbol only displaying on your screen, you've stuffed up and it is a true brick...
yakub234go said:
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
Click to expand...
Click to collapse
Hey the procces struck whe i flash system img, stuck at "sending sparse 'system' (524056 KB)" Can you help me please?
After a long time waiting, probably over 1 hour i touch my phone screen then it just powered off suddenly. I really need help please
EDIT: i figured out that when sending sparse, after 10 second my phone just turned off
Maybe this tutorial works for you: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Sent from my GT-I9500
krasCGQ said:
Maybe this tutorial works for you:
Sent from my GT-I9500
Click to expand...
Click to collapse
I can't access my phone, how am i gonna turn on USB Debuggin when it's on bootloop ?
okokokokok i meet it
i have done adb side load but cant turn my phone. so, i went fastboot mode to flash it. but the bootloader is locked and cannot unlock it. when i enter the command flashing unlock,there is no response in the command prompt. can you also tell me how can i turn on usb debugging without switch on my android phone
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
pedrofg said:
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
Click to expand...
Click to collapse
if you are on 64 bit windows and fastboot flash system system.img gives you error. probably you are not using 64 bit fastboot tool below is the link to 64 bit tool
https://drive.google.com/open?id=0B72QQTXqZSRwUkFRMl81b1pWa0k
The problem still remains!
The problem still remains!
"C:\adb>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.022s]
sending sparse 'system' 1/12 (259338 KB)...
OKAY [ 11.418s]
writing 'system' 1/12...
FAILED (remote: size too large)
finished. total time: 11.471s"
Hello guys!
Well, i manage to understand my problem and solv it!
I bought my phone from Gearbest, and the problem begins there. Why? Because, regarless my phone is a CN device, it came somehow with a WW sku. You must know that a CN device have system partition smaller than the WW device.
So, when i tried to updated it with a more recent WW system there was no room for that, and the instalation stops with a error message.
After many "Trial and error", i understand what my problem is, and tried to install a CN system version by "fastboot flash" with a system.img with root that i find here: "https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw"
To fastboot i used the fastboot tool that sukhwant717 told me to, in the post #15.
Well, that worked, so i now have a phone working. Them i go to Asus website and downloaded the latest CN firmware to my divece, copy it by USB to the internal memory of my device and upgrade it.
So, now i have a phone working with a factory system but with no google apps.
I found this website with google installer: "https://www.digitbin.com/google-installer-apk/" follow the intructions and finaly i have Google play in my phone!
Now everithing works fine!
I hope that my story could help someone with the same problem!
" SOLVED - System was using 19.99 gb's required user data format. " Cant flash any of 3 factory images ? Anyone have a clue why ? I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space " I flashed images just fine a couple weeks ago on both my Nexus 6 and my Nexus 9 but for some reason I keep getting this problem.
I have tried using flash-all.bat and that is what I get. I never have had any luck using flash-all.bat in the past with my Nexus 6 & 9 so I would use the manual method which I"am listing below but there are a lot more things to flash on these pixel XL. So hopefully someone can list how to manually flash an image on the pixel XL because its totally different. Hopefully someone can tell me what is the problem ?
Run fastboot commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Add next step for Nexus 9
fastboot flash vendor vendor.img
I have also tried the following steps and on the last step flashing the image I still get " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Steps I tried are:
fastboot flash bootloader bootloader-marlin-8996-012001-1608281716.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012511-1609150631.img
fastboot reboot-bootloader
fastboot -w update image-marlin-nde63l.zip
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
M9guy said:
I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Click to expand...
Click to collapse
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I was in bootloader fastboot mode and i saw same issue.
rootSr. said:
I was in bootloader fastboot mode and i saw same issue.
Click to expand...
Click to collapse
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I put phone in bootloader mode and held down shift button and righted clicked on my folder with my adb tool that I extracted all files to.
http://androiding.how/flash-firmware-factory-image-google-pixel/
jaythenut said:
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
Click to expand...
Click to collapse
The method at the link below I had tried it previously and it did format my data but now each time I boot the phone I get " There"s an internal problem with your device. Contact your manufacturer for details. "
http://androiding.how/flash-firmware-factory-image-google-pixel/
zaksimmermon said:
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
Click to expand...
Click to collapse
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
rootSr. said:
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
Click to expand...
Click to collapse
I have the update downloaded to the phone it just wont install it think because I was rooted, even after formatting user data starting over it still would not install the update with no supersu installed.
Do you remember where the update was downloaded to on your phone what folder, or did you download the update somewhere else to your computer ?
cam30era said:
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
Click to expand...
Click to collapse
It makes sense, I will update and verify. Thanks for quick reply Cam
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
I just tried updating my Minimal ADB and Fastboot [10-22-16] and still same error. I thought I had already updated but I tried again anyway and still no go, and that was updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
M9guy said:
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
Click to expand...
Click to collapse
What version is your pixel running now? I'm on NDE63P.
zaksimmermon said:
What version is your pixel running now? I'm on NDE63P.
Click to expand...
Click to collapse
I"am on NDE63L
You need to try updating the SDK through the SDK manager. It'll have a box to check of to update SDK 25.
Sent from my Pixel XL using Tapatalk
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
It did work without any issues. I have cleared old SDK and downloaded new. Worked flawless. Thanks. :good:
When I try to run the flash-all.sh script from the November 2017 release of Android 8, I am getting the following error on my phone
Code:
$ ./flash-all.sh
// Script output until final command in script
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Does anyone know what is going on here? It works when I remove the -w flag from the last command in the shell script
It's the same for me... Really strange, I had to sideload the full ota to update
same here as well, are you guys rooted ??
-Z
I'm trying to run my with -w
fastboot -w update factory_image.zip
still getting the same error.
Yes, I am rooted.
Update: Tried November image and got the same thing. I don't think it's related to the factory image, but possibly something with the phone. Previously, I was able to flash the Nov. image just fine.
By the way, I'm on the first Pixel XL.
zipsnet said:
same here as well, are you guys rooted ??
-Z
Click to expand...
Click to collapse
I am rooted with Magisk. No custom recovery or anything. I'm planning to unroot and reload factory firmware except the flashing isn't working
darkfire404 said:
I am rooted with Magisk. No custom recovery or anything. I'm planning to unroot and reload factory firmware except the flashing isn't working
Click to expand...
Click to collapse
Have you guys updated the Android platform & ADB?
That might be the problem.
the script flash-all.bat is expecting a different version of the bootloader. What I did is to revert back to November image, sideload OTA and then you can do a flash-all.bat.
The solution to this problem is the following
Re-flash your dtbo.img from your factory img.
fastboot flash dtbo dtbo.img
Also , If you guys are running 8.1 do not use Magisk Manager: v5.4.3 since this version will patch up your dtbo.img. Instead use magisk-manager 5.4.0
Make sure you Uninstall Magisk Manager before re-flashing dtbo. Also - open the magisk manager and go to settings and turn-off update notification option
Let me know if that helps !!
Thanks to @Shadow/Walker for this solution to another problem
So after you run this command, then you can run the flash-all command?
I'm getting this error trying to flash the Dec 8.1 factory image on my Pixel 2.
Have you all tried to download the image again? The image might be corrupted.
I flashed the factory image as soon as it was available. Everything went smooth. I had 8.1 DP2 installed prior, and it was rooted. I didn't uninstall the Magisk.
All I did was boot into the bootloader and run flash-all.bat.
Yes, I just downloaded the image a little while ago. I'm not rooted, just have unlocked bootloader on Pixel 2. I sideloaded the image yesterday, and just wanted to do a clean flash of the stock image when I ran into the issue. I was previously on the Nov. 8.0 build.
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
This is very helpful, thanks for posting.
Sent from my Pixel 2 using Tapatalk
alarsama said:
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
Click to expand...
Click to collapse
For the record this did not work for me, Maybe because i ran the coommand `sudo install adb /ust/local/bin` after downloading the latest platform-tools. However I did download platform-tools and move everything in there as you are suppose to.
Any way the solution for me was to edit the `flash-all.sh` file and force it to run fastboot relative to platform.
So what I did was replace every instance of `flashboot` with `/path/to/platform-tools/flashboot` and it worked flawlessly and my stock ota boots up nice
my working flash-all.sh file contents:
Code:
#!/bin/sh
./fastboot flash bootloader bootloader-taimen-tmz12b.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-taimen-g8998-00164-1710262031.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-taimen-opm1.171019.013.zip
My experience has been to not extract the folder inside the extracted download. Just put it in with the platform tools. Seems the flash-all is expecting to extract that before flashing.
And I made the mistake of not unlocking critical. The January image has a new bootloader and won't install the system image without doing the bootloader.
@Larzzzz82, the first command really inside `flash-all` is `fastboot flash bootloader bootloader-taimen-tmz12b.img`, so I think you do need to extract the initial stock OTA zip file. At least I need to, and the command seems to explain why.
I just retested it today, the issue in the OP for me was because the `sudo install adb` command moves fastboot into your path, so when you type `flash-all.sh` its running fastboot from /usr/local/bin when it should be running in the same directory as your flashables.
So alarmsama's solution actually would work for me if i just delete /usr/local/bin/fastboot, or remove it from my path, or maybe even just drop a symlink from the directory containing the flashables.
Personally im going to just keep using my hacked script because i prefer it, as you can see from the code you can really have the files anywhere you want if you use absolute paths.
Larzzzz82 said:
My experience has been to not extract the folder inside the extracted download. Just put it in with the platform tools. Seems the flash-all is expecting to extract that before flashing.
And I made the mistake of not unlocking critical. The January image has a new bootloader and won't install the system image without doing the bootloader.
Click to expand...
Click to collapse
This is what worked for me. It seems that the process expects more than the 4 files I usually use to flash the images, and one of them was in the platform tools folder.
I scratched me head for a few minutes then first time i flashed this awesome piece of hardware. I have a lot more reading to do. Flashing this phone is completely different than my N6.
alarsama said:
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
Click to expand...
Click to collapse
oh you are god, thank you :good:
alarsama said:
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
Click to expand...
Click to collapse
you are a genius and my life saver~! managed to flash after...
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Jpdel said:
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Click to expand...
Click to collapse
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
5.1 said:
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Click to expand...
Click to collapse
Jpdel said:
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
Click to expand...
Click to collapse
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
5.1 said:
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Jpdel said:
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
JarMagic said:
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
Click to expand...
Click to collapse
Hi,
This is not a "shime in if you have a similar issue" thread. You may open your own thread. But well, do you have the proper factory image for taimen? Is your USB cable ok? Is your ADB / Fastboot up to date? In the message above yours i posted a link with the latest version. Try this...
Sébastien.
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
JarMagic said:
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
Click to expand...
Click to collapse
Hello,
Do you have acces to recovery? Tried to sideload: https://dl.google.com/dl/android/aosp/taimen-ota-rp1a.201005.004-b5dff51e.zip
Good luck...
Sébastien.
5.1 said:
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Jpdel said:
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Click to expand...
Click to collapse
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
5.1 said:
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Jpdel said:
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Click to expand...
Click to collapse
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
5.1 said:
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Jpdel said:
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Click to expand...
Click to collapse
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
5.1 said:
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Jpdel said:
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Click to expand...
Click to collapse
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
5.1 said:
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
Click to expand...
Click to collapse
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Jpdel said:
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Click to expand...
Click to collapse
Update: I finally was able to make the phone work!!!
In a last-ditch effort, I wiped the device, ran the Deuce Script, Reboot, Ran the flash-all.bat, Reboot, went to Recovery Mode > Enable ADB Update > Tried Sideload again of the OTA file, and there you go, I now again have a working device!!!
Thank you Sebastien @5.1 again for all your super kind support and knowledge! Truly am really grateful for your helpfulness!