Hi everyone , this is second time happening , first I forgot my pin , now my brother tried to unlock the phone ,I had screen lock with pattern , and he failed 5 times , now it says to give the gmail and password , I am doing that , and doing it right, because I can login in computer @ gmail but cannot in device , at forgot pattern option , it says incorrect email or password, even tho im doing it right. How is that possible, maybe because its not connected in internet , wifi or internet-through-pc . Can't recovery with volumedown button because volume buttons dont work.
P.S : USB Debugging is enabled on phone.
I have tried earlier when I forgot my pin , with ADB method but seems that ADB cannot recognize my device or I dont know what .
Any solution as soon as possible please Why it says incorrect email/password when Im doing it right ...
Windows version??
If you're using W8 try another pc running W7 or xp in order to use adb commands (install drivers first)
Shutdown the phone
Plug it (it will be recognized)
Then open cmd and write: adb reboot recovery
Maybe it don't works at first, try several times
Once in recovery, full wipe and flash a Rom
Enviado desde mi Nexus 4
pascuals said:
Windows version??
If you're using W8 try another pc running W7 or xp in order to use adb commands (install drivers first)
Shutdown the phone
Plug it (it will be recognized)
Then open cmd and write: adb reboot recovery
Maybe it don't works at first, try several times
Once in recovery, full wipe and flash a Rom
Enviado desde mi Nexus 4
Click to expand...
Click to collapse
Problem solved with factory reset thanks , but I dont still know why Windows doesnt recognize my phone , I want to install a CUSTOM ROM and windows doesnt recognize, im a noob at developement and cant install a custom rom
Related
Hi guys !
I rooted my phone and then tried to setup some roms. But when I try to go in the download mode, it says "Downloading... Do not turn off the target" but on my computer, it cannot recognize the usb. I setup the usb drivers, tried another ports and there is no problem about my usb cable. It works normally, but whenever I go in the download mode, this thing happens and I cant continue to Odin. Does anyone know anything about that ?
burhannde said:
Hi guys !
I rooted my phone and then tried to setup some roms. But when I try to go in the download mode, it says "Downloading... Do not turn off the target" but on my computer, it cannot recognize the usb. I setup the usb drivers, tried another ports and there is no problem about my usb cable. It works normally, but whenever I go in the download mode, this thing happens and I cant continue to Odin. Does anyone know anything about that ?
Click to expand...
Click to collapse
When you install custom ROMs, you need to go to recovery mode ( Volulme Up + Power + Home ), not to download mode
MayB4ck said:
When you install custom ROMs, you need to go to recovery mode ( Volulme Up + Power + Home ), not to download mode
Click to expand...
Click to collapse
I am trying to setup ClockWorkMode Recovery. That's why I go in to download mode
burhannde said:
I am trying to setup ClockWorkMode Recovery. That's why I go in to download mode
Click to expand...
Click to collapse
You can install it easily if your phone is rooted just
-put the downloaded recovery.img in /mnt/sdcard
-download & install "Terminal Emulator" in play store
-open it then type "su" and click enter
-allow root access..
-then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13" then click enter
-then some text will show in bottom
-exit terminal..
check the recovery by turning off the device then turn on with volume up botton, home button, and power button pressed together..
until "Galaxy W" screen shows up, release the power button only.. then you will enter CWM
MayB4ck said:
You can install it easily if your phone is rooted just
have the same problem + a bootloop...
what should i do?!
the phone is rooted
windows cant detect it when in download mode (wich i need to connect with odin)
now i cant even get the stock rom back on my phone
Click to expand...
Click to collapse
zekare said:
MayB4ck said:
You can install it easily if your phone is rooted just
have the same problem + a bootloop...
what should i do?!
the phone is rooted
windows cant detect it when in download mode (wich i need to connect with odin)
now i cant even get the stock rom back on my phone
Click to expand...
Click to collapse
What version of windows are you running, it couldn't work on windows 8 and 8.1 so i installed 7 and all the drivers for the phone and it works, i dont have the phone now but i do beleive that will, anyway... if you have bootloop that means you are still able to pass the bootloader screen right?? then try to go to recovery and flash roms from there, having an sd card would help transfering roms from pc directly to phone....
Reply again if you need some assistance.. I'm not online very often
Click to expand...
Click to collapse
MayB4ck said:
zekare said:
What version of windows are you running, it couldn't work on windows 8 and 8.1 so i installed 7 and all the drivers for the phone and it works, i dont have the phone now but i do beleive that will, anyway... if you have bootloop that means you are still able to pass the bootloader screen right?? then try to go to recovery and flash roms from there, having an sd card would help transfering roms from pc directly to phone....
Reply again if you need some assistance.. I'm not online very often
Click to expand...
Click to collapse
i have windows 10 pro.
yes, first the samsung logo apears then the galaxy W logo.
it stays 1 or 2 minutes on this galaxy W logo screen then it reboots.
is it even possible to flash it with the original bootloader from a sd card?
and would the original bootloader detect this type of image (.tar.md5) ?
Thank you for reply
Click to expand...
Click to collapse
zekare said:
MayB4ck said:
i have windows 10 pro.
yes, first the samsung logo apears then the galaxy W logo.
it stays 1 or 2 minutes on this galaxy W logo screen then it reboots.
is it even possible to flash it with the original bootloader from a sd card?
and would the original bootloader detect this type of image (.tar.md5) ?
Thank you for reply
Click to expand...
Click to collapse
You can try putting any custom rom and flash from a custom recovery if you can access it, if not download the stock rom and get a windows 7 pc. make sure you install all the samsung drivers ( kies should do the job ) and try flashing it from odin
Click to expand...
Click to collapse
MayB4ck said:
zekare said:
You can try putting any custom rom and flash from a custom recovery if you can access it, if not download the stock rom and get a windows 7 pc. make sure you install all the samsung drivers ( kies should do the job ) and try flashing it from odin
Click to expand...
Click to collapse
so is win10 the problem ?
i tried 100 things to connect pc with the phone in downloadmode. nothing workd.
if i can find a win 7 pc i will try it. but is there any other way?
i also tried adb on windows it also not works.
then i did a ubuntu usb drive and tried to do it with heimdall but im not a coder. it was very confusing.
at least i was able to detect the device but thats it.
well, anyway thanks alot for your help.
i will try it on a win7 pc
Click to expand...
Click to collapse
Download mode Windows 8.1 10
To connect your phone in download mode on Windows 8.1 and 10 you need to apply this registry file (in my attached zip file).
Mirror Link
It happens for most old phones.
More Info: https://blogs.msdn.microsoft.com/us...ows-8-0-but-fail-on-windows-8-1-with-code-43/
Also note Odin3 (the one which is used for newer phones) doesn't work for Galaxy W! (Use Odin Multi Downloader.)
--------
Update: It seems that this registry key isn't needed. Make sure to connect the USB cable after downloading... screen appears. If it wasn't recognized try disconnect and reconnecting the USB cable or try other USB ports on PC till it gets recognized.
mat1371 said:
To connect your phone in download mode on Windows 8.1 and 10 you need to apply this registry file (in my attached zip file).
Mirror Link
It happens for most old phones.
More Info: https://blogs.msdn.microsoft.com/us...ows-8-0-but-fail-on-windows-8-1-with-code-43/
Also note Odin3 (the one which is used for newer phones) doesn't work for Galaxy W! (Use Odin Multi Downloader.)
Click to expand...
Click to collapse
still doesn't work for me, can you please post the drivers you are using ?
If you see the USB device is not recognized error it's not a driver issue.
Windows automatically downloads the drivers through Windows Update. BTW here are the drivers:
SAMSUNG.zip - 13.5 MB
deleted
mat1371 said:
Download mode Windows 8.1 10
To connect your phone in download mode on Windows 8.1 and 10 you need to apply this registry file (in my attached zip file).
Mirror Link
It happens for most old phones.
More Info: https://blogs.msdn.microsoft.com/us...ows-8-0-but-fail-on-windows-8-1-with-code-43/
Also note Odin3 (the one which is used for newer phones) doesn't work for Galaxy W! (Use Odin Multi Downloader.)
--------
Update: It seems that this registry key isn't needed. Make sure to connect the USB cable after downloading... screen appears. If it wasn't recognized try disconnect and reconnecting the USB cable or try other USB ports on PC till it gets recognized.
Click to expand...
Click to collapse
it works. thank u so much...
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.
inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too
1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10
CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen
CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790
ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.
Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works
I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.
I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.
inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.
Hey everyone hopefully someone has an idea what is wrong with this phone.
I cannot enter the bootloader it keeps blinking and eventually just goes to the official recovery.
Tried going into xfstk (which i have used before), cant connect get usb drive has malfunctioned on computer.
Inside the OS (6.0) when i plug it in to the computer i get cant connect get usb drive has malfunctioned on computer.
I tried replacing the usb board same thing.
Also quick charge doesnt work anymore (im guess all related).
Is it a mobo problem, or any other things i can try?
Have you tried ? , update from sd card --putting the firmware you are on or the next updated version ,on ext sd before booting into recovery and updating ,
i have tried this method recently , hope it works for you ?
sharkie545 said:
Hey everyone hopefully someone has an idea what is wrong with this phone.
I cannot enter the bootloader it keeps blinking and eventually just goes to the official recovery.
Tried going into xfstk (which i have used before), cant connect get usb drive has malfunctioned on computer.
Inside the OS (6.0) when i plug it in to the computer i get cant connect get usb drive has malfunctioned on computer.
I tried replacing the usb board same thing.
Also quick charge doesnt work anymore (im guess all related).
Is it a mobo problem, or any other things i can try?
Click to expand...
Click to collapse
here are few things you can try.
1. enable usb debugging and connect your phone to PC.
now assuming you already got adb and fastboot driver on pc..
run command adb reboot-bootloader
if this does not work. try other method.
2. download droidboot.img firmware image and place in in root of your phone
download turminal on phone. now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/droidboot.img of=/dev/block/mmcblk0p13
# reboot bootloader
third you can try updating firmwware via recovery as timbernot suggested. if it fails as well. then xfstk is needed.
there may be chance your fastboot partition is wasted. i have never tried to erase in via adb. i will try to erase it via adb and tell you if got success
timbernot said:
Have you tried ? , update from sd card --putting the firmware you are on or the next updated version ,on ext sd before booting into recovery and updating ,
i have tried this method recently , hope it works for you ?
Click to expand...
Click to collapse
I tried to apply update via recovery. Same problem.
sukhwant717 said:
here are few things you can try.
1. enable usb debugging and connect your phone to PC.
now assuming you already got adb and fastboot driver on pc..
run command adb reboot-bootloader
if this does not work. try other method.
2. download droidboot.img firmware image and place in in root of your phone
download turminal on phone. now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/droidboot.img of=/dev/block/mmcblk0p13
# reboot bootloader
third you can try updating firmwware via recovery as timbernot suggested. if it fails as well. then xfstk is needed.
there may be chance your fastboot partition is wasted. i have never tried to erase in via adb. i will try to erase it via adb and tell you if got success
Click to expand...
Click to collapse
I'm not rooted, so with su? Nothing happens.
Xfstk was my first choice, but when I plug my phone into computer I can never get the phone to connect (get USB drive has malfunctioned). I have used it successfully before.
I can't enable USB debugging either for some reason. Once it says developer options enabled. I cannot find developer options.
Tapping build number numerous times ?
Nothing ?
---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------
sharkie545 said:
[/HIDE]
I tried to apply update via recovery. Same problem.
[/HIDE]
I'm not rooted, so with su? Nothing happens.
Xfstk was my first choice, but when I plug my phone into computer I can never get the phone to connect (get USB drive has malfunctioned). I have used it successfully before.
I can't enable USB debugging either for some reason. Once it says developer options enabled. I cannot find developer options.
Click to expand...
Click to collapse
re update from sd , firmware UL- blah blah , put another .zip on the end , so should read as user.zip.zip
Wipe data first cache too and try again
timbernot said:
Tapping build number numerous times ?
Nothing ?
---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------
re update from sd , firmware UL- blah blah , put another .zip on the end , so should read as user.zip.zip
Wipe data first cache too and try again
Click to expand...
Click to collapse
Ill try reflashing again, as i said reflashing works but still same problems. - didnt wipe data though - so will give that a try.
USB developers showed this time oddly enough, but still get A request for the USB device descriptor failed. on computer when i plug it in. (two diff computers - drivers installed - different cords - windows 7 and 10)
sharkie545 said:
Ill but still get A request for the USB device descriptor failed. on computer when i plug it in)
Click to expand...
Click to collapse
You have to tick the box on screen of phone to allow it to make contact with the pc , maybe your phone screen timed out and you missed the pop up on phone? , set phone screen to time out for a couple of mins and attempt again
:good:
Ps the wipe data , can take a while
sharkie545 said:
Ill try reflashing again, as i said reflashing works but still same problems. - didnt wipe data though - so will give that a try.
USB developers showed this time oddly enough, but still get A request for the USB device descriptor failed. on computer when i plug it in. (two diff computers - drivers installed - different cords - windows 7 and 10)
Click to expand...
Click to collapse
well seems like you have broken partition. need to flash xfstk. as it is booting properly you will not get it detected as moorefield. but even though install soc driver. then run xfstk. load files and click begin download. now connect your phone to pc in switch off mode and turn on
timbernot said:
You have to tick the box on screen of phone to allow it to make contact with the pc , maybe your phone screen timed out and you missed the pop up on phone? , set phone screen to time out for a couple of mins and attempt again
:good:
Ps the wipe data , can take a while
Click to expand...
Click to collapse
Unfortunately, still same problem yea it does take a long time lol never understood why. - wiped, clean install same problem. No popsups on phone ever just goes device has malfunctioned on computer.
sukhwant717 said:
well seems like you have broken partition. need to flash xfstk. as it is booting properly you will not get it detected as moorefield. but even though install soc driver. then run xfstk. load files and click begin download. now connect your phone to pc in switch off mode and turn on
Click to expand...
Click to collapse
Unfortunately i have tried that a dozen times, i know its supposed to from a off phone when you turn it on theres a delay from your phone actually turning on till when you see the asus logo, this is when xfstk takes over - but even then i get device malfunctioned on computer - (begin download mode is on).
sharkie545 said:
[/HIDE]
Unfortunately, still same problem yea it does take a long time lol never understood why. - wiped, clean install same problem. No popsups on phone ever just goes device has malfunctioned on computer.
[/HIDE]
Unfortunately i have tried that a dozen times, i know its supposed to from a off phone when you turn it on theres a delay from your phone actually turning on till when you see the asus logo, this is when xfstk takes over - but even then i get device malfunctioned on computer - (begin download mode is on).
Click to expand...
Click to collapse
Can you confirm build /date info ?
timbernot said:
Can you confirm build /date info ?
Click to expand...
Click to collapse
Build Number: MMB29P.WW-ASUS_Z00A-4.21.40.184_0577_user
Kernel: 3.10.72-x86_64_moor-gcb00463
sharkie545 said:
Build Number: MMB29P.WW-ASUS_Z00A-4.21.40.184_0577_user
Kernel: 3.10.72-x86_64_moor-gcb00463
Click to expand...
Click to collapse
edit my mistake you are on 6.0 already
Out of ideas , cannot help but think its something simple , even tho developers options is ticked , is USB debugging ticked lower down ? Going back to home screen - swipe down and flick thru different options, camera- charge only- file transfer ?
Driver issue but doesnt explain it happening on other pc`s so seems more like ^^^
Then again if a USB hardware issue on phone, usb charge board -- i havent witnessed it so not able to comment.
If i come up with any ideas i will post - goodluck
I am going to try something on my own fone first before i let you know
I am going to attempt the official downgrade version of LP WW-52.20.40.196 from .144 M - via sd card and update from sd in recovery , with the view of updating/downgrading droidboot in the process- i have just managed the downgrade from .184 M to .144 via same method which is nice to learn
@sharkie545
Success -- Downgrade of MM to LP works with the downgrade firmware above works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , detected .134 and ..144 and .184 MM update packages
timbernot said:
edit my mistake you are on 6.0 already
Out of ideas , cannot help but think its something simple , even tho developers options is ticked , is USB debugging ticked lower down ? Going back to home screen - swipe down and flick thru different options, camera- charge only- file transfer ?
Driver issue but doesnt explain it happening on other pc`s so seems more like ^^^
Then again if a USB hardware issue on phone, usb charge board -- i havent witnessed it so not able to comment.
If i come up with any ideas i will post - goodluck
I am going to try something on my own fone first before i let you know
I am going to attempt the official downgrade version of LP WW-52.20.40.196 from .144 M - via sd card and update from sd in recovery , with the view of updating/downgrading droidboot in the process- i have just managed the downgrade from .184 M to .144 via same method which is nice to learn
@sharkie545
Success -- Downgrade of MM to LP works with the downgrade firmware above works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , detected .134 and ..144 and .184 MM update packages
Click to expand...
Click to collapse
Im going to try a few things first, i believe it has to do with the chip, or ribbon cable or IC chip. So im going to try to purchase a broken asus zenfone 2 (lcd problem) and swap some parts see if it fixes it. If it does well i know thats the problem. As i believe this is hardware related.
sharkie545 said:
[/HIDE]
Im going to try a few things first.
Click to expand...
Click to collapse
Wow just wow !!!!!!!!
timbernot said:
Wow just wow !!!!!!!!
Click to expand...
Click to collapse
Hehehe I appreciate the help. I have reformated many times lol. But since xfstk cannot be detected either (moorfield USB drive has malfunctioned) leads me to believe it has to be hardware related. Since moorfield is irrelevant of software/bootloader. It's kinda like the ultimate savour. Saved me out of some hetic problems before. (Leading me to wipe me imei #s lol which I had to than learn how to reprogram back lol)
Thank you again.
As the saying goes 'nothing ventured ......'
At least for all my hard work I found a way to downgrade from MM to LP with no PC , which obviously rewrites boot loader
Thank you
And you are two minutes away from finding out , should you decide to gamble like me
Although I have many phones to fall back on
Hello guys!
Today i make a big mistake. I want to install CM 14 to my LG g3 . At first i can't go into TWRP . After 1 hour a somehow managed to boot in twrp but after formating the old os the phone is not responsing at all.
Things that i try:
I try to install a bootloader with ADB but the my pc cant recognise the device.
Things that the phone does:
There is no boot screen all it does is led and blue LED is blinking.
If i connect to the pc it recognise it as "Android " but i cant do nothing with it.
Please help me. Thank you
Did you try to connect in download mode and flash stock firmware with the official toolkit? I don't remember it's name though
Balino said:
Did you try to connect in download mode and flash stock firmware with the official toolkit? I don't remember it's name though
Click to expand...
Click to collapse
Yes of course but the pc diden't recognise the phone and it say its " not cot connected"
You need to install device drivers and ADB drivers before trying. Use USB 2.0 ports too, it's acting wired with 3.0 ones
Greetings first
S.A
I flashed PA10 on My Mi a2 lite and worked greet but i entered to recovery rom to check something and when i restart to system i did press on Install TWRP if isnt installed ... i got bootloop when he booted to system
i connected the phone to Mi flash but when i connect him to pc FastBoot showing " usb can't recognize "
Same when i Enter EDL MODE ( pin Test ) " usb can't recognize "
The Problem not from Cable i tryd 6 cable same problem
Help me please and sorry for prolongation & English
M3Do0 said:
Greetings first
S.A
I flashed PA10 on My Mi a2 lite and worked greet but i entered to recovery rom to check something and when i restart to system i did press on Install TWRP if isnt installed ... i got bootloop when he booted to system
i connected the phone to Mi flash but when i connect him to pc FastBoot showing " usb can't recognize "
Same when i Enter EDL MODE ( pin Test ) " usb can't recognize "
The Problem not from Cable i tryd 6 cable same problem
Help me please and sorry for prolongation & English
Click to expand...
Click to collapse
reinstall the drivers ,provided with MiFlash ,if the problem presists ,change the usb to another on your pc
nikoman1987 said:
reinstall the drivers ,provided with MiFlash ,if the problem presists ,change the usb to another on your pc
Click to expand...
Click to collapse
Still Dont work 3 computer and 1 PC Cafe same problem
the last usb device you connected to this computer malfunctioned and windows does not recognize it
Help please i got this MSG from / Fast boot / EDL
M3Do0 said:
Still Dont work 3 computer and 1 PC Cafe same problem
the last usb device you connected to this computer malfunctioned and windows does not recognize it
Help please i got this MSG from / Fast boot / EDL
Click to expand...
Click to collapse
sorry ,never faced that kind of issue ,try installing different drivers ,because if the device malfunctioning ,then driver issue or hardware...