Develop Bugs

Problem in kernel Arc S

Kernel when flashing the device does not work, but when entering Hotbot mode it works
(Kernel does not work I have)
My Phone Is Xperia Arc S
http://www.youtube.com/watch?v=1U0kBrHz3xQ&feature=youtu.be

What exactly You need? If You want to flash new kernel, try with QuickIMG.

darkknightma said:
Kernel when flashing the device does not work, but when entering Hotbot mode it works
Click to expand...
Click to collapse
Use the right command. fastboot flash boot kernel.img

XperienceD said:
Use the right command. fastboot flash boot kernel.img
Click to expand...
Click to collapse
I used the right command but kernel not working

What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.

pypcier said:
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
Click to expand...
Click to collapse
Lol was just about to post something and you beat me to it
And make sure the kernel img is in firmware folder of flashtool you where flashing it from your desktop folder

tallman43 said:
Lol was just about to post something and you beat me to it
And make sure the kernel img is in firmware folder of flashtool you where flashing it from your desktop folder
Click to expand...
Click to collapse
You seem pretty competent when it comes to fastboot so can you help me with something? Every time i want to flash a new kernel after opening CMD I have to change directory to a folder containing boot.img and its pretty frustrating for me. Is there a folder for img files so fastboot will find them automatically? I've thought about creating a shortcut so CMD will open in right directory automatically but I'm lazy.

pypcier said:
You look pretty competent when it comes to fastboot so can you help me with something? Every time i want to flash a new kernel after opening CMD I have to change directory to a folder containing boot.img and its pretty frustrating for me. Is there a folder for img files so fastboot will find them automatically? I've thought about creating a shortcut so CMD will open in right directory automatically but I'm lazy.
Click to expand...
Click to collapse
To be 100 % honest not sure!I know in windows you can change default opening behavior of directories to open to your favorite folder etc,I once did ita long time ago but forgot how to
But what your suggesting sounds like a good idea:good: yep me lazy too don't use cmd much to be honest I use Doomlord's toolbox lol

So it looks like a customized shortcut is my only option. I like fastboot because its simple and reliable also typing stuff in black window is always cool. Life on the edge *****es!

pypcier said:
So it looks like a customized shortcut is my only option.
Click to expand...
Click to collapse
"Shift + Right Click" opens a command window in whatever folder you are in.
---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------
darkknightma said:
I used the right command but kernel not working
Click to expand...
Click to collapse
If it hot boots then it should flashboot and usually doesn't because People use the wrong command.

ALT + Right Click" opens a command window in whatever folder you are in.
Click to expand...
Click to collapse
Not on windows 8. I could do a shift + right click combo for "open cmd here" but this is useless because fastboot needs to be running with administrator rights. To be honest I don't care anymore because I've made a shortcut for opening cmd in a right folder with admin rights and even fancy blue font (*****es love blue fonts).

pypcier said:
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
Click to expand...
Click to collapse
this image when I flash kernel in fastboot but not working
{
"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"
}

Its pretty bad :c you have a bad block in your kernel "partition" and its preventing you flashing kernels. As far as I know this can't be fixed. You can't flash custom kernels I'm sorry :<
edit
It's a physical error in a memory chip in your phone. After searching for more info I think there is nothing you can do.

Can't flash system.img (TWRP/FASTBOOT)

Hi xda!
I can't flash system with TWRP or Fastboot
Fastboot:
Code:
C:\Users\manager\Desktop\coils\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.741s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.776s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.557s
TWRP:
{
"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 try fastboot erase system
I try repair partition in TWRP
I try change filesystem to ext2 and back to ext4
I try in TWRP
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and
Code:
make_ext4fs /dev/block/mmcblk0p41
Can any body help me with this problem?

Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have the latest version, I use this fastboot early and everything was fine

bzz11g said:
I have the latest version, I use this fastboot early and everything was fine
Click to expand...
Click to collapse
Obviously not. The error you are getting is due to an out of date fastboot.
Sent from my Nexus 5X using Tapatalk

piousinquisitor said:
obviously not. The error you are getting is due to an out of date fastboot.
Sent from my nexus 5x using tapatalk
Click to expand...
Click to collapse
IT'S LATEST VERSION
Code:
Microsoft Windows [Version 6.1.7601]
(c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
C:\Users\manager\Desktop\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.532s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.605s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.178s
C:\Users\manager\Desktop\Nexus>fastboot --version
fastboot version 8f855a3d9b35-android
C:\Users\manager\Desktop\Nexus>

When i had this problem, i had a bad download. Go redownload the image you are attempting to flash, make sure to check MD5. And where are you getting your fastboot drivers from?

I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?

bzz11g said:
I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?
Click to expand...
Click to collapse
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk

Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.

Make sure to download the latest platform-tools, pal
That'll fugure out your problem for sure. The do the fastboot and you're just gonna be fine. No reason to go around bushes. Follow the Root 5x thread.

SlimSnoopOS said:
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I try system.img from 7.0 and 6.0.1 and always get the same error
AtField said:
Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.
Click to expand...
Click to collapse
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?

bzz11g said:
I try system.img from 7.0 and 6.0.1 and always get the same error
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?
Click to expand...
Click to collapse
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.

AtField said:
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.
Click to expand...
Click to collapse
yes, i try this key's
if you look in log
Code:
target reported max download size of 536870912 bytes
it already 512 Mb
536870912 bytes / 1024 = 524288 kB / 1024 = 512 Mb

@bzz11g Issue the following command (after updating your fastboot, lol) and try again.
Code:
fastboot format system
note that there is a difference between erase and format.
Have you tried using the flash-all script?
If nothing else works use the TOT method to fix your phone.

@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?

bzz11g said:
@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?
Click to expand...
Click to collapse
You can't flash system.img that way. It isn't a standard .img file.
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
I know for sure it has no problems flashing the NRD90M system.img as I did it a few days ago.
If that doesn't work, then the problem is not with fastboot or the usb dll that uses.

sfhub said:
You can't flash system.img that way. It isn't a standard .img file.
Click to expand...
Click to collapse
I know, I want try to restore System with TWRP
sfhub said:
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
I try it now, thank you

@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s

bzz11g said:
@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s
Click to expand...
Click to collapse
So it isn't related to fastboot.
Are any of your partitions on the remote device full? cache or userdata?
If you can boot into stock recovery, you might want to try the FULL OTA from the nexus factory image site which you can try installing over adb sideload.
---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ----------
bzz11g said:
I know, I want try to restore System with TWRP
Click to expand...
Click to collapse
Is that system.img from a factory image or is it from twrp backup?
If it is from factory image, I am not sure if TWRP does what is necessary to restore it either.
---------- Post added at 11:55 AM ---------- Previous post was at 11:44 AM ----------
You didn't mention you were at Qualcomm loader.
You need to use LGUP and the TOT file in the other thread.

I got the same error message a while back - I solved it by re-installing SDK on my computer. I know you have previously said that you have the most recent version of SDK, and I thought I did as well. But I went ahead and uninstalled everything related to SDK on my computer and reinstalled a fresh version. Once I tried flashing system.img after that, it worked perfectly. I'd suggest that you try the same.

[T00F] Stuck with Nothing but Droidboot & Recovery

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

fastboot flash system: partition not found

Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$

Hey,
I have the same issue, did you ever find a solution?

You must unlock first

You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work

natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"

bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.

this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working

Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help

i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd

altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.

For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK

Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)

josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?

Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.

Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.

{
"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"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151

So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?

No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)

I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work

Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool

Lenovo P2 stuck in "Fast boot" menu. Bricked?

I have a Lenovo P2, unrooted, on stock Android, with a 256mb micro SD card. It hasn't been unlocked/flashed/rooted in any way apart from Developer Options to allow ADB.
A couple of days ago the phone started to lag and lock up, and then rebooted into "AP Fastboot Flash Mode (Secure)" menu. The only options are Start/Barcodes/Power Off.
The Start and Power Off/On options simply reboot back to the same screen after a couple of seconds. It won't boot back into Android with any combination of volume up/down/power buttons, or offer me any other options such as recovery or clear cache etc.
I've tried rebooting with/without the SD card - it makes no difference.
The phone still appears to be recognised by ADB when I connect it to a laptop - it appears in 'fastboot devices' - but I still can't get it to exit fastboot and boot back into Android with any ADB command.
I've tried downloading Reiboot and "15 second adb" toolkits which claim to exit fastboot mode, but without success.
I'm assuming the bootloader is corrupted.
Can anyone please point me towards any possible action for fixing it, or is it bricked?
Many thanks.
{
"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 thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?

If your rom is not booting you might need to reinstall it.

Keno_I said:
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
Click to expand...
Click to collapse
Here's what I've tried with ADB - the phone seems to be connected as evidenced by "fastboot devices", but I don't know what to do now. "Fastboot reboot" just brings me back to the same Fastboot screen in my original post, as does holding down vol+/vol-/power for several seconds.
I successfully unlocked/flashed a ZTE San Francisco Blade back in the day, so I don't mind trying to flash this P2 if that's the answer and you can point me towards a noob-friendly guide, please.

Reinstall the stock rom from fastboot

@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.

bigajm said:
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
Click to expand...
Click to collapse
You have to find and flash a valid flash image, try with the same version you were installed on

Can someone provide me with a twrp restore file? I tried to flash the stock rom but the bat file that came with it tampered with some files and I can't even boot into the stock rom