Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
NinjaKenZen said:
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
Click to expand...
Click to collapse
If you can push files on sd card, use the TWRP back-up from here to restore to stock.
http://forum.xda-developers.com/showthread.php?t=2414238
You'll at least get it working again.
Thanks, somehow when I updated the bootloader, the boot.img restriction got lifted after I just entered the command again when 'unknown failure' came up. I was at this point able to access the sd card under a buggy rom start-up.I used TWRP to flash a new rom.
Fixed.
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
loaybilal said:
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
Click to expand...
Click to collapse
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
imcontreras said:
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
Click to expand...
Click to collapse
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
roshak said:
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
Click to expand...
Click to collapse
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
roshak said:
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
Click to expand...
Click to collapse
Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
Thank you!
Related
my device is stuck in bootloop with no backup and is not showing up in adb for me to push rom to phone? suggestions????
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
NasaGeek said:
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
Click to expand...
Click to collapse
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
jizang said:
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
1.0.31 and tried both twrp and cwm
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
NasaGeek said:
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
Click to expand...
Click to collapse
yea ridiculous amount times
I had the same problem i could not adb sideload a Rom,in the end i had to flash stock ruu to save my phone
Sent from my HTC One X+ using xda premium
indie12 said:
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
Click to expand...
Click to collapse
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
reaper90 said:
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
Click to expand...
Click to collapse
doesn't work with twrp either,
also forgot to mention is odd that adb doesn't find device since i can flash new recovery / kernal via fastboot?
adb discovering my device in sideload now but not allowing the sideload? how can i push the rom to sdcard via adb?
indie12 said:
doesn't work with twrp either
Click to expand...
Click to collapse
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
reaper90 said:
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
Click to expand...
Click to collapse
its just worked, transfering the rom now, no idea what caused it to work this time but it is so thanks
Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.
[[ SOLVED ]]
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
rikrdoVe said:
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
Click to expand...
Click to collapse
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
reaper90 said:
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
rikrdoVe said:
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
Click to expand...
Click to collapse
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
reaper90 said:
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
Click to expand...
Click to collapse
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
rikrdoVe said:
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
Click to expand...
Click to collapse
Did you use the right version of CWM for android 4.4+?
reaper90 said:
Did you use the right version of CWM for android 4.4+?
Click to expand...
Click to collapse
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
rikrdoVe said:
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
Click to expand...
Click to collapse
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
reaper90 said:
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
Click to expand...
Click to collapse
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
rikrdoVe said:
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
Click to expand...
Click to collapse
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
reaper90 said:
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
Click to expand...
Click to collapse
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
rikrdoVe said:
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
Click to expand...
Click to collapse
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
reaper90 said:
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
Click to expand...
Click to collapse
A month without phone and thanks to you it works again!
Thank you so much, I could not pass the zip in any way but with "adb push rom.zip / data/media/0 /" if it happened and I could flash ...
I Repeat .... THANK YOU!
have the same problem with my HTC One X.
Can you gave me an answer?
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Hi. so today i thought i would try to unlock bootloader and root then install a custom rom. I got everything ready on windows 8.1 . managed to unlock the bootloader and then when to flash twrp. Now the error i made is instead of flashing twrp i booted into it. I then proceeded to make the necessary wipes and then went to mount phone to pc so i could transfer the zip for the new rom and the phone just wouldnt show up on my pc. I tried eveything. So now i can only do 2 thing.s Boot into fastboot or into stock reocvery which offers 2 choices. update with update zip already placed in phone or clear data. When i boot into fastboot and then connect hpone and opem command prompt then type adb usb it starts daemon then says devices. In device manager it shows adb interface fine. So what can i do now as i need this phone to work as dont have a spare. How can i get it to let me use adb usb properly so i can flash twrp and then flash rom. It currently has no os on phone. Is there a way to flash via the phone itself? Also if i let it boot up it auto matically open stock reocvery. Can anyone please help asap thanks.
Heyyo, @dead4ngel
Derp! Just figured it out. Once you're in fastboot you don't use adb devices command, it changes to stuff like fastboot devices
Hence there's an adb.exe and a fastboot.exe
So for example once you're in fastboot on your phone and you plug in your usb cable? To flash TWRP you would do this on your command prompt
fastboot flash recovery twrp.img
by chance have you tried this guide? Worked for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151/
You legend!!!!
ThE_MarD said:
Heyyo, @dead4ngel
Derp! Just figured it out. Once you're in fastboot you don't use adb devices command, it changes to stuff like fastboot devices
Hence there's an adb.exe and a fastboot.exe
So for example once you're in fastboot on your phone and you plug in your usb cable? To flash TWRP you would do this on your command prompt
fastboot flash recovery twrp.img
by chance have you tried this guide? Worked for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151/
Click to expand...
Click to collapse
Thank you so much. That worked right away. Theen all i had to do is mount in twrp and install mtp device. Now copying rom to internal and i should be good to go. Im so happy was ****ting bricks thinking iv just killed this phone only after 3 months of having it lol.
dead4ngel said:
Thank you so much. That worked right away. Theen all i had to do is mount in twrp and install mtp device. Now copying rom to internal and i should be good to go. Im so happy was ****ting bricks thinking iv just killed this phone only after 3 months of having it lol.
Click to expand...
Click to collapse
Glad to hear you got her sorted out
If you experience fingerprint reader issues when your device is asleep please flash an updated version of the modem firmware. I know it sounds odd but it does affect fingerprint reader performance when the device is asleep.
Chinese 26s 05.09 from here works good
https://yadi.sk/d/woKdrlRrv8yhr/Китай
But others have preferred developer 466D from here
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Modem firmware is separate from the ROM so you can flash them freely without risk of wiping out your ROM
Try each for a few days and see which one works best for you