I'm unlocked via HTC Dev and I was using Android Revolution HD w/ Android 4.3. I made backups of my data and was attempting to run Moonshine so that I could S-Off and try a KitKat rom. The software failed for some reason, but I found instructions somewhere that said to take the unsecure_boot.img file that came in the Moonshine zip and move it to the adb/fastboot tools folder, and to run "fastboot flash boot unsecure_boot.img."
Now after trying to reboot my device it's stuck on the quietly brilliant screen and not recognized by fastboot and adb. Holding the power button in for a good minute doesn't force a reboot like I'm used to.
Any ideas how to fix?
woodie said:
I'm unlocked via HTC Dev and I was using Android Revolution HD w/ Android 4.3. I made backups of my data and was attempting to run Moonshine so that I could S-Off and try a KitKat rom. The software failed for some reason, but I found instructions somewhere that said to take the unsecure_boot.img file that came in the Moonshine zip and move it to the adb/fastboot tools folder, and to run "fastboot flash boot unsecure_boot.img."
Now after trying to reboot my device it's stuck on the quietly brilliant screen and not recognized by fastboot and adb. Holding the power button in for a good minute doesn't force a reboot like I'm used to.
Any ideas how to fix?
Click to expand...
Click to collapse
Fixed it via the solution here http://forum.xda-developers.com/showpost.php?p=41800036&postcount=9 in case anyone else is stuck at the boot screen. How can I get this thread closed?
Related
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
ziggy46 said:
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
Click to expand...
Click to collapse
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
glyphs said:
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
Click to expand...
Click to collapse
no problem
Use the thanks button
Sent From My Amaze.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
jared407 said:
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
Click to expand...
Click to collapse
Thank you so much, i made an account just to personally thank you for this.
I was stuck on the Bootscreen for cm10 and couldn't figure out what was wrong, but i tried your reply And it worked for me.
Thank you so much sir.
Isn't 4EXT like... the *COUGH*BEST RECOVERY FOR HTC DEVICES*COUGH*
Hopefully some one can help me because my thunderbolt is a paper weight at the moment. I used the android dev method for unlocking my bootloader. All went well and i had a factory reset phone with an unlocked boot loaded. I then used adb and flashed clockwordmod recovery ver. 5.0.2.1. Then used flashboot reboot command to reboot then held vol down and power button and got back into hboot/bootloader/flashboot etc menu. Went to recovery and it went to the white screen then to clockworkmod. I wiped the cache and also the cache in the advanced menu. I then installed liquid ICS. It went through it steps and said it installed correctly. Then I rebooted the phone from clockworkmod and it hung on the white screen. I tried to reboot it a few times with the same result. I then tried to install a gingerbreak rom and had the same affect. I read and dug around and found the stock pg05img and put it on my sd card. I booted back into hboot and it installed checked and installed pg05img. I rebooted again from the Hboot menu and it hung on the white screen again. So now I feel stuck. Is my phone toast. How do I get this thing back on its feet. Ive rooted and installed custom roms on my xoom but I am def a newbie. Any help would be appreciated.
Thanks in Advance,
Barry.
Lancaster CA
With the HTC unlock you cannot flash boot.img's through recovery, so any non sense based and/or non gingerbread roms will not boot. I'd suggest flashing one then getting s-off.
Sent from my ThunderBolt using Tapatalk 2
trter10 said:
With the HTC unlock you cannot flash boot.img's through recovery, so any non sense based and/or non gingerbread roms will not boot. I'd suggest flashing one then getting s-off.
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the advice! I'm still pretty uneducated when it comes to my thunderbolt. what rom do you reccomend I flash and what procedure should I use now that I am stuck at the white screen?
I tried eternity 8-4 with the same result. I used clockwork to install it and reboot the phone. What am I missing?
barryth said:
I tried eternity 8-4 with the same result. I used clockwork to install it and reboot the phone. What am I missing?
Click to expand...
Click to collapse
With the rom file on the comp. Unzip it, and put the boot.img in the folder with fastboot you used to unlock. Then open that folder and hold shift and right click and click open command prompt here. Then connect the phone in fastboot mode. Once its connected, run
Code:
Fastboot flash boot boot.img
Then
Fastboot reboot
And it should boot. Then use the tbolt tool to get S-OFF
Sent from my ThunderBolt using Tapatalk 2
trter10 said:
With the rom file on the comp. Unzip it, and put the boot.img in the folder with fastboot you used to unlock. Then open that folder and hold shift and right click and click open command prompt here. Then connect the phone in fastboot mode. Once its connected, run
Code:
Fastboot flash boot boot.img
Then
Fastboot reboot
And it should boot. Then use the tbolt tool to get S-OFF
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
I was able to get it working. Thanks for the help, but I have another issue now witch I posted in a new thread above this one. With the tbolttool it will not take s-off and my wifi isnt working. All the details are in my other post.
Thanks!
I recently went from being HTC Dev unlocked 1.58 to JuopunutBear S-Off. Before I was able to do fastboot commands but coundn't flash a recovery. I figured that maybe doing Jbear might do something for the issue since I wanted to S-Off anyway. Due to some ignorance I did the Jbear process and wiretrick to achieve S-off. But, Instead of using a Jbear Bootloader I though I could downgrade also by flashing a 1.13 RUU. I did it and my phone worked. When I went to the bootloader it read: S-Off 1.40 ect. (with no Locked/Unlocked bar at top). I wanted to flash a ROM and it didn't work so I thought i should try to unlock the phone bootloader. This did not work.
I then found out I had to use a Jbear bootloader and I am now on: Hboot 1.50.5050 with S-Off and (Joupunutbear) at top. Now whenever I try to use fastboot or adb commands I get the error *device not found* or -waiting for device-. I want to flash a recovery and then a rom but neither is possible now.
Things I have researched and checked:
1. htc sync drivers work/are up to date(i used them before this issue occurred and have tried others)
2. usb debugging is on.
3. I can not do a logcat. I get the same error.
4. I tried to install the recovery through the rom manager app but it got the same error.
Any help in advance would be appreciated.
(I apologize if there is already a solution on the site. I have searched to the best of my ability.)
If your phone boots up, go to developer options and make sure android debugging is enabled
Otherwise, it sounds like you are in boot loader. You need to navigate to fast boot
Then when your USB is connected it should read fast boot USB
Flash recovery
Make a backup
Wipe all partition except SD
Flash ROM/gapps whatever
Reboot
Sent from my Evo V 4G using xda app-developers app
hossman said:
If your phone boots up, go to developer options and make sure android debugging is enabled
Otherwise, it sounds like you are in boot loader. You need to navigate to fast boot
Then when your USB is connected it should read fast boot USB
Flash recovery
Make a backup
Wipe all partition except SD
Flash ROM/gapps whatever
Reboot
Sent from my Evo V 4G using xda app-developers app
Click to expand...
Click to collapse
I have rooted my two previous phones, one of them being HTC android so I have some experience. What I'm saying is that I have usb debugging on and I boot to bootloader, then fastboot and get fastboot-usb.
Despite doing everything correctly it still gives errors with the device. For example, i tried again this morning and waited until it said -waiting for device- to go into fastboot and it did something different:
* attached an image of my commands since I coundn't link them. (new user)
the second command is what happens when i start in fastboot usb.
All commands dealing with fastboot result in *Device not found*
Thanks for the response, I understand those common issues get posted a lot.
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
clrsri2006 said:
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
Click to expand...
Click to collapse
UPDATE : The reboot to boot loader via power button + volume down works but it took about 2 mins of holding those buttons, which is unusually long time. So its not a brick As experienced developers say DO NOT PANIC, staying calm and read the forums thoroughly has helped.
I'm trying to see how I can fix the .zip install failures now.
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
clrsri2006 said:
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
Click to expand...
Click to collapse
UPDATE : After many attempts I could work it out by using guru reset .zip file (1.26.502.12). I did this before as well but was not able to get s-off previously. This time I asked to install superuser when resetting using guru reset file. I got the 1.26 one back with disabled touchscreen. Then I used rumrunners and got s-off and then used the ruu for 3.17.502.3 exe file to get the working on.
Now the bootloader just says unlocked but not tampered. I got the twrp recovery again as it was very handy for me.
I was able to get supercid. Now trying for ARHD 51.0.
After I got the RUU for 3.17.502.3 the only issue i noticed is that when phone boots up I just see HTC instead of "HTC quitely brilliant"
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)