Keep getting:
sending 'system' (955771 KB)
FAILED (remote: (00000006))
finished. total time: 0.004s
When trying to flash system.img
Can flash boot and recovery no problems, any ideas?
I've the same thing, I think it's normal.
How did you get around it?
Related
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Do what everyone should be doing... use Rezo's tool to root and install CWM. Then use CWM to flash your ROM. Simple.
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Is your bootloader unlocked? It must be to do that
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Boot your device on HBOOT, and select FASTBOOT and then connect with PC. (USB Debugging must be enabled)
Follow the instructions here to Flash ROM :
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
It's done now.
Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...
Just got my phone trying to flash the custom recovery to no joy (bootloader unlocked)
Keep getting
C:\Users\graem\Desktop\1p3>fastboot flash recovery recovery.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (17776 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.022s
C:\Users\graem\Desktop\1p3>fastboot flash recovery recovery.img
sending 'recovery' (17776 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.013s
C:\Users\graem\Desktop\1p3>
Any thoughts guys
This was using the [email protected]_radaideh-v2.1
How i got it working was installing stock recovery from tool then install custom and all worked fine.
I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3
lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.