After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
C:\Users\rikku>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\rikku>adb devices
List of devices attached
1c576f70 sideload
C:\Users\rikku>adb usb
error: closed
Click to expand...
Click to collapse
mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Changing miui roms still require the bootloader to be unlocked.
mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Dobsgw said:
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Click to expand...
Click to collapse
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
mkioshi said:
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
Click to expand...
Click to collapse
Seriously try Linux
Dobsgw said:
Seriously try Linux
Click to expand...
Click to collapse
I installed a virtual Ubuntu machine, did the passthrough but no dice
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mkioshi said:
I installed a virtual Ubuntu machine, did the passthrough but no dice
Click to expand...
Click to collapse
good day please was this problem solved cause i have the same screen as above
Related
I am having issue connecting to PC (on XP here but also issues on Vista 64 at home). No matter what I try I can't access storage to copy to/from my PC to my phone. I understand that JB now uses MTP rather than USB Storage, but having spent about three hours now trying to find a solution I have to admit I am completely stumped
Having tried many options without success, and having installed and uninstalled HTC Sync at least six times I have started again from scratch reinstalling everything I could think of which might have a bearing. I have just reinstalled the full SDK, installed Windows Media Player 11 (for MTP), reinstalled .NET 4, installed latest version of HTC Sync, but still when I connect I get an error in device manager with Other Devices>Android Phone (also get the Hardware Wizard popup which always ends up saying not installed/could not locate software even if pointed directly at the Google USB driver folder in the SDK so it's obviously not this), and in HTC Sync it always shows no device connected. Fastboot and ADB both see it (devices). If I disable USB Debugging then it is recognised as an MTP device but then the Android Phone error kicks in and Sync doesn't see it.
This is my issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...and this...
Both of these are taken with the phone connected to PC, and whilst connected I can run ADB commands!
What am I missing? This is driving me mad
Try the Universal Naked Driver.
leppie said:
Try the Universal Naked Driver.
Click to expand...
Click to collapse
Well that sounds like fun What is it?
Dunc001 said:
Well that sounds like fun What is it?
Click to expand...
Click to collapse
Haha sounds like fun.
I think its a generic sort of driver
Wilks3y said:
Haha sounds like fun.
I think its a generic sort of driver
Click to expand...
Click to collapse
Hmm, found it - it's just drivers for ADB/fastboot which I don't have an issue with. This is my issue:
...and this...
Both of these are taken with the phone connected to PC, and whilst connected I can run ADB commands!
Dunc001 said:
Hmm, found it - it's just drivers for ADB/fastboot which I don't have an issue with. This is my issue:
...and this...
Both of these are taken with the phone connected to PC, and whilst connected I can run ADB commands!
Click to expand...
Click to collapse
On the Android device in device manager right click then uninstall, tick delete drivers if the tick box is there (sometimes it isnt)
Keep doing that until it doesn't even say android device (it will keep reinstalling it) it should say unknown device or something similar. Then reinstall the htc driver software and try again
Windows buggers up like this sometimes, has several drivers for the same thing, AFAIK its a case of getting rid of all the "spares" and installing just the one driver
Hope this helps
Sent from my HTC One X using xda app-developers app
Dunc do you try on another PC?
jamm513 said:
Dunc do you try on another PC?
Click to expand...
Click to collapse
+1 if it's a driver thing then this should confirm it
Sent from my HTC One X using xda app-developers app
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Yakumichan said:
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Click to expand...
Click to collapse
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
jhedfors said:
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
Click to expand...
Click to collapse
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did this somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yakumichan said:
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did dis somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
Click to expand...
Click to collapse
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
jhedfors said:
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
Click to expand...
Click to collapse
Right, sorry. It's German and it says that the command "fastboot" either has been written wrong or hasn't been found.
And also: Yes, it is:
I think you need to check your drivers
The device should be connected via adb interface driver or android driver
After that you should be able to see ur device
This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.
Yes please that would cut down a lot
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!
randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days
Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character
Hi, i want to unlock the bootloader of my old Redmi note 5, but there's a problem, when I go into fastboot mode, the Xiaomi's software can't find it, even using ADB the device is impossible to find. If I turn it on normally i can find it. Why it happens?
Hey u may give this a try as based on my understanding Xiomi devices will require u to install mi flashtool on PC as it has driver installation option. Remember some times you are required to disable driver signature verification.
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
plusminus_ said:
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
Click to expand...
Click to collapse
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
Weird.
Maybe try a different cable?
Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
U might be using an Amd based system. Usb 2.0 hub is ur solution
Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
drnightshadow said:
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
Click to expand...
Click to collapse
Can you tell me about this usb 3 reg patch?
Actually i am outstation and don't have my usb hub and i want to do faatboot commands
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Banty448 said:
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Click to expand...
Click to collapse
Read the thread and don't be troll. You didn't even read post before you post it your own. Ignorance is a bliss.
Good luck and stay safe.
Hello people of XDA
My Redmi 5A got softbricked and I'm not sure why since I wasn't (and never have) using it for rooting/installing new ROM/etc., I was using it for normal usage. (Didn't install anything that might cause the phone to just shutdown like that too)
Currently, my Redmi only shows:
-The system has been destroyed screen
-Fastboot mode
-Recovery mode
Methods I've tried:
-Mi Assistant/Mi PC Suite, which is useless because my phone cannot connect to it because the USB debugging is not turned on and I have no way of turning it on. Which made my phone unable to be recognized by the assistant, but it is recognizable by my laptop. (for extra info)
-ADB & Fastboot, which is also fruitless as of this far because after running the flash_all.bat, it says that my device is locked and cannot be erased. (exta info: I downloaded the EU-fastboot version)
-Factory reset and reboot.
I'm really not familiar with this situation, but as far as I've learned in the internet, that means my Redmi's bootloader is locked (?)
I do have the option to go to Xiaomi's service center, but I just want to know if this is fixable at home.
Thank you in advance for any help!
kitsunekoi said:
Hello people of XDA
My Redmi 5A got softbricked and I'm not sure why since I wasn't (and never have) using it for rooting/installing new ROM/etc., I was using it for normal usage. (Didn't install anything that might cause the phone to just shutdown like that too)
Currently, my Redmi only shows:
-The system has been destroyed screen
-Fastboot mode
-Recovery mode
Methods I've tried:
-Mi Assistant/Mi PC Suite, which is useless because my phone cannot connect to it because the USB debugging is not turned on and I have no way of turning it on. Which made my phone unable to be recognized by the assistant, but it is recognizable by my laptop. (for extra info)
-ADB & Fastboot, which is also fruitless as of this far because after running the flash_all.bat, it says that my device is locked and cannot be erased. (exta info: I downloaded the EU-fastboot version)
I'm really not familiar with this situation, but as far as I've learned in the internet, that means my Redmi's bootloader is locked (?)
I do have the option to go to Xiaomi's service center, but I just want to know if this is fixable at home.
Thank you in advance for any help!
Click to expand...
Click to collapse
I can flash your device using this tool.
You can flash the device in edl mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mvikrant97 said:
I can flash your device using this tool.
You can flash the device in edl mode.
View attachment 5914529
Click to expand...
Click to collapse
Can you tell me more about what app do you use?
kitsunekoi said:
Can you tell me more about what app do you use?
Click to expand...
Click to collapse
Its a paid software but I'll help you to flash your device for free
mvikrant97 said:
Its a paid software but I'll help you to flash your device for free
Click to expand...
Click to collapse
Sorry but how do you suppose to do that when my device is with me??
kitsunekoi said:
Sorry but how do you suppose to do that when my device is with me??
Click to expand...
Click to collapse
Using Remote access through anydesk.
I think I will go to the service center, thank you for the offer though.
kitsunekoi said:
I think I will go to the service center, thank you for the offer though.
Click to expand...
Click to collapse
I know you are not comfortable giving remote access.
I will make a tutorial on Monday to flash the device without authorisation.