Related
I flashed a new ROM to the phone and rebooted. At reboot, when the first "android" screen comes up it gets stuck there.
If I reboot in to the recovery screen it will go there but I can't do ANYTHING! Can't scroll to a command, can't "Alt+" any command.
At the very bottom of the screen it says:
Build : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No space left on device)
HELP?!? Did I finally manage to find a way to brick my phone?
I do not expect that you bricked your phone. What SPL do you have installed? If you have 1.33.2003 or 1.33.2005 installed, you have always he possiblity to go to fastboot mode and flash a new recovery.
AndDiSa said:
I do not expect that you bricked your phone. What SPL do you have installed? If you have 1.33.2003 or 1.33.2005 installed, you have always he possiblity to go to fastboot mode and flash a new recovery.
Click to expand...
Click to collapse
I AM able to get it in to fastboot. I'm still a bit of a newbie though, so I'm not sure what SPL I have...? Possibly Danger? How do I flash a new recovery?
AndDiSa said:
I do not expect that you bricked your phone. What SPL do you have installed? If you have 1.33.2003 or 1.33.2005 installed, you have always he possiblity to go to fastboot mode and flash a new recovery.
Click to expand...
Click to collapse
Oh! I see in fastboot that I do have 1.33.2005. So how do I flash a recovery? Thanks!
Nevermind, I Got it!! Thanks for the suggestion/help!
1.33.21005 is DangerSPL, so you have the possibility to use fastboot. There is a tutorial here in the forum to setup adb and fastboot. Unfortunately I do not have the link at the moment.
If you have setup your fastboot environment, you should be able to flash a new recovery with the following command:
fastboot flash recovery recovery.img
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.5 D/S ADS using XDA App
Excellent
AndDiSa said:
1.33.21005 is DangerSPL, so you have the possibility to use fastboot. There is a tutorial here in the forum to setup adb and fastboot. Unfortunately I do not have the link at the moment.
If you have setup your fastboot environment, you should be able to flash a new recovery with the following command:
fastboot flash recovery recovery.img
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.5 D/S ADS using XDA App
Click to expand...
Click to collapse
I had the exact same issue and this worked from me...using Amon_RA's method:
"via fastboot :
* Requires engineerings SPL!
Code:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
"
I just saved recovery-RA-dream-v1.7.0.img to the "tools" folder of the android-sdk and ran cmd from there (Hold shift + Right-click in win7).
Rebooted holding home and I was in RA-dream-v1.7.0 without the error.
Click the recovery image link in my sig for more info.
Thanks!!
To all of you that have suggested things, I figured it out thanks to your suggestions!! I appreciate all of your help on this issue!!
I unlocked the bootloader then went to flash recovery and it shows it flashed but won't reboot into recovery. What am I doing wrong? Thank you
Sent from my Nexus One using XDA App
are u rooted? and just download rom manager from the market and flash through the app.
Sent from my LG-V909 using Tapatalk
I'm not rooted. How would I root without flashing recovery?
Sent from my Nexus One using XDA App
Make sure you have a recovery for the nexus one.
Go into fastboot. Flash the recovery. Then enter the command fastboot reboot recovery. Do that with out booting into the os.
Read the Wiki, Recovery section, and follow the guide for unlocked bootloader.
I did all that and it won't go into recovery. I have read the wiki quite a few times
Sent from my Nexus One using XDA App
fastboot boot name-of-recovery.img
If you reboot your phone, the stock recovery will be reinstalled...
Exactly. I guess you're not following the guide properly.
The guide says:
"fastboot flash recovery recovery.img"
"fastboot reboot recovery"
Did you execute those as above? Or did you do it in some other way?
I did the commands just like that. One of u guys says its "fastboot boot recovery " and the other says reboot. Which is it? When I do the recovery.kimgom command it says its sending and writing it
Sent from my Nexus One using XDA App
"fastboot boot recovery.img" sends the image to boot from your HD, and doesn't check the image that is already in recovery partition.
"fastboot reboot recovery" uses the boot image from recovery partition - the one you just wrote.
What happens when you execute "fastboot reboot recovery"?
Nothing on the phone. On the command window the recovery shows
Sent from my Nexus One using XDA App
Do I have to put the recovery image on the SD card to?
Sent from my Nexus One using XDA App
The recovery can't show on command window.
Again, what happens when you execute "fastboot reboot recovery"?
Print the screen, because it looks like you can't explain what's going on.
No, you just need to follow the guide correctly.
Does OP need to run these before he reboots and right after flashing new recovery--
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
If he doesn't even boot into OS - then no, he doesn't need it and can't do it from bootloader anyway.
gotcha--thanks Jack
When I execute the command nothing happens.
Sent from my Nexus One using XDA App
Are you sure you got the drivers installed?
Are you sure the bootloader is unlocked.
The commands have to work. Boot into fastboot and issue this command. Fastboot devices. Your devices serial number should show up in the command prompt.
What makes you think the recovery flashed
Did you put recovery in your SDK tools folder and go to that path in terminal before fastbooting the .img
I also read somewhere a long time ago, some phones like mine don't accept reboot command thru fastboot
You could run your commands and then adb kill-server, disconnect phone and reboot using phone buttons
When I turn in the phone it shows the unlocked padlock. I put the image in my tools folder and I pit the command fastboot devices and get my serial #
Sent from my Nexus One using XDA App
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
Hi everyone
I stuck with root procedure (first link when you type "htc mini 2 root" in google)
I did unlock bootloader with htcdev, I am able to run adb and fastboot - meaning I can restart my phone into fastboot loader but I cannot run TWRP recovery, I dont know why. I downloaded few versions of this .img file, I run command fastboot boot recovery xxxx.img, with some files there is no reaction at all, with file recovery-twrp-2.8.5.0 phone is restarting but into normal function, there is no twrp screen. I have CWM-SuperSU-v1.30 on sd card in the phone
Does anyone have clue what can be wrong here?
Thank you
pudlll said:
Hi everyone
I stuck with root procedure (first link when you type "htc mini 2 root" in google)
I did unlock bootloader with htcdev, I am able to run adb and fastboot - meaning I can restart my phone into fastboot loader but I cannot run TWRP recovery, I dont know why. I downloaded few versions of this .img file, I run command fastboot boot recovery xxxx.img, with some files there is no reaction at all, with file recovery-twrp-2.8.5.0 phone is restarting but into normal function, there is no twrp screen. I have CWM-SuperSU-v1.30 on sd card in the phone
Does anyone have clue what can be wrong here?
Thank you
Click to expand...
Click to collapse
you using wrong command.
try:
fastboot flash recovery xxx.img
for root i recommend using TWRP and flash the SuperUser.
Make sure you using the correct recovery image...
All you need in here
kativiti said:
you using wrong command.
try:
fastboot flash recovery xxx.img
for root i recommend using TWRP and flash the SuperUser.
Make sure you using the correct recovery image...
All you need in here
Click to expand...
Click to collapse
It didnt worked, I download again twrp files and this time I guess I found newest version which worked with fastboot boot recovery.img
Thanx anyway
Hello, I unlocked the bootloader and have been trying to flash roms. I downloaded the latest platform tools, usb drivers, cables, computers. . The instructions state to "fastboot flash boot <recovery_filename>.img" but I was getting "failed to write to partion not found" but when using "fasboot flash boot_a and boot_b" the recovery works. But when trying apply update from adb using "abd sideload rom.zip" I keep getting that "cannot read zip" Flashing magisk does work though. What could be going wrong?
There can be 2 reasons
Your zip file is Encrypted or it is Corrupted