hi guys
i have lg g3 D855 after update its dead and now its only stay on lg logo i tried to flash new rom but when i try to go the download mode its going to fastboot mood then i try to flash laf.img its give me this error
C:\New folder\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 2147483648 bytes
sending 'boot' (12800 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 10.470s
C:\New folder\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (17408 KB)...
OKAY [ 0.552s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 10.617s
C:\New folder\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.036s
also i get the same error with flashing the recovery file
so whats wrong and what should i do to fix this?
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
itsbighead said:
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
Click to expand...
Click to collapse
thx for replay me
i did that (fastboot boot laf.img) its say done with showing some words on the phone monitor but nothing happen also still cant go the flash mode
Try this
Boot into TWRP
Enable MTP and copy laf.img to sdcard
Go to Terminal Command in Advanced
Run the commands below using TWRP
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Related
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Thajin said:
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Click to expand...
Click to collapse
Use HTC_fastboot and not the generic fastboot..
nopynel said:
Use HTC_fastboot and not the generic fastboot..
Click to expand...
Click to collapse
I have the same problem and just ask now because i am really confused about the hole stuff here.. Have we now to tipp in cmd
C:\Android>HTC_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img ??
Edit: Ok, i find HTC_Fastboot there > ruu.lalleman.net/HTC_M8S%28QL_UL%29/Tools/Fastboot/ and it solve this problem.
But i think its still not everything fine.. if i change to hboot on bootlader i get this infomations
fs5.directupload.net/images/160727/z9lr634u.jpg
whether unlock bootloader?
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse
flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system
Hi guys, I have just flashed a new TWRP from the command line and wanted to boot to it with fastboot using "fastboot boot recovery.img". Unfortunately I did not pay enough attention when recalled the original command from the CLI and issued "fastboot flash boot recovery.img" instead of the correct "fastboot boot recovery.img" command. The device is still in fastboot mode - how can I restore boot? This was the output of the command:
c:\Program Files (x86)\totalcmd\plugins\wfx\ADB\bin>fastboot flash boot e:\Letöltések\twrp_v3111_hydrogen-helium_nijel8-MOD_A7.1.2.img
target reported max download size of 536870912 bytes
sending 'boot' (16176 KB)...
OKAY [ 0.569s]
writing 'boot'...
OKAY [ 0.230s]
finished. total time: 0.803s
Any help is appreciated - I am scared ****less.
Edit: extracted boot.img from the flashable .zip of the ROM I originally wanted to flash and flashed it with fastboot, hope it works
Hi,
My Asus Zenfone 5 A500CG T00F was bricked earlier and I followed the community help to unbricked it.
Everything went fine except last step of flashing the ROM.
Somehow I messed up and now I have nothing but a locked droidboot (IFWI Version 59.29) loader and messed up recovery (ASUS_T00F-WW-2.21.40.44).
I have tried all available help regarding unlock the bootloader but It didn't worked. I can't flash using sideload due to *invalid cache(Invalid Argument)*.
I can't fix the partitions because it says the *GPT command failed*.
I am totally clueless now. Really appriciate any pointers.
flukebox85 said:
Hi,
My Asus Zenfone 5 A500CG T00F was bricked earlier and I followed the community help to unbricked it.
Everything went fine except last step of flashing the ROM.
Somehow I messed up and now I have nothing but a locked droidboot (IFWI Version 59.29) loader and messed up recovery (ASUS_T00F-WW-2.21.40.44).
I have tried all available help regarding unlock the bootloader but It didn't worked. I can't flash using sideload due to *invalid cache(Invalid Argument)*.
I can't fix the partitions because it says the *GPT command failed*.
I am totally clueless now. Really appriciate any pointers.
Click to expand...
Click to collapse
Moreover, Whenever I tried flash anything with fastboot it goes smoothly, NO Errors. But when I reboot I get back same old droidboot.
Use TWRP recovery instead
nheolinkin said:
Use TWRP recovery instead
Click to expand...
Click to collapse
Hi,
I am not able to install that because bootloader is NOT unlocked, that's where I am stuck at.
Anyway to install TWRP recovery on locked bootloader ?
If your fastboot is from 2.21.40.44 too, you can not flash ifwi for unlocking bootloader. Perhaps you wanna give some information about how you unlock bootloader or what error you get from fastboot gui.
nheolinkin said:
If your fastboot is from 2.21.40.44 too, you can not flash ifwi for unlocking bootloader. Perhaps you wanna give some information about how you unlock bootloader or what error you get from fastboot gui.
Click to expand...
Click to collapse
{
"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"
}
It says droidboot version 2.1 Build May 12 2015. Nothing more.
nheolinkin said:
If your fastboot is from 2.21.40.44 too, you can not flash ifwi for unlocking bootloader. Perhaps you wanna give some information about how you unlock bootloader or what error you get from fastboot gui.
Click to expand...
Click to collapse
For unlocking , I tried flashing (UBL Toolkit for Zenfone 5, Unlook Bootloader tool v4.0 and others) but no success. Problem is while doing any flashing with fastboot there is no error as such but It give me same screen after reboot. I may be doing something wrong I am not sure. If you can provide me the step to follow I can repeat the steps and tell you the result.
flukebox85 said:
For unlocking , I tried flashing (UBL Toolkit for Zenfone 5, Unlook Bootloader tool v4.0 and others) but no success. Problem is while doing any flashing with fastboot there is no error as such but It give me same screen after reboot. I may be doing something wrong I am not sure. If you can provide me the step to follow I can repeat the steps and tell you the result.
Click to expand...
Click to collapse
Run this tool
Choose option 1 in every step.
If it does not work, show me what it said on ADB window when tool was running.
nheolinkin said:
Run this tool
Choose option 1 in every step.
If it does not work, show me what it said on ADB window when tool was running.
Click to expand...
Click to collapse
Hi,
Sorry I don't have any windows setup for now. So I tried running the commands manually.
1) UNLOCK.bat
Option 1 points to files/patch.bat
2) files/patch.bat
Option 1 points to files/115fastboot.bat
3) files/115fastboot.bat
:Selection1
echo ' UPDATING FASTBOOT
fastboot flash dnx generaldnx_osr.bin
fastboot flash fastboot 1.17.40.16_fastboot.img
fastboot reboot-bootloader
sleep 20
echo ' RELOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi 115ifwi.bin
fastboot reboot-bootloader
sleep 20
echo ' UNLOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi if.bin
fastboot reboot-bootloader
sleep 20
echo ' SUCCESSFULLY PATCHED
pause
goto Quit
So. I tried running following commands manually with fastboot/droidboot on Zenfone5 and USB connected.
Below is the output.
-----------------------------------------------------------------------------------------------------------------------------------------------------
echo ' UPDATING FASTBOOT
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx_osr.bin
target reported max download size of 1320454826 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.509s]
writing 'dnx'...
OKAY [ 0.667s]
finished. total time: 1.177s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash fastboot 1.17.40.16_fastboot.img
target reported max download size of 1320454826 bytes
sending 'fastboot' (12421 KB)...
OKAY [ 1.787s]
writing 'fastboot'...
(bootloader) secure device
(bootloader) signed image
OKAY [ 2.128s]
finished. total time: 3.915s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.325s]
finished. total time: 0.326s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Phone rebooted to fastboot fine.
echo ' RELOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1320681472 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.500s]
writing 'dnx'...
OKAY [ 0.652s]
finished. total time: 1.152s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi 115ifwi.bin
target reported max download size of 1320681472 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.697s]
writing 'ifwi'...
OKAY [ 0.863s]
finished. total time: 1.560s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.319s]
finished. total time: 0.319s
-----------------------------------------------------------------------------------------------------------------------------------------------------
At this Phone DIDN'T rebooted to fastboot. Manually has to rebooted to fastboot.
This happens always with ifwi flash. It's show that my battery dies but if I manually reboot it reboots fine.
echo ' UNLOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1321028266 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.505s]
writing 'dnx'...
OKAY [ 0.650s]
finished. total time: 1.155s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi if.bin
target reported max download size of 1321028266 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.698s]
writing 'ifwi'...
OKAY [ 0.867s]
finished. total time: 1.565s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.321s]
finished. total time: 0.321s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Sadly, It's same droidboot/fastboot after each reboot.
Nothing changed. Ifwi and DroidBoot version are same.
flukebox85 said:
Hi,
Sorry I don't have any windows setup for now. So I tried running the commands manually.
1) UNLOCK.bat
Option 1 points to files/patch.bat
2) files/patch.bat
Option 1 points to files/115fastboot.bat
3) files/115fastboot.bat
:Selection1
echo ' UPDATING FASTBOOT
fastboot flash dnx generaldnx_osr.bin
fastboot flash fastboot 1.17.40.16_fastboot.img
fastboot reboot-bootloader
sleep 20
echo ' RELOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi 115ifwi.bin
fastboot reboot-bootloader
sleep 20
echo ' UNLOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi if.bin
fastboot reboot-bootloader
sleep 20
echo ' SUCCESSFULLY PATCHED
pause
goto Quit
So. I tried running following commands manually with fastboot/droidboot on Zenfone5 and USB connected.
Below is the output.
-----------------------------------------------------------------------------------------------------------------------------------------------------
echo ' UPDATING FASTBOOT
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx_osr.bin
target reported max download size of 1320454826 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.509s]
writing 'dnx'...
OKAY [ 0.667s]
finished. total time: 1.177s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash fastboot 1.17.40.16_fastboot.img
target reported max download size of 1320454826 bytes
sending 'fastboot' (12421 KB)...
OKAY [ 1.787s]
writing 'fastboot'...
(bootloader) secure device
(bootloader) signed image
OKAY [ 2.128s]
finished. total time: 3.915s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.325s]
finished. total time: 0.326s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Phone rebooted to fastboot fine.
echo ' RELOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1320681472 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.500s]
writing 'dnx'...
OKAY [ 0.652s]
finished. total time: 1.152s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi 115ifwi.bin
target reported max download size of 1320681472 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.697s]
writing 'ifwi'...
OKAY [ 0.863s]
finished. total time: 1.560s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.319s]
finished. total time: 0.319s
-----------------------------------------------------------------------------------------------------------------------------------------------------
At this Phone DIDN'T rebooted to fastboot. Manually has to rebooted to fastboot.
This happens always with ifwi flash. It's show that my battery dies but if I manually reboot it reboots fine.
echo ' UNLOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1321028266 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.505s]
writing 'dnx'...
OKAY [ 0.650s]
finished. total time: 1.155s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi if.bin
target reported max download size of 1321028266 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.698s]
writing 'ifwi'...
OKAY [ 0.867s]
finished. total time: 1.565s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.321s]
finished. total time: 0.321s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
And I still with the same droidboot. Nothing changed on reboot.
flukebox85 said:
And I still with the same droidboot. Nothing changed on reboot.
Click to expand...
Click to collapse
I see. It's not about the fastboot.
Try command "fastboot erase cache" and see it works or not
If it doesn't, then I can't help for now.
nheolinkin said:
I see. It's not about the fastboot.
Try command "fastboot erase cache" and see it works or not
If it doesn't, then I can't help for now.
Click to expand...
Click to collapse
[email protected]:~$ fastboot erase cache
erasing 'cache'...
OKAY [ 1.830s]
finished. total time: 1.830s
[email protected]:~$
ZENFONE 5
sAME PROBLEM HERE its been softbricked now fastboot recovered but cannot get into recovery only ifwi changes from 59.29 thru 59.2a to 59.27 now could anybody advice which fastboot and recovery shld i flash to get into recovery
Really s...s
And getting error e:/unable to mount cache during factory reset
I unlocked bootloader with option 1 all went fine now im on ifwi 59.a1 shld I flash fastboot recovery same version i proceeded bootloader unlock with?
Kind regards
Looking for a custom recovery I found this page where it contains a TWRP that is supposedly compatible with the Moto G20.
Download TWRP 3.5.2 For Moto G20- How to install » The TechGyan Gadgets
How To Install TWRP Recovery on Moto G20-Step 1. Bootloader Unlock on Moto G20.Step 2. Install TWRP Recovery on Moto G20.
mytechgyangadgets.com
Link TWRP:
motorola twrp recovery.img
drive.google.com
I did not want to risk trying it since I do not know much about this and what can happen if it is not correct. Someone to solve my doubt? or know of a compatible custom recovery? Gracias. :XX
Hey!
I tried booting directly into twrp in fastboot mode using ./fastboot boot twrp recovery.img and get this:
Sending 'boot.img' (26460 KB) OKAY [ 0.688s]
Booting OKAY [ 0.000s]
Finished. Total time: 0.717s
But the Phone only restarts into normal Motorola OS.
Robyn_232 said:
Hey!
I tried booting directly into twrp in fastboot mode using ./fastboot boot twrp recovery.img and get this:
Sending 'boot.img' (26460 KB) OKAY [ 0.688s]
Booting OKAY [ 0.000s]
Finished. Total time: 0.717s
But the Phone only restarts into normal Motorola OS.
Click to expand...
Click to collapse
hello! Thanks for replying, I guess we have to wait. :c
voy a intertar
it can not i put this .\fastboot.exe flash recovery "C:\Program Files (x86)\Minimal ADB and Fastboot\motorola twrp recovery.img"
and this appears
Sending 'recovery' (26460 KB) OKAY [ 0.748s]
Writing 'recovery' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
and when I enter the recovery the default revorey appears
Watch the Thread called "Building TWRP for Moto G20" there is someone with a working twrp but theres no download link until now.