Develop Bugs

[Q] Help needed. Stuck on htc bootimage

Hello all. Im kinda new to this thing but with some help of my friend I managed to succesfully downgrade, root and flash a new radio and leedroid 2.2.3 rom to my unbranded DHD. Now after a week the Rom Manager updated my Clockwork mod to 3.0.0.5 and now that I had to boot my phone I'm stuck on htc bootimage. I can still get to recovery and have tried to restore backup but nothing works. I think it is because of the Clockwork mod is on v. 3.0.0.5 and backups are 2.5.1.3. What is there to be done at this point? Can I downgrade CWM somehow or do I need to flash a new ROM that supports CWM 3.x.x.x? Any help is appreciated

hi i had the same problem
but i took my sd card and connected it directly to comp.
I then downloaded and copied over the cm7 update package the went in to recovery and installed from ZIP..
I was then able to at least boot up so i could get into clockwork to do my backup

Download recovery-clockwork-2.5.1.3-ace.img
MD5 checksum
Place in the sdk folder where your fastboot.exe, adb.exe is located.
Boot your phone into Bootloader FASTBOOT, and connect to pc with USB cable. It will change to FASBOOT USB.
Open CMD and navigate to that folder (cd\program files\android\android-sdk-windows\tools\ on my pc, maybe different on yours)
Type in: fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img
After done, type: fastboot reboot, disconnect, click on BOOTLOADER / RECOVERY
Back up sdcard first, just in case your backed up recoveries become corrupted, never know.

UpInTheAir said:
Place in the sdk folder where your fastboot.exe, adb.exe is located.
Boot your phone into Bootloader FASTBOOT, and connect to pc with USB cable. It will change to FASBOOT USB.
Open CMD and navigate to that folder (cd\program files\android\android-sdk-windows\tools\ on my pc, maybe different on yours)
Type in: fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img
After done, type: fastboot reboot, disconnect, click on BOOTLOADER / RECOVERY
Back up sdcard first, just in case your backed up recoveries become corrupted, never know.
Click to expand...
Click to collapse
So I place the both img and checksum to sdk folder? And by booting to fastboot you mean first goin to hboot then selecting the fastboot option on screen?

Yes, Fastboot. Make sure it changed automatically to Fastboot usb when connected to pc.
You don't need to put the md5 txt file in the same folder. It is used to check the the download was not corrupted, use a md5 checker from Google, and if numbers match same as the txt file you download before, all will be good to flash.
Sent from my Desire HD using XDA App

The MD5 file seems to be empty :/ Nevermind found the md5.
Now that I tried to flash the img the cmd says that can't find AdbWinUsbApi.dll since the SDK has moved it and adb.exe platform-tools instead of just tools :/
It tells me to update path enviroment but how do I do that?
Thx
Edit2: Thx UpInTheAir for the tips! Got my DHD alive again ! In ROMManager App it still says I have the 3.0.0.5 isntalled. Is this only a bug since I didn't update anything I think :/?

[SOLVED]What happen if I flash ROM using the not recommended recovery?

Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)

Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App

Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(

From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery

3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App

kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.

It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..

SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"

Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)

superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.

I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/

superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........

1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.

superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App

I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.

UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???

superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.

Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/

UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows

superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.

[Q] Arc S, fastboot stuck at " sending 'boot' "

Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen

First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i

The file from the zip file is called "boot.img". I have copied it to the fastboot folder, and I am running "fastboot flash boot boot.img", as the "how to-" says.

Reinstall drivers
Sent from my LT15i using xda premium

espenta said:
Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen
Click to expand...
Click to collapse
did you make the phone enter fastboot mode?
you should run "fastboot devices" to see.

Thanks for the replies!
I tried on a different computer this morning, and here it worked immediately. Not sure what was wrong on the other one, because I installed the same SDK packages and USB driver. Installing ROM at the moment.
[Edit]: Everything seems to be working fine. Very happy with CM10 at the moment

dewa999 said:
First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i
Click to expand...
Click to collapse
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...

Tech-G.ONE said:
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...
Click to expand...
Click to collapse
You already asked for help in another topic, why here again?

Someguyfromhell said:
You already asked for help in another topic, why here again?
Click to expand...
Click to collapse
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....

Tech-G.ONE said:
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....
Click to expand...
Click to collapse
i dont like flashing kernel by flashtool, as far i done several 2011 devices the best method allways was over adb:good: & it pretty easy.
download android sdk & open the exe. leave all like it is (only may make sure google usb drivers are checked) & press on install.
after install place the boot.img here: ...\sdk\platform-tools
2. connect device into fastboot mode (blue led)
3.click in a empty space in the folder. now HOLD SHIFT & right click, choose ''open command line window here'' (<-- or sth like that sorry my setup is german)
4. enter 'fastboot devices' --> your device should be recognized as a bunch of numbers.
5. flash kernel by entering ''fastboot flash boot boot.img'' it tells you all done.
6. ''fastboot reboot''
7. enjoy new kernel

[Q] How to restore back to factory settings after using towel root

I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.

Flash a stock r for your phone
swagg blasted from TMO LG G3

jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?

If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?

fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.

@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.

Doesn't the boot loader have to be unlocked to flash a ROM via adb?

try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img

Thank you very much I will try this today.

I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?

Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).

I badly need help

I have the Zenfone 2 and it is stuck in bootloop.
My brother boot it to CWM and flashed Paranoid Android without unlocking the bootloader and flashing TWRP. Now the phone stuck in bootloop, i tried flashing system.img the stock one but it is telling me that system.img cannot be loaded. What should i do? It is now bootlooping. I dont know what to do.

ebanreb37 said:
I have the Zenfone 2 and it is stuck in bootloop.
My brother boot it to CWM and flashed Paranoid Android without unlocking the bootloader and flashing TWRP. Now the phone stuck in bootloop, i tried flashing system.img the stock one but it is telling me that system.img cannot be loaded. What should i do? It is now bootlooping. I dont know what to do.
Click to expand...
Click to collapse
Hi, I unfortunatelly am not able to solve your Problem, but maybe you could help me with mine. Could you pls upload the System.img? I am only able to find *.zip and adb doesn´t want to Flash it at all
Thanx in advance

Blubber120 said:
Hi, I unfortunatelly am not able to solve your Problem, but maybe you could help me with mine. Could you pls upload the System.img? I am only able to find *.zip and adb doesn´t want to Flash it at all
Thanx in advance
Click to expand...
Click to collapse
Go to Original Android developement. It's in the pre-rooted thread, these are the ONLY img files for roms available unless you push the zip file using ADB...

Flash the system zip file rather than trying to flash simply the .img. The zip files are in this thread (http://forum.xda-developers.com/zenfone2/development/asus-zenfone-2-rom-t3054956) and might help because you're also flashing default recovery... could be CWM.
Also try flashing using fastboot.

your phone model?

ze55m1

Rma

What worked with me, Problem is simmilar, I flaged the Boot.img and androidboot.img, which Werke attached in the custim Rom folder, too. Without that, I gut stuck at the Boot Logo, now all works fine and I am trying to be up to date with the Roms.

Blubber120 said:
What worked with me, Problem is simmilar, I flaged the Boot.img and androidboot.img, which Werke attached in the custim Rom folder, too. Without that, I gut stuck at the Boot Logo, now all works fine and I am trying to be up to date with the Roms.
Click to expand...
Click to collapse
1. download the latest recovery from here https://dl.twrp.me/Z00A/ and firmware from here http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.97-user.zip
2. download and install adb and fastboot driver from here http://forum.xda-developers.com/showthread.php?t=2317790 and intel usb drivers from here https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
3.the adb driver should have installed in your pc OS drive [ which is C: ] put the downloaded recovery and firmware in that folder [where adb is installed] then in that folder, open command window by pressing shift and right click and a dialogue box will appear then open the command window from there and enter this command fastboot flash recovery {name of the recovery twrp something}.img then connect your phone to your pc and enter bootloader in your phone and press enter in command window.
4.after that put the downloaded firmware in any sdcard and put it in your phone then open recovery mode in your phone and go to reboot>recovery [yeah you have to reboot the recovery] then when recovery open again then go to wipe>advanced wipe> and select system,data,cache,dalvik and internal storage [internal storage is optional but if you choose it then it will wipe all your data in your phone] then wipe it and go to install section then choose the extsdcard [it should be written internal storage click on that then you can choose your external storage] then in the extstorage choose the firmware you downloaded and just swipe to flash.
5.patience ..because it would take time and maybe get stuck at 52% or 59% ..so just let it take time for installation [btw connect your phone to thr charger in this process]
6.after it done then reboot your phone and ALL DONE. [the first boot will take some mins to boot up]
Sent from my ASUS_Z00A