Database Info

fastboot Error while Flashing Android M

Well i downloaded the new developer preview for m
and tried to flash the usual way
Then i encountred this error
{
"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"
}
tried running cmd in admin mode too, no effect.
The method i used is as follows
I extract the zip in the folder to get access to the images inside and then flashed them manually.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system sysytem.img (did not work)
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Running Fastboot and adb v 1.4 from here
http://forum.xda-developers.com/showthread.php?t=2588979
Kindy someone assist thank you

Your image doesn't show
Sent from my Android M Nexus 5 yo!

Try to reboot to your bootloader, and then flash system.img.

Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
i try this and still get the error

Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
I tired that.
I actually even tried restarting the bootloader after flashing every component.
Seems this fastboot has some issues with android m.
Can anyone who has flashed it provide some input.
Sent from my A0001 using XDA Free mobile app

I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.

I had no issues flashing M through fastboot - even used flash-all.sh.

I couldn't get M to boot until I individually erased each part using fastboot, and then individually flashed each part, extracted from Google's zip, also using fastboot.

lnchbx said:
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
Click to expand...
Click to collapse
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.

theChief_ said:
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
Click to expand...
Click to collapse
You need to pass the '-s' argument to fastboot to be able to flash system.

Redownload the file could be corrupt. Only other thing try using mfastboot(google it)

Can't flash Android M?!!

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

Unofficial twrp for Elephone u pro v3.2.1.0

{
"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"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Notice1:
U Pro has A/B partitions. to prevent issues its good to flash it in both slot, because i/we can not know on which partition you are
Notice 2:
This version only working on Eragon roms
Maybe soon I'll manage it to work on stock rom
Notice 3: Sdcard now working
DOWNLOAD
TWRP for 20180227 Base via Qfil Flashtools:
Go here : https://drive.google.com/file/d/1650peMjuk_WTFkxlufL84aJ6cMG5-g3q/view?usp=drivesdk
TWRP for 20180423 Base and newer:
Go here: https://drive.google.com/file/d/1vzDDVRl8vKMGzybVm_FYvufHlmOygOud/view?usp=drivesdk
INSTALLATION
if you use the old 20180227 Base you have to use Qfil Flashtools , because fastboot commands dont work in that Build.
we have a good guide of how to use FLashtools already
look here: https://forum.xda-developers.com/android/development/guide-elephone-pro-user-manual-t3775895
if you are on 20180423 Base and newer you can use fastboot commands
required : ADB and fastboot
enable usb debugging in developer settings.
do this:
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a twrp.img
after that we flash it also in slot b
Code:
fastboot falsh boot_b twrp.img
Special thanks to
teamwin for this awesome custom recovery
@travis82 for his advices
And @skeleton1911 for his help

smartphone does not leave twrp
Thank you in advanced if you can help me.
Has given an error on startup and I can not restart system, restarting twrp

Givanildo01 said:
Thank you in advanced if you can help me.
Has given an error on startup and I can not restart system, restarting twrp
Click to expand...
Click to collapse
Join us on Telegram group
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
And for your problem it's because you are coming from stock rom and that's for the meantime not working because of data encrypted

(Solved) Stuck on fastboot while re-downloading magisk (Asus ZMP M1)

Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM

{
"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"
}

Cocomug_ said:
Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
Click to expand...
Click to collapse
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.

Slim K said:
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Click to expand...
Click to collapse
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You

Cocomug_ said:
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Click to expand...
Click to collapse
how did you flashed it?

Can I flash redmi 10a fastboot rom in redmi 9a?

They have same code name and almost same specs. I couldn't find any 12.5 fastboot rom for redmi 9a.
As there is no android 11 supported twrp, I can't flash magisk.
I can't copy the boot .img from the fastboot rom too.
Any ideas?

Flahsing magisk using twrp is the WORST way for flashing magisk.

Use fastboot to flash magisk

NO，you CANT!(I TRIED THAT and bricked it)(can be rescued with Emergency Download Mode)
I have the same device as yours. It's needed to PATCH boot with magisk on the device
I have to tell you that DONT WONDER if TWRP OR IMGs from the redmi 9A to work on this device，since the employee on official Chinese forum said they are INCOMPATIBLE.
{
"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"
}

Just download the latest rom in the system update and you'll find it in downloads folder in your internal storage.
then extract it and find vbmeta.img and boot.img
copy them to somewhere you can find and use magisk app to patch the boot.img.
now copy the 2 imgs to computer
connect and reboot to fastboot,flash boot.img AND VBMETA.img with the option of --disable-verity --disable-verification.
NOW enjoy.

Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !

VD171 said:
Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
Click to expand...
Click to collapse
good warning since i did tried that lol

sd369888 said:
good warning since i did tried that lol
Click to expand...
Click to collapse
I just tried that recently, too...
Sad.