Related
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.
_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.
I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK
Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img
hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok
sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot
Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Hi
Greetings,
Install HTC drivers for abd to recognize your phone, this will help you to atempt abd sideload and also fastboot commands
Flash the recovery againg
"fastboot flash recovery name-of-recovery-.img"
And try again by adb sideload this is your last option before flashing a ruu
Sent from my HTC Sensation Z710e using xda premium
mfadhil said:
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Click to expand...
Click to collapse
I'm in a similar boat, did a "format data" in TWRP and now I can't boot. I can access the phone via ADB tho. I'll let you know if I find a solution.
Same thing here
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
NoDroid4U said:
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Click to expand...
Click to collapse
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
matt95 said:
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
Click to expand...
Click to collapse
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
NoDroid4U said:
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
Click to expand...
Click to collapse
i think you downloaded an OTA and not a RUU
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i won't suggest to hit that factory reset button! causa actually it soft-bricked some devices... you've been lucky
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
as long as i know the only file that you can flash in that OTA is the firmware.zip that will update your bootloader but i'll do it after some more tries...
please paste here the output of
Code:
fastboot getvar all
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
Have you tried "fastboot -w" this will factory reset your phone from fastboot. Then try re-flashing recovery again.
NoDroid4U said:
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
Click to expand...
Click to collapse
I've had this problem on the one x plus, what I did and please bear with me, it does work Firstly flash cwm and clear cache, once you have done that you should be able to boot recovery. Once in cwm format everything including data! yep I said data! then reboot back to fastboot and flash TWRP and rewipe everything again (including data) then sideload or push your rom across to your phone.
Done this twice now on mine when I got bricked (for no reason!) I can only think the file system becomes corrupt somehow.
alright guys, i solved the issue and my phone is back to normal !
to those guys still facing the issue, i suggest you flash the latest cwm then try using the sideload function > adb sideload <filename.zip>
mine came back to life after that, heh
cheers!
Also fixed
Hey guys, thanks so much for everyones help last night. I also got mine all fixed and set away. For anyone interested, I used the ruu and steps in this thread: http://forum.xda-developers.com/showthread.php?t=2250904
Thanks again to everyone for their help!
So I was trying to wipe fresh Kinology and the device got stuck in a recovery bootloop. Not such a big problem" i thought to myself,
"I'll just wipe everything" and so I did. Except one little detail. I ****ed up and wiped EVERYTHING, including the SD card and *that thing that boots the OS*.
Now, it wasn't such a big problem either, I could just boot into recovery, mount the SD card, transfer the files to the kinlde, buuuut there was one little problem. Once I connected the kindle to PC, a USB device was detected, but no storage was shown up. I got to the recovery terminal and it said
E: unable to locate volume information for usb storage mode
Click to expand...
Click to collapse
Okay, once again, no such a big deal, I can boot into fastboot, reflash stock and live happily ever after. I go into fastboot mode (note that the kindle is indeed connected AND DETECTED by PC and I have drivers installed). And guess what? Fastboot won't detect the kindle! (screenshot related)
Now I have a kindle with no OS installed, which can't mount storage and can't connect to fastboot. What should I do?
tldr: wiped everything, no os, can't mount in twrp, can't connect to fastboot, wat do?
SlimThePineapple said:
So I was trying to wipe fresh Kinology and the device got stuck in a recovery bootloop. Not such a big problem" i thought to myself,
"I'll just wipe everything" and so I did. Except one little detail. I ****ed up and wiped EVERYTHING, including the SD card and *that thing that boots the OS*.
Now, it wasn't such a big problem either, I could just boot into recovery, mount the SD card, transfer the files to the kinlde, buuuut there was one little problem. Once I connected the kindle to PC, a USB device was detected, but no storage was shown up. I got to the recovery terminal and it said
Okay, once again, no such a big deal, I can boot into fastboot, reflash stock and live happily ever after. I go into fastboot mode (note that the kindle is indeed connected AND DETECTED by PC and I have drivers installed). And guess what? Fastboot won't detect the kindle! (screenshot related)
Now I have a kindle with no OS installed, which can't mount storage and can't connect to fastboot. What should I do?
tldr: wiped everything, no os, can't mount in twrp, can't connect to fastboot, wat do?
Click to expand...
Click to collapse
I had to swap cables for my fastboot to show up;boot into fastboot then go back to stock cable. I also had to use specific commands like "fastboot -i 0x1949" then the command. Hope this helps any.
zander78 said:
I had to swap cables for my fastboot to show up;boot into fastboot then go back to stock cable. I also had to use specific commands like "fastboot -i 0x1949" then the command. Hope this helps any.
Click to expand...
Click to collapse
I don't have a fastboot cable, I enter fastboot mode through recovery
I've tried the SRT tool today and if I press "Check fastboot status" it just stays the same as on the screenshot 1.
And if I choose the second option, it just stays like that (screenshot 2) without any movement.
Help me, please D:
SlimThePineapple said:
I've tried the SRT tool today and if I press "Check fastboot status" it just stays the same as on the screenshot 1.
And if I choose the second option, it just stays like that (screenshot 2) without any movement.
Help me, please D:
Click to expand...
Click to collapse
You're gonna need a fast boot cable. You can make one if you know how to solder. Or buy one from skorpn. http://forum.xda-developers.com/member.php?u=500006
Okay, for anyone interested: I've solved my problem (partially). I used ADB Sideload from TWRP and sideloaded CM10, but sideloading kinology didn't work for me and resulted in a bootloop.
You need to flash the stock Amazon OS, wipe everything EXCEPT INTERNAL STORAGE first then flash the stock os, then kinology.
Sent from my KFHD7 running ParanoidAndroid using Tapatalk 2
dugoy13 said:
You need to flash the stock Amazon OS, wipe everything EXCEPT INTERNAL STORAGE first then flash the stock os, then kinology.
Sent from my KFHD7 running ParanoidAndroid using Tapatalk 2
Click to expand...
Click to collapse
That's exactly what I did, and it resulted in a bootloop
SlimThePineapple said:
That's exactly what I did, and it resulted in a bootloop
Click to expand...
Click to collapse
If adb sideload isn't working reliably, you can just use "adb push filename.zip /sdcard/" to copy files manually to your Kindle. This will work for whatever zips you want, be it gapps, CM10.1, kinology, stock, etc.
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
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.
sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it
akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.
sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!
sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.
rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!
sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...
Please does anyone have a solution to this? please help me
Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?
Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.
i did that but no response.
Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers