Please help,
I made a complete format with an internal storage, now my computer can not see the phone "MTP USB devices "this devices canot start (code 10)" and I can not load anything. I can go into fastboot mode and and TWRP, but it displays a password entry. Computer doesnt see internal storage. I tried almost everything but no result. Is possible to fix it by ADB SIDELOAD from thsis thread : https://forum.xda-developers.com/le-max-2/help/help-accidentally-wipe-data-twrp-t3537033
Before i flashed MIUI 8 from this thread: https://forum.xda-developers.com/le...max2-x820-822-miui8-1-6-12-3december-t3526832
Please!
If you go to fastboot , will your computer recognize the device?
Not really, computer does not recognize as a disk. I cant install nothing. When I try to upload the driver, displays the message this devices canot start (code 10). Maybe problem with phone partitions. I can go into fastboot mode and can flash TWRP. In TWRP requires a password. Maybe some command in adb or fastboot, flasing by OTG????
Please HELP
anameeeen said:
If you go to fastboot , will your computer recognize the device?
Click to expand...
Click to collapse
Not really, computer does not recognize as a disk. I cant install nothing. When I try to upload the driver, displays the message this devices canot start (code 10). Maybe problem with phone partitions. I can go into fastboot mode and can flash TWRP. In TWRP requires a password. Maybe some command in adb or fastboot, flasing by OTG????
I found this: https://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927
Can I try it on my device?
Please HELP
Not sure about the the password, sounds encryption related. You might need to sort that out first and I think there were some threads about it.
In any case, didn't have the password issue, but I had a wiped phone and found MTP didn't work in TWRP for me. I didn't try OTG but I think people have had problems with that as well. If you can get to fastboot and boot TWRP you should be able to use ADB sideload. In TWRP I think it's under Advanced, and then you select sideload and swipe to enable it. Then, assuming you have ADB working you can type the following on the cmd: "adb sideload NewRom.zip" to flash.
I used this thread as a reference and section 7 details sideloading (assuming you have ADB working. If not, using the 15 second ADB Installer let me skip sections 2-4):
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
if sideload doesn't work try theese passwords:
default_password
standard_password
i had that issue once. what worked for me was just hit cancel at the password prompt, wipe everything, hit the format data button, type yes and reboot to recovery again.
@bwalter
about mtp not working in twrp:
while in twrp, open device manager (devmgmt.msc)
if you have the yellow exclamation mark at your mtp device update the driver manually (choose from a list). pick mtp-usb (should be the first in the list matching the name).
should work.
Gesendet von meinem LEX820 mit Tapatalk
Thanks, I think the main problem is ADB drivers, because in fastboot mode I wrote: adb devices - enter, and no devices was recognized. I am little advaced beginner and I dont know how to resolve this isue. Anyway thanks for your help. I will write effects soon.
I look forward to other ideas please.....
install drivers on another pc and see if the phone will be recognized.
macjed said:
Thanks, I think the main problem is ADB drivers, because in fastboot mode I wrote: adb devices - enter, and no devices was recognized. I am little advaced beginner and I dont know how to resolve this isue. Anyway thanks for your help. I will write effects soon.
I look forward to other ideas please.....
Click to expand...
Click to collapse
fastboot is not adb.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
if sideload doesn't work try theese passwords:
default_password
standard_password
i had that issue once. what worked for me was just hit cancel at the password prompt, wipe everything, hit the format data button, type yes and reboot to recovery again.
@bwalter
about mtp not working in twrp:
while in twrp, open device manager (devmgmt.msc)
if you have the yellow exclamation mark at your mtp device update the driver manually (choose from a list). pick mtp-usb (should be the first in the list matching the name).
should work.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
default_password
standard_password does not work in TWRP5.8TeaMSpaiN (I have instaled) , in device manager is only: Android Devices- "Android Composite ADB Interface" without any mark and no MTP devices. If good?
How to use sideload option?
anameeeen said:
install drivers on another pc and see if the phone will be recognized.
Click to expand...
Click to collapse
I tried, but no effect.
macjed said:
TWRP5.8TeaMSpaiN (I have instaled)
Click to expand...
Click to collapse
you need this one https://dl.twrp.me/x2/
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
you need this one https://dl.twrp.me/x2/
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
Instaled this TWRP, restart and stuck on LeEco, Device manager show MTP USB Device with yellow triangle, when I try instaling drivers, shows "This Device can not start. (code 10). ?????
In cmd I wrote "adb devices" shows 11571fb8 device ?????
In fastboot mode "adb devices" - nothing shows
Device manager show ADB Sooner Single ADB Interface
In TWRP after wiping evetything is -"Filed to mount '/cache' (Invalidargument"
- unable to mount storage
Maybe new drivers?
macjed said:
Instaled this TWRP, restart and stuck on LeEco, Device manager show MTP USB Device with yellow triangle, when I try instaling drivers, shows "This Device can not start. (code 10). ?????
In cmd I wrote "adb devices" shows 11571fb8 device ?????
In fastboot mode "adb devices" - nothing shows
Device manager show ADB Sooner Single ADB Interface
Maybe new drivers?
Click to expand...
Click to collapse
you cant use adb in fastboot mode. thats two different things.
lets try it simple:
enter fastboot mode
type:
fastboot boot twrp.img
↑ or whatever the name of your twrp image is.
twrp should boot.
go to advanced, adb sideload and slide to start it.
type:
adb sideload romname.zip
that should do it.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
you cant use adb in fastboot mode. thats two different things.
lets try it simple:
enter fastboot mode
type:
fastboot boot twrp.img
↑ or whatever the name of your twrp image is.
twrp should boot.
go to advanced, adb sideload and slide to start it.
type:
adb sideload romname.zip
that should do it.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
Thank you for clear explanation because a little confused at all. For the moment I will try again, already the day I struggle with this problem and I am angry and a little tired. I write how it went soon.
What I did was format data instead of wipe internal storage,then pushed the twrp backup from my laptop,sideloading rom threw error even then
RISHI RAJ said:
What I did was format data instead of wipe internal storage,then pushed the twrp backup from my laptop,sideloading rom threw error even then
Click to expand...
Click to collapse
When I trying sideload mode and typing cmd: "adb sideload STOCKrOM.zip"
terminate called after throwing an instance of 'std::bad_alloc
this aplication has requested the Runtine to terminate it in an unusual way
What is wrong?
macjed said:
When I trying sideload mode and typing cmd: "adb sideload STOCKrOM.zip"
terminate called after throwing an instance of 'std::bad_alloc
this aplication has requested the Runtine to terminate it in an unusual way
What is wrong?
Click to expand...
Click to collapse
you have pm.
Gesendet von meinem LEX820 mit Tapatalk
ADB Sideload Complete
Failed
No idea what can I do elese?
Thanks to A.N.Droid, my device has come to life.
Everything works as it should.
Once again, many thanks for your help. You're a great brother
Related
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
lorenk93 said:
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
Click to expand...
Click to collapse
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
oziboy said:
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
When I write adb sideload file_name.zip, it
returns "error: closed". why?
lorenk93 said:
When I write adb sideload file_name.zip, it
returns "error: closed". why?
Click to expand...
Click to collapse
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
oziboy said:
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
Click to expand...
Click to collapse
so... I have to write "ADB usb file_name.zip". tath's right?
lorenk93 said:
so... I have to write "ADB usb file_name.zip". tath's right?
Click to expand...
Click to collapse
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
oziboy said:
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
Click to expand...
Click to collapse
I don't know why, but when I write adb usb it returns "error: device not found"
lorenk93 said:
I don't know why, but when I write adb usb it returns "error: device not found"
Click to expand...
Click to collapse
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
oziboy said:
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
Click to expand...
Click to collapse
I did it... Thanks to you... So thank you so much...
lorenk93 said:
I did it... Thanks to you... So thank you so much...
Click to expand...
Click to collapse
No problem, I had almost the same problem and just told what I did xD
Hi all,
I'm here because i don't know where else to look..
I've got a nexus 9 tablet running 5.1.1, its rooted with an unlocked bootloader, running twrp custom recovery, i was trying to flash a new rom, now all i get is a constant google logo upon bootup, I can enter recovery and fastboot and all of that, but none of my computers can see the tablet in adb or fastboot when I plug it in via usb, so Im not able to flash anything from my computer, does anyone have any ideas? or have I totally ****ed my nexus 9?
I have 2 laptops running Ubuntu, and my desktop is Windows 7 with all the necessary drivers, I've never had issues connecting my devices in the past, so I'm kinda at a loss.
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
kacang87 said:
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I have tried to do that, factory reset just resulted in no change to the tablet
corkiejp said:
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
Click to expand...
Click to collapse
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Baskinmfr said:
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Click to expand...
Click to collapse
change your cable connect to computer..some cable cannot sent data..happen to me
Sent from my Nexus 9 using Tapatalk
Can you enter recovery? If you can then use your computer to copy the zip file of a rom and install it. Otherwise check your cable, I had problems with the one htc gave me.
I'm having issues attempting to unlock the bootloader on my g5. I can boot into fastboot mode from the os. Once I'm in fastboot however the driver won't install in windows to allow me access to run the fastboot oem unlock command.
I've installed the correct LG G5 Driver set (LG United Mobile Driver) as far as I can tell. I've tried manually selecting the driver in windows. Everything works perfectly in debug mode in the os but once I've used the adb reboot bootloader command and it reboots, it goes off the radar and I can't do anything else.
I'm using the LG G5 T-Mobile edition H830 v10d.
Try running adb kill-server after doing adb reboot bootloader. Then do you get anything when you run fastboot devices?
Keep in mind, you'll need to have "Enable OEM Unlock" flipped in USB Debugging.
Also, if you're using the h830, you should post this in the tmobile specific forums.
Well got same problem here. Once in bootloader, i have the welcome to Fastboot Mode phone screen but i can't do anything using command prompt. Fastboot devices returns nothing attached.
Even pushing 10s power button does nothing. Have to pull out battery.
Don't understand.
Any help ?
Thanks.
WILMANS2M said:
Well got same problem here. Once in bootloader, i have the welcome to Fastboot Mode phone screen but i can't do anything using command prompt. Fastboot devices returns nothing attached.
Even pushing 10s power button does nothing. Have to pull out battery.
Don't understand.
Any help ?
Thanks.
Click to expand...
Click to collapse
Did you solve this? I have the same problem.
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
WILMANS2M said:
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
Click to expand...
Click to collapse
Just the Google USB drivers or the whole SDK? What version of Windows are you on?
Can u post a link to the download?
WILMANS2M said:
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
Click to expand...
Click to collapse
???
For anyone having the issue, I solved it as follows (on Windows 7):
You've used adb to reboot into fastboot, but fastboot isn't responding. "fastboot devices" in adb shows no devices.
1. Go to device manager
2. Look for a device called Other Device, or something similar. Expand that, you should see a device called Android with yellow exclamation a mark.
3. Right click the device, select Update Driver Software.
4. Select Browse my computer for driver sofware
5. Select Let me pick from a list....
6. In the column on the right, find something a driver that says Fastboot driver or something similar (I can't see it now that I've installed it).
7. Install that, go back to your command line interface, type fastboot devices to confirm you now have access.
I have the same problem with h850
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Have you tried with another cable or diffrent USB port?
I did but same result. Any other advice I can follow?
TSKXDA said:
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
MobyDuhFreak said:
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
Click to expand...
Click to collapse
If I try to fastboot into recovery I still get the same error.
TSKXDA said:
If I try to fastboot into recovery I still get the same error.
Click to expand...
Click to collapse
Is your phone a redmi 5(codename Rosy) or a redmi 5 plus or a redmi note 5 in India (codename Vince)?