Please help. I had Omni rom running fine. One day I turned on the tablet and got stuck in a bootloop. I tried to boot into twrp and it just sits there on the teamwin logo and wont go into twrp. I have factory cable and can get into fastboot, but the system.img will not write to the tablet. I have tried KFFirstAide and KFHD System.img Restore Tool and it will not write the system.img. I've tried multiple system.img, so it's not a corrupt file as the MD5 matches. Do I have a failed internal SD? I cant understand why twrp hangs either. UHHHHGGGG!!!
Here is what I get:
C:\>fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.408s]
writing 'system'...
FAILED (remote: : Write partition)
finished. total time: 315.015s
Any help would be appreciated.
Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.
Code:
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s
Im not sure where to go from here, any tips?
Chris_Krz said:
Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.
Code:
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s
Im not sure where to go from here, any tips?
Click to expand...
Click to collapse
Your device won't override. So you can erase the system
fastboot erase system -w
then flash
fastboot flash system system.img
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?
JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone
YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device
dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.
i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Can you enter erecovery??
Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.
I am currently trying to flash TWRP to my old Xperia Z and when I try to flash it, fastboot spew me with an error:
Sending 'recovery' (15198 kB) OKAY [ 0.500s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: command failed
I unlocked the bootloader already and Treble Check reported that I have A-only
Can someone give me some solution to this?
The only way i got my phone to flash is by flashing it via the Sony Mobile Flasher
Dl: https://www.ytechb.com/sony-mobile-flasher/
once there unpack the RAR file
then get the fastboot and flasher drivers
and the driver for your specific model
then connect your device in fastboot mode
click the flash button (top left corner)
click fastboot mode
click flash kenel
change the explorer to search for .img files
click the TWRP img for you phone
hopefully should work