Related
Hello,
I’ve been following guides to root my phone and put a custom ROM onto it. I had no experience in doing this so I thought I would follow an idiots guide and was stupid enough not to back up the original ROM along with not reading up properly on what I was about to do… (yes you can call me names I shall accept it)
The problem I'm having is after putting the custom ROM which was ViperX3.2.0 The phone just stays stuck on the HTC one Tm with beats audio and keeps resetting it self, anyway i can fix it? or have i bricked it.
I'm a complete noobie cause I've been looking around for the past 3 days and still can't find anything (or something I can understand) :angel:
- I've wiped cache, dalvik cache and battery stats
- I go to recovery and click mount sd card nothing happens mount usb storage nothing happens.
- I don't understand next to nothing, need like android for idiots. :good:
- When phones booting up my computer recognises something but has not drivers and fails (But i had drivers and could transfer stuff too and from)
So if you can help i will love you forever
Many Thanks
RIch
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Did you flash the boot.img file in fastboot? fastboot flash boot boot.img followed by fastboot erase cache
tomascus said:
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Click to expand...
Click to collapse
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Richlilrich said:
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Click to expand...
Click to collapse
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Ahh, i've done what you just said it looks like i'm getting somewhere.
looks like i'm stuck on this one.
C:\fastboot>fastboot flash zip 3.16.61.6.zip
sending 'zip' (12875 KB)...
OKAY [ 1.786s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.130s
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
tomascus said:
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
Click to expand...
Click to collapse
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Richlilrich said:
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Click to expand...
Click to collapse
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
tomascus said:
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Whoopsie, did fastboot flash boot boot.img didn't start up so i thought i would check recovery and earse some caches, theres an error for it to load. (a phone laying down with an exclaimation mark) so i can't do a wipe
Reflash the custom recovery
Fastboot flash recovery recover.img
Fastboot erase cache
Anyway to get the recovery back? so i can try another ROM to see if that could possibly fix the problem, just can't get into recovery D: happy my phone turns on lol however no network or can't connect to wifi
by fashing the boot did nothing but crash it more.
so i had to redo what you taught me, thank you again and i'm back to where i said i was
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Mr Hofs said:
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Click to expand...
Click to collapse
Many thanks, recovery up and running. now that I know this I'll try to reinstall the ROM.
Are there any reasons why I'm not getting signal or WiFi? along with that from the unlock it seem rather slow,
But I guess it's time for me to experiment, now that i know how to fix it if I mess up
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Mr Hofs said:
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Click to expand...
Click to collapse
I am sure I have done that a few times, going to try re downloading and try to reinstall. May not be installing right,
Thanks
Just signed up to say thanks Mr Hofs for the help you've posted in this thread in particular but also in many other threads I've been referring to over the last 4 hours or so. I was well on my way to brickage following a screwed up attempt to root my HOX, but thanks to you I'm now up and running again. Admittedly I'm back at square one with a non-rooted handset, but I never would've believed that would be such a happy place to be, plus I feel a tiny bit less of a noob now.
Anyway, apologies for crashing your thread Richlilrich - as you were!
Screwed up my One X
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
DrUmMiSt said:
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
Click to expand...
Click to collapse
Would like to add that I would prefer Viper to stock but stock would help for now
Before going for RUU and stuff, try any other roms.
I'd say do this :
Flash TWRP - Better than CWM anyday.
Go to recovery. Mount USB. Copy Viper (or any other) rom to phone.
Reboot to bootloader.
Flash boot.img.
Fastboot erase cache.
Go to recovery.
Clean install ROM.
Reboot and wait for it. First boot takes pretty long sometimes.
There is no better recovery, a recovery is personal. I'm using CWM now for 2 years....never had a problem with that.....
Now the issue.
How to copy it is in the post above, however before you install the rom you need to make a real good full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom...and ofcourse flash the boot.img from the rom.zip
The option to mount in CWM is under mounts and storage copy the rom.zip over and unmount.
The way i personally follow is :
Flash the boot.img (fastboot, bootloader mode) then enter the recovery and follow the above....make sure you unplug the usb cable BEFORE installing the rom.zip
I had to restore back to stock and I do not use windows. I was looking for threads but all of them needed windows. So, I am making a tutorial on how to go back to stock on Win/Mac/Linux.
Note - I used my netbook which runs arch linux to complete these steps. I have not tried any other os but it should work.
Requirements On all systems -
Usb drivers (HTC sync provides them on windows. They are preinstalled on linux/mac)
Fastboot
RUU for your device
On linux/mac you need wine. Get wine from your distro on linux and for mac you need to build it manually. Afaik there a few programmes to provide prebuilt wine on mac.
If you don't have wine, get the rom.zip for your RUU from someone here or a windows machine.
Acknowledgementsckpv5 for his tutorial (http://forum.xda-developers.com/showthread.php?t=1705484)
mirGantrophy for his tutorial on how to do it on linux (http://forum.xda-developers.com/showthread.php?t=1974272) Check his thread for pics and screenies.
eLukas for teaching me how to extract rom.zip (http://forum.xda-developers.com/showthread.php?t=1729898)
CafeKampuchia for his tutorial (http://forum.xda-developers.com/showthread.php?t=1706070)
Some other forum(forgot its name) for telling me about a command (fastboot oem rebootRUU)
Let's start
Download the ruu for your device from ruu.androidfiles.org (gsm one v = primoU, cdma = primoC and dual sim = primoDS)
Extract the rom.zip
Linux - Use elukas' script
Mac - get the rom.zip from somewhere. Sorry.
Windows - Run the ruu. Search for temporary folder and copy the rom.zip to somewhere safe.
Extract the rom.zip. We need to flash recovery and kernel(boot_signed.img) from this folder.
Reboot phone to bootloader. Connect it to your system. Make sure fastboot detects the phone.
For recovery
Code:
sudo fastboot flash recovery recovery_signed.img
For kernel
Code:
sudo fastboot flash boot boot_signed.img
Code:
sudo fastboot erase cache
Now we flash the Ruu
Code:
sudo fastboot oem rebootRUU
You may get an error related to hboot. Flash the zip again.
I hope it works for you. If you're on windows, you don't need to type sudo before fastboot.
This worked well, did it in litterally 4 minutes :good:
Is there anything I should add to it?
Umm getting the Ruu was a bit confusing, but i figured it out. Primo....
Thanks, I'll add that the gsm version is primou ,cdma is primoc and primods is dual sim.
arnavk007 said:
Is there anything I should add to it?
Click to expand...
Click to collapse
where do i get mac zip?
vialsofliquid said:
where do i get mac zip?
Click to expand...
Click to collapse
The zip varies from device to device, so you need to download the RUU for your device and then extract the rom.zip from it.
Hi.. thank you for the guide..
actually I am still collecting information in case I need to flash back the stock rom,
but the thing that I want to ask is, do you know where I can get the stock kernel?
Is it also extracted from the windows ruu?
thanks in advance for your reply
-Rif- said:
Hi.. thank you for the guide..
actually I am still collecting information in case I need to flash back the stock rom,
but the thing that I want to ask is, do you know where I can get the stock kernel?
Is it also extracted from the windows ruu?
thanks in advance for your reply
Click to expand...
Click to collapse
Yeah, the RUU contains everything you need. Follow the guide and you'll be fine.
arnavk007 said:
Is there anything I should add to it?
Click to expand...
Click to collapse
I get this is old but, after
fastboot oem rebootRUU
You should
fastboot flash zip rom.zip
Thanks for posting this guide
Good work.
!#quote my post if you want to get my attention more quickly
HTC One S 1.5Ghz Soft Bricked to!
Hey! I have a similar problem to with my HTC One S. I tried the above mentioned but it always get stuck in ''Sending'' When I try to flash recovery or RUU.zip file
Edit: It's not stuck in sending anymore but I get this error:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
I'm thinking that this RUU.zip isn't a zip file I can install via fastboot. And is a SD-card zip file. Which is a problem due to that I can't mount the SD card. And this is the only RUU matching my cellphone and there's no .exe files I found for it
HTC-One-User said:
Hey! I have a similar problem to with my HTC One S. I tried the above mentioned but it always get stuck in ''Sending'' When I try to flash recovery or RUU.zip file
Edit: It's not stuck in sending anymore but I get this error:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
I'm thinking that this RUU.zip isn't a zip file I can install via fastboot. And is a SD-card zip file. Which is a problem due to that I can't mount the SD card. And this is the only RUU matching my cellphone and there's no .exe files I found for it
Click to expand...
Click to collapse
I gave up on RUU files all together and tried different ROMs til I found one that worked. Also managed to fix the SD card error with this guide: http://forum.xda-developers.com/showthread.php?t=2086156
ZE551ML - 4gb ram
I encountered this error when flashing thru fastboot.
My phone came from no fastboot/recovery then flash firmware with xFSTK, was able to get fastboot.
Tried commands like;
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
none of this works, getting " FAILED (remote: flash_cmds error!) " error.
Images are from WW_ZE551ML_2.15.40.13_20150506 official rom.
tried the clear cache command it just escape out of fastboot mode.
Also tried Asus Flash tool but getting failed error.
I hope someone could help.
Try flash the raw for .13 in flashtools ...5 minutes after you get "xfstki"- 'success!' but leave your cable in fone. Hopefully you see it flash to fone in that time. When you do see it flash leave it a while
Then start the flashtools ..if you see small green then red text in fastboot...restart flashtools when until it goes 'sky blue and bigger bold text' you will then get success there
P's, can you put all the links for fwr dnx and ifwi and raw etc here for me for .13 should I need these again ..my pc crashed ugh!
Thanks for your reply,
I'm at work right now.
But I'll try this later.
[SOLVED] FAILED (remote: flash_cmds error!)
This guide help me out..
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Thanks XDA.
Thanks for that,glad you`re sorted out... pc restored now saved all the stuff for zenny , pheeeew !
@asus_abz May i know how did you get rid of "FAILED (remote: flash_cmds error!) " error."
I am trying to fix my hard bricked Zenfone 2 and the only thing that seems working is fastboot but i keep getting the above error message.
Thank you!
ulbx said:
@asus_abz May i know how did you get rid of "FAILED (remote: flash_cmds error!) " error."
I am trying to fix my hard bricked Zenfone 2 and the only thing that seems working is fastboot but i keep getting the above error message.
Thank you!
Click to expand...
Click to collapse
Same problem here. Anyone got any experience on this? Tried the guide above. Getting this error message in CMD:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (12395 KB)...
OKAY [ 2.009s]
writing 'boot'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.831s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13967 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.917s
C:\adb>fastboot flash system system.img
error: cannot open 'system.img'
Asus Zenfone 2 (ZE551ML) /MM Z00A_WW_4.21.40.134
Workaround Solution to the dreaded remote: flash_cmds error!
Osaci said:
Same problem here. Anyone got any experience on this? Tried the guide above. Getting this error message in CMD:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (12395 KB)...
OKAY [ 2.009s]
writing 'boot'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.831s
...
Click to expand...
Click to collapse
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
Updated 07-30-17: Some of the source file links were reported as broken and an alternative source was found by and provided courtesy of @beachbouy Thanks beachbouy!
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Open (EXTRACT) the .RAW image file with Winrar, 7zip or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
nucleare GOD BLESS YOU !!! you saved my fuc***d Zenfone 2 now i can send it back to ASUS becouse the camera keep on closing. Thank you
Marvelous stuff , this should be in a thread of its own for those with gpt trouble
nucleare said:
I was getting the exact same error after using ... to unbrick my Asus Zenfone 2 ZE551ML. ... Hit the Thanks if it does!
Click to expand...
Click to collapse
Thanks, you save me!
great guide OP
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Hnk1 said:
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Click to expand...
Click to collapse
Thanks @Hnk1 for pointing that out! To be sure, (and feel free to correct me if I'm wrong) if I'm not mistaken, the commands are going to depend if they're unbricking from a failed Lollipop to Marshmallow brick, or a Lollipop to Lollipop update brick, or essentially the last stable android file system build prior to the brick. And just to note in case someone finds this thread far in the future, the commands referenced the filenames that originated from the extracted downloads which had been linked to tutorials and were not changed. Therefore, if restoring using alternative RAW files, one would need to adjust the img/bin files accordingly.
~-`-`-`-`-~
@Raul74 and @CrazyPhantomBR Thank you for the appreciation posts! It totally makes the time spent writing that all up worthwhile. And, I know that feeling of relief to see your device finally working again , so I am glad to have played a part in providing that experience for you guys
nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began(Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Start device in bootloader and connected with fastboot and run the following commands
Optionally (if you want to restore the full .RAW version)
Then seal the deal with
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
You rocked buddy :good:
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Hnk1 said:
great guide OP
Sometimes you will need the following commands too
Make sure you type the correct name
Click to expand...
Click to collapse
U 2 buddy...great work
nucleare said:
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Click to expand...
Click to collapse
Where other post-xFSTK instructions left me hanging, this helped immensely. Thanks so much!
nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Open (EXTACT) the .RAW image file with Winrar or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
GOD bless you and your family for this tutorial )
nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Open (EXTACT) the .RAW image file with Winrar or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
This Must ba a Sticky Solved Topic Not Tried yet but All Text Blog Telling my Situation
Edit:14.02.2017 GOD bless you Man Working Like a Magic Pls Mods Stick This Solution...
thank you to all for the kind words and more glad to hear it helped you. Perhaps I should rewrite the "tutorial" in a more 'toned down' and chronologically-and-well-laid out manner to be considered for sticky
EDIT: **that is of course, if the MODs see it as a worthwhile effort/meaningful contribution since this can be seen /regarded as a more lengthy answer to a troubleshooting question.
To clarify additional commands:
Hnk1 said:
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Click to expand...
Click to collapse
For the future reference of any who stumble upon this page in the future, the aforementioned commands from @Hnk1 will apply to you if you did not use, or did not successfully flash already with, xfstk-downloader_v1.x.x to previously restore from no loading screen type brick to USB icon screen boot-loop type brick and more specifically stands in as an alternative method for flashing ifwi/dnx_fwr/droidboot/OSP as outlined in the program's (xFSTK's) Standard Operating Procedure Documentation PDF excerpt, which is commonly found with the filename "ZE550ML_ZE551ML_xFSTK_SOP.pdf" and included in many, if not all, current unbrick Zenfone methodologies.
Man, you are awesome!, i lost two fk.. days trying to do this with the asus flashtool, but no sucess, with your tip worked perfecly!.
I'm saving it offline in case somethink like it happens again, (probably will, since i love testing roms).
Hey guys,
Recently I have bought used m8 with custom rom. Seller said he sells it because after trying to do factory reset (thinking it could restore to stock) he lost any gsm signal, only wifi worked. I had some experience with flashing sony mobiles and lg few years ago, so thought it would be easy to install stock rom and use device again. Googled a bit about flashing HTC devices, then downloaded rom, after that had some dificulties with win 8 and htc drivers, so tried to put rom into sd, it was too small. Somehow managed to put rom into device, tried to flash, had some errors, tried another roms, got another fails, changed my cid and mid, played with locked/relocked things, that didn't help either. Tried to restore a nandroid backup, even if it says restore was successful, after i choose reboot, it only boots me in bootloader. Now i cant access twrp, my pc recognises phone, but none of adb commands work.
I apologise if anyone got similar problem, but tried to look for explainations on my own, and found nothing, so this is my last hope to get it working.
Any help or info will be appreciated, I also am very interested in what you guys are doing, so i could even donate for people who can help alot.
***RELOCKED***
M8_WLV PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OS-6.12.401.4 (6.12.401.4)
eMMC-boot 2048mb
If any info more needed, just write, ill add anything you ask.
iTrolis said:
***RELOCKED***
M8_WLV PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OS-6.12.401.4 (6.12.401.4)
Click to expand...
Click to collapse
A big mistake has been made, either by you, or the previous owner. As you indicated the previous owner lost GSM signal, I would guess that person may be the culprit.
Here's what I mean: Your M8 version is Verizon, indicated by the product name M8_WLV. I can see from the OS number (6.12.401.4) that installation of Euro firmware was attempted.
The Verizon version is somewhat unique, in that its designed for use on US Verizon carrier's CDMA network (in addition to GSM, HSPA, LTE) and therefore has its own partition layout, radio firmware, etc. Trying to flash any other version's firmware to this device will not work, and may result in a permanent radio brick. Essentially, only Verizon firmware or RUUs should only be installed to this device. Unlike most other M8 versions, you cannot convert the Verizon M8 to another version by changing the CID/MID (after s-off) and flashing another version RUU.
Indeed, the OS number in parenthesis indicates a problem with the firmware. And I'll venture to guess that this line is also in red font (which also indicated a firmware problem).
Your best (and really, only) option is to try the proper Verizon RUU. A lot of times, this will fix the firmware, and get the radio to work. Although there is a possibility that its a permanent radio brick (as we've seen a number of times). Try the 6.21.605.3 RUU from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another couple mistakes that I can see:
There was never a need to relock the bootloader for what you are doing, since the device is s-off. Its not needed to do this in order to flash firmware or RUU (the main reason to relock bootloader) as this requirement is bypassed by s-off. A relocked bootloader won't interfere with the RUU I recommended. But it would hamper trying to install TWRP custom recovery.
adb won't work unless you are booted to Android OS, or in TWRP. Since neither of those are working, it is normal and expected that adb command won't work. Fastboot command should work, while booting into bootloader-fastboot mode (and only that mode). While fastboot is related to adb, there are important conditions and differences.
redpoint73 said:
Your best (and really, only) option is to try the proper Verizon RUU. A lot of times, this will fix the firmware, and get the radio to work. Although there is a possibility that its a permanent radio brick (as we've seen a number of times). Try the 6.21.605.3 RUU from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
If the latest RUU doesn't fix the radio signal, I suggest to install the lowest version 1.5x. as the lower version usually will fix the NV partition which related to radio and unbrick it. (This is what I read in VZW thread before)
ckpv5 said:
If the latest RUU doesn't fix the radio signal, I suggest to install the lowest version 1.5x. as the lowest version usually will fix the NV partition which related to radio and unbrick it. (This is what I read in VZW thread before)
Click to expand...
Click to collapse
Good to know, I wasn't aware.
I think the 1.5x files would be here: https://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
Edited my earlier post.
Your earlier link is good ... click 4.4.4 RUU zip link, it's 3.28.605.4 RUU
The only way to reset the partition to out of the box stock is to flash your carrier's 4.4.4 firmware and the stock recovery for you device. Reboot to recovery and select factory data reset and let it do it's thing. If you watch the reset log you will see it mention resetting the NV partition.
Source : https://forum.xda-developers.com/showpost.php?p=57453624&postcount=2
guys, thank you for help, downloaded latest .zip file, renamed it to 0P6GIMG.zip, did fastboot flash zip 0P6GIMG.zip and it shows this: target reported max download size of 1826
Invalid sparse file format at header magi
any ideas?
iTrolis said:
guys, thank you for help, downloaded latest .zip file
Click to expand...
Click to collapse
Try the 4.4.4 RUU as ckpv5 advised in his most recent post.
what if i have changed cid and mid thinking to make my device to international?
now my cid is HTC__032
and MID 0P6B12000
i have to change these to original for verizon?
iTrolis said:
what if i have changed cid and mid thinking to make my device to international?
now my cid is HTC__032
and MID 0P6B12000
i have to change these to original for verizon?
Click to expand...
Click to collapse
That's correct, you will need to change back to the Verizon CID and MID to run the RUUs, firmware. Sorry, I missed that in the details you provided.
Alternately, if you change to SuperCID (11111111) in most cases this will bypass the MID check (and save you some steps).
now got RUU mode with exclamation marks on the edges of screen..
changed cid to vzw__001, but now need to get to fastboot again, to change it to supercid and will try 6,0 ruu.exe 4,4,4ruu.exe and 6,0 .zip files i have downloaded
Edit: cid changed to supercid, still stuck on silver htc logo with 4triangles on the edges. cant find a solution...
Read this on how-to : https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your ruu.zip not the one in the guide.
At the end of the guide, you'll see there are 3 methods to install ruu.zip
tried your method and got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip rom.zip
sending 'zip'... (46028 KB) OKAY
writing 'zip'... FAILproject does not have sa key to decrypt rom
FAILED (remote: project does not have sa key to decrypt rom)
Execution time is 2(s)
already tried to do it with ARUwizard.exe and stuck on silver HTC letters with 4 triangles nad exclamation marks on the edges of the screen, cant boot to bootloader, and i dont have enough storage in SD card to put rom in it
edit: trying again with another .zip file, now got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip 1.zip
sending 'zip'... (1760932 KB) OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL24 parsing android-info fail
FAILED (remote: 24 parsing android-info fail)
Execution time is 56(s)
ckpv5 said:
Read this on how-to : https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your ruu.zip not the one in the guide.
At the end of the guide, you'll see there are 3 methods to install ruu.zip
Click to expand...
Click to collapse
another question, what should be there in that ruu.zip? downloaded few and there is one with rom.zip, adb.exe, ARUwizard.exe, alot of .dat files and bitmap images inside, others are only with boot-signed.img and android-info.txt
iTrolis said:
another question, what should be there in that ruu.zip? downloaded few and there is one with rom.zip, adb.exe, ARUwizard.exe, alot of .dat files and bitmap images inside, others are only with boot-signed.img and android-info.txt
Click to expand...
Click to collapse
What are those you downloaded ? Which link ?
In my earlier post, I specifically suggested this one : https://www.androidfilehost.com/?fid=95784891001604006
If in ruu.zip you downloaded has all those files, it means you need to extract the ruu.zip then run the ARUwizard.exe to install.
ckpv5 said:
What are those you downloaded ? Which link ?
In my earlier post, I specifically suggested this one : https://www.androidfilehost.com/?fid=95784891001604006
If in ruu.zip you downloaded has all those files, it means you need to extract the ruu.zip then run the ARUwizard.exe to install.
Click to expand...
Click to collapse
yes i have downloaded exactly this and two more, now extracted this, ran wizard and got error 171 usb connection error, tried another usb cable, another usb slot but same error, what could solve this?
Do you have latest HTC USB drivers installed ? As explained in this guide - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
where it says - first you need this ?
Also try with USB2.0, if running it with ARUwizard.exe (that also explained in the same guide in the link at the lower part).
Or take only the rom.zip then
htc_fastboot flash zip rom.zip
ckpv5 said:
Do you have latest HTC USB drivers installed ? As explained in this guide - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
where it says - first you need this ?
Also try with USB2.0, if running it with ARUwizard.exe (that also explained in the same guide in the link at the lower part).
Or take only the rom.zip then
htc_fastboot flash zip rom.zip
Click to expand...
Click to collapse
downloaded htc sync manager, uninstalled it, tried both usb cables on all three different usb ports, same 171 error, tried to flash zip, got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip rom.zip
sending 'zip'... (46028 KB) OKAY
writing 'zip'... FAILproject does not have sa key to decrypt rom
FAILED (remote: project does not have sa key to decrypt rom)
Execution time is 3(s)
I downloaded the 3.28.605.4 ruu.zip to see what's going on here .. it's a signed RUU, you're not supposed to extract it. No normal zip archiver can extract it properly.
Rename the whole as ruu.zip or rom.zip then htc_fastboot it after you put the device in RUU mode
fastboot oem reboot RUU
fastboot flash zip ruu.zip (or rom.zip if you renamed it rom.zip)
fastboot reboot-bootloader
also make sure your windows extension is not hidden so it won't actually become ruu.zip.zip where you will have unable to load ruu.zip error
The whole
0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_HSM_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393779_signed_1.zip
is the rom.zip
ckpv5 said:
I downloaded the 3.28.605.4 ruu.zip to see what's going on here .. it's a signed RUU, you're not supposed to extract it. No normal zip archiver can extract it properly.
Rename the whole as ruu.zip or rom.zip then htc_fastboot it after you put the device in RUU mode
fastboot oem reboot RUU
fastboot flash zip ruu.zip (or rom.zip if you renamed it rom.zip)
also make sure your windows extension is not hidden so it won't actually become ruu.zip.zip where you will have unable to load ruu.zip error
The whole
0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_HSM_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393779_signed_1.zip
is the rom.zip
Click to expand...
Click to collapse
downloading that .zip again, but i think that RUU fail doesnt let me to work now, how can i access fastboot when im locked to that ruu fail screen? power+vol up then vol- just restarts me to that black screen with htc letters and four triangles on the corners of screen
type command
fastboot reboot-bootloader
First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.
Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.
I flashed everything except system and boot on top of Omni rom. Everything works great.
Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.
On x720 some of the files were divided into scatter files, had to do some research to get them sorted.
Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation
Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:
tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.
ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same