Hi,
I have a Sprint htc one that I had previously unlocked, rooted and installed twrp and cm10.1 on. I was trying to restore the factory rom and now I can't boot up. seams like i have deleted all OS'. I can open the bootloader and twrp. I can not find any zip in twrp to reinstall cm10 just to get the phone working again. I have tried the adb function in twrp but it keeps failing. i have also tried to install the RUU file but can not get it to work. it states that my device has 1.31.651.2 and the RUU I'm trying to use is 1.29.651.7. Is there somewhere I can download the 1.31.651.2 image version. Or is there another way to unbrick my phone.
help
Now I cannot get into TWRP.
Can you get into bootloader?
wondernad said:
Now I cannot get into TWRP.
Click to expand...
Click to collapse
1) Get into bootloader (Power and volume down)
2) go to fastboot
3) Copy the recovery you want to the directory you use for abd and rename it recovery.zip
4) fastboot flash recovery recovery.zip
5) Run fastboot erase cache
6) Then open recovery
7) Go to sideload and sideload a ROM you want. Make sure that is for SPRINT HTC ONE
8) Reboot and good luck
imurg said:
1) Get into bootloader (Power and volume down)
2) go to fastboot
3) Copy the recovery you want to the directory you use for abd and rename it recovery.zip
4) fastboot flash recovery recovery.zip
5) Run fastboot erase cache
6) Then open recovery
7) Go to sideload and sideload a ROM you want. Make sure that is for SPRINT HTC ONE
8) Reboot and good luck
Click to expand...
Click to collapse
Ok so im in fastboot. Is the recovery the 1.31.651.2ruu? or should it be twrp or the like?
wondernad said:
Ok so im in fastboot. Is the recovery the 1.31.651.2ruu? or should it be twrp or the like?
Click to expand...
Click to collapse
Get your recovery here
http://www.teamw.in/project/twrp2/171
After that you should be able to get to sideload in advanced
sideload
how long should the sideload take?
wondernad said:
how long should the sideload take?
Click to expand...
Click to collapse
It takes a while depending on how big the ROM is. Buy you can see the advance in the % dont worry it'll get there
Patience... is it grasshopper?
imurg said:
It takes a while depending on how big the ROM is. Buy you can see the advance in the % dont worry it'll get there
Patience... is it grasshopper?
Click to expand...
Click to collapse
It doesn't give me a %. I'm wondering if its recognizing my device. I do cmd adb devices and it doesn't show the phone. but the phone says it is waiting for package. I've tried it on my desktop(xp but runs ok) and my laptop(windows 7, but slow).
wondernad said:
It doesn't give me a %. I'm wondering if its recognizing my device. I do cmd adb devices and it doesn't show the phone. but the phone says it is waiting for package. I've tried it on my desktop(xp but runs ok) and my laptop(windows 7, but slow).
Click to expand...
Click to collapse
It doesn't seem to recognize the phone. Do you have the latest HTC SYNC Manager? it has the drivers
imurg said:
It doesn't seem to recognize the phone. Do you have the latest HTC SYNC Manager? it has the drivers
Click to expand...
Click to collapse
Yes I did reinstall the drivers. trying to update my android sdk right now.
wondernad said:
Yes I did reinstall the drivers. trying to update my android sdk right now.
Click to expand...
Click to collapse
Just run "adb version" latest is 1.0.31
imurg said:
Just run "adb version" latest is 1.0.31
Click to expand...
Click to collapse
That seams to open a command window for about a millisecond.
wondernad said:
That seams to open a command window for about a millisecond.
Click to expand...
Click to collapse
You need to open a command window. Double click command prompt (The black icon with the c:\_)
imurg said:
You need to open a command window. Double click command prompt (The black icon with the c:\_)
Click to expand...
Click to collapse
ok it is the latest version
wondernad said:
ok it is the latest version
Click to expand...
Click to collapse
Now do not close the command window and try adb devices
If you see your device then try the sideload again without closing the command window until you are finished.
imurg said:
Now do not close the command window and try adb devices
If you see your device then try the sideload again without closing the command window until you are finished.
Click to expand...
Click to collapse
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
wondernad said:
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
Click to expand...
Click to collapse
Still not seeing the device. I've tried switching versions of twrp and twrp sideload keeps saying failure. so I put CWM on it and it is opening sideload but the device is not recognized by the computer.
wondernad said:
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
Click to expand...
Click to collapse
I think the safest at this point where FASTBOOT recognizes your devices but ADB doesn't is to go back to stock flashing a RUU this only requires FASTBOOT.
This thread will show you how
http://forum.xda-developers.com/showthread.php?t=2251800
Best of lucks
imurg said:
I think the safest at this point where FASTBOOT recognizes your devices but ADB doesn't is to go back to stock flashing a RUU this only requires FASTBOOT.
This thread will show you how
http://forum.xda-developers.com/showthread.php?t=2251800
Best of lucks
Click to expand...
Click to collapse
That isn't working either. the only RUU file I can find is for 1.29.651.10RUU instead of the 1.31.651.2RUU. I have tried running it anyway hoping to limp it back to life but it won't take it. I really need the 1.31.651.2RUU. but can't find it.
http://forum.xda-developers.com/showthread.php?t=2391161&page=4
chack this
Related
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
chamo311 said:
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
Click to expand...
Click to collapse
did you install the correct version for the htc one sprint(wls)(spr)
Aldo101t said:
did you install the correct version for the htc one sprint(wls)(spr)
Click to expand...
Click to collapse
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
chamo311 said:
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
Click to expand...
Click to collapse
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Kraizk said:
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Click to expand...
Click to collapse
That sucks! So should I do try adb fastboot or go back to the previous version (2.5)?
What sucks is that without 2.6 working properly, I won't be able to flash any ROM with the new android version (4.2)
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Did the ADB and still the same problem. Should I go back to previous version of TWRP?
chamo311 said:
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Click to expand...
Click to collapse
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Aldo101t said:
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Click to expand...
Click to collapse
It is broken, several users are reporting it in the original TWRP post as well
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
Now that's some "good news" LOL! because I thought I screwed my phone and I wasn't going to be happy about it. I went back to v2.5 and everything works great!!
Thank you so much for all your help, guys!
Bless!!:good:
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
that could be, thanks for the heads up
STUCK in TWRP Recovery
Aldo101t said:
that could be, thanks for the heads up
Click to expand...
Click to collapse
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
just revert back to 2.5.0.0 and you are good to go
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you just recently update your firmware to the new base? The reason I ask is because after I did I used the the firmware with the bootloader and recovery included. I had reflashed TWRP 2.5. Well I noticed that the method of holding down volume key and and power button would not work for me at all whether I was in the os, bootloader or recovery. So I flashed the Rom I was on again and it fixed it. So I am wondering this is what is happening to you. Maybe just let the phone lose charge then plug it in reboot to the os then into bootloader and flash the 2.5 TWRP recovery. Only thing I can think of your not bricked
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you try holding the phone under a bright light then holding power and vol down to reboot. This works sometimes
Sent from my jacked HTC One!!
Aldo101t said:
just revert back to 2.5.0.0 and you are good to go
Click to expand...
Click to collapse
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
mzel said:
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
Click to expand...
Click to collapse
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Aldo101t said:
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Click to expand...
Click to collapse
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
mzel said:
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
Click to expand...
Click to collapse
that error is nothing don't worry about it, if you install a custom rom(make sure it's for sprint)that will go
Ok guys I went to wipe my htc one using twrp and I accidently wiped my internal storage so there nothing on my device to boot up I can get into twrp but I dont have any zips on there to flash I also tried to sideload but adb wont recognize my device which is weird because fastboot works fine I went to bestbuy Walmart radioshack to by an otg cable and try it with flash drive but no one has one so I ordered one from ebay but it will take a week to get it can someone please help with any other sugestions please pleasee I need my phone back
You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.
SaHiLzZ said:
You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.
Click to expand...
Click to collapse
What will switching recoverys do?
Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?
Novasunshine said:
Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?
Click to expand...
Click to collapse
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4
maxtcee said:
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4
Click to expand...
Click to collapse
Try it in recovery and also check to see if the device is being detached while in recovery by typing in "adb devices" in the command prompt.
Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing
maxtcee said:
Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing
Click to expand...
Click to collapse
So when you type in "adb devices" while in recovery it shows nothing? No device attached? Also what version of windows are you on?
Yea it shows nothing I'm using windows vista
maxtcee said:
Yea it shows nothing I'm using windows vista
Click to expand...
Click to collapse
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still
Novasunshine said:
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still
Click to expand...
Click to collapse
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude
maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
Click to expand...
Click to collapse
Takes about 1 - 5 minutes depending on rom size also adb wont say anything till its finished
---------- Post added at 05:21 AM ---------- Previous post was at 05:16 AM ----------
maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude
Click to expand...
Click to collapse
Your welcome glad its working finally
Hey,
I just S-OFF'ed my phone with Firewater (http://forum.xda-developers.com/showthread.php?t=2632351)
Anyyone got a link for me with how i can remove the red text?
I've HBOOT 1.54.0000
killerbie said:
Hey,
I just S-OFF'ed my phone with Firewater (http://forum.xda-developers.com/showthread.php?t=2632351)
Anyyone got a link for me with how i can remove the red text?
I've HBOOT 1.54.0000
Click to expand...
Click to collapse
flash custom firmware (without red text)
kamilmirza said:
flash custom firmware (without red text)
Click to expand...
Click to collapse
Where can I find that, please?
thx
ps: so I falsh custom firmware, then recovery again, than my rom again. Or am i wrong?
killerbie said:
Where can I find that, please?
thx
ps: so I falsh custom firmware, then recovery again, than my rom again. Or am i wrong?
Click to expand...
Click to collapse
please use search before posting
check THIS or THIS or THIS(dark bootloader)
no need to flash recovery or ROM after updating firmware
Got another problem.
When the phone is on, I can give commands via the command prompt (reboot etc works)
When in bootloader it always says 'waiting for device"
I've already relocked the bootloader to install the firmware
killerbie said:
Got another problem.
When the phone is on, I can give commands via the command prompt (reboot etc works)
When in bootloader it always says 'waiting for device"
I've already relocked the bootloader to install the firmware
Click to expand...
Click to collapse
uninstall HTC Sync with drivers, restart PC
download and install these DRIVERS
try again
kamilmirza said:
uninstall HTC Sync with drivers, restart PC
download and install these DRIVERS
try again
Click to expand...
Click to collapse
I get this in command prompt:
c:\adb>adb devices
List of devices attached
FA35MW903859 device
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
< waiting for device >
-> after reboot I do get a windows message saying devices not recognised, wierd. when the phone is on i can get an adb connection, but not in bootloader
EDIT: when the phone is in bootloader I find an unknown usb device in device manager, i'm going to install those drivers manully there.
(this ones http://www.sendspace.com/file/j26i6g)
killerbie said:
I get this in command prompt:
c:\adb>adb devices
List of devices attached
FA35MW903859 device
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
< waiting for device >
-> after reboot I do get a windows message saying devices not recognised, wierd. when the phone is on i can get an adb connection, but not in bootloader
EDIT: when the phone is in bootloader I find an unknown usb device in device manager, i'm going to install those drivers manully there.
(this ones http://www.sendspace.com/file/j26i6g)
Click to expand...
Click to collapse
boot into bootloader 1st
choose fastboot in the bootloader
then use all the fastboot comands in command prompt - it should work
eg. c:\adb\fastboot devices
BIGMOH said:
boot into bootloader 1st
choose fastboot in the bootloader
then use all the fastboot comands in command prompt - it should work
eg. c:\adb\fastboot devices
Click to expand...
Click to collapse
Still doesnt' work. My pc revognises the phone only when its IN android I think :/
Is it possible to flash the firmware.zip via adb sideload? or recovery? or just when android is on? in those cases adb works
killerbie said:
Still doesnt' work. My pc revognises the phone only when its IN android I think :/
Is it possible to flash the firmware.zip via adb sideload? or recovery? or just when android is on? in those cases adb works
Click to expand...
Click to collapse
By any chance are you using Windows 8.1?
killerbie said:
I get this in command prompt:
c:\adb>adb devices
List of devices attached
FA35MW903859 device
c:\adb>adb reboot bootloader
c:\adb>fastboot reboot-bootloader
< waiting for device >
-> after reboot I do get a windows message saying devices not recognised, wierd. when the phone is on i can get an adb connection, but not in bootloader
EDIT: when the phone is in bootloader I find an unknown usb device in device manager, i'm going to install those drivers manully there.
(this ones http://www.sendspace.com/file/j26i6g)
Click to expand...
Click to collapse
BIGMOH said:
By any chance are you using Windows 8.1?
Click to expand...
Click to collapse
seems like Windows 8.1
Sent from my One using Tapatalk
kamilmirza said:
seems like Windows 8.1
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Yep, Windows 8.1. I'm going to try get my hands on a windows 7 machine this evening
Ok I was trying to update my trwp to 2.6.3.3 on my HTC one so I could install the new Viper One Rom. I located the img file in flashify hit flash. It said it was flashed and booted into recovery then it was stuck. Was able to restart my phone but now when I try to go into recovery it gets stuck. How do I fix this. Is there a way to fix this. should I unroot the phone or what I'm lost on what to do. Any suggestions would be appreciated.
Sent from my HTCONE using XDA Premium 4 mobile app
The newest version of TWRP does not work with the Sprint HTC One
Sent from my HTCONE using xda app-developers app
Ok so how do I at least get 2.6.3.0 back should I use goo manager to reinstall it. And how can HTC one users install the new roms. I've been using a 4.1 Rom for two long.
Sent from my HTCONE using XDA Premium 4 mobile app
whitetiger2429 said:
Ok so how do I at least get 2.6.3.0 back should I use goo manager to reinstall it. And how can HTC one users install the new roms. I've been using a 4.1 Rom for two long.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Per TWRP Page ( http://teamw.in/project/twrp2/171 )
Download: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img and copy it to the folder that you have fastboot.exe located.
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
Reboot and you should have TWRP custom recovery.
weidnerj said:
Per TWRP Page ( http://teamw.in/project/twrp2/171 )
Download: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img and copy it to the folder that you have fastboot.exe located.
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
Then type
fastboot erase cache
Reboot and you should have TWRP custom recovery.
Click to expand...
Click to collapse
Fixed
GooManager from the playstore is the best to keep your recovery updated. it knows what recovery to install for you.
BD619 said:
Fixed
Click to expand...
Click to collapse
Ok I tried that and it doesn't work, when I bring up the command prompt and type that in it tells me its not recognized, Im pretty sure I have the right drivers installed, ive gone into device manager and it says its up to date, adb is set up right. Not sure whats going. I did use a toolkit to root it.
whitetiger2429 said:
Ok I tried that and it doesn't work, when I bring up the command prompt and type that in it tells me its not recognized, Im pretty sure I have the right drivers installed, ive gone into device manager and it says its up to date, adb is set up right. Not sure whats going. I did use a toolkit to root it.
Click to expand...
Click to collapse
Uninstall everything HTC form your PC
Unplug phone
Reboot your PC
Install these drivers http://d-h.st/FXC
Plug phone in and let the drivers install
Go back to Device Manager and do this to install correctly
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
BD619 said:
Uninstall everything HTC form your PC
Unplug phone
Reboot your PC
Install these drivers http://d-h.st/FXC
Plug phone in and let the drivers install
Go back to Device Manager and do this to install correctly
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Ok ill try that im running with windows 8
whitetiger2429 said:
Ok ill try that im running with windows 8
Click to expand...
Click to collapse
The phone is not saying fastboot usb. just fastboot when I plug it in.
whitetiger2429 said:
The phone is not saying fastboot usb. just fastboot when I plug it in.
Click to expand...
Click to collapse
Did you press power to select?
BD619 said:
Uninstall everything HTC form your PC
Unplug phone
Reboot your PC
Install these drivers http://d-h.st/FXC
Plug phone in and let the drivers install
Go back to Device Manager and do this to install correctly
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Ok fastboot usb came but it seems to be stuck on waiting on device in Cmd
whitetiger2429 said:
Ok fastboot usb came but it seems to be stuck on waiting on device in Cmd
Click to expand...
Click to collapse
Try rebooting your bootloader
BD619 said:
Did you press power to select?
Click to expand...
Click to collapse
Yes and it went into fastboot usb once I hit down on the vol key
BD619 said:
Try rebooting your bootloader
Click to expand...
Click to collapse
ok I rebooted the bootloader, should I re do it now
whitetiger2429 said:
ok I rebooted the bootloader, should I re do it now
Click to expand...
Click to collapse
Flash twrp 2.6.3.0
fastboot flash recovery nameofrecovery.img
fastboot erase cache
BD619 said:
Flash twrp 2.6.3.0
fastboot flash recovery nameofrecovery.img
fastboot erase cache
Click to expand...
Click to collapse
Ok did everything you told me but im still getting waiting on device
Check PM
BD619 said:
Flash twrp 2.6.3.0
fastboot flash recovery nameofrecovery.img
fastboot erase cache
Click to expand...
Click to collapse
Ok did everything you told me but im still getting waiting on device
Do I need to have fastboot on on the phone. Of course that may be a dumb ?
whitetiger2429 said:
Ok did everything you told me but im still getting waiting on device
Do I need to have fastboot on on the phone. Of course that may be a dumb ?
Click to expand...
Click to collapse
It should say fastbootusb
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
See if you can flash a rom from your sd. hopefully you have something on there. Also see if you can see anything on fastboot since adb is not seeing anything
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
htcoveblue said:
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
Click to expand...
Click to collapse
Update your android SDK. Then try again.
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
I read the story, then at the end is your problem. well, part of it. you weren't using adb in the bootloader, it doesnt work there, ever. you were using fastboot, and you should've fastboot devices
That's encouraging. Any idea how to get past the system.img file is too large error?
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
Is your SDK updated?
My drivers are updated using the Google USB Drivers from this link: http://developer.android.com/sdk/win-usb.html
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
There is a different fast boot that you have to use called mfastboot.
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
The fastboot not being recognized can sometimes be a driver error. Is it recognized look through device manager and try uninstall then unplug USB and plug back in.
Also the android naked drivers might help. Give them a try. http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Sent from my Nexus 6 using Tapatalk
htcoveblue said:
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
Click to expand...
Click to collapse
Can you not use MTP from TWRP?
Jnewell05 said:
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
htcoveblue said:
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
Click to expand...
Click to collapse
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Evolution_Tech said:
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Click to expand...
Click to collapse
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
htcoveblue said:
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
Click to expand...
Click to collapse
No problem. I've run this and as long as you follow the installation instructions precisely, it is very stable and capable of being a daily driver.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
There's another flashable here:
http://forum.xda-developers.com/showthread.php?t=3066052
I haven't run this one but it seems to be getting good reviews.