Related
Is there a newer CWM (currently using 4) for those of us stuck with HBOOT 1.5?
And if so, where can I find it? I've searched but every recovery I try won't work with this crappy HTC Method.
lcars123 said:
Is there a newer CWM (currently using 4) for those of us stuck with HBOOT 1.5?
And if so, where can I find it? I've searched but every recovery I try won't work with this crappy HTC Method.
Click to expand...
Click to collapse
Have you tried TWRP? I'm htc unlocked 1.5 and it works fine for me. Try that or have a look at this.
lcars123 said:
I've searched but every recovery I try won't work with this crappy HTC Method.
Click to expand...
Click to collapse
In theory, the only issue should be HTC not unlocking the boot partition while booted in the standard recovery mode.
I'm s-off with revolutionary, but curious, what about the custom recovery's don't work for you? What error messages do the custom recovery's provide?
joeykrim said:
In theory, the only issue should be HTC not unlocking the boot partition while booted in the standard recovery mode.
I'm s-off with revolutionary, but curious, what about the custom recovery's don't work for you? What error messages do the custom recovery's provide?
Click to expand...
Click to collapse
I can't install the latest CWM Recovery. That is the main issue. I'm stuck with an outdated version. If I try to load it via Rom Manager, after trying to boot into recovery, i get the splash screen, a black screen, then the phone reboots. I've tried to pull it from the CWM website and flash it via fastboot and the same thing happens. Is there something that has to be modified for recovery to work when unlocked via the HTC method?
Is there a version of the latest CWM 5.0.2.0 that will work with the HTC unlock method on hboot 1.5? Anyone? Anyone?
I am on hboot 1.5 and have been able to flash different recoveries fine. So far I have used TWRP 1 & 2. You should be able to flash via bootloader which includes adb commands sent from cmd on your PC.
You need:
Android SDK (Install from Android site)
HTC ADB Drivers (should install automatic..if not google and find and install)
Put your desired .img (recovery) into the folder where ADB.EXE exists (android-sdk sub-directory)
Reboot into bootloader---->fastboot
RUN THIS COMMAND FROM YOUR PC WITH THE PHONE ATTACHED VIA USB CABLE cd c:/******* fastboot flash recovery recovery.img
where ******* is the path to ADB.EXE (same folder as .img file and ADB.EXE)
for example cd c:/android fastboot flash recovery recovery.img
I installed a custom ROM (carbondev) but when my phone loads it just shows a carbondev load screen.
I have no back up in clockworkMod to revert back to the stock ROM...
Iv managed to use adb push to send ROM's to my phone.. i know its worked because in cmd it says (so many bytes in so many seconds)...
I cant manage to locate any ROM's in clockwork mod to install one through recovery.
Did you installed the boot.img for the Rom? If not try it via Fastboot.
Cold Ice said:
Did you installed the boot.img for the Rom? If not try it via Fastboot.
Click to expand...
Click to collapse
Im no expert and only managed to do what iv done so far with instructions...
I wouldnt know how to do that.
When i click HBOOT i get...
SD checking ...
failed to open usb master mode
[preload] failed to open usb master mode
loading... image and so on
http://forum.xda-developers.com/showthread.php?t=1752270
This is a good Tutorial for installing Boot.img via Fastboot. We can't flash boot.img with the .zip in the Rom because S-ON won't allow it (If I read correclty).
If you need more help you can write me a PM
Thanks i'll try this after download the ROM again and putting it back in the folder.. think iv deleted the boot.img for it xD
done the.... fastboot boot boot.img
but the phone is just getting stuck in the HTC screen
Re: [Q] Help cynogenmod stock in boot circle.
Don't boot the image, you need to flash it. "Fastboot flash boot boot.img".
Sent from my HTC One X+ using Tapatalk 2
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%
So I have been installing this rom http://forum.xda-developers.com/showthread.php?t=2188931 .
I installed just the rom and not the update and now my phone will not boot it turns onto the htc first screen and vibrates a few times.
I have tried going into recovery mode and starting again but recovery does not now boot the phone restarts and the above happens.
I have installed fast boot on my computer but when I run it, it flashes up for a second then closes.
Thanks in advance for your help.
sodamhall said:
So I have been installing this rom http://forum.xda-developers.com/showthread.php?t=2188931 .
I installed just the rom and not the update and now my phone will not boot it turns onto the htc first screen and vibrates a few times.
I have tried going into recovery mode and starting again but recovery does not now boot the phone restarts and the above happens.
I have installed fast boot on my computer but when I run it, it flashes up for a second then closes.
Thanks in advance for your help.
Click to expand...
Click to collapse
Well, without knowing any details about your phone and what update you were on, which recovery you used, whether or not you are S-On / S-Off, then we're just shooting in the dark trying to help.
If fastboot flashes for a sec and closes, then you are not using fastboot right. You have to run it from the Command Prompt. You don't double click on the fastboot.exe .
Can you still get to the bootloader mode?
And I have to ask, but you're sure you got the right rom from the right forum as there are quite a few different variants of the Desire...?
es0tericcha0s said:
Well, without knowing any details about your phone and what update you were on, which recovery you used, whether or not you are S-On / S-Off, then we're just shooting in the dark trying to help.
If fastboot flashes for a sec and closes, then you are not using fastboot right. You have to run it from the Command Prompt. You don't double click on the fastboot.exe .
Can you still get to the bootloader mode?
And I have to ask, but you're sure you got the right rom from the right forum as there are quite a few different variants of the Desire...?
Click to expand...
Click to collapse
How do I open fastboot from a command prompt I just need to know what to type.
I can still get into bootloader fine on the phone and my pc knows its contected via usb.
I know the phone was running a different recovery mode than standard but I don't know witch one. I think it may have been xloader or something with a x.
Its a standard desire. Regards Wayne
I have manged to load bootloader with command prompt and I want to remove the rom I have installed how do I go about this? Regards again, Wayne
O.K so I have loaded up bootloader and thought -w would be the command I am looking for, all I get from bootload on my computer is: waiting for device. I have attached a screen shot. Regards Wayne
You'll have to find an appropriate recovery.img and use fastboot to install. Make sure the img file is in the fastboot directory and while connected in bootloader/fastboot mode:
fastboot flash recovery recovery.img (where recovery.img is the name of your file - it can be whatever.img and you can rename it to whatever you want as long as you don't change the extension .img)
and see if you can boot to recovery at that point. If not, then you will probably have to use an RUU to return to stock and start over.
If you can get into the custom recovery, then you can reinstall another rom. Keep in mind, if S-On, then you will probably need to use fastboot to install the boot.img like so:
fastboot flash boot boot.img (here boot.img should remain named that)
I am using TWRP to install a flash (Because the Phone is getting stuck a HTC's logo) and after I finished flashing it, I reboot and it gets me back to TWRP so it's not working. What to do?
How did you install TWRP on your device? it must be Fastboot-ADB folder where you have already copied the recovery .img file. Open the command window in this folder by Shift and Right click combo and type the following command with the part of command of your recovery image file:
fastboot flash recovery(yourRecoveryFileName) and then type .img at the end of the command – hit Enter
The process of installing of your chosen custom recovery will now start on HTC One Max.