Hi all,
Seen many topics about this topic but no solutions.
I'm trying to restore my phone to stock but I have the dual problems of:
A. Not having a working rom/android state to boot into
B. Unfortunately, after trying various stock methods, no longer recognizes fastboot commands (e.g., fastboot devices lists nothing). I connected previously so this is not an issue
Is there anything to be done to restore to stock or am I simply screwed?
I am working from a Mac OS X computer but can access Windows if it helps.
Thanks in advance.
none_of_the_above said:
Hi all,
Seen many topics about this topic but no solutions.
I'm trying to restore my phone to stock but I have the dual problems of:
A. Not having a working rom/android state to boot into
B. Unfortunately, after trying various stock methods, no longer recognizes fastboot commands (e.g., fastboot devices lists nothing). I connected previously so this is not an issue
Is there anything to be done to restore to stock or am I simply screwed?
I am working from a Mac OS X computer but can access Windows if it helps.
Thanks in advance.
Click to expand...
Click to collapse
does adb recognize it if you let it boot normally? if it gets to booting the kernel and adb recognizes it you may be able to push the system files manually via terminal. from there you can add recovery and at least have that option....but you would have to be very careful if you can't get to fastboot.
Related
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
iBlameLag said:
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
Click to expand...
Click to collapse
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
exad said:
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
Click to expand...
Click to collapse
Thank you, flashed over twrp and the computer recognizes it. Thanks so much for your help!
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Reserved for any solutions
This could help
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
androidsatti said:
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Click to expand...
Click to collapse
langelog said:
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
Click to expand...
Click to collapse
Nope
No solution till now
Hi guys,
Before i start, just be informed that i have tried google all possible solutions and tried them but to no avail. I know its a long shot but perhaps someone may be able to help however small the chances are.
My phone is a Xiaomi Redmi Note 3 Snapdragon variant and is rooted.
What happened was, i tried installing TWRP (kenzo version) on my phone and so following the "instructions" in the downloaded file.
I used Flashify to flash the boot.img and then redmi_note_3_Twrp.img then the phone prompted me to reboot.
Now my phone is stuck in bootloop. The only thing i can do is to boot into Fastboot. So i tried accessing fastboot via ADB hoping to be able to some how flash the original boot.img back.
The problem i have now is that i am unable to access the phone at all even though i can go into fastboot. It wont be detected by my PC. I tried Minimal ADB and Fastboot and PdaNet.
Is there any other way for me to detect my phone and run some form of command to get it started again? Any help at all is appreciated. The phone is fairly new and i'm regretting trying to get the latest ROM for it.
I'm hoping i'll have some luck in a helpful community such as this.
Thanks guys.
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Marticco said:
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Click to expand...
Click to collapse
Fret not my friend. For i have found the solution and managed to unbrick my phone. Thank the good guys at MIUI for this.
Head over to the MIUI forum and search unbrick under the Redmi Note 3 forums. I can't post the link here unfortunately
You can also thank me after you unbrick your phone.
This only applies if you are uaing the Redmi Note 3 Pro
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Marticco said:
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Click to expand...
Click to collapse
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
willetan said:
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
Click to expand...
Click to collapse
yes it is unlocked,
i think? When i entered fastboot mode. One of my apps says bootloader enabled and when i typed 'fastboot devices' in the Minimal ADB and Fastboot its shows:
0123456789ABCDEF devices
whereas if I type 'adb devices' i just shows:
List of devices attached
The main problem is the driver, i cant get adb to find my device. I have tried the universal usb drivers like Kouch but no success. My device is listed in the Unspecified section in my computer
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.