Hello,
I am in a bit of a troubled spot right now. My AT&T HTC One phone currently has no OS on it. I tried updating to the latest CM 10.1 firmware but I noticed that some apps started to bug out so I flashed an older version of CM. But it resulted in a boot loop. From there I tried to fix it but it got worse.
-I formatted my phone so there is no OS
-TWRP is working
-I have no roms
-Phone is rooted
When I tried to plug in to my Windows laptop, it shows that the drivers are installed but adb and the toolkit cannot find the device. I was thinking of sideloading a rom with adb but that didn't work cause the device was invisible. I then tried the toolkit but no luck again cause the program can't find the device. Any help would be great appreciated! Thanks for the help.
Dear readers,
I've got an HTC One S Ville on which CM Mod was running. I am travelling at the moment, on the other side of the world, so I really need my phone!
Once connected to wifi it asked to install 10.1.3, which I stupidly accepted.
Since then I'm stuck in a bootloop. I've tried a factory reset, which didn't help. I know reflashing boot.img might help, however I cannot connect my phone to any pc, because it doesn't recognize the device. Even a clean pc (borrowed laptop, I don't have one), on which I installed the HTC sync driver and BMP driver downloaded from http://forum.xda-developers.com/showthread.php?t=2191279 doesn't show any approachable device.
I've given up and am lost in a forest of unknown tools etcetera and wish I'd never installed CM mod in the first place.
Who knows what to do?
My HBOOT is 2.15 and I can still enter the recovery console etc.
However, in the recovery console I cannot mount /sdcard, it gives an error.
Really, is it so ****ed up that no one knows an answer?
Well I assume you don't have a nandroid or you would have tried that already
At this point you either hope your phone supports otg and can mount an external flash drive or you need to install fastboot and adb and drivers or figure a way to get the sdcard to work, there really isn't a magic answer sorry
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hello friends at XDA!
I need some help. I have a Tmobile M7 HTC One. I have TWRP 2.7 running just fine. I have been able to flash a few ROM's using just that. I now want to install Kitkat GPe and it seems to require S-Off or else I get stuck in a bootloop. For what it's worth, I have Hboot 1.44. The phone has developer mode turned on. And it has USB debugging turned on.
I made such a mess that I formatted the whole device and had to flash a new ROM via USB OTG. It's back in working order now... but, not with the ROM I want. Currently running the newest stable Cyanogen Mod.
I have attached the phone to a Windows 7 and Windows 8 computer. Neither of them will recognize the phone.
On the Win7 machine, I had HTC Sync installed and closed. I also installed Squabbi's Toolkit and attempted to install the drivers from it. When I click the HTC Drivers button, nothing happens. I have tried connecting to adb through the tooklit and turning S-off... but, they all return some version of the Error: Device Not Found message.
On the Win8 machine, there was no HTC software, so I installed Squabbi's kit. I pressed the HTC Drivers button and it said it had installed new hardware... but, again, ADB won't connect.
I, frankly, don't care about ADB or s-off, as I've never needed them before. I just want to install 4.4 GPe. If I can do that without S-off, please point me in that direction. If I can turn S-off directly from the phone without ADB, please point me in that direction. And if I really need ADB to work, please help!
I'm almost certain this solution is already posted somewhere... and I'm just not able to find it... sorry to be a drag if that's the case. Either way, I'd be happy to reward (paypal) the person/people who help me get this resolved. I'm thinking like $10...
Thanks everyone!
Hello,
I hope that I am not asking a already existing question again, if so, please send me the link and I will follow the instructions there.
I could not find anything, so far, but I am nearly going mad after a day of trying to unbrick my phone.
So, I had CM 11 Snapshot M10 installed, the current clockworkmod, bootloader unlocked through htcdev.
Today I wanted to do a full wipe (including /sdcard, because there were tons of files which I didn't know, lately).
I don't know why, but i ended up wiping /system and /sdcard at the same time.
Now I don't have any system on the phone in order to boot and get adb or mount the phone as a USB drive, and no firmware on the phone which I could flash. I really have no idea how I can get any rom onto the phone, now...
I tried official RUUs ("Please download the RUU which fits your phone), ADB sideload with CWM ("no devices found"), ADB sideload with TWRP (same as with CWM), and now I am running out of ideas...
Does anyone have an idea how to or get ADB sideload working (USB drivers are installed on my PC, but it doesn't seem to work), or how to get a RUU wiorking (I would like to go back to the stock rom anyway, I miss sense by now), or any other way how to revive my phone?
I do have access to the bootloader, fastboot is working, and so is the recovery. Is there any information you would need?
It is an enrc2b international, no branding. CID is HTC__102.
fastboot getvar version-main outputs 2.18.401.3
I really hope that someone can help me out...
Moritz
Adb sideload needs up to 5min to recognise the device.
Or you flash twrp recovery. Which has mtp support (access via windows explorer)
If crusader's suggestion didn't work then:
Try to use a different USB port. If USB 2.0 use USB 3.0 and vice versa.
If that doesn't work too, try running cmd as admin.
Last resort : install Ubuntu or any other Linux distro, and install dev tools on it (check for guides ) .. I have a similar issue to yours when it comes to windows, restarting to Linux always works for me
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
elektrobastler said:
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
Click to expand...
Click to collapse
Someone posted his backup files somewhere here on the forums...
First look at your CID (found at the top of the boot loader)
And secondly you can just install sense-based ROMs like viper or revolutionHD (I think that's what it was called) .. RevolutionHD is just stock sense basically with a few performance improvements.
Thank you very much!
You really saved my day
I was able to install CM11 now, it booted.
I instantly shut it down again, though, because I will now try RevolutionHD.
Stock sense (especially the gallery and camera app, never found anything comparable so far) with a few improvements sounds just awesome.
Exactly what I was hoping for, but I never imagined someone had actuall done it!!
Downloading it now, I think this will stay my ROM for the next year(s), depending on how long my X+ will keep on working...
March 22 2019 - Solved because I'm an idiot. Story on page 2
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
What I need help with:
Adb communicating with Fastboot
How far I got:
Unlocked bootloader (unlock symbol when booting)
Installed plethora of Adb Driver's via Google, Xiaomi, Qualcomm
Used USBDeview to uninstall all drivers even from my past devices and try reinstalling just drivers involving Xiaomi, Poco ect...
What does work:
Adb commands recognized in Miui
Adb commands recognized in Miui Recovery as sideload (after selecting pc suite option)
Miui unlocking tool (was able to unlock and can still detect the device unlocked in Fastboot)
In Miui File Transfer & PTP mode
What I tried:
Different USB ports 2.0 & 3.0 directly in the back of the PC and the front hub
Different USB C cords with and without extension cord (even though that shouldn't matter)
Different drivers old and new
Powershell & CMD as administrator.
What's already been done before you suggest it:
2nd computer, different ports, satanic ritual, different cords, turning PC on and off again after driver installs.
Trying methods from First 5 results when you Google anything along the lines of "Poco f1 adb Fastboot not recongnized"
Uninstalling drivers and retrying
USB Debugging on, duh.
Oem unlock on, duh.
Basically it's this, clearly the device is being recongnized and being talked to, just able to unlock the device via Xiaomi unlock tool is proof enough of that it's detected in and out of Fastboot, but in a adb window via powershell or cmd-here, it's just not recongnized my device in Fastboot. In Miui or recovery theres no issue, they communicate fine.
Or if there's an alternative way to install TWRP that doesn't involve Fastboot I'm all ears on that.
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
I want the recovery so I have an option that isn't miui.
My phone isn't slow, but it's running more than a fair share of mi bloat.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Also can you roll back to 8.1 without twrp, root, or adb?
I tried rolling back via the update screen and selecting the package/downgrade, but Miui won't allow installing/flashing older software, which is something I tried before.
No one else has this problem?
Chocolina said:
No one else has this problem?
Click to expand...
Click to collapse
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
tnsmani said:
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
Click to expand...
Click to collapse
Don't you need TWRP to install root?
I haven't rooted 1st and then did recovery since the Nexus 5 days, every device I've had since has had root guides that wanted me to fastboot flash the recovery first and install root that way.
And i dont know if my pc is Ryzen, not a pc gamer so all I have is on board, but it is old amd machine running windows 10. I also don't have a monitor these days, I have my pc setup to accept remote desktop so I interact with it that way because it's rare I need a pc these days
All I know is adb works with miui and recovery (sideload) fine, it's fastboot giving me problems, and all the root guides require fastboot
Also same exact issue regarding my mi pad I just got too
https://forum.xda-developers.com/mi-pad-4/help/please-help-troubleshoot-xiaomi-t3910249
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Tell me more about this Linux/your method
I never used Linux, so I don't know what I'd do to get it or if I could boot it temporarily off of another form of storage or something.
Chocolina said:
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
Click to expand...
Click to collapse
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Dose the roms solve touch issue???????
MasterFURQAN said:
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Click to expand...
Click to collapse
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Chocolina said:
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Click to expand...
Click to collapse
If it's more than 5 years old, then it's not ryzen. Fyi Ryzen is the newest range of CPUs from AMD.
I went out and bought an Intel laptop and it still won't work!!
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Chocolina said:
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Click to expand...
Click to collapse
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
tnsmani said:
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
Click to expand...
Click to collapse
It was a headache because my precautions weren't working. Next time I'm just going to check if it'll take flash commands anyway before asking for help.
On the plus side, I got to learn what a laptop made by RCA is like. It's **** sure, I'd expected as much, but it was as bad, if not worse than those $99 "windows 8" tablets from 2014-2015 running those archaic Intel Z3735 Atom series processors. Stay away