Related
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
cburch85 said:
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
Click to expand...
Click to collapse
donwload the all in one toolkit use it to erase cache then install recovery. after that either mount usb otg and copy rom to sd or sideload a rom. all in one toolkit automates everything you need to do:good::good:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
cburch85 said:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
Click to expand...
Click to collapse
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
skinsfanbdh said:
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
Click to expand...
Click to collapse
Thanks for getting me this far. Mounting didn't work, so I sideloaded rom. it is showing up on the phone as "sideload.zip" i try to run and it fails. Any ideas?
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Guich said:
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Click to expand...
Click to collapse
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
im guessing your using twrp but just select no dont root the rom is already rooted and it should boot. may take getting through a few aroma freezes but it will boot
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Guich said:
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Click to expand...
Click to collapse
OK, so I didn't say yes to the question this time after sideloading android revolution. same thing. goes blank then reboots to bootloader menu. So I tried sideloading viperrom 1.04. This time after it finished sideloading it randomly installed instelfl, and now viperrom is installed, its booting up to the phone now finally, yet before anything can initialize, it just reboots again. It's been caught in this boot loop about ten minutes now. No end in sight. Any ideas?
ViperRom from Sprint or AT&T one forum?
Your phone is branded or no-brand?
However, boot into recovery, and use this command:
Code:
adb push name_of_rom.zip /sdcard
, then flash it
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
cburch85 said:
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
Click to expand...
Click to collapse
Have you tried to flash the boot.img from fastboot?
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
cburch85 said:
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
Click to expand...
Click to collapse
Where did you find the RUU for sprint? I cant seem to find one that works with my CID: SPCS_001.
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
zach832 said:
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
Click to expand...
Click to collapse
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Can't detect SD Card
Guich said:
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Click to expand...
Click to collapse
Hi, I'm having sort of the same problem. My phone is stuck on a bootloop, I flashed a new recovery because the previous TWRP stopped working. When I try to wipe data/factory reset, It says that it can't detect E:\ or the SD Card. I can't even mount it. Any ideas? Please help. Thanks
Hello guys,
So i unlocked the bootloader, used TWRP recovery, made a nandroid back up, saved a copy of back up on my pc and then flash the Trickdroid rom. Every thing went smoothly till then, as the proximity sensor wasnt working, i installed the xposed framework then went into recovery and flashed the zip file for it. After the reboot, the phone hung on HTC one boot screen, i used the Vol down + power button but the phone is just not switching on in recovery or anything. Connected to my PC, gave adb reboot recovery but it says "device not found". Did the vol+power thing in light as well but didnt help.
What should i do? Please help.
coolboy2343 said:
Hello guys,
So i unlocked the bootloader, used TWRP recovery, made a nandroid back up, saved a copy of back up on my pc and then flash the Trickdroid rom. Every thing went smoothly till then, as the proximity sensor wasnt working, i installed the xposed framework then went into recovery and flashed the zip file for it. After the reboot, the phone hung on HTC one boot screen, i used the Vol down + power button but the phone is just not switching on in recovery or anything. Connected to my PC, gave adb reboot recovery but it says "device not found". Did the vol+power thing in light as well but didnt help.
What should i do? Please help.
Click to expand...
Click to collapse
check your pm
nflndu curtail
Thanks Bhavpreet,
Finally managed to get the piece of rock alive, connected it to PC and used fastboot reboot and then phone came alive. Wonder what went wrong that the phone got stuck at the boot screen.
coolboy2343 said:
Thanks Bhavpreet,
Finally managed to get the piece of rock alive, connected it to PC and used fastboot reboot and then phone came alive. Wonder what went wrong that the phone got stuck at the boot screen.
Click to expand...
Click to collapse
Can U share I have a similar problem, recovery bootloopes and sideload flash doesnt work
Pum4 said:
Can U share I have a similar problem, recovery bootloopes and sideload flash doesnt work
Click to expand...
Click to collapse
I now know the mistake i did, i flashed trick droid on my one and i was coming from stock 4.1.2. Developer had mentioned that for those coming from 4.1.2, we need to first wipe, install rom, do 1 boot cycle and then wipe again, i missed the last part hence got stuck at the boot screen.
I tried adb but it didnt work, so i used fastboot reboot command and the phone came alive, after which went to recovery and restored my nandroid. What happened to your device?
Boot into bootloader by turning off device and keeping volume down pressed, and then connect your device to your pc so you see "fastboot usb" in red, and then type "fastboot erase cache" followed by "fastboot reboot"
Sent from my HTC One using xda app-developers app
Bhavpreet said:
Boot into bootloader by turning off device and keeping volume down pressed, and then connect your device to your pc so you see "fastboot usb" in red, and then type "fastboot erase cache" followed by "fastboot reboot"
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I made a really amateur mistake. Installed a normal xposed version instead of the custom for One. Now I'm stuck on the boot screen. I can load bootloader and recovery. Tried using ur method and still stuck. Also cannot read internal memory and can't push xposed disabler.. All with no nandroid backup. Any helpful tips?
nkchii said:
I made a really amateur mistake. Installed a normal xposed version instead of the custom for One. Now I'm stuck on the boot screen. I can load bootloader and recovery. Tried using ur method and still stuck. Also cannot read internal memory and can't push xposed disabler.. All with no nandroid backup. Any helpful tips?
Click to expand...
Click to collapse
xposed is universal for all phones so it wasnt xposed maybe an xposed module that doesnt work on our phone
try moving everything from your sd to computer the format sd
nkchii said:
I made a really amateur mistake. Installed a normal xposed version instead of the custom for One. Now I'm stuck on the boot screen. I can load bootloader and recovery. Tried using ur method and still stuck. Also cannot read internal memory and can't push xposed disabler.. All with no nandroid backup. Any helpful tips?
Click to expand...
Click to collapse
If you dont have any nandroid backups then im afraid theres really nothing you can do besides factory reset..go into the bootloader and try reseting the phone, see if that works.
The reason your computer doesnt read your phone is normally a drivers issues. Heres what you can do to get your computer to notice your phone.
download the file from here and extract the whole FOLDER to your desktop: http://forum.xda-developers.com/showthread.php?t=1996051
1. boot into recovery
2. connect your phone to the computer
3. go to device manager, just search for it
4. In other devices, there should be something called android phone, open it, and choose update drivers
5. instead of letting the computer search for the drivers, choose the second option to choose your own
6. choose the folder, the whole folder, and your driver, and click install
Now your phone should be recognized by your computer, check by using adb devices in command. If it works, go from there, try pushing xposed disabler, or push a nandroid to your device and restore.
Heres a link to how to install the drivers if you didnt get my explanation: http://forum.xda-developers.com/showthread.php?t=2139767
List of RUU's and nandroids: http://forum.xda-developers.com/showthread.php?p=39588860
List to HTC drivers if you wanna try this before using the universal naked ones: http://forum.xda-developers.com/showthread.php?t=2191279
skinsfanbdh said:
xposed is universal for all phones so it wasnt xposed maybe an xposed module that doesnt work on our phone
try moving everything from your sd to computer the format sd
Click to expand...
Click to collapse
Can't mount usb storage... :crying: It's Icon Themer that I'm using. Used it a dozen times on my own HTC One and nothing went wrong. Used it once on friend's One and this happens.
nkchii said:
Can't mount usb storage... :crying: It's Icon Themer that I'm using. Used it a dozen times on my own HTC One and nothing went wrong. Used it once on friend's One and this happens.
Click to expand...
Click to collapse
when you select format sd does it give you errors?
skinsfanbdh said:
when you select format sd does it give you errors?
Click to expand...
Click to collapse
Not going to try that yet since I don't want to lose data until it's really impossible..
does it say 0mb internal storage
Bhavpreet said:
If you dont have any nandroid backups then im afraid theres really nothing you can do besides factory reset..go into the bootloader and try reseting the phone, see if that works.
The reason your computer doesnt read your phone is normally a drivers issues. Heres what you can do to get your computer to notice your phone.
download the file from here and extract the whole FOLDER to your desktop: http://forum.xda-developers.com/showthread.php?t=1996051
1. boot into recovery
2. connect your phone to the computer
3. go to device manager, just search for it
4. In other devices, there should be something called android phone, open it, and choose update drivers
5. instead of letting the computer search for the drivers, choose the second option to choose your own
6. choose the folder, the whole folder, and your driver, and click install
Now your phone should be recognized by your computer, check by using adb devices in command. If it works, go from there, try pushing xposed disabler, or push a nandroid to your device and restore.
Heres a link to how to install the drivers if you didnt get my explanation: http://forum.xda-developers.com/showthread.php?t=2139767
List of RUU's and nandroids: http://forum.xda-developers.com/showthread.php?p=39588860
List to HTC drivers if you wanna try this before using the universal naked ones: http://forum.xda-developers.com/showthread.php?t=2191279
Click to expand...
Click to collapse
Device Manager it's Android USB Device with My HTC driver. Removable Disk comes up under My Computer but can't open it. Says "Insert disk"
---------- Post added at 02:46 AM ---------- Previous post was at 02:42 AM ----------
skinsfanbdh said:
does it say 0mb internal storage
Click to expand...
Click to collapse
I'm using CWM.. Philz Touch 5 to be exact. Used Free Browse mode, I can still see the individual folders.. nothing else I can do tho
nkchii said:
Device Manager it's Android USB Device with My HTC driver. Removable Disk comes up under My Computer but can't open it. Says "Insert disk"
---------- Post added at 02:46 AM ---------- Previous post was at 02:42 AM ----------
I'm using CWM.. Philz Touch 5 to be exact. Used Free Browse mode, I can still see the individual folders.. nothing else I can do tho
Click to expand...
Click to collapse
do you have all in one toolkit?
skinsfanbdh said:
do you have all in one toolkit?
Click to expand...
Click to collapse
nope
nkchii said:
nope
Click to expand...
Click to collapse
you should download it and use erase cache option then reinstall recovery and see if that helps but i think you will probably end up having to format sd. if you have htc sync it might be able to get some of the stuff from sd before you format
nkchii said:
Device Manager it's Android USB Device with My HTC driver. Removable Disk comes up under My Computer but can't open it. Says "Insert disk"
---------- Post added at 02:46 AM ---------- Previous post was at 02:42 AM ----------
I'm using CWM.. Philz Touch 5 to be exact. Used Free Browse mode, I can still see the individual folders.. nothing else I can do tho
Click to expand...
Click to collapse
it seems like your computer recognizes your device then. Go into recovery, then from your computer type adb devices, does it show your device?
Bhavpreet said:
it seems like your computer recognizes your device then. Go into recovery, then from your computer type adb devices, does it show your device?
Click to expand...
Click to collapse
yes! for awhile it didn't. now it does
Had this same exact problem, AIO helped me , i had installed TWRP and the AIO opened recovery, then chose recovery and then tried side loading, while doing i then sideloaded the ARHD and voila am back to normal.
The problem and my question is , i flashed with bulletproof kernel and then that created all the problem. now somehow it has booted and i still have bulletproof kernel. Am scared to reboot (am a noob all over again since i bought wp) , if i flash it with a stock kernel deodexed or odexed will that create a problem? I have ARHD10.2 Stock ROM. Please advice.
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.
@rider5512 Sounds right to me. Thanks for clarifying.
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.
Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.
if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq
I was having a problem with not receiving calls, so I foolishly went into the internal sdcard and deleted everything and then used TWRP to wipe everything else with the intention of starting fresh on a new rom. I currently can boot into TWRP recovery. My computer can recoginize that there is a drive connected, but it is shaded out and says that there is no drive on there when I click on it. I fastbooted a stock boot img from here http://forum.xda-developers.com/showthread.php?t=2236418. I can recognize my phone now with ADB, but when I try to ADB sideload paranoidandroid.zip I get "failed to write data 'protocol fault (no status)'
Any help would be much appreciated as to how to fix my phone. I have tried to google for other solutions, but HTC made searching for only the HTC one so hard with all the other phones they have released under the one name.
gothmog1114 said:
I was having a problem with not receiving calls, so I foolishly went into the internal sdcard and deleted everything and then used TWRP to wipe everything else with the intention of starting fresh on a new rom. I currently can boot into TWRP recovery. My computer can recoginize that there is a drive connected, but it is shaded out and says that there is no drive on there when I click on it. I fastbooted a stock boot img from here http://forum.xda-developers.com/showthread.php?t=2236418. I can recognize my phone now with ADB, but when I try to ADB sideload paranoidandroid.zip I get "failed to write data 'protocol fault (no status)'
Any help would be much appreciated as to how to fix my phone. I have tried to google for other solutions, but HTC made searching for only the HTC one so hard with all the other phones they have released under the one name.
Click to expand...
Click to collapse
Did u mount under twrp? That should mount it as a usb allowing u to transfer the rom
luigi311 said:
Did u mount under twrp? That should mount it as a usb allowing u to transfer the rom
Click to expand...
Click to collapse
incorrect
you cant mount usb with this phone while in recovery at all
Easiest way is to use this tool http://forum.xda-developers.com/showthread.php?p=40341536 and side load whatever Rom you want. You may also have to click the install HTC drivers for within this tool.
Sent from my HTCONE using xda app-developers app
flex360 said:
incorrect
you cant mount usb with this phone while in recovery at all
Click to expand...
Click to collapse
Really? I never even bothered to try it so I was just going by past phone experience. Then the only way I can think of is using adb push from fastboot
Konfuzion said:
Easiest way is to use this tool http://forum.xda-developers.com/showthread.php?p=40341536 and side load whatever Rom you want. You may also have to click the install HTC drivers for within this tool.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I think my problem was that I was doing the right thing but with the wrong rom. The rom I kept trying to sideload gave me an error, "failed to stat /system/build.prop" but then when I tried a different rom it worked.
Thanks!!!
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?