Hi everybody, i've an issue with my LG G3 D855(Hong Kong). I bought it with the D85510M version (kitkat). I flashed it with the D85510B with "flashtool 1.8, tot file and a dll file" but it stopped at 94%. Since then, i can't access download mode and recovery. The phone stucks in the Logo and after few minutes goes to fastboot mode. I khow that i have to flash the partitions to restore download mode but the problem is that i can execute the command "Fastboot reboot" but not the other commands. fastboot erase "partition" returns: "failde to erase partition". Fastboot flash "partition" file.img returns: "flash write failure". The latest Android ADB drivers are installed (android adb interface in device manager).
adb devices return nothing. fastboot devices : "? Fastboot."
What is the problem ? Help me please... I'm in windows 10 but i have the same probleme when using Ubuntu. please help me...
SamKat said:
Hi everybody, i've an issue with my LG G3 D855(Hong Kong). I bought it with the D85510M version (kitkat). I flashed it with the D85510B with "flashtool 1.8, tot file and a dll file" but it stopped at 94%. Since then, i can't access download mode and recovery. The phone stucks in the Logo and after few minutes goes to fastboot mode. I khow that i have to flash the partitions to restore download mode but the problem is that i can execute the command "Fastboot reboot" but not the other commands. fastboot erase "partition" returns: "failde to erase partition". Fastboot flash "partition" file.img returns: "flash write failure". The latest Android ADB drivers are installed (android adb interface in device manager).
adb devices return nothing. fastboot devices : "? Fastboot."
What is the problem ? Help me please... I'm in windows 10 but i have the same probleme when using Ubuntu. please help me...
Click to expand...
Click to collapse
Helpe please....
SamKat said:
Helpe please....
Click to expand...
Click to collapse
follow this. it worked for me.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Jahanzaibawan said:
follow this. it worked for me.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
Thank's for the reply. I've seen this tuto yet but as it's a little bit risky to do this, i decided to look for other solutions. I'm desesperate so i think i'll try this. But, tell me, you did this with wich kind of wire ?
SamKat said:
Thank's for the reply. I've seen this tuto yet but as it's a little bit risky to do this, i decided to look for other solutions. I'm desesperate so i think i'll try this. But, tell me, you did this with wich kind of wire ?
Click to expand...
Click to collapse
I did this on two different mobiles and worked like a charm. It's really useful.
Just use any jumper wire.But be cautious to use thin wire which touch only single pin.
Jahanzaibawan said:
I did this on two different mobiles and worked like a charm. It's really useful.
Just use any jumper wire.But be cautious to use thin wire which touch only single pin.
Click to expand...
Click to collapse
Ok, Thank's a lot.
Related
Hi,
I've wrote some days ago this post
Hi there!! First of all thanks for the explanation! I've try to understand in wich position is my KF.... but nothing...
A little bit of history:
KF HXD 8,9
I've rooted the KF, after that I've install Safestrap Recovery APK and successfully flash/install 2 different rom into 2 different rom slot not in the stock rom(backed up in the device).
Great! I've tested both and chose one running well. I've chose to delete one and give to the one more space... 7GB.
Well after the installation I've reboot the device........ white fix logo (all white) on screen.... after some reboot pushing the power button (I don't how) it show a screen where I can chose restore device or reboot. I've restored the device to the default factory...
Well now I really don't know what can I do. The command adb devices doesn't recognize any device. Fastboot: ./fastboot getvar product is waiting for the device...
p.s. Only one positive thing is when I plug the KF with the usb in my MAC start Android Transfer Tool.
Any help or suggestions are welcome.
Thanks.
sorry for the bad english
Click to expand...
Click to collapse
and they move me to this section....
Well now I really don't know what I have to do. And in wich state is my kf... brick/no brick
Plase can you suggest me the right way?
Now I'm using an ubuntu 12.04 as pc, there are some tool or script that can I run into ubuntu?
Thanks.
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
macman005 said:
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
Click to expand...
Click to collapse
I've run the fastboot command from the platform-tools folder into the Android sdk and...
still < waiting for device >
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
macman005 said:
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
Click to expand...
Click to collapse
with the mac it's start Android Transfer tool but it say that it can't find the device, into ubuntu 12.40 nothing.
Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?
ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv
Stuck on boot logo !!!!! :crying:
Can't :
1. Can't boot to ROM (as doing so just stays on boot logo)
2. Can't boot into recovery (as doing this gets me to either black screen or just boots back to the boot logo)
Can :
1. Can enter bootloader
2. Can able to use fastboot commands
Tried:
1. flashing stock ROM several times,
2. flashing stock recovery
3. flashing twrp recovery
:crying:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
alirazaagha said:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
Click to expand...
Click to collapse
Friend thanks for the reply but your link just says "Duplicate thread. "
hackiee said:
Friend thanks for the reply but your link just says "Duplicate thread. "
Click to expand...
Click to collapse
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Thanks for your post friend, but, your guide doesn't fulfill my situation.
As, I am stuck on bootliader or boot logo.
I have flashed all firmwares s048,s233,s244,s51 through fastboot but none of them able to get me out of it.
Even tried flashing various recoveries both stock and twrp but neither of them helped
If, anyhow I can be able to enter into TWRP. It will solve the problem. But, I don't know nothing seems to work.
Even tried corrupting the bootloader and then flashing blankflash, but that too didn't able to get me out of the bootlogo.
Please help ?
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
hackiee said:
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
Click to expand...
Click to collapse
It's alright.
alirazaagha said:
It's alright.
Click to expand...
Click to collapse
nothing strange ? Ok thanks
hackiee said:
nothing strange ? Ok thanks
Click to expand...
Click to collapse
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
alirazaagha said:
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
Click to expand...
Click to collapse
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
hackiee said:
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
Click to expand...
Click to collapse
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
alirazaagha said:
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
Click to expand...
Click to collapse
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
hackiee said:
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
Click to expand...
Click to collapse
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system
See the difference now? :silly:
Please, discuss it on that thread if need so others could also benefit from it.
alirazaagha said:
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system.
Click to expand...
Click to collapse
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
hackiee said:
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
Click to expand...
Click to collapse
OK. I though that you only tried Format command not erase. You should skip this command and do the whole process. I have added this command so that previous system files are erased. But, I booted my phone without using this command first time. Second time, I tried to see if I can do it all in a single process then I added this command and it worked without any issues and all the process went smooth and phone booted like a new one.
Try all commands but skip erase system command.
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
DrGhost001 said:
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
Click to expand...
Click to collapse
Did you find any solution?
Same issue here, I guess it's a hardware issue: SSD is damaged ?
fastboot erase system
fastboot format:ext4 system
Maybe related to the file system ?
i have the same probelm, do you guys find any solution ?
hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.
"fastboot set_active other" to switch slot
I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.
HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?
kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)
ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files
Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?
cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done