Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.
Related
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.
I have multiple problems so read on.
A couple weeks ago the computer stopped recognizing my verizon gnex that was rooted, unlocked and running jbsourcery 5.1 that it previously had no problems seeing. It still charges via wall and usb with original m-usb cable. I've tried numerous times to re-install the samsung driver on the computer with wug's toolkit with no luck. I've tried another samsung m-usb cable...no luck. My computer is new so no problems with usb ports (I've tried all of them) and have tried the ver 2.0 port. USB debugging is on and fastcharge is off.
My second and worst problem:
Yesterday in a fit of stupidity I restored one of my original backups ( I believe made with CWM recovery ) that turned out to be a stock. img and after restoring it OTA updated to stock JB. All my other backups were done with TWRP and it's no longer present on the phone. I tried installing BootUnlocker from play store but it says I have no root access and the phone won't flash either recovery so I'm stuck with only Fastboot ver. 9 that only wants to flash something from adb. I've exhausted my knowledge and eyes are crossed from reading forums.
I don't know if I can use something like Terminal Emulator for this or even how to use it.
If you know enough to see that I'm totally screwed...Please tell me! (I'm a big boy)
If you think you have a solution...You are a god!
If you need more info...I can provide it
earbuster said:
I have multiple problems so read on.
A couple weeks ago the computer stopped recognizing my verizon gnex that was rooted, unlocked and running jbsourcery 5.1 that it previously had no problems seeing. It still charges via wall and usb with original m-usb cable. I've tried numerous times to re-install the samsung driver on the computer with wug's toolkit with no luck. I've tried another samsung m-usb cable...no luck. My computer is new so no problems with usb ports (I've tried all of them) and have tried the ver 2.0 port. USB debugging is on and fastcharge is off.
My second and worst problem:
Yesterday in a fit of stupidity I restored one of my original backups ( I believe made with CWM recovery ) that turned out to be a stock. img and after restoring it OTA updated to stock JB. All my other backups were done with TWRP and it's no longer present on the phone. I tried installing BootUnlocker from play store but it says I have no root access and the phone won't flash either recovery so I'm stuck with only Fastboot ver. 9 that only wants to flash something from adb. I've exhausted my knowledge and eyes are crossed from reading forums.
I don't know if I can use something like Terminal Emulator for this or even how to use it.
If you know enough to see that I'm totally screwed...Please tell me! (I'm a big boy)
If you think you have a solution...You are a god!
If you need more info...I can provide it
Click to expand...
Click to collapse
wrong forum!
animaleyes76 said:
wrong forum!
Click to expand...
Click to collapse
Yeah...Sorry ...I moved it already
Hi, I have a rooted HTC One running the Google Play Edition ROM (first rooted device) but I stupidly hit the 4.3 OTA update when I got the notification. Apparently this is a big no-no, but I didn't know any better and now my phone can't get past HTC's splash screen. I can still enter bootloader and recovery (CWM 6.0.3.2) but that's about it.
I don't have a ROM on the internal memory, so can't just revert to the previous 4.2.2 and because I can't enter the phone's settings to turn on USB Debugging. The phone does not show up in Windows Explorer, nor in 'adb devices' when I do the usual thing on Command Prompt. The phone shows up in Device Manager under Android USB Devices as 'My HTC' but again, no device will appear in Command Prompt, otherwise I'd adb push a new ROM onto the phone.
I've tried clearing cache, dalvik and so on with zero luck. It's causing me all sorts of grief and I've been pulling out my hair since yesterday. I've heard that an OTG micro-USB cable might help by loading a ROM onto a flash card, but I'm looking at a few days delivery (at least) and would like to get this problem sorted ASAP. If you can help, I'll name my firstborn after you.
Strand0410 said:
Hi, I have a rooted HTC One running the Google Play Edition ROM (first rooted device) but I stupidly hit the 4.3 OTA update when I got the notification. Apparently this is a big no-no, but I didn't know any better and now my phone can't get past HTC's splash screen. I can still enter bootloader and recovery (CWM 6.0.3.2) but that's about it.
I don't have a ROM on the internal memory, so can't just revert to the previous 4.2.2 and because I can't enter the phone's settings to turn on USB Debugging. The phone does not show up in Windows Explorer, nor in 'adb devices' when I do the usual thing on Command Prompt. The phone shows up in Device Manager under Android USB Devices as 'My HTC' but again, no device will appear in Command Prompt, otherwise I'd adb push a new ROM onto the phone.
I've tried clearing cache, dalvik and so on with zero luck. It's causing me all sorts of grief and I've been pulling out my hair since yesterday. I've heard that an OTG micro-USB cable might help by loading a ROM onto a flash card, but I'm looking at a few days delivery (at least) and would like to get this problem sorted ASAP. If you can help, I'll name my firstborn after you.
Click to expand...
Click to collapse
I think an RUU for your carrier will do the trick. There are a lot of RUU's posted in the HTC One forums in the various sections, search and find the one for your phone/carrier. Pretty sure that will do the trick!
dgtiii said:
I think an RUU for your carrier will do the trick. There are a lot of RUU's posted in the HTC One forums in the various sections, search and find the one for your phone/carrier. Pretty sure that will do the trick!
Click to expand...
Click to collapse
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Strand0410 said:
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Click to expand...
Click to collapse
Dude, have you a phone that won't get past the splash screen, and you're worried about losing data? If you could get a computer to see the phone, you could push a rom to it in ADB and then sideload it in recovery. If you can't, I think you're left with an RUU I'm afraid.
Strand0410 said:
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Click to expand...
Click to collapse
You can just root/unlock/s-off it after, you've come this far already so you should be familiar with the short process
Flash a ROM using an OTG cable if you have one.
AllAboutTheCore said:
Flash a ROM using an OTG cable if you have one.
Click to expand...
Click to collapse
Cheers for the info guys. I think I'll wait till Monday to buy an OTG cable, fingers crossed this will work. In hindsight, I should have kept some ROM on the phone memory or left debugging on. At least now I'll know not to do an OTA update on a rooted phone.
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?
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
AlkaliV2 said:
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
Click to expand...
Click to collapse
So, I've been on stock until I switched over to CM12. I do have a twrp backup but apparently only did that after I moved to CM12. I have only the most basic (read basically nonexistent) understanding of ADB, and can follow directions I find online but no real knowledge as to how anything works. I also did not use wugfresh, but unlocked via ADB and rooted via chainfire. Honestly, I followed most of the direction I found on youtube via a creator called wwjoshdo (I'd link but I'm not allowed).
Otherwise that feels like the info. I didn't fiddle with my nexus until I started have battery issues and then decided to unlock/root/flash, and that was about 6 weeks ago. I'm also running what standard apps for a rooted device on CM12, flashify, cyandelta, setcpu, and, Titanium Backup. Help?
llawhsoj said:
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
Click to expand...
Click to collapse
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
RMarkwald said:
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
Click to expand...
Click to collapse
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
llawhsoj said:
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
Click to expand...
Click to collapse
So this link will get you up and running with ADB (if it isn't already working): http://forums.team-nocturnal.com/index.php?/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10-updated-9-11-2015/
These are the most common commands that are used with ADB once you get it installed. Also, an excellent way to pull a log from the command prompt: http://developer.android.com/tools/help/shell.html
Assuming you can see the device once you pass the command, "adb devices" it means you are connected but the MTP driver hasn't been loaded properly. I had to fix this by cycling Android debugging and ADB notification in developer's option until Windows was like, "Hey! There it is!" Also, MTP works properly for me when booted into TWRP so if you desperately need to transfer a file you can do it from the TWRP recovery menu.
Noob Tip/Reminder: Make sure that when you plug it in the first time you change it from 'Charge Only' to MTP and if things still seem quirky reboot Windows. It's all just a game of getting it recognized at this point.