Database Users

X800 Fastboot brick

Hi guys I tried to root my LeTV 1 Pro but it didn't worked.
My phone keeps rebooting in fastboot ( I see the penguin 10-15sec and it reboot again and again) or it stays alight with the penguin.
Computer doesn't recognize it.
Thanks.

Try and plug it to your computer then keep power and wol down pressed for like 15 sec: now fastboot should stick and device shouldn't reboot, so you can flash a recovery (TWRP?) and start over with a new ROM.

Thank you for your reply,
It still doesn't work, penguin stays on screen but it's not recognized by computer ( before the brick it was)
I'm not very experienced in rooting btw.
Edit : The recovery.bat in the file X1_X800_TWRP_Recovery2.8.7.0 says "Complete! The device is ready to reboot into Recovery." which I do but it keeps reboot with the pinguin on.

I recieved my phone today and it just wont stay in fastboot mode. I can do anything I want but it just keeps rebooting before I can flash anything. Any suggestions on how I should keep the Phone in Fastboot mode?

You need to install drivers. After that it will not reboot anymore. That worked for me atleast.

What kind of drivers do I need? Please link them to me I have tried a lot of drivers. The thing is that the phone also does not stay in Fastboot mode when not plugged into the PC.

It's my topic for my problem so don't ask questions for you on it please u_u

zamul said:
It's my topic for my problem so don't ask questions for you on it please u_u
Click to expand...
Click to collapse
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.

DatNoob said:
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.
Click to expand...
Click to collapse
Zamul don't be mean. He just asked for help as you did...
I have downloaded drivers (I think) from https://twrp.me/devices/letvle1pro.html where I also get twrp 3.0.2.0
Btw if you are using Windows you can open Device Manager and there you will see your device and what drivers it has installed (you can always use update drivers function, maybe that will help too).
Here is a little guide how I managed to get twrp:
Just download it (drivers and intall them) (and download twrp also). Place twrp file to the folder where you have your adb installed.
In phone settings go to developer menu (first you need to unlock it) and you need to switch on usb debugging.
Connect phone to the pc via usb.
Open command prompt in your adb folder and type Adb devices (if you have drivers installed corectly you will se your devices connected under some code).
Then just write Adb reboot booloader and phone will restart to the recovery.
Type into the comand prompt: fastboot flash recovery name***.img (where the name is the file name of twrp you have downloaded- just a tip: rename it so it is easier to remember for example to twrp. Then the command will look like: fastboot flash recovery twrp.img)
If succesful, write fastboot reboot and that is all.
Btw for me it did not work first time. I had to load twrp for second time and when I wrote fastboot reboot then I immediately pressed volume up so It went directly to twrp recovery.
Hope it helps. Cheers

I have this problem
Hello
I have your problem have you solve this?
Thanks

Hi guys. I have a problem! My letv x800 CN boots to TWRP but doesn't start the system (EUI logo loading all the time) I don't know how to transfer ROM into the phone in order to flash it. I installed all the drivers and PC recognize it. PLEASE HELP!!!

My lenovo a6000 is hard bricked. PC not detecting it.

Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?

arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method

JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc

arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.

I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected

sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.

arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.

sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference

One update. I can get into the fastboot mode. But the bootloader is locked. What to do?

arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.

sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"

arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.

sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight

sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".

arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?

sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed

arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.

sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.

arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock

arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".

[Help] I bricked my Axon. Need help.

So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.

You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?

senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?

nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.

raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.

senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...

Try the Marshall London Bootloader Interface driver maybe?

nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?

senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.

*SOLVED* Embarrassed to ask for help - but please help!

Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil

nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool

marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?

nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power

it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.

You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“

marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.

nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?

No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.

Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped

The system has been destroyed please help

So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?

Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328

emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen

lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637

lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.

lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"

emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.

lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?

emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.

Try flashint stock on EDL mode.

Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!

Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.

yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.