footer is wrong and signature verification is wrong - Nexus Player Q&A, Help & Troubleshooting

Trying to root my nexus player i have got this. I am in stock recovery trying to rescue my system taking "apply update from ADB" but this not works:
I have tried downloading first the recovery images from nexus player (LMY47V), opening file and extracting the .img file (image-fugu-lmy47v.zip in this case) and runing "adb sideload image-fugu-lmy47v.zip" but the system answer is:
Verifying updatye package....
E:footer is wrong
E:signature verification failed
Instalation aborted
Above that message system say:
Android system recovery <3e>
LMY47V
And i think that .img must work..., but i have tried make the same with all the nexus player images. And with all have the same answer.
{
"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"
}

Related

[Q] Can't flash ROM because of "Received Data of Bad Length"ERROR

When I try "fastboot flash system system.img.ext4" or Super Tool script(http://forum.xda-developers.com/showthread.php?t=2627654) , it always get error of "(bootloader) Received Data of Bad Length" like this.
{
"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"
}
And following to"FAILED (status read failed(Too many links))".
The another solution of using restore file and OTA file in custom or stock recovery dosen't work due to Status 7 error except for 4.2.2 ROM.
try this maybe...?
Try a good quality usb cable, and onboard motherboard usb port instead of the front panel ones. Re-download the tool again maybe?

Struck on boot screen

When I updated lollipop , I was stuck in " no command " error on boot screen
{
"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"
}
and I tried to flash with stock rom there is an error . Please help me to load stock android. My device is NEXUS 7 2012 MOBILE.
Hello,
In the Command Prompt it says that the update package is missing the crucial system.img . Can you try redownloading the update package? Make sure the md5 checksums are the same. You can download freeware md5 checksum checkers on the web. Assuming you want to go to 4.4.4, here's the link: https://dl.google.com/dl/android/aosp/nakasig-ktu84p-factory-ef6aaa76.tgz . The md5 checksum is 09a2f56cc12ea45d77d2f451e924ecb7. Link taken from this website: https://developers.google.com/android/nexus/images#nakasig
Good luck!

E:Couldn’t load bitmap fill_ball (Error_7)

anyone, can help me??
every i open recovery mode, always display erorr message :
E:Couldn’t load bitmap fill_ball (Error_7)
Warrning: No file_context
supported API :3
at the bottom screen.
and id i choose Apply update from adb, display erorr message :
E: failed to open driver control : Permission Denied
{
"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"
}
TWRP won't load
I have the same issue with my other max pro m2.
Android version: 9 Pie
Build Number: PKQ1.WW_Phone-16.2017.2009.097-20200826
i was on stock android pie.
then i unlocked my phone and it was successful.
after unlocking the phone i tried to install TWRP and it is successful.
but when trying to go to recovery (power + volume down) it will go to the stock recovery with the error shown below.
E:couldn't load bitmap fill_ball (error -7)
Supported API: 3
can anyone help me/us on this?

Problem with error: Supported API: 3 E: Failed to clear BCB message

Hello
I have a Xiaomi Mi A1 phone
The developer option is not enabled
It is not unlocked either
Whatever I do, I can not fish.
It is not unlocked even through fast boot
There is an error in the recovery section
" Supported API: 3
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: operation not permitted"
{
"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"
}
You have to flash rom using miflash 2019 with the latest stock rom pie, because the bootloader not unlocked use testpoint method
I have same issue.
Did you find some fix?
same here, can anybody send links?

"couldn't load bitmap....failed to open...." errors in Tab (SM-T550) recovery mode

"couldn't load bitmap....failed to open...." errors in Tab (SM-T550) recovery mode
Hey all,
I'm seeing some strange error messages inside the Recovery Mode of my Galaxy Tab A (SM-T550):
"E: couldn't load bitmap pocchange_00009 (error -7)"
........
"E:failed to open /dev/block/boot/device/by-name/misc: no such file or directory"
- please see attached photo of screen.
Important to note that this tablet has never been rooted or had a custom recovery or rom put on.
Stock all the way.
I tried a factory reset and even flashing the original firmware via Odin.
Unfortunately neither of these made these weird messages disappear.
Any ideas??
Sorry for the push by myself but I edited the original to include the error messages in text.
and here's the image again
{
"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"
}

Resources