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.
Related
My nexus has been rooted. I up rom 4.3 by nexus 7 toolkit failed. When it change to fastboot mode, recovery failed, start failed so i choose power off. Now it won't boot just black screen forever (. Somebody help me please !
minhpro9xhp said:
My nexus has been rooted. I up rom 4.3 by nexus 7 toolkit failed. When it change to fastboot mode, recovery failed, start failed so i choose power off. Now it won't boot just black screen forever (. Somebody help me please !
Click to expand...
Click to collapse
Just manually try flashing recovery through fastboot .
Code:
fastboot flash recovery recovery.IMG
There are tons of similar threads like this . please try to search before posting.
Red Devil said:
Just manually try flashing recovery through fastboot .
Code:
fastboot flash recovery recovery.IMG
There are tons of similar threads like this . please try to search before posting.
Click to expand...
Click to collapse
Thank for your help but i tried and it just show "waiting for devices". My nexus still not display
minhpro9xhp said:
Thank for your help but i tried and it just show "waiting for devices". My nexus still not display
Click to expand...
Click to collapse
Oh did you install the drivers that are required on Windows from Asus ? Make sure you install them.
Code:
fastboot devices
will let you know if your device is connected well.
Red Devil said:
Oh did you install the drivers that are required on Windows from Asus ? Make sure you install them.
Code:
fastboot devices
will let you know if your device is connected well.
Click to expand...
Click to collapse
yes, i insalled driver from asus and i tried to press POWER ON and VOLUME DOWN so it change to APX mode. So, i update driver, pick driver from my computer>C:user/minh/download/usb_driver and nexus 7 still on APX mode with "ASUS Transformer prime APX interface" driver.
fastboot devices--->nothing
adb devices-->nothing
hi same thing happened to me
can you post the link of where to get the asus drivers from
any luck with your nexus yet??
Driver from Asus? Pretty sure you just use the one from the Android SDK.
GldRush98 said:
Driver from Asus? Pretty sure you just use the one from the Android SDK.
Click to expand...
Click to collapse
thanks for that
and do you have any idea on how to get the nexus back up and running
or anyone else
Can you get in to fastboot? If so, you can flash a recovery or system imaged or anything from there. Fastboot should always work (volume up + volume down + power all at the same time)
GldRush98 said:
Can you get in to fastboot? If so, you can flash a recovery or system imaged or anything from there. Fastboot should always work (volume up + volume down + power all at the same time)
Click to expand...
Click to collapse
yes i was, when in fastboot mode i choosed start and recovery mode but all failed so i choosed power off (very stupid thing). Now my device is brick.
minhpro9xhp said:
yes i was, when in fastboot mode i choosed start and recovery mode but all failed so i choosed power off (very stupid thing). Now my device is brick.
Click to expand...
Click to collapse
Tried plugging it in to the a/c adapter and charging for a few hours?
minhpro9xhp said:
fastboot devices--->nothing
adb devices-->nothing
Click to expand...
Click to collapse
^ This sounds like a driver issue if you are not getting anything to show up. You could try the zip I have attached its the google drivers I use and they work fine.
{
"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"
}
View attachment google-usb_driver.zip
GldRush98 said:
Tried plugging it in to the a/c adapter and charging for a few hours?
Click to expand...
Click to collapse
i tried
dpdurst said:
^ This sounds like a driver issue if you are not getting anything to show up. You could try the zip I have attached its the google drivers I use and they work fine.
Click to expand...
Click to collapse
i don't thing the driver issue, i tried many driver but it not working.
google nexus 7 ADB interface
google nexus ADB interface
google nexus 7 BootLoader interface
google nexus bootloader interface
asus fastboot interface
...
thanks for replying
i tried many times to do various combinations o fholding down the power and up,down volume...nothing
i will try later when i am on my desktop to look at fastboot...and update the drivers
right now when i plug the nexus into the pc it comes up as not recognised...
if the nexus were completely dead would it still even come up in the device manager??
i also tried to pull the battery for a few minutes and then try again....nothing
i charge it into the mains with cable and nothing...
i will need to check it when i get home on my main pc in a few hours
please wirte any further siggestions or any web video/links which may help in this situation
THIS is the point where i turned the power off in the FIRST SCREEN
http://loewald.com/blog/?p=5198
i am on my main pc right now
i have downloaded the SDK manager and installed the Android SDK platform tools and Google USB driver
nothing happens when i plug the nexus into the PC
do i need to actually manually install these drivers or they are already installed when i ran the SDK manager...
the nexus shows as unknown device right now
Try to install WugFresh's toolkit. http://www.wugfresh.com/
Follow the driver installation guide and make sure thet the previous drivers is removed.
Choose the recomended driver.
If you can start your device in fastboot mode (bootloader) it should be salvageable.
If you use Windows 8, getting a working driver can be quite a struggle.
it was wugfresh toolkit that i was using
so i uninstalled all drivers and installed the drivers from his toolkit
sadly the usb device is still not recognised
well, i searched google and they said there was one way to fix hard brick nexus 7. It is using "JIG usb". If somebody used "JIG usb" please reply me.
I think I'm having the same problem as you, but I am still able to get into bootloader mode. It may take up to around 20 seconds holding the volume down and power button to get back into bootloader mode. In fastboot bootloader, going into recovery freezes (freezes on the "Teamwin" screen), "start" freezes on the "Google" screen with padlock unlocked. Used Wug's to try to go back to factory setting (but to 4.3 instead of 4.2.2), failed to write 'bootloader' and device never boots back up when it says "waiting for device". Then tried using Nexus 7 toolkit (not Wug's) to lock it back up and now I can't unlock again...same thing..."waiting for device" and device never boots back up.
any update for this problem?
any update for this problem?
i try alot of solution but nothing change
i saw N7 can connect to APX with correct Driver however we can do anything
i try connect power about 8 h but nothing change
what the F *K with OTA update ........
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.
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
Hi guys.
Is my case here is still got hope? ?
{
"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"
}
The only reason is the wrong version of SuperSu. Maybe I use custom made SuperSu for OnePlus 3T.
Before I flashed that SuperSu Zip file using TWRP there is no such problem. Only after flash SuperSu cause this issue .. ?
Before this flash, LG G2's is a new fresh install custom LineageOS for LG G2. Everything is OK. Only no root access. TWRP already installed.
LG G2 still can go to Download Mode as shown by holding the power button and connect USB cable to PC. But the problem is the PC & laptop cannot install the required driver properly. I think I've tried installed/reinstall all the suggested drivers but to no avail.
I even cannot enter the recovery mode using the key combination. When the phone is power on, it will continue to show that Boot certification verify alert.. Ermm ...
Just now just praying PC / laptop can detect and use tools installed on my computer to get to boot into the recovery mode. But is it still possible?
Or this totally means that I will never can use my LG G2 anymore?
Thanks guys.
try to put the ROM via tot aver if you accept it
---------- Post added at 12:17 AM ---------- Previous post was at 12:16 AM ----------
mie_shariff said:
Hi guys.
Is my case here is still got hope?
The only reason is the wrong version of SuperSu. Maybe I use custom made SuperSu for OnePlus 3T.
Before I flashed that SuperSu Zip file using TWRP there is no such problem. Only after flash SuperSu cause this issue ..
Before this flash, LG G2's is a new fresh install custom LineageOS for LG G2. Everything is OK. Only no root access. TWRP already installed.
LG G2 still can go to Download Mode as shown by holding the power button and connect USB cable to PC. But the problem is the PC & laptop cannot install the required driver properly. I think I've tried installed/reinstall all the suggested drivers but to no avail.
I even cannot enter the recovery mode using the key combination. When the phone is power on, it will continue to show that Boot certification verify alert.. Ermm ...
Just now just praying PC / laptop can detect and use tools installed on my computer to get to boot into the recovery mode. But is it still possible?
Or this totally means that I will never can use my LG G2 anymore?
Thanks guys.
Click to expand...
Click to collapse
try to put the ROM via tot aver if you accept it
wtf same thing happend to me
This happened to me too once.
Security error normally means that you should have flashed bumpboot.zip after supersu.zip.
You should still be able to get into TWRP (PWR+Down until Logo appears, then Up+Down).
Some LG drivers seem to miss something. Try older versions or alternative generic ADB drivers.
TOT method always worked for me in the end.
Install SRK Tools to fix boot partition. After that, you could enter in download mode easily.
Edit: LinageOS have your exclusively SuperSU. Next time, install the proper version in lineageOS Website. That problem happen to me, same problem...
Thanks to all.
But whatever fix you suggested, first the laptop/PC needs to detect the phone and install the driver correctly first right?
That is where I'm stuck now.
Even my office laptop also have the same problem, cannot install the driver properly.
Any help?
Thanks.
Williknot said:
Install SRK Tools to fix boot partition. After that, you could enter in download mode easily.
Edit: LinageOS have your exclusively SuperSU. Next time, install the proper version in lineageOS Website. That problem happen to me, same problem...
Click to expand...
Click to collapse
Thanks.
I've already downloaded this before.
But I could not find the option you mentioned.
Can you please guide me more details.
And if the laptop still cannot recognized my LG G2 properly, can I still proceed?
Thank you.
Latest status at my office laptop...
I have tried numerous drivers but to no avail.
Any help?
Thank you.
I mananged to get into this when I let the phone boot with a totally blank and black screen...
Any help with SRK Tools in this case?
Thank you.
Thank you so much guys.
Yes this SRK Tool is really amazing - https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
I can now get back into recovery mode and most importantly my computer can detect my phone!! Thanks a lot.
But now it seems that my Lineage OS has become corrupted and I don't think I want to install it anymore because the display is very poor in brightness.
So my next question is with such condition ie improper Lineage OS installation on the phone right now, how do I get back to the latest stock OS.
How do I start?
Thank you so much for the help.
After flashing SuperSU do as @MB525 suggests, flash Boot Image Bumper/ bumpboot-v1.0-blastagator-signed.zip
http://www.gregtwallace.com/lgg2-projects/miscellaneous/
This needs to be done with Magisk too.
Same thing happen to me
mie_shariff said:
Thank you so much guys.
Yes this SRK Tool is really amazing - https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
I can now get back into recovery mode and most importantly my computer can detect my phone!! Thanks a lot.
But now it seems that my Lineage OS has become corrupted and I don't think I want to install it anymore because the display is very poor in brightness.
So my next question is with such condition ie improper Lineage OS installation on the phone right now, how do I get back to the latest stock OS.
How do I start?
Thank you so much for the help.
Click to expand...
Click to collapse
use lgup to flash the stock rom and ready in LG firmware:fingers-crossed::fingers-crossed:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
I always power off my phone. Then hold both volume buttons down and plug it in. MSM tool sees my phone and hit start.
which Qualcomm drivers you installed ? because my phone is not connecting with MSM tools ....
I'm having the same issues. Anyone find a fix?
Charles: said:
I'm having the same issues. Anyone find a fix?
Click to expand...
Click to collapse
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Zain ul Abedin said:
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Click to expand...
Click to collapse
Which TWRP?? Did you load it via Fastboot and use Fastboot commands? Are you A11? Which Qualcomm drivers?
I basically forget that , but search about it . And install TWRP in your phone
otoyayamaguchi said:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
Click to expand...
Click to collapse
I think it's supposed to only last for a few seconds. Pull up the MSM Tool and pay attention to the "Status of Connection" field for any of the COM lines in the MSM Tool. When you connect, it should say "Connected" for one of those lines. If that happens at all, then you're good to proceed. Make sure you have TMO selected in the drop-down, click "Enum" once you plug in your device, then click Start. Try to do this quickly. Let me know if this helps.
I am having the same problem with my 7T Pro McLaren, the pc recognizes it but msm tool does not, someone has already found the way
{
"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 had the same issue. One easy fix is switching from a USB 3.0 port to USB 2.0 port. The other method that worked for me is a little more of a process.
1) Have MSM open
2) Connect phone to PC
3) Power phone off
4) Then, the moment it powers down, hold the vol +, -, & power button
5) Keep holding it. Your PC will make a sound notifying you that it's detected the phone, but you want to keep
holding the buttons until you hear it being detected for the second time.
6) Release buttons.
Hopefully that makes it stay in EDL mode for you.
I wrote on this somewhere, but you can try having the program open and placed at the right settings, then move quickly once the phone is in EDL mode. Not ideal but worked for me. Once the process begins it won't exit out of EDL mode in my experience.
hii, from most tutorial i have seen so far, the com number is show in the msm tool upon starting the program, most the two msm tools i have tried so far dont show com number... and its not detecting my phone.