Database Users

[Q] Can "see" device in ADB, not in fastboot....

Hey guys,
Bare with me please as I am fairly new-ish to Android but have some experience with Samsungs, HTCs and the beloved LG GT540.....
I appreciate if anyone can help me on my plight.....
My girlfriend was running Cyanogen Mod for the last year or so on her device and decided that she wanted to try out a different ROM on her phone....
I wanted to install the Oxegen ROM....
Originally I was thinking it would be easy and I could put it on through Clockwork Recovery and flash the zip no problem, for some reason when I rebooted to recovery clockwork would not load up on the device.... just blank screen....
Not content with this, bored on a Sunday afternoon I gave it a couple of hours of my time and in the process messed my girlfriends phone up....
What I did was I tried flashing back to stock using the LG KDZ updater, that was fine and the phone rebooted and has since stuck on the Android logo....
According to this thread : http://forum.xda-developers.com/showthread.php?t=1078745&highlight=stuck+on+android+screen I gave all this a go and I can not get the device showing up in Fastboot, I can not enable USB debugging on it either as I can not get into the phone to tick the box....
In my cmd prompt I am seeing this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In my device manager when my device is connected and powered on I am seeing this :
When I am connected and the device is in "download mode" my devices are like this :
I understand the steps provided in the link above and I am fairly confident I could do them if I can get the device "seen" in Fastboot....
I have installed and re-installed all the USB drivers in hope that it may be a driver issue, now I am wondering is it maybe my OS? Win7 64Bit Ultimate?
I can try it on XP netbook if thats all thats causing my issues....
I am kinda lost now and wondering have I bricked it? It will be the first phone I have if thats the case....
Any help would be appreciated, thanks a lot guys....
Mods if this is in the wrong area, please feel free to move my post.....

did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.

m1st3r1 said:
did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.
Click to expand...
Click to collapse
Fastboot and ADB works on Windows 7 Home Premium 64bit. I installed LG Drivers then Google USB Driver. It worked then. But I know I did struggle to finally get it working.

Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!

Ko_Ka said:
Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!
Click to expand...
Click to collapse
i think u got it wrong.
read here: http://android-dls.com/wiki/index.php?title=Fastboot and here: http://wiki.cyanogenmod.com/wiki/Fastboot
first of all, i need to ask u the question (again), can u boot to fastboot (or bootloader) when u pressed power (the reject/red phone button) and camera button altogether? the fastboot screen in the phone will be like black screen, but with a little amount of backlight (u'll notice the difference) or blue screen with texts if u flash a kdz-modified-fastboot. if u cant go to bootloader/fastboot, then u need to flash a kdz with fastboot.
u can try this: when u type adb devices, type: adb reboot bootloader
though im not sure if ur gf's phone has fastboot/bootloader (might be missing during the kdz flashing that u've done).
when u type adb devices

m1st3r1 - if you ever come to Dublin, I will buy you a beer!
After nearly 3 days of pulling what hair I have left on my head out, my problem was I was mistaking Fastboot for Download mode.....
I was connecting the phone holding the volume down so it came up "download mode" now all I did was hold the camera + red button and off it went with the command from the post above....
I feel like an idiot, but im a happy idiot right now.....
Thanks a lot, means a lot to me.... (and my girlfriend!)

LOL welcome to the hackers club

Bricked for good?

Hi, I tried to push the 4.3 update and unroot my device through Wugfresh kit and all went well. But when it initially booted, I had this constant popup saying that "Bluetooth Share has stopped working" making the device unusable as it was stuck on the welcome screen. So, I rebooted into bootloader and tried to use the "Unroot + Stock" option saying my device had a soft brick and flash 4.2.2. But now nothing starts, it stays on the Google screen and that's it. I am however able to boot into recovery. I've checked the manual way of doing it but it says my USB debugging needs to be turned on (but I can't boot into the OS to do that)... To top it up, my computer isn't recognizing my device. I've used mskip's toolkit as well, no go. Are there any solutions or is my table gone for good?
Thanks
Oh yeah I tried again with Wugfresh it says this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You need to install this to use ADB in recovery.

Thanks, I've downloaded those drivers and followed the instruction for windows 8 but still adb doesn't recognize my device and I cannot boot into the device to change it to debugging mode as I cannot go past the Google screen =\ any other ways to make it recognize my device?
my brother has a nexus 7 do you guys think if I deleted all the drivers and put his into debugging mode it'll install drivers for mine too?

What you installed is needed to use ADB while in recovery. Here is the latest Android Composite ADB Interface Driver from SDK that you need for use of ADB while booted and fastboot in bootloader.
http://d-h.st/kDu
You do not need USB debugging to use ADB while in recovery or fastboot.

Username invalid said:
What you installed is needed to use ADB while in recovery. Here is the latest Android Composite ADB Interface Driver from SDK that you need for use of ADB while booted and fastboot in bootloader.
http://d-h.st/kDu
You do not need USB debugging to use ADB while in recovery or fastboot.
Click to expand...
Click to collapse
Hi, thanks again. However, I have no idea what to do with those files (the drivers) with ADB

Install or update through device manager.

I had a similar issue. My pc went to BSOD in the middle of writing system. To made it worse, fastboot stopped working altogether. My solution was to do the flashing from my Linux partiton. I know it's a crazy advice, but linux commands never fail, and you won't need drivers at all.
Still, try to use the "flash-all.bat" from the factory image, and stay away from toolkits.

When I plug in my nexus in (while in bootloader) on my device manager this pops up but then I try to update the drivers it says it can't update unknown device

You may have to disable Window's Driver Signature Enforcement.

I do not have a linux partition I'm using a windows 8 and I have 2 other PCs with win7 and xp. My windows 8 digital signature checking is disabled.
EDIT: plugging my bro's nexus did not make mine get recognized by the PC. I am installing linux on my other PC just to see if it works + i've never used linux so a new experience

running it on ubuntu 12.04 did not help either =\ while in bootloader in terminal I type in adb devices and not devices are listed under "List of devices attached"

When you are in boot loader mode you need to use fastboot instead of adb, I.e. try:
fastboot devices
(I suppose you have the latest SDK installed ...)
Sent from my Nexus 7 using xda app-developers app

Well guys, I've been doing this for about 12 hours straight lol and I'VE FINALLY DONE IT THROUGH UBUNTU OMG I LOVE UBUNTU! YES!!! Thank you all for the amazing support and advice! Much appreciated. Thank you ALL! :highfive:

It's not as if your device was bricked in the first place
Installing the drivers in Ubuntu is very easy using "sudo apt-get install android-tools".

FASTBOOT working?

guys i'm facing problem with getting fastboot to work
no matter which drivers i use fastboot doesnt recognize my phone
I,m using win 8.1 x64 if anybody got fastboot to work pls guide me

Same issue here. I'm also having troubles installing fastboot drivers. In fact, there are some drivers missing in device manager as per this screenshot -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Don't know if you've heard about it yet, but if you type stuff in to this called google you can find all sorts of stuff. fastboot windows 8

XperienceD said:
Don't know if you've heard about it yet, but if you type stuff in to this called google you can find all sorts of stuff. fastboot windows 8
Click to expand...
Click to collapse
Its not windows 8 that is giving problms mate. It is that our phone's bootloader drivers aren't workinng. And this is best place to search for our device.

XperienceD said:
Don't know if you've heard about it yet, but if you type stuff in to this called google you can find all sorts of stuff. fastboot windows 8
Click to expand...
Click to collapse
Already tried those methods of installing drivers in Win 8.1 x64, nothing works. Adb works fine, but fastboot drivers doesn't get installed and we still see those unknown E7 devices as mentioned above. If someone else have all drivers installed, kindly share us the method to install all drivers properly. Another reason to hate this driver enforcement crap!

1manshow said:
Same issue here. I'm also having troubles installing fastboot drivers. In fact, there are some drivers missing in device manager as per this screenshot -
Click to expand...
Click to collapse
did you tried on any other OS i tried installing e7 bootloader drivers via inf but windows didnt allowed by saying it is not digitally signed

Can you share the bootloader drivers you are trying to install via inf files? I can try it on my system. I've already enabled test mode on my system and disabled driver enforcement checks.

1manshow said:
Can you share the bootloader drivers you are trying to install via inf files? I can try it on my system. I've already enabled test mode on my system and disabled driver enforcement checks.
Click to expand...
Click to collapse
the official drivers from
http://gionee.co.in/oldsite/Download/GN_MTK_USBDriver(Factory)_V1.1.0_1.rar
contains bootloader drivers. if you install these via inf and able to fastboot let me know

Fastboot Drivers
Did anyone figure out how to get fastboot working? I am having the same issue. ADB works fine when the phone is off (battery charging logo on the screen) but when I go into fastboot mode (the red gionee logo displayed) the phone is not recognized by ADB or FASTBOOT commands.

^^ That issue can't be resolved under Windows 8.1 64 bit, I tried almost everything but vain. Only way it can work is to install Win XP 32 bit, and then try with the drivers posted above. It should work hopefully. Problem is my SSD is quite low on space so I won't be able to dual boot XP. If anyone else can try this on XP, let us know.

1manshow said:
^^ That issue can't be resolved under Windows 8.1 64 bit, I tried almost everything but vain. Only way it can work is to install Win XP 32 bit, and then try with the drivers posted above. It should work hopefully. Problem is my SSD is quite low on space so I won't be able to dual boot XP. If anyone else can try this on XP, let us know.
Click to expand...
Click to collapse
i am trying xp as i've bricked my phone there seems no other way than to try unbrick with xp

dhirajranger said:
i am trying xp as i've bricked my phone there seems no other way than to try unbrick with xp
Click to expand...
Click to collapse
I have bricked my phone too and I am using Windows XP 32 bit. I am still not able to get fastboot working
Attached is the image of my device manager

trishulrai said:
I have bricked my phone too and I am using Windows XP 32 bit. I am still not able to get fastboot working
Attached is the image of my device manager
Click to expand...
Click to collapse
can you boot into fastboot mode by vol down + power (flashing gionee logo). if yes then it would be easy to unbrick your phone. i will post whole unbrick guide as soon as i unbrick my phone.

You people need to install the E7 Flash tools posted in development thread on your XP. Then use that to flash back the Gionee stock firmware to your phone.

dhirajranger said:
can you boot into fastboot mode by vol down + power (flashing gionee logo). if yes then it would be easy to unbrick your phone. i will post whole unbrick guide as soon as i unbrick my phone.
Click to expand...
Click to collapse
When I press the vol down + power button, it turns the phone off if it is ON. When I press vol down + power when the phone is OFF, it just shows a RED Gionee Logo (no flashing logo). when I run adb reboot-bootloader, it also goes to this red Gionee logo screen and stays there. I assumed this was the fastboot mode. When the red gionee logo shows, my PC does not recognize the phone at all. Pressing Vol up + power loads the Android System Recovery (3e)
1manshow said:
You people need to install the E7 Flash tools posted in development thread on your XP. Then use that to flash back the Gionee stock firmware to your phone.
Click to expand...
Click to collapse
I downloaded the GNQC_Download_User_V1.6.9.0, but I cannot understand how to use it. All the instructions included are in Chinese and google translate also doesn't do a very good job translating it in English that I can understand. Is there a guide available on how to use this tool in English?

trishulrai said:
When I press the vol down + power button, it turns the phone off if it is ON. When I press vol down + power when the phone is OFF, it just shows a RED Gionee Logo (no flashing logo). when I run adb reboot-bootloader, it also goes to this red Gionee logo screen and stays there. I assumed this was the fastboot mode. When the red gionee logo shows, my PC does not recognize the phone at all. Pressing Vol up + power loads the Android System Recovery (3e)
I downloaded the GNQC_Download_User_V1.6.9.0, but I cannot understand how to use it. All the instructions included are in Chinese and google translate also doesn't do a very good job translating it in English that I can understand. Is there a guide available on how to use this tool in English?
Click to expand...
Click to collapse
i,m going to post all instructions . your phone gets in fastboot mode that is a plus (even if its not detected by pc). i will post all instructions here as soon as i unbrick my phone (currently having problms installing xp as i have harddisk in GPT)
dont worry your phone is fully recoverable

Yo! Win8.1 here too, don't see the phone.

Can't boot into recovery or system

I flashed the latest chinese 7.1.1 and it bootloops. So I tried going into recovery to wipe/reinstall and found that it wasn't working. The led blinks 3 times and the phone turns off.
I can boot into bootloader, but Windows is not recognizing my device, it just says "Android" under device manager.
Any ideas how to fix this?

have you tried EDL method to restore your original firmware?

otaconremo said:
have you tried EDL method to restore your original firmware?
Click to expand...
Click to collapse
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing

bornlivedie said:
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing
Click to expand...
Click to collapse
try to remove the previous drivers on windows or reinstall another qcom driver. or maybe try from another computer. unless it gets 9008 mode in windows, you can't do anything on it.

otaconremo said:
try to remove the previous drivers on windows or reinstall another qcom driver. or maybe try from another computer. unless it gets 9008 mode in windows, you can't do anything on it.
Click to expand...
Click to collapse
Already did all those things
tried multiple installations of windows, multiple drivers
QUSB_BULK is installed but MiFlash or axon7root won't detect it

Dumb question but did you try booting normally? Power button only, no vol buttons.
Should take you to the ZTE logo followed by the bootloader unlocked screen.

You said you can boot into bootloader, right? Did you try fastboot commands? If fastboot works, try flashing stock boot and recovery from yoir previous rom and reboot to recovery.

t2jbird said:
Dumb question but did you try booting normally? Power button only, no vol buttons.
Should take you to the ZTE logo followed by the bootloader unlocked screen.
Click to expand...
Click to collapse
Yes, i can see the bootloader screen and go into fastboot.
otaconremo said:
You said you can boot into bootloader, right? Did you try fastboot commands? If fastboot works, try flashing stock boot and recovery from yoir previous rom and reboot to recovery.
Click to expand...
Click to collapse
Windows is not recoginizing the phone while in fastboot. It just says "Android" under device manager. Can't make it work with google usb drivers.
I need the correct drivers to flash the firmware while in EDL mode.

bornlivedie said:
Yes, i can see the bootloader screen and go into fastboot.
Windows is not recoginizing the phone while in fastboot. It just says "Android" under device manager. Can't make it work with google usb drivers.
I need the correct drivers to flash the firmware while in EDL mode.
Click to expand...
Click to collapse
Possibly it is a driver issue. Maybe try disabling driver signature in windows? Just google it.

otaconremo said:
Possibly it is a driver issue. Maybe try disabling driver signature in windows? Just google it.
Click to expand...
Click to collapse
It's off...
I just reinstalled windows 10 and now this is happenning:
Windows 10 recognizes my device as Handset Diagnostic Interface(DFU) (COM3) after installing the QUSB_BULK driver
forcing the QUSB_BULK drivers is not working, as it says that windows couldn't verify the compatibility of the drivers, installs them anyway, and shows the device as COM10 and no tool detects the phone....

Try reading this thread. They're discussing about drivers here as well.
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
And here's another one i came across with.
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201

I also had trouble with the drivers when trying to unlock the bootloader. It wasn't easy.
I had to put the phone in CD mode to install the supplied drivers. It's a must.
Then I followed the guide and some guys' extra comments on the post to unlock the G variant. It was tricky... I suggest you read that guide and "choose an user name" comment here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379/page32

I have terrible experience between Windows 10 and axon's driver - it's not work with any reason.
Try with again with Windows 7 (or at least Windows 8.1) , it may work for you.

bornlivedie said:
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing
Click to expand...
Click to collapse
If you're able to connect to EDL then is driver is the issue... Try connecting from your friend pc...
I always go using the below method to get in EDL mode.. If you haven't tried... Check this as well
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried flashing the chinese firmware as well without b15 bootdtack... But able to boot to recovery.. But the version of twrp shows as 3.0N 1...i thought it's a glitch and flashed the recovery 3.04.1 and it showed correctly... Don't know it helps at this level
Sent from my ZTE A2017U using Tapatalk

`SBR` said:
If you're able to connect to EDL then is driver is the issue... Try connecting from your friend pc...
I always go using the below method to get in EDL mode.. If you haven't tried... Check this as well
I tried flashing the chinese firmware as well without b15 bootdtack... But able to boot to recovery.. But the version of twrp shows as 3.0N 1...i thought it's a glitch and flashed the recovery 3.04.1 and it showed correctly... Don't know it helps at this level
Click to expand...
Click to collapse
3.0.N1 came from the bootstack. If I remember correctly, it's one that unjustified_dev compiled to go with it.

I think i broke my Redmi

I bought my first redmi ever that is used phone and the previous owner said "its stuck on Mi logo after updating SU"
I tested the device first with these conditions
1. plugged to charger and its charge properly (led is on)
2. cannot go to recovery or power on (had to use deep flash cable to get into fastboot)
3. used deep flash cable, Quacomm shown and installed properly
4. Flashed the image. its says success but i accidentaly look at most bottom window. its says "flash_all_lock.bat"
5. unplugged the cable tried to turn on, it doesnt work
help me .. did i miss something here?
EDIT:
1. plugged to laptop, it says usb malfunctioned unlike before
2 is it normal if i get into fastboot using deep flash the screen show nothing?

1. Deep flash cable is to open the edl mode (not fastboot) and yes the screen is black in edl (download mode)
2. Make a clean flash and try it with qfil
3. You can find videos on youtube how you can fix redmi 4 prime hard bricks (complete guides)

Danoz88 said:
1. Deep flash cable is to open the edl mode (not fastboot) and yes the screen is black in edl (download mode)
2. Make a clean flash and try it with qfil
3. You can find videos on youtube how you can fix redmi 4 prime hard bricks (complete guides)
Click to expand...
Click to collapse
ok new problem, i plug the deep flash cable and it says hardware malfunctioned repeatedly
this one scared me and the device cannot charge
i'm thinking about test point method but i have to wait ordered small torx driver on monday

UPDATE:
After using test point. nothing changed except the device ID number is weird
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How is it displayed in fastboot mode? Deepflashcable also doesn't worked for me because I read that on the newer rom's the edl mode is blocked so no chance with dfc anymore (thanks xiaomi...). It only reboots if I tried everything (commands,dfc,file..).
I had to flash an older version first via fastboot mode. After this I was able to reboot into edl mode with 0 problems. And I never tried the test point methode, not the right tools.

cant goto recovery, cant go to fastboot, test point tested 2nd time and its work.. flash success
but the screen still blank.
if i plug my usb cable to laptop its onlt shows MTP and green led light

I Know How To Fix This...
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .
---------- Post added at 04:29 AM ---------- Previous post was at 04:23 AM ----------
rs168 said:
I bought my first redmi ever that is used phone and the previous owner said "its stuck on Mi logo after updating SU"
I tested the device first with these conditions
1. plugged to charger and its charge properly (led is on)
2. cannot go to recovery or power on (had to use deep flash cable to get into fastboot)
3. used deep flash cable, Quacomm shown and installed properly
4. Flashed the image. its says success but i accidentaly look at most bottom window. its says "flash_all_lock.bat"
5. unplugged the cable tried to turn on, it doesnt work
help me .. did i miss something here?
EDIT:
1. plugged to laptop, it says usb malfunctioned unlike before
2 is it normal if i get into fastboot using deep flash the screen show nothing?
Click to expand...
Click to collapse
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .

amangupta711 said:
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .
Click to expand...
Click to collapse
nope, cannot go to fastboot or recovery
flash succeed with test point method but the screen went blank after tried to power on the device
EDIT: forgot to mention, flashed with global stable, china stable , china developer.. the result still the same

Try this!!!
rs168 said:
nope, cannot go to fastboot or recovery
flash succeed with test point method but the screen went blank after tried to power on the device
EDIT: forgot to mention, flashed with global stable, china stable , china developer.. the result still the same
Click to expand...
Click to collapse
Hold power and vol down button for 20 sec.

amangupta711 said:
Hold power and vol down button for 20 sec.
Click to expand...
Click to collapse
it has been said.. nothing