[Q] Need help with updating my M7 - One (M7) Q&A, Help & Troubleshooting

Hey guys,
About a year ago, I decided that I wanted to try Cyanogenmod on my HTC one M7 (international).
Thus I unlocked my bootloader, rooted, and installed Cyanogenmod. It was a very new old version (10.2 or something), but I still liked it more than Sense.
Fast forward to last week, when someone gave me a Chromecast, which did not work with my phone because of a lack of Google services.
Since then I have been trying to figure out how to update my phone in order to install a newer rom on it, because it cannot install Cyanogenmod 11.x.
I think it has to do with my very old firmware (1.44.0000).
The first problem that I run in to is that abd does not detect the M7.
I first tried on a Windows 8.1 PC, but like others that did not work. On a Windows 7 PC it does get detected, with Android 1.0 drivers, but it still does not show up in adb (using the command "adb devices").
There are a lot of threads about phones not being detected, but I cannot find one where a phone does get detected in Windows with Android 1.0 drivers, but not in adb.
My second problem is with what it is exactly that I need to do in order to install a much newer Rom.
This is what I think I need to do, is it correct?
Step 1, install an old rom that works with the old firmware (I can do this without adb, using a USB OTG tranfer cable)
Step 2, get S-Off using Revone
Step 3, Install the newest Hboot using adb (to do this my phone needs to be detected)
Step 4, Install the new rom
Thanks for your help,
Sahrum

Sahrum said:
Hey guys,
About a year ago, I decided that I wanted to try Cyanogenmod on my HTC one M7 (international).
Thus I unlocked my bootloader, rooted, and installed Cyanogenmod. It was a very new old version (10.2 or something), but I still liked it more than Sense.
Fast forward to last week, when someone gave me a Chromecast, which did not work with my phone because of a lack of Google services.
Since then I have been trying to figure out how to update my phone in order to install a newer rom on it, because it cannot install Cyanogenmod 11.x.
I think it has to do with my very old firmware (1.44.0000).
The first problem that I run in to is that abd does not detect the M7.
I first tried on a Windows 8.1 PC, but like others that did not work. On a Windows 7 PC it does get detected, with Android 1.0 drivers, but it still does not show up in adb (using the command "adb devices").
There are a lot of threads about phones not being detected, but I cannot find one where a phone does get detected in Windows with Android 1.0 drivers, but not in adb.
My second problem is with what it is exactly that I need to do in order to install a much newer Rom.
This is what I think I need to do, is it correct?
Step 1, install an old rom that works with the old firmware (I can do this without adb, using a USB OTG tranfer cable)
Step 2, get S-Off using Revone
Step 3, Install the newest Hboot using adb (to do this my phone needs to be detected)
Step 4, Install the new rom
Thanks for your help,
Sahrum
Click to expand...
Click to collapse
everything you need is already explained in the FAQ sticky thread.

Related

[Q] At wits end!! Please Help.

OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.

[Q] AT&T HTC One COMPLETELY wiped...

a friend of mine went out and got the HTC One, we rooted it and put on a nightly of CM 10.2 - and the phone worked relatively well, very well in fact, except the MMS/Group messaging was causing the phone to lockup and reboot. we've had a group message going on for an eternity involving a few of our friends, so many times a day this would happen.
not knowing what to do, i suggested he download a new rom, the stable or the latest nightly, and erase everything, and reinstall. somewhere in the process he erased everything - including the new rom, the phone is completely blank and in a boot loop. we can boot into fastboot or into the recovery.
and, we are Mac guys, except for an older Vista laptop i have. (to give you an idea on it's age, it has a 25gb hdd).
when we had first rooted it, i used MTP to copy the new rom over to the phone. the stock rom was still in place, the xfer went fine. but now there's no rom on the device, MTP doesn't work, the computer sees it as a 'One' but has no driver, and i'm at a bit of a loss.
i have tried to install the HTC SyncManager to get the phone to connect to my Vista machine with no luck, every time i connect Windows tries to look for a driver and it fails. somewhere in the forums i found a 'universal driver kit' which said it covered the HTC One (called it a Google Nexus Device, but recognized it at least).
however, my admittedly weak knowledge of fastboot and adb has proven not enough to get a new rom on the phone. i don't know if it's drivers or my lacking skillset, and i'd love any suggestions on taking a completely wiped HTC One with Koush's CWM on it, and getting a rom on it.
thanks.
dorf71 said:
a friend of mine went out and got the HTC One, we rooted it and put on a nightly of CM 10.2 - and the phone worked relatively well, very well in fact, except the MMS/Group messaging was causing the phone to lockup and reboot. we've had a group message going on for an eternity involving a few of our friends, so many times a day this would happen.
not knowing what to do, i suggested he download a new rom, the stable or the latest nightly, and erase everything, and reinstall. somewhere in the process he erased everything - including the new rom, the phone is completely blank and in a boot loop. we can boot into fastboot or into the recovery.
and, we are Mac guys, except for an older Vista laptop i have. (to give you an idea on it's age, it has a 25gb hdd).
when we had first rooted it, i used MTP to copy the new rom over to the phone. the stock rom was still in place, the xfer went fine. but now there's no rom on the device, MTP doesn't work, the computer sees it as a 'One' but has no driver, and i'm at a bit of a loss.
i have tried to install the HTC SyncManager to get the phone to connect to my Vista machine with no luck, every time i connect Windows tries to look for a driver and it fails. somewhere in the forums i found a 'universal driver kit' which said it covered the HTC One (called it a Google Nexus Device, but recognized it at least).
however, my admittedly weak knowledge of fastboot and adb has proven not enough to get a new rom on the phone. i don't know if it's drivers or my lacking skillset, and i'd love any suggestions on taking a completely wiped HTC One with Koush's CWM on it, and getting a rom on it.
thanks.
Click to expand...
Click to collapse
1. Download Parallels Desktop for Mac & a copy of Windows 7 x86 (torrents available)
2. Install Android SDK to Windows C drive (exactly to C:/)
3. Download the AT&T RUU here to C:/. (The RUU is an .exe you run with the phone connected to pc in recovery to flash it.) Note: you may run into errors once or twice flashing it, but keep trying and it should eventually work.
4. Connect phone to pc and boot into recovery
5. Run the RUU you downloaded
6. After you finish the flash, reboot your phone if it doesn't automatically.
7. Your phone should now have stock AT&T running.
I hope this helps. -Mike

[Q] HTC One Stock Rooted De-Odex 3.22.1540.1 - HTC Sync and ADB failures

I have been perusing the forums for years, never needed to join til now. I have rooted, and added custom roms to, a Backflip, Galaxy S, SII Skyrocket, and have never ran into the issues that I have with this lovely HTC One.
Last night I made a serious boo-boo, but recovered from it. I switched recoveries from CWM to twrp to allow for a downgrade to get s-off, and ended up wiping system clean. I made my way through adb, and recovered it after a few failed attempts. Thank goodness for dual boot, as Windows 8.1 doesn't recognize the One in recovery/bootloader mode. Windows 7 saved me.
After everything was said and done, phone is running great, minus the excess MTP icons when connected to PC. However, HTC Sync will not connect, it sees the phone but does not actually connect, and yes the options are set to connect. Along with the ADB interface drops for no apparent reason. I can be in adb shell, and it will just drop like I removed the phone, while I never touched it. It also drops connection using Droid Explorer. For the life of me I can not figure out what the issue is.
Any assistance would be great, I really do not want to reload the rom again.
Okay, so did I place this is the wrong spot? Or did I not include enough information? Using Scott's Rom De-Odex 3.22.1540.1 I get all the pretty little MTP icons on my status bar, but Sync Manager can not see phone in Windows 7, nor Windows 8.1.
Thanks for the help..
Having a similar problem, I am running the same ROM and got my device S-OFF but after rebooting ADB will not see the device. HTC Sync Manager will run and see the device but ADB does not so now I cant get super CID and flash any RUU's. Any help greatly appreciated.
SOLVED:
Fastboot still worked so I was able to SuperCID and flash RUU.

[Q] Trying to gain Root on M7 (AT&T) but wiped recovery and no fastboot!!

I've been looking for a while for a forum with someone who has my problem hoping to solve it on my own but i haven't found one so if this is a duplicate please post a link so i can do it! thank you!
As far as i know, this m7 has never had s-off because as long as i've had it i haven't been able to access fastboot. i bought it from swappa and it already had root and a custom rom. However a few months later i thought i was going to sell it so i flashed an RUU onto it and declined root. the sale fell through and i'm trying to put a custom rom on it again but i don't have a recovery anymore. it must have gotten wiped when i flashed the RUU? i declined root when i flashed it (because of the sale) and not having root OR a recovery OR access to fastboot i'm not sure what to do from here.
ADB works just fine, as far as i know. i DO have the fast boot option turned off within the os (which is the only thing that boots) i have Hboot 1.44 which should apparently be a BREEZE to get s-off and root with except neither I, or any of the apps, programs, one click root's i've tried have been able to access fastboot.
i HAVE tried multiple machines with multiple OS. (windows 8.1 and Ubuntu 14) i've tried multiple cables. i've tried usb 3.0 and usb 2.0. i've installed htc sync drivers on the windows machine. i've tried the 'naked' unsigned drivers that a few people have said made fastboot work for them but they never worked. although what confuses me most is i've never had a problem with ADB. adb reboot bootloader works for me no issue but as soon as i get into fastboot this device has never been recognized.
at this point i'm rrreeeaaalllyyy tempted to just trash it but i was hoping this phone would last me until the rest of the year so i could save up for the m9.
Thank you so much for your help!! I was as thorough as I could be with the details.. I hope it's enough.
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
shinji257 said:
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
Click to expand...
Click to collapse
i haven't had the option yet to try with windows 7 but i had hoped that Ubuntu would recognize it because all the problems i've heard from windows 8+ were with the usb drivers.. i will see if i can get my hands on a win 7 machine though.

A Hot Mess, Need Help - M7, S-On, Trouble with ADB

The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?

Categories

Resources