Tried to update TWRP 2.6.3.3. with flashify to latest. Got into recovery, didnt see anything happening, so we rebooted.
But it didnt reboot. Went to black screen. Can not get into recovery. Tried to access via adb and whatever command I send, all I get is < waiting for device >
it seems my phone is not even being seen with ADB, as the same < waiting for device > comes up when the phone is not connected or error: device not found
bocadave said:
Tried to update TWRP 2.6.3.3. with flashify to latest. Got into recovery, didnt see anything happening, so we rebooted.
But it didnt reboot. Went to black screen. Can not get into recovery. Tried to access via adb and whatever command I send, all I get is < waiting for device >
it seems my phone is not even being seen with ADB, as the same < waiting for device > comes up when the phone is not connected or error: device not found
Click to expand...
Click to collapse
adb only works when recovery is loaded
do you remember what the file you installed was
and can you get to the bootloader / fastboot
>>>>> do you remember what the file you installed was
The latest TWRP
>>>>>>>and can you get to the bootloader / fastboot
No
./fastboot reboot-bootloader
< waiting for device >
bocadave said:
>>>>> do you remember what the file you installed was
The latest TWRP
>>>>>>>and can you get to the bootloader / fastboot
No
./fastboot reboot-bootloader
< waiting for device >
Click to expand...
Click to collapse
hold volume up plus power for 20 seconds
then volume down + power to get to the bootloader
when you get to the bootloader / fastboot usb
flash the custom recovery with fastboot
clsA said:
hold volume up plus power for 20 seconds
then volume down + power to get to the bootloader
Click to expand...
Click to collapse
tried that, Nothing
bocadave said:
tried that, Nothing
Click to expand...
Click to collapse
what happens when you plug it into a PC what driver does it try and load
clsA said:
what happens when you plug it into a PC what driver does it try and load
Click to expand...
Click to collapse
QHSUSB
bocadave said:
QHSUSB
Click to expand...
Click to collapse
yeah your bricked
go here >> http://forum.xda-developers.com/showthread.php?t=2770684
I saw that you made a fix already-- do u have a linux install?
bocadave said:
I saw that you made a fix already-- do u have a linux install?
Click to expand...
Click to collapse
No i used a 32bit Ubuntu flash drive
clsA said:
No i used a 32bit Ubuntu flash drive
Click to expand...
Click to collapse
Dexter says " download the appropriate package for the device."
I didnt see that there. What does he mean ?
How do I do 32bit Ubuntu flash drive?
bocadave said:
Dexter says " download the appropriate package for the device."
I didnt see that there. What does he mean ?
How do I do 32bit Ubuntu flash drive?
Click to expand...
Click to collapse
I used these ubuntu-13.10-desktop-i386.iso
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
more help here >> http://forum.xda-developers.com/showthread.php?t=2606577
The unbrick files are here >> http://d-h.st/GS9
ok.. trying now.
Damn win7 wont boot into usb.
bocadave said:
ok.. trying now.
Damn win7 wont boot into usb.
Click to expand...
Click to collapse
sure it will, you have to bring up the boot menu when you boot the PC, it's usually f12 or f10, it will say it on the first boot screen
clsA said:
sure it will, you have to bring up the boot menu when you boot the PC, it's usually f12 or f10, it will say it on the first boot screen
Click to expand...
Click to collapse
Crap PC-- no option to boot from USB drive in bios
made a linux bootup dvd--
put phone in 4 usb ports.
device not found.....
can't believe updating the TWRP would fry my phone
bocadave said:
made a linux bootup dvd--
put phone in 4 usb ports.
device not found.....
can't believe updating the TWRP would fry my phone
Click to expand...
Click to collapse
Well the thing with Flashify is it uses your build.prop to determine what recovery to install
If you had a custom rom that changed the build prop to an M8 your recovery would be over written with the wrong size files
clsA said:
Well the thing with Flashify is it uses your build.prop to determine what recovery to install
If you had a custom rom that changed the build prop to an M8 your recovery would be over written with the wrong size files
Click to expand...
Click to collapse
so any other solutions besides
JTAG-
Send to HTC
bocadave said:
so any other solutions besides
JTAG-
Send to HTC
Click to expand...
Click to collapse
Well if windows see's the phone in QHSUSB you should be able to detect it in linux
lets ask @Danny201281
clsA said:
Well if windows see's the phone in QHSUSB you should be able to detect it in linux
lets ask @Danny201281
Click to expand...
Click to collapse
thats what bothered me, that it was seeable in Win7
Who is Danny, and how do we ask him?
Related
ok here is what i have done
rooted and cwm after unlocking boot loader then installed arhd 3.5
relocked bootloader to return to stock then tried to flash the rru file but it wouldnt work phone wouldnt boot so unlocked bootloader again but now stuck on start up screen
is it fixable or have i broken it altogether ??
thanks
can you get into recovery?
MacHackz said:
can you get into recovery?
Click to expand...
Click to collapse
yes i can get to cwm recovery but i have no file to flash as i deleted it after it installed correctly also my cwm backup is on my hdd as well
First wrong sector to post
Second download the All In One Toolkit and push your .zip via adb to your phone
m3dd0g said:
First wrong sector to post
Second download the All In One Toolkit and push your .zip via adb to your phone
Click to expand...
Click to collapse
ohh ok i didnt know ...where should i post
tried to do that says device not found ........but when i use normal fastboot devices command it shows a serial number
grud1e said:
ohh ok i didnt know ...where should i post
tried to do that says device not found ........but when i use normal fastboot devices command it shows a serial number
Click to expand...
Click to collapse
Go to cwm, press install zip from sideload, then on your pc type 'adb sideload <filename of update.zip>'
MacHackz said:
Go to cwm, press install zip from sideload, then on your pc type 'adb sideload <filename of update.zip>'
Click to expand...
Click to collapse
thanks i tried that and i just get a load of text showing in the cmd box but nothing happens text show various adb commands but funnily enough shows no sideload command ??
grud1e said:
thanks i tried that and i just get a load of text showing in the cmd box but nothing happens text show various adb commands but funnily enough shows no sideload command ??
Click to expand...
Click to collapse
Can you post a screenshot, or host a meeting on TeamViewer so I can see/help?
MacHackz said:
Can you post a screenshot, or host a meeting on TeamViewer so I can see/help?
Click to expand...
Click to collapse
yes i can dl team viewer and host a meeting ....you prefer mac or windows
grud1e said:
yes i can dl team viewer and host a meeting ....you prefer mac or windows
Click to expand...
Click to collapse
Mac is best, just PM me or whatever with the meeting code
MacHackz said:
Mac is best, just PM me or whatever with the meeting code
Click to expand...
Click to collapse
aye mac is best just plugged it into another usb and its side loading right now so hopefully it will be ok perhaps it dont like usb 3 for some reason
i will let you know how it goes
thanks
grud1e said:
aye mac is best just plugged it into another usb and its side loading right now so hopefully it will be ok perhaps it dont like usb 3 for some reason
i will let you know how it goes
thanks
Click to expand...
Click to collapse
Good news sometimes USB ports play up, I have a bad history with them. Once one malfunctioned during a re-partition of my old Galaxy S2 and bricked it -.-
PHEW
MacHackz said:
Good news sometimes USB ports play up, I have a bad history with them. Once one malfunctioned during a re-partition of my old Galaxy S2 and bricked it -.-
Click to expand...
Click to collapse
yippee not bricked returned to working ...thanks for you help
grud1e said:
yippee not bricked returned to working ...thanks for you help
Click to expand...
Click to collapse
Great enjoy
Moved to Q&A for you. Remember, all questions go in Q&A and never in development.
So have you managed to return it to stock after?
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
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
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
What happens when u choose reboot in fastboot mode in the bootloader??
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
Can you reboot into recovery again and enter to fastboot mode?
Can go between fast boot and the Bootloader menu but if I hit reboot, it just comes back to Bootloader. If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
cknuth said:
If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
Click to expand...
Click to collapse
fastboot erase cache
nkk71 said:
fastboot erase cache
Click to expand...
Click to collapse
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
cknuth said:
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
Click to expand...
Click to collapse
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
nkk71 said:
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
Click to expand...
Click to collapse
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
cknuth said:
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
Click to expand...
Click to collapse
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
nkk71 said:
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
Click to expand...
Click to collapse
ok so the guide walks me up to the point of installing fastboot for unbuntu using a couple cmd lines but for my specific situation will I need any files saved in specific locations? I have never used Ubuntu or Linux before so youll have to bear with me.
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
cknuth said:
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
Click to expand...
Click to collapse
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
nkk71 said:
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
cknuth said:
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
Click to expand...
Click to collapse
doesn't sound like a brick at all, as long a hboot (ie bootloader is fine) no brick should be involved.
but i have to call it a night, hopefully someone will be along shortly, and take over... (timezones ) take it ease, DO NOT PANIC, DO NOT RUSH things!!
Cool, all your help is greatly appreciated. So I should hold off on the trip to the phone store?
Any other ideas to get communication to the phone?
Different Computer, USB Port, and USB Cable. Without saying FASTBOOT USB on the phone, can't do anything.
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?
Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2
lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.
Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.
lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.
Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.
lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.