LG Leon H340N fastboot not working - LG Leon Questions & Answers

Hello!
I have a very big problem. My LG Leon H340N is "bricked" totally, there is only fastboot mode in phone, nothing else.
The problem is that fastboot is not working, when i try to execute some commands it all the time gives me answer: FAILED(Unknow Command) and i don't know how to fix this, i don't have access to download mode, i don't have access to hard reset menu, i don't have access to recovery mode, only fastboot
Could somebody help me ?

How did you get into fastboot mode?

I connect device and laptop via USB and device is starting into fastboot mode automatically.
When device is connected i open cmd (run as administrator) and C:\ cd adb = C:\adb> fastboot devices - and it shows me my device connected as fastboot device then I try to execute some commands but it always gives FAILED(UnknowCommand). The fastboot drivers are installed - original google drivers from android sdk. I'm using Windows 7 Home Premium, i try execute some commands on other laptop with windows 7 starter but the same thing - FAILED(Unknow Command).
Thank you for reply, Regards

Flash the version MS34510d_00

I don't have MetroPCS version it's h340n. And i can't flash anything, because fastboot is not working

Install android 5

Dude, i know, i want to install android 5 but you don't see that fastboot in my phone IS NOT WORKING ? every time, when i try to exec some commands it gives me: FAILED(UnknowCommand)

for mode download

Related

Fastboot, waiting for device.

Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
ejnahuj said:
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
Click to expand...
Click to collapse
Hello
1. you need to install a ROM with fastboot the most common is europe + fastboot (KDZ) ROM.
http://www.mediafire.com/?96nu9lb6afx22a7
2. once its finished phone will reboot, then fast login into fastboot mode CAMERA + POWER
3. You are missin 1 thing, OEM usb drivers not GOOGLE usb drivers as some tutorial says, those are just for Android Developer Phones (ADP), Nexus One, and Nexus S.
LG_Android_USB_Driver_Rebuilt
http://www.mediafire.com/?pbigrb8cimmxa4d
* these drivers are for your pc to recognize your phone in fastboot mode, they are not the normal LG usb drivers
4. for install the drivers abouve follow these smll tutorials
* if using windows 7:
http://developer.android.com/sdk/win-usb.html#Win7
* if using windows XP:
http://developer.android.com/sdk/win-usb.html#WinXp
once is installed plug your phone in fastboot mode to your pc, now your pc has to recognize your phone wait until it finish installing the drivers and read it properly
5. unzip the new ROM files into C:\*SDK\tools
6. open CMD Terminal and go to C:\*SDK\tools, type:
cd C:\*SDK\tools
7. once in, type
fastboot flash recovery recovery_clockwork_3.x.x.x_swift.img"
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
*Just in case it drops you an error AdbWinApi.dll missing here is the file. place it in C:\*SDK\tools and try again
http://www.mediafire.com/?3s3z5uym2rw5r7u
Any other question PM me
fastboot "waiting for device"
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
murthy.krishna00 said:
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
Click to expand...
Click to collapse
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Quinny899 said:
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Can you please clearly explain it, I couldnt get that. The prob was even though I installed the diver fastboot cannot detect the device..
Turn the phone off normally and when you'from holding down power to turn it on, also hold down camera until you get a black screen.
Sent from my GT540 using XDA App

(Solved) Yureka Plus YU5510A - Rooted/TWRP 2.8.7.0

DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:
OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse
nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.
Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP

New ROM

Hello there
I had a custom rom on my op2 then i deletet everything over the recorvery. Now i have no OS installed so it only shows the boot screen. I can get into the twrp recorvery and fastboot mode but if i try to fastboot or adb sideload a new rom im unable to connect my op2 to my PC. I doesnt show up.
I tried this guide : https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
I cant make my device show up in my device manager. (I did the windows driver thing).
Can you connect through fastboot? In fastboot mode type in: fastboot devices
If so: flash this https://www.androidfilehost.com/?fid=529152257862717275

Fastboot doesn't detect my phone, please help

I want to install LineageOS so I closely followed the fastboot and adb instructions on the official site. During my first (failed) attempt, there were some old Google USB and ADB things on my PC, so I deleted everything and started again with a clean slate.
I managed to make ADB work (adb devices detects my device, could authenticate the computer, all seems good there). But if I start the phone in fastboot mode, connect and run fastboot devices, I get nothing back. It doesn't give any sign of the connected device. Windows's "Devices" window lists a device called "Android", but it's under "Unspecified" and has the yellow triangle/exclamation mark on the icon.
1. Am I right to assume that this will stop me from unlocking the bootloader (if I will use the unofficial method) and flashing TWRP and a custom ROM on the device?
2. More importantly: What could be wrong, how can I make fastboot see my phone?
Many thanks for the suggestions!
hi,
first do you have latest ADB and Fastboot
then connect your device and run adb devices. check if it detect the device means from the command prompt run "adb reboot bootloader" (without quotes)
now once after device reboots to bootloader check fastboot devices it will detect now
if not then goto device manager,right click on the device and click on update driver software and choose android fastboot interface
you are done now run fatboot devices,it will detect the device
Solved!
adbdriver com/downloads/

HTC U Ultra stuck in bootloop..Can you experts validate the STEPS to solve the issue?

So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?
noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.
Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.

Categories

Resources