Hi, I am trying to flash back to stock in my pixel but whenever I tried to do it I got the following error in terminals
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
fastboot(14811,0xa6f311c0) malloc: *** mach_vm_map(size=1590816768) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1589227196 bytes
error: update package missing system.img
Is there any workaround with this as I really need to get my pixel back to stock fully, also I have 7GB avaiable in my phone so I don't think it is problem caused by the lack of avaiable memory.
Thanks you for answering in advance!
Are you using the Minimal version of fastboot by any chance? If so use Google's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Saw this in another thread
Thanks you for answering, however i dont think this is the problem since bootloader and radio can be flash successfully, its just the system update img that cannot be flash, but thanks anyway!
Sent from my Pixel using Tapatalk
Thanks
This was the fix for me, thanks for ending my struggle brother:highfive:
ansontyl96 said:
Thanks you for answering, however i dont think this is the problem since bootloader and radio can be flash successfully, its just the system update img that cannot be flash, but thanks anyway!
Click to expand...
Click to collapse
Is the system.img extracted from zip?
Try putting all those files in the subfolder into same folder as all the rest and the tools.
Sent from my sailfish using XDA Labs
ansontyl96 said:
Hi, I am trying to flash back to stock in my pixel but whenever I tried to do it I got the following error in terminals
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
fastboot(14811,0xa6f311c0) malloc: *** mach_vm_map(size=1590816768) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1589227196 bytes
error: update package missing system.img
Is there any workaround with this as I really need to get my pixel back to stock fully, also I have 7GB avaiable in my phone so I don't think it is problem caused by the lack of avaiable memory.
Thanks you for answering in advance!
Click to expand...
Click to collapse
It always sticks there at what seems to be an error message, but it's not. Let it keep going at that point. It takes about 30 seconds to a minute or so and it will continue on its on and finish installing. Just make sure you have ./ In front of the fastboot commands in the flash-all zip.
Related
Hey gang,
Brand new problem that has me a little perplexed. I have been using the 'Returntosctock2.3.5.script' that has been posted in a previous thread, and restoring to 2.3.5. via AP Fastboot along with the Stock Restore .bat file, but now that is not working. It is now showing that after running the script, it goes through its steps but then says:
...
sending 'mbmloader' <39 KB>... FAILED <command write failed <no such file or directory>>
sending 'mbm' <256 KB>... FAILED <command write failed <no such file or directory>>
rebooting into bootloader... FAILED <command write failed <no such file or directory>>
sending 'cdt.bin' <16 KB>... FAILED <command write failed <no such file or directory>>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, after it does the rest of its business, and after the reboot, it bootloops from splash screen to boot animation and back again, continually. I tried using RSD Lite for the first time and restored 2.3.5. and without any issues. So, what's up with restoring through AP Fastboot not working but the other method does? I have restored using AP Fastboot countless times, and without any problems. I don't get it.
Damn gremlins
I for one have not used the "returntostock" script. I didn't even know it existed until now. I did use RSD lite for the first time the other day and am impressed at how quick and well it worked. Kinda stinks they don't make it compatible with Linux. Doesn't make sense really.
mtnlion said:
Damn gremlins
Click to expand...
Click to collapse
I know, right?
KEB64 said:
I for one have not used the "returntostock" script. I didn't even know it existed until now. I did use RSD lite for the first time the other day and am impressed at how quick and well it worked. Kinda stinks they don't make it compatible with Linux. Doesn't make sense really.
Click to expand...
Click to collapse
I was just happy that RSD worked, and worked well. Still, I'm very befuddled as to why the script method didn't yield the same results it has for me every other time I've used it. I just don't get it...
If any of you want to change your splash screen, it's pretty easy. I just followed this guide. Please give TrueBlue_Drew thanks.
Requirements:
Unlocked
Rooted
S-OFF
This might work for other Butterfly devices as well, but I'm not 100% sure.
As a test, I found a random splash screen, resized it to 1080x1920, converted and flashed it using EZ Splash Screen Flasher, and bam, changed splash screen. The htc development message is still there, though.
Here are some images I used:
HTC Anime Girl
Hero Droids
The above images were found in the guide I linked above, so original credit goes to whoever provided those images. I'd be happy to credit them here if I find who they are.
If you don't want to go through the process of creating your own splash screen, you can download the attached zips with the img file inside, put the img file somewhere you can use the fastboot command. You'll need to put your phone in fastboot and use the command
Code:
fastboot flash splash1 splash.img
Then, just reboot and you should see the change right away.
Thanks
Thanks it has worked for me...!
hi
I checked that thread and question I have.
How to create 1080x1920 image by SplashFlasher_1.0??
thanks
not allowed
I'm S-OFF and unlocked, but I get an error flashing splash1:
sending 'splash1' (4050 KB)... OKAY
writing 'splash1'... FAILED (remote: not allowed)
Anyone an idea?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some anime's splash images
http://androidfilehost.com/?fid=22946563261203120
I have uploaded private album.
http://forum.xda-developers.com/picture.php?albumid=9471&pictureid=36117
http://forum.xda-developers.com/picture.php?albumid=9471&pictureid=36118
I unquestionably longed for to rise a acknowledgement to be means to appreciate we for all a glorious contribution we have been display on forum.xda-developers.com . My enlarged internet poke has right away been famous with great strategies to go over with my friends as well as family. we would demonstrate which most of us visitors essentially have been unquestionably sanctified to exist in a conspicuous village with really most undiluted people with profitable hints. we feel indeed beholden to have detected your web pages as well as demeanour brazen to so most some-more extraordinary mins celebration of a mass here. Thank we again for all a details.
webdepp said:
I'm S-OFF and unlocked, but I get an error flashing splash1:
sending 'splash1' (4050 KB)... OKAY
writing 'splash1'... FAILED (remote: not allowed)
Anyone an idea?
Click to expand...
Click to collapse
u need to flash eng hboot first .
Ok, so when I turn on the phone, it gets stuck on the HTC screen logo forever. With the volume down and power button, I'm able to get into hboot/hboot usb plug when connected to the computer. The recovery, factory reset, image crc options don't work. In my linux computer, when I type fastboot devices, I'm able to get serial number of the phone. The picture links below summarize my current state
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The commands that I've tried are below.
(command): /fastboot devices [output] SH******** fastboot -- (note: here I did get my serial number but I know better than to post it here.
(command): ./fastboot oem rebootRUU [output]... FAILED (status malformed (1 bytes))
(command): ./fastboot flash zip PD15IMG.zip [output]: sending 'zip' (322693 KB)... FAILED (status malformed (1 bytes))
Tools in hand: android-sdk-linux, linux mint, PD15IMG.zip and phone
note: I also tried all of the above commands on windows 7 home premium 64 bit with adb installed and got the same error messages from fastboot. I tried the official htc bootloader unlocker but kept getting that error: 120 battery less than 30%.. although my battery is fully charged and that stopped the tool from unlocking the boot loader.
I read somewhere If i find the orginal stock recovery image, I might get out of this but I cannot find it anywhere yet.
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
RUU?
gesange said:
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
Click to expand...
Click to collapse
Yeah I tried RUU and it gets stuck all the time at Rebooting bootloader or waiting for bootloader
I can't flash Android M:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't find any boot.sig and recovery.sig, only find .img files with the M package. Any advice will be greatly appreciated.
Manually flash each IMG as opposed to using the flash-all.bat (others have had this same issue)
EddyOS said:
Manually flash each IMG as opposed to using the flash-all.bat (others have had this same issue)
Click to expand...
Click to collapse
Yes That's exactly I was doing. I flash it one by one still get can't find .sig file....
pyth0ner said:
Yes That's exactly I was doing. I flash it one by one still get can't find .sig file....
Click to expand...
Click to collapse
No, what I'm saying is DON'T use the flash-all.bat script as that's causing the issue. You have to extract the ZIP file and manually flash each IMG file one at a time, e.g.
fastboot flash bootloader bootloader.img
fastboot-reboot bootloader
fastboot flash radio radio.img
fastboot-reboot bootloader
fastboot flash system system.img
fastboot-reboot bootloader
fastboot flash recovery recovery.img
fastboot-reboot bootloader
fastboot flash boot boot.img
fastboot-reboot bootloader
etc, etc, etc.
Maybe you shouldn't be flashing a developer preview if you don't know what you're doing?
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Maybe you shouldn't be flashing a developer preview if you don't know what you're doing?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well said well said
Sent from my Nexus 5 using XDA Free mobile app
It happens to me some times regardless of the android version, if I use the computer front ports. It's always better to use the ones directly on the motherboard.
the *.sig thing always appear but I also recommend you to avoid the .bat file and do it manually.
Issues with Image
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
Do a clean flash. You didn't if the notification drop down doesnt work
Sent from my Nexus 5 using Tapatalk
When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Fastboot Enhance shows I have a super partition 11.5GB in size:
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?
Hello. I have an idea as follows. if you need to do that, look for a rom specifically for flashing super.img, not a rom that contains a lot of images like this
bubugugu said:
When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
View attachment 5769945
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
View attachment 5769943
Fastboot Enhance shows I have a super partition 11.5GB in size:
View attachment 5769965
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
View attachment 5769959
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?
Click to expand...
Click to collapse
Did you every solve this? I'm having the same problem.