Try any version of KDZ firmware, extract DZ and then extract boot.img is all 0kb. What's the matter??? How to correctly extract the complete boot IMG file??
hello
maybe you don't use the right tool
post a download link of your firmware and i'll try to extract it
exemple here :
{
"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"
}
thank. I have found a method to extract boot IMG file. Now there are new headaches. My g8x can't enter the FastBoot mode. I tried all the methods mentioned on the network, but I can't enter the FastBoot mode. I wonder if it is the firmware problem?
hqsun said:
thank. I have found a method to extract boot IMG file. Now there are new headaches. My g8x can't enter the FastBoot mode. I tried all the methods mentioned on the network, but I can't enter the FastBoot mode. I wonder if it is the firmware problem?
Click to expand...
Click to collapse
Write this with Qfil to partition abl_a and abl_b.That will get you fastboot back.
Related
I own a micromax A63 fun, and it is stuck in bootloop on root attempt..I don't have a recovery installed in it(only stock recovery)..I wanna flash its stock rom back, but, no zip file available..I got its rom in rar format, installable via MTK SP FLASH TOOLS. I have the tool, but the problem is here:
my phone is restarting on charging or switching on or connecting to pc. It becomes stable only when I enter recovery mode in it(adb is also stable at recovery mode). I googled and couldn't find any info regarding installing rom when I am on recovery mode. Can u please help me?
Can I flash rom when I am in recovery mode?
{
"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"
}
:crying::crying::crying::crying::crying:
{
"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"
}
Installation:
Copy the .zip file to the internal memory of your device to enter recovery mode and install and enjoy
BootLogo
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Credits:
Create BootLogo: @droidjbc​
Very cool logos! Will this overwrite the dreadful bootloader unlocked warning?
EDIT: Answering my own question: YES!
Please, make tutorial to create custom logos!
GOOD JOB!
I used Moto Boot Logo Maker to get rid of unlocked bootloader warning, you can replace it and the normal boot logo with any image, and create a logo.bin to flash with fastboot, or create a zip flashable in custom recovery:
http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667
anyone can help me
my asus mimo pad7 stock on asus start up,...
i follow this thread http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
i'm done with this command
but when i click recovery it restart and igot 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"
}
thanks
i got to DROIDBOOT PROVISION OS
and i'm done with the CMD command
but when i click recovery it restart and i got this error
how can i flash this via sideload or update zip from sd card when i cannot enter to recovery,..
hope someone can help
thanks in advance....
Hi guys ,
After not being able to flash the system partition for an itel 1404 with research downloader, I decided to create a custom recovery which eventually allowed gave me a shell to recover, backup and even install custom roms.
{
"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"
}
NB:This recovery has been tested with itel 1404
Use at your own risk.
How to install.
************************************************************
Rename the extracted package from itel_1404__sc7715_recovery.img to recovery.img.
Download itel1404 pack file.
Open research downloader and choose your recovery file instead of the one chosen for you.
Make sure you don't choose format all whenever you are flashing a phone with research downloader, as this has been seen to permanently kill devices.
Flash all the files normally.
Then power of the device and boot into recovery.
************************************************
GOODLUCK
How to flash s custom ROM
I followed https://www.xda-developers.com/root/ to root my phone, using boot.img downloaded via
https://www.mediafire.com/file/v0llvwlwv4emnkd/Wiko_View_Max_MT6739_V01.43_270918_8.1.0.zip/file
The phone's chip is Mediatek MT6739.
Magisk shows itself as installed
{
"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"
}
When I choose Uninstall Magisk and Restore Images, it says "Stock backup doesn't exist".
How can I install appropriate drivers or restore the pre-root state.
Please help me, this is an emergency.
My recommendation: Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
My downloaded Wiko_View_Max_MT6739_V01.43_270918_8.1.0/Firmware/ has the following files:
APDB_MT6739_S01_alps-trunk-o1.bsp_W18.08
Android_Key_P200AN_8.1_WIK_FR_OM_81_45.bin
DA_SWSEC_1804_P200AN_8.1_WIK_FR_OM_81_45.bin
MDDB_InfoCustomAppSrcP_MT6739_S00_MOLY_LR12A_R2_MP_V18_P22_1_ulwtg_n.EDB
MT6739_Android_scatter.txt
boot.img
cache.img
efuse_MT6739_P200AN_8.1_WIK_FR_OM_81_45.xml
firmwarefile.com.url
lk-verified.img
loader_ext-verified.img
logo-verified.bin
mcupmfw-verified.img
md1dsp-verified.img
md1img-verified.img
misc2.img
odmdtbo-verified.img
preloader_p200.bin
recovery-verified.img
spmfw-verified.img
system.img
I have patched boot.img ->
magisk_patched-23000_9K0eo.img
by Magisk, therefore I should flash boot.img, right?