Develop Bugs

[Q] NOOB bricked acer a100 help!

I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!

same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.

are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps

[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.

Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.

cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.

were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!

pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.

you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.

pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium

not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper

I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.

Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?

[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.

did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?

I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.

i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.

mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696

eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"

My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?

Fastboot-unbrick your device with 'no display'

How to USE FASTBOOT commands in case your Device got Soft-Bricked with NO DISPLAY
Click to expand...
Click to collapse
Let's describe Softbrik:-Anything caused to your phone except damage to Hardware of your phone which put your Device into a state where it is not booting up and kept showing White, Gray, Blue or Black Screen or Either It gets stuck at Company logo Screen. This may occur if something goes wrong during Rooting, flashing Recovery or ROMs or during Updating in Recovery Mode or either being caught by some wrong software or VIRUS !!!
Preface to the Guide:
Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host computer via USB. It allows flashing of unsigned partition images and also can erase partitions. Its a part of Android Developement Kit (Android SDK).
Use of FASTBOOT is disabled in production devices since USB support has been disabled in the bootloader. You must have an Engineering SPL, or an SPL that is S-OFF or Unlocked bootloader to use 'fastboot'.
After installing the Android SDK or ADB Standalone you can use 'fastboot' in addition to the more common ADB.
One can use the attached .android folder if u want to skip downloading Android SDK. (Refer Attachment)
Verify SPL S-OFF or Bootloader Unlocked:
Not required for Micromax !! But certain Production Devices like Sony HTC LG etc may need bootloader to be unlocked before carrying out this process. My simple advice to people is.. "If you enjoy experiments on your device, you must be ROOTED and to ROOT you device you may need to have unlock bootloader"
Preparations:
(1) Download attached .android.zip, Extract and place .androidfolder on C:/ drive of your PC. So the path of this folder will look likeC:/.android
(Never remove this ".android" folder from C:/ coz you will require it whenever u want to experiment with you Droid using ADB or FASTBOOT methods. I assure... You can do a lot more with it; if you really explore how to use various commands !!!)
.android folder is containing adb.exe, fastboot.exe and related drivers adb_usb.ini, android_winusb.ini AdbWinApi.dll and AdbWinUsbApi.dll and other files; all together not more than 800KB
(2) Connect Device in 'USB debugging ON' mode.
Ensure Drivers for your Device are already installed on the host computer
Note: I recommend you should always keep USB Debugging opetion 'ON' as it only can help you, in case, your device get SoftBricked and you cant see anything on Device Screen. Remember that with USB debugging 'OFF' your Device can't communicate with your Host Computer.
(3) Host Computer Ability to Launch Command Prompt:
On Windows-XP or earlier, to start ADB (Android Debug Bridge) You need to locate your folder containing adb.exe where as Windows-7/Vista/Other-Latest-OS can directly launch command prompt from the Folder itself by Shift+Right Click on Mouse and Selecting "Open Command Prompt from here".
Hence 'Locating 'adb' folder-steps' are for XP users only, However higher OS users can skip it and can directly start giving 'adb' commands after opening cmd from .android folder.
(4) So now, Open Command Prompt (in Windows XP), it will return like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\USERNAME>
(As our adb.exe is in C:/.android.... we will type: Cd C:\.android)
C:\Documents and Settings\USERNAME>Cd C:\.android (Hit Enter)
C:\.android>
Let's give command to detect attached device by writing: 'adb device'. On hitting enter it will list all devices attached to your PC.
Code:
C:\.android>adb devices
List of devices attached
XXXXXXXX-XXXX device
Now u can do a lot while your Device is attached in 'adb mode' e.g.:
Code:
1. Rebooting into Bootloader (FASTBOOT)
2. Installing apps on as /system/app or /data/app
3. Copying Files to/from your SDCARD
4. Pulling Files or Apps already installed on your /system or /data partition
To Understand adb commands and how they work please read:
http://developer.android.com/tools/help/adb.html#commandsummary
Let's come back to ISSUE: "We have a SOFTBRICKED devices !!!"
(1) Booting into FASTBOOT mode:
Let's come back to'fastboot' as we need to flash new ROM or to apply update.zip in a Softbricked deviceNote: Let your device remain connected to PC and don't disconnect untill You finish you job-successfully and get your Device again in working Factory Condition.
""fastboot reboot-bootloader" This command is used to reboot your device into bootloader i.e into fastboot mode) and In this Mode your device will stuck into boot logo only and u cant operate it. ;D Well we are not concerned as we already have a bricked device with no screen display !!!. Lets go ahead...on cmd follow:
Code:
C:\.android>adb reboot-bootloader
C:\.android>fastboot devices
XXXXXXXXXXXX fastboot
(2) Unlocking-ReLocking Bootloader:
(Skip if u working with pre-unlocked devices)
C:\.android>fastboot oem unlock
...
SUCCESSFUL
finished. total time: 118.063s
Click to expand...
Click to collapse
(Accept/Decline warning on your devices screen. Select YES to Unlock)
(Once ROM is flashed) To relock Bootloader use command: fastboot oem lock:
Code:
C:\.android>fastboot oem unlock
...
SUCCESSFULL
finished. total time: 118.063s
(Accept/Decline warning on your devices screen. Select YES to ReLock)]
(Skip if u working with pre-unlocked devices)
(3)Get 'Recovery.img' and 'Update.zip' for your Device:
Lets Wipe the Data and then proceed to Flash new ROM/Update.zip
IMPORTANT: Copy the stock recovery.img and your devices' Update.zip[ in .android folder(You can get it even by searching it in this forum or by Googling for it..) So I assume that you have it....in your .android
Abbreviations:
recovery.img = Stock Recovery of your Device
Update.zip = Update Package/Stock ROM of your Device
Let's start wiping and updating process with following commands:
(4)Wiping Old Data and Flashing new Update.zip:
Code:
C:\.android>fastboot -w
SUCCESSFUL
C:\.android>fastboot update Update.zip
(Here Replace Update with Full Name of your any Update.zip that you copied to .android folder)
Your phone will update and automatically reboot into the Factory State. Cheers !!!
Note: Its important to spell the file name correctly that u want to flash/update. No space between name are allowed. This process will only be successful if your device is still carrying recovery partition 'intact'.
.....If above wiping/updating FAILS....
If you still in "No Display State", extract update.zip to .android folder (U can use 7zip).
You will find following main .img files, each incorporate specific partition on any android device. In our case we can extract following:
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Code:
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partionsusing the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Code:
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img :(here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
..If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Code:
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Code:
C:\.android>adb push update.zip /data/sdcard
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Code:
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)'ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!! ​

One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?

RmatriX1218 said:
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
Click to expand...
Click to collapse
bro if your volume + key is not working so how can u say that your device is soft bricked...
i think you should repair your volume keys and than try to move to recovery...
& one more thing without installing all drivers/thing u will not be able to access fastboot mode.....

Hey!!
Please please help me!!
I have MICROMAX a54 ninja 3.5.my mobile stuck in bootloop and soft bricked!!
When I turn on my devices it stuck in logo ninja 3.5.
I also try to go in recovery mode by pressing volume up+home key+lock key!
But it doesn't enter in recovery mod!!
Now what am I do??
Please please help me.
Thank you in advance..

I think for going in recovery:-
1. Press and hold power button.
2. While holding power key, press and hold both volume keys, (vol+ & vol-)
3. When mmx logo comes it will display a message vol(+) for recovery and vol(-) for fast boot then again press vol(+) for once,
And now your in recovery

I lost my recovery.
And I can't go into recovery mod!!
Please help me
Sent from my YU5010 using XDA Free mobile app

What do u mean by, lost your recovery???

I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app

Ok ok just try flashing your official rom
---------- Post added at 10:35 AM ---------- Previous post was at 10:17 AM ----------
Aakash mehta said:
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Just download your official rom, Your device driver for pc, and install the rom to your device using "sp flash tool"

Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app

Aakash mehta said:
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
1.First download your stock recovery for your mmx a54 from here http://d-h.st/D7G
2. Now download sp flash tool from here https://drive.google.com/file/d/0B9S_ERLSMngHVE9Qc25ObGU1UU0/edit?pli=1 install it to your pc.
3. Download drivers for a54 from here singledrivers.blogspot.in/2013/12/micromax-ninja-a54-usb-driver-for.html?m=1 install the driver to your pc.
4. Download your phone stock rom from here http://d-h.st/fg2 place it in your external sd card(mmc) of your device.
5. Download scatter file from here www.mediafire.com/view/rvz1c5tiifx7yck/MT6575_Android_scatter.txt
6. Now run sp flash tool in your pc, browse to the scatter file.txt, turn off your phone remove the battery and connect it through usb to your pc. (Connect the device without battery)
7. Now select the recovery tab in sp flash tool browse to the recovery.img file (Which we hv downloaded before). Now select the option download in sp flash tool it will Start flashing your stock recovery to the device, A green tick marked will be comes as the flashing complete, now remove your device from pc.
8. Now goto recovery by vol key combination.
9. Now select apply update from sd card and select the stock rom.zip file
10. When flashing done then, Wipe Cache Partition and factory data reset of your device.
Now just select reboot device now it will take around 10min to boot for the first time so wait. Hope this helps you

Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app

Aakash mehta said:
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Don't say thanks my Buddy just press thanks button.

Hello
I tried sp tool flasher!!
I followed all steps which were given by you!!
BT although not any change in my mobile..
When I tick recovery and then browse recovery.img file and click download button but nothing had happened..
It didn't detect my mobile and didn't go for procedure!!
So now what am I do???
You helped me very much!!
Bu please further help me...
Sent from my YU5010 using XDA Free mobile app

Hv u installed driver properly, just trust me try different usb ports

Yeah i installed drivers properly!!!
Sent from my YU5010 using XDA Free mobile app

So your device is not recognizing by sp flash tool r8

I think so
Sent from my YU5010 using XDA Free mobile app

micromax a210
I have a problem with fastboot stuck on system erasing on adb fastboot mood also userdata and cache only flash recovery and boot img sp flash not working with this phone I do other mtk android with sp tool successfully what I do

What if the device is recongised in adb as : (device name) recovery, but can't actually boot into recovery (twrp) and thus when entering the command : adb reboot fastboot it can never actually boot into fastboot ?
Are there any adb commands that can do the trick or is it game over ?

LG G3 Bricked / No ADB / No download mode / No recovery

Hi,
Since the rom ( http://forum.xda-developers.com/lg-g3/development/rom-resurrection-remix-lp-v5-5-5-t3198675 ) of my phone crashed. After reboot, the phone is blocked on LG logo. Now, i can't enter in recovery mode (or in the download mode) and when I start my phone, it's fixed on the LG for 5 to 10 minutes, and after that it goes to a terminal (started fastboot mode).
I have read several tutorials to use fastboot to flash the recovery to reinstall a rom, but i have a error when i tried to erase or flash the recovery partition.
I look on my phone, and this error appear : "failed to send erase grp start address".
what can i do to fix this error ?
Thanks.

up please

Use the "boot" command instead of "flash" and it should boot up into recovery or downloadmode, depending on which file you use

I tried but i am stucked on teamwin logo.
Which file do i use for download mode ?

Hard to tell, there are some laf.img files floating around on xda and google or even better, extract the laf.img from the stock kdz depending on your android version (for instance you flashed 6.0 you pick the 30b kdz and extract it with the firmware extraction tool)
I would suggest you to and try to use the boot command with them..
Be carefull, do not use the flash command until you found one that boots into downloadmode properly or you can loose your fastboot mode aswell
From then on you should be able to boot into the downloadmode and flash a new firmware via the lg flashtool

I need help please. What can i do to re install a rom ?

Does your PC recognise the port.?
I found tutorial under bender_007 signature. People seemed happy with tool.
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
Doesn't hurt to read and ask some questions.

no i can't connect my phone with port. I think, i nned to correct the error with fastboot. (remote : failed to erase partition)

th0was said:
no i can't connect my phone with port. I think, i nned to correct the error with fastboot. (remote : failed to erase partition)
Click to expand...
Click to collapse
Can you elaborate, how exactly your phone crashed, it is very unlikely that it will mess all the partitions just by crashing the rom?

The rom crushed twice, and now i can not access to recovery to install a new rom. I only have access to the fastboot command. Adb not working.
I tried to boot on recovery.img, but it's not working.
Thank for your help.
Regards,

Help please ?

Today i can connected to my phone with ADB when i tape this fastboot command : fastboot boot ./recovery.img.
I can too go into my phone as root with adb command : adb shell.
i tried to push flash_image on my phone and use it, but it donesn't work.
how can i flash my phone with adb command ?

D855 Stuck at Boot Screen

So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.

First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...

bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.

In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)

bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.

it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor

bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?

check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)

bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.

Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.

HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)

bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.

HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it

Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.

[SOLVED] TWRP Bootlop, no ROM installed, fastboot not detected...

SOLVED, the solution is simple, i just quickly installed the adb drivers during the TWRP screen showed up... have to attempt a few times but finally get it to works, then i flashed the rom using fastboot mode
Hey, i was in twrp and i wiped data and system, and it suddenly reboots...
after booting it shows some error messages then it reboots again in loop... i have no OS installed currently
i tried go to fastboot mode, installed adb drivers on 3 different computers each running windows 7, 8, and 10 but still cannot detect the device in fastboot mode...
anyone knows the solution ?? Thanks Before...
If video not show up, heres the link https://www.youtube.com/watch?v=FDQqBLMvD0E
See the attachment to see the error message

- download "P2a42_S048_161111_ROW_fastboot"
- Download this file" flashall.rar"
- Go to the file "P2a42_S048_161111_ROW_fastboot" and unzip it .. !!
- Unzip the file "flashall.rar" and move the file to the folder (P2a42_S048_161111_ROW_fastboot / sw )
Then Install ROM ... by fastboot mode ... and clicking on the flashall file

Permeableaxis5 said:
Don't do this if you don't want to have your phone baseband completely removed meaning no sim card function at all. I did exactly this when trying to install stock room and it deleted my baseband. Luckily I had made a backup a month before that. I restored it from the backup and the phone (sim card) started working again.
Anyways, back to the original issue. So you're saying your phone isn't recognized in fastboot? When I wipe system and data and then go into fastboot and enter "fastboot devices" it shows nothing but I can still flash files into the phone. I'm guessing this is because the phone has no 'name' due to the system wiping. So try going into fastboot on your phone, connect it to PC and open adb, and then enter the command 'fastboot flash recovery twrp.img' (download the latest version of TWRP for Lenovo P2 and rename it to twrp).
If then you are able to enter TWRP after rebooting, download stock Lenovo P2 ROM and flash it.
Click to expand...
Click to collapse
How did you make backup

i have soled it, i will edit the post, thanks for all the help