I was flashing a TrickDroid ROM just now, having had Jellytime 17.1 previously. I did a full backup and full wipe before attempting to flash the TrickDroid ROM.
I got distracted during the process, and when I came back to my phone, it was showing the Jellytime boot animation, but never gets to the UI.
OK, so I figure I can hold the power and volume down button and get into recovery. Nope. When I try to select Recovery from the boot loader, it doesn't do anything at all.
Am I hosed up for good here?
When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.
Teichopsia said:
When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.
Click to expand...
Click to collapse
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike
TheImpalaKid said:
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike
Click to expand...
Click to collapse
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.
If it goes into the bootanimation then you can use ADB. Connect the phone to pc and let it go into the bootloop and then use "adb reboot recovery" from the command line on your pc.
If it stil doesn't work then you'll need to reflash your recovery. Download a recovery image like ClockWorkMod, go into bootloader while connected to pc. It should show "Fastboot USB" on the bootloader screen. Then use ""fastboot flash recovery [name of the image.img]" to flash a new recovery.
Try going into recovery again and see if it helps.
Teichopsia said:
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.
Click to expand...
Click to collapse
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike
Its strange though.. flashing a ROM doesn't tamper the recovery partition so it shouldn't have happened.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
TheImpalaKid said:
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike
Click to expand...
Click to collapse
You won't need to give it to AT&T.. just run an RUU and root it again if it comes to it.
Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.
Teichopsia said:
Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike
TheImpalaKid said:
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike
Click to expand...
Click to collapse
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...
if4ct0r said:
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...
Click to expand...
Click to collapse
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike
TheImpalaKid said:
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike
Click to expand...
Click to collapse
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.
if4ct0r said:
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.
Click to expand...
Click to collapse
I guess... I can't get my laptop to recognize the phone or load any drivers for it. So when I try to run adb, I get no devices.
I have a teenage son who I may sic on this problem.
Mike
You have HTC Sync installed? You have ADB as well? Make sure you have it installed. It installs connectivity drivers for your phone.
If you're indeed getting into bootanimation your phone should be recognized by ADB. After installing HTC Sync, try running "adb devices" if it shows no devices try running "adb kill-server" and then "adb devices" again. If all drivers are correctly installed it should recognize your phone.
Tips: You can get adb by running the advanced ace hack kit once
Update
My two sons were able to finally get the phone reset to factory spec sometime last night. :victory: So I'll have to re-root the phone and then I can restore my ROM from the backups.
One weird thing... the speaker/microphone doesn't work now. This is no big deal as I rarely receive or make calls.
I'm probably not your typical Android user in that I'm 55, and I love to try out the different ROMs that are available. Favorites are BlackIce, Trickdroid, and JellyTime.
Most of my peers have some sort of iPhone and really don't care anything about behind-the-scenes or jailbreaking, etc.
Thanks to everyone who's offered help and information.
Mike
TheImpalaKid
Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Hello everyone!
I just updated ROM Manager which prompted me to update my CWM Recovery to 5.0.1.0. Well, I just did so, and now I'm stuck at the HTC screen at boot...
Will reinstalling the ROM fix it? Or is there simpler solution?
Thanks!
krakout said:
Hello everyone!
I just updated ROM Manager which prompted me to update my CWM Recovery to 5.0.1.0. Well, I just did so, and now I'm stuck at the HTC screen at boot...
Will reinstalling the ROM fix it? Or is there simpler solution?
Thanks!
Click to expand...
Click to collapse
Pull the battery and phone should restart normally,seems to be a few bugs with this new release some say to flash the new recovery from fastboot,I found that reflashing from ROM manager a second time worked,still get the odd hang but tested backup and restore which seem to work and I am using it. Over on the DZ forums there is alot of similar stories,either go back to an earlier version or try reflashing again.
bombadier said:
Pull the battery and phone should restart normally,seems to be a few bugs with this new release some say to flash the new recovery from fastboot,I found that reflashing from ROM manager a second time worked,still get the odd hang but tested backup and restore which seem to work and I am using it. Over on the DZ forums there is alot of similar stories,either go back to an earlier version or try reflashing again.
Click to expand...
Click to collapse
Thanks for your reply; unfortunately, pulling the battery was the first thing I tried and still got the same result
Is there a way to go back to a previous CWM version *through* the recovery menu maybe? [EDIT] Ah yeah, you say so, but how? I can't even find a link for it outside the market...
Thanks again!
T
PS "DZ Forum"? Desire Z?
krakout said:
Thanks for your reply; unfortunately, pulling the battery was the first thing I tried and still got the same result
Is there a way to go back to a previous CWM version *through* the recovery menu maybe? [EDIT] Ah yeah, you say so, but how? I can't even find a link for it outside the market...
Thanks again!
T
PS "DZ Forum"? Desire Z?
Click to expand...
Click to collapse
Yeah sorry the Desire Z forum
here : http://forum.xda-developers.com/showthread.php?t=834731
Can you get into recovery?
If not, to use fastboot you need to have ADB set up on your computer,search the forums for a guide.
Let me know if I can help further.
Yeah, I can get into recovery alright. I'm now browsing the CMW repository, damn if I can remember what name the HD goes by
[EDIT] According to this it's the Ace. Keep forgetting...
[EDIT2] I pushed 5.0.1.0 again, same result. I've just pushed 3.0.2.6, but... still stuck?!? Ok, now I'm stumbled. Any help much appreciated...
PS How can you update Recovery through Recovery? I see no such option?
krakout said:
Yeah, I can get into recovery alright. I'm now browsing the CMW repository, damn if I can remember what name the HD goes by
[EDIT] According to this it's the Ace. Keep forgetting...
[EDIT2] I pushed 5.0.1.0 again, same result. I've just pushed 3.0.2.6, but... still stuck?!? Ok, now I'm stumbled. Any help much appreciated...
PS How can you update Recovery through Recovery? I see no such option?
Click to expand...
Click to collapse
Ok your problem is that when you boot the phone you just get the htc screen and your rom does not load?how do you get into recovery? no you can't update recovery from within recovery thats where fastboot comes into play,will try and help as best I can,
PS have you the fastboot file and adb setup on a computer?
PPS What do you mean by you have pushed recovery?
bombadier said:
Ok your problem is that when you boot the phone you just get the htc screen? how do you get into recovery? no you can't update recovery from within recovery thats where fastboot comes into play,will try and help as best I can,
PS have you the fastboot file and adb setup on a computer?
Click to expand...
Click to collapse
yes, I get stuck in the HTC screen, but I can get into Recovery by removing the battery, powering up and keeping the VolDown keypress just fine. Both Recovery images that I mentioned work OK, but I jsut can't get past the HTC logo when booting normally...
Yes, I got all the programs required set up.
Thanks for helping out...
Could you restore a nandroid then?It sound like something got messed up,if you can get into recovery then the problem must lie with the rom?So try restoring a backup or flash a new ROM
Yeah... I didn't have enough room on the SD for a backup so there's none unfortunately. So I guess it's down to reinstalling the ROM and all the mods again, which I was trying to avoid, but oh well, that's life I guess!
Once more, many thanks.
Some things are worth making some space for........ Glad to help,hope a reinstalled ROM gets you up and running again
Already reinstalling, I'll update with more info when it's done
krakout said:
Already reinstalling, I'll update with more info when it's done
Click to expand...
Click to collapse
And remember make some room for a Nandroid backup,case and point!!!!!!!!!!!
Best of British to you sir!!!!!!!!
...or upgrade to a 16GB card at last
Ok, booting now... yup, it worked! Argh, long night ahead to customize it again, but beggars can't be choosers!
Cheers
T
Hi, I was flashing a new rom but I accidentally select the sideload option and now I'm stuck there,
I tried to hold power button 30 seconds, even more,(also volume down + power button) but nothing happens.
Any idea?
It says:
"ClockworkMod Recovery v6.0.2.3
Sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>"
Please help I'm n00b -.-
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
jsgraphicart said:
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
Click to expand...
Click to collapse
Thank you so much man, that worked!
ARMIGUER said:
Thank you so much man, that worked!
Click to expand...
Click to collapse
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
jsgraphicart said:
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
Click to expand...
Click to collapse
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
ARMIGUER said:
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
Click to expand...
Click to collapse
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
but rdleye
jsgraphicart said:
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
Click to expand...
Click to collapse
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
ARMIGUER said:
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
Click to expand...
Click to collapse
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
jsgraphicart said:
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
Click to expand...
Click to collapse
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
ARMIGUER said:
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
Click to expand...
Click to collapse
No problem. I hope you get it working. Or at least to boot up again.
Supposedly sideload in cwm is a bug with no way to back out unless you pull the battery or have usb connected [exit in command prompt?]. I was starting to like the touch recovery option, but recently i've accidentally pressed a couple of things i shouldnt have.
Sorry to hijack, but I'm attempting to sideload the 4.2.2 update from stock, and my sideload command seems to do nothing. I'm sure i'm connected as it displays my device number and "sideload" next to it. Using the sideload command simply displays the "help" list of the adb commands.
Is it a driver issue perhaps? Something else? (i noticed my batter was low just before attempting this).
Now i'm stuck in the waiting for adb sideload file.
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
bodh said:
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
Click to expand...
Click to collapse
I do NOT see the sideload option in the help output. I have all the latest updates from the SDK manager. Maybe i need to reinstall the SDK. I will give that a go. Thanks.
Edit: Downloaded the latest SDK/ADB and that worked. From 1.0.29 to 1.0.31
I've messed my phone with SideLoad, please help
I booted my Galaxy Nexus into custom recovery (CWM) for some other task but mistakenly gone into sideload menu!
Got no option to get back to main menu or reboot, i took the battery out and re-inserted. Now, my cell is not turning on since then!
Tried another time, took battery off but no luck..... what to do?
I've custom ROM, MIUI V5 4.2.2. My cell is unlocked and rooted, of course.
Please help.
What if the battery is non-removable?
Had stuck in that *** sideload on my SM-E500H and been waiting for the battery to drained it up all.
Yep, tried hardware button combinations as many times as I could.
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
lesmanaz said:
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
Click to expand...
Click to collapse
What if I'm still in sideload and get this error?
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Hi,
I just installed the the Revolution ROM on my desire HD and then when i rebooted it it went straight to the revolution reboot menu....
As i am a NOOB i downloaded the Clockwork recovery, reinstalled the revolution rom but same thing happens...
When i reboot the system it starts up (HTC screen) turns off starts back up again and goes straight to "clockworkmod recovery" menu...
I cant even go to the original boot menu...
To make things worst i can only connect usb as storage...
Can anyone please identify my problem and make a step by step solution, as my knowlege on android phones is close to nothing :crying:
madskor said:
Hi,
I just installed the the Revolution ROM on my desire HD and then when i rebooted it it went straight to the revolution reboot menu....
As i am a NOOB i downloaded the Clockwork recovery, reinstalled the revolution rom but same thing happens...
When i reboot the system it starts up (HTC screen) turns off starts back up again and goes straight to "clockworkmod recovery" menu...
I cant even go to the original boot menu...
To make things worst i can only connect usb as storage...
Can anyone please identify my problem and make a step by step solution, as my knowlege on android phones is close to nothing :crying:
Click to expand...
Click to collapse
Did you do a full wipe (system, data, and cache) before flashing? Are you S-Off with AAHK or S-On with unlocked bootloader?
bananagranola said:
Did you do a full wipe (system, data, and cache) before flashing? Are you S-Off with AAHK or S-On with unlocked bootloader?
Click to expand...
Click to collapse
Yes, i did a full wipe before flashing...
I cant see if i´m S-ON or Off because i can´t go to the original boot menu, but i think its S-Off because the Rom that was in the phone before i messed with it was not the original
madskor said:
Yes, i did a full wipe before flashing...
I cant see if i´m S-ON or Off because i can´t go to the original boot menu, but i think its S-Off because the Rom that was in the phone before i messed with it was not the original
Click to expand...
Click to collapse
An unlocked bootloader with S-On still permits flashing of custom ROMs. Is your recovery updated? If not, do that.
bananagranola said:
An unlocked bootloader with S-On still permits flashing of custom ROMs. Is your recovery updated?
Click to expand...
Click to collapse
i dont know as i said i´m a huge noob when it comes to tecnology
isn´t there a way to do everythig again, but the right way ?
i already installed revolution 3 or 4 times and it installs just fine but wont start up the right way.... always comes back to this menu....
madskor said:
i dont know as i said i´m a huge noob when it comes to tecnology
isn´t there a way to do everythig again, but the right way ?
i already installed revolution 3 or 4 times and it installs just fine but wont start up the right way.... always comes back to this menu....
Click to expand...
Click to collapse
The guide in post #7 of the guide in my signature is pretty clear. Read that. What is important to know is whether your phone is S-On bootloader unlocked or S-Off. Since you didn't hang on the boot splash when you flashed ARHD, I'm guessing S-Off. But just to be safe: to find this information, reboot while holding power and volume-down. That is your bootloader, known as hboot. What does it say? Finally, my hunch is that you need to update your recovery. The guide has instructions for that, but basically, download the image to your computer and flash it from fastboot.
Oh, and you may need to install your drivers on your computer. Install HTC Sync from the HTC website.
bananagranola said:
The guide in post #7 of the guide in my signature is pretty clear. Read that. What is important to know is whether your phone is S-On bootloader unlocked or S-Off. Since you didn't hang on the boot splash when you flashed ARHD, I'm guessing S-Off. But just to be safe: to find this information, reboot while holding power and volume-down. That is your bootloader, known as hboot. What does it say? Finally, my hunch is that you need to update your recovery. The guide has instructions for that, but basically, download the image to your computer and flash it from fastboot.
Oh, and you may need to install your drivers on your computer. Install HTC Sync from the HTC website.
Click to expand...
Click to collapse
I´ve tried to turn the phone on wli holding power + volume, but the result is the same.... powers up then down then up again straight to clockwork...
can you give me the link to the instruction? i cant find them
What image do i have to download?
Sorry for all the questions..... and thanks for your patience
madskor said:
I´ve tried to turn the phone on wli holding power + volume, but the result is the same.... powers up then down then up again straight to clockwork...
can you give me the link to the instruction? i cant find them
What image do i have to download?
Sorry for all the questions..... and thanks for your patience
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1824379. But if power and volume-down (you're using down, not up, right?) boot into CWM, sounds like a problem with your volume buttons.
bananagranola said:
http://forum.xda-developers.com/showthread.php?t=1824379. But if power and volume-down (you're using down, not up, right?) boot into CWM, sounds like a problem with your volume buttons.
Click to expand...
Click to collapse
OMG.... huge noob mistake.... i was using the volume-up button.... you must be so mad at me right now
I can see it now.... on the top of the boot menu says: *** UNLOCKED *** ACE PUT SHIP S-ON...
so i guess you were right.... whats the best ting to do then?
I think it may something to do with the boot image but dont know how to fix it
Update recovery. Guide has instructions.
bananagranola said:
Update recovery. Guide has instructions.
Click to expand...
Click to collapse
Thank you for your patience... i´ll give it a try...
I´ve been trying to solve it by myself for the past 12 hours... i´m exausted
Hope this will fix it....
madskor said:
Thank you for your patience... i´ll give it a try...
I´ve been trying to solve it by myself for the past 12 hours... i´m exausted
Hope this will fix it....
Click to expand...
Click to collapse
When you're tired, it's best to get some sleep. Most mistakes happen when sleepy and tired (been there!) so I'd suggest a little shut-eye and continue then
Sounds to me like the problem will get solved pretty soon, just read the guides and don't rush things. If unsure, read the guide (for what-ever you are doing) a second or a third time and don't try doing many things at the same time (ie.don't try updating your radio, rom, & recovery all at the same time ).
Pretty much anything can be fixed as long as you got recovery working so don't stress too much. Best of luck and hope you get your phone working soon :good:
Still havn´t found a solution for my problem, but i think i´m on to something....
I think the problem with my phone is the boot.img.... i can´t flash it correctly...
Dont know what program to use or what file to download.... i tried openning a command list but i and type "fastboot flash boot boot.img" as i´ve seen on other posts but i always get "this is not known as an internal or external command, etc...."
What can i doooooooooooooo?!!!! going crazy with this
Hey buddy, stay calm haha. I had the exact same problem. The problem is that although you tried to flash it, you nee to have the boot.img and some files including fastboot.exe. All of the files you need and how to flash the rom are in a guide by glevitan. You can just google it.
Sent from my HTC Desire HD using xda app-developers app
TheJurgenp1 said:
Hey buddy, stay calm haha. I had the exact same problem. The problem is that although you tried to flash it, you nee to have the boot.img and some files including fastboot.exe. All of the files you need and how to flash the rom are in a guide by glevitan. You can just google it.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
I´m trying to keep my cool .... hehehe
the problem is just that... i already googled so many solutions an tried so many things i´m starting to loose hope...
I´m a noob when it comes to these things...
and the fact that english is not my native thong doesnt help either... there are some expressions i dont understand...
Do you still have the link to that solution you mentioned?
You need drivers. Install HTC Sync from the HTC website.
bananagranola said:
You need drivers. Install HTC Sync from the HTC website.
Click to expand...
Click to collapse
already done that... on clockwork recovery mode i can mount usb storage and have access to sd card... that means the drivers are ok... right?
also tried to instal fastboot on my pc but when i clic on the application it doesnt open the cmd window....
what else should i do?
You need to type fastboot from the cmd.
bananagranola said:
You need to type fastboot from the cmd.
Click to expand...
Click to collapse
already did but it wont recognize the command
Then your drivers aren't working. Uninstall and reinstall with the phone unplugged.
Hello, I recently flashed sphongle on my HTC ONE V, and it was working fine. I later installed gapps, which was also working fine (downloaded a few app and recovered my contact etc... using Titanium) for a while until I rebooted the phone. After this I could not get past the loading screen for sphongle. I do not know if Gapps was the issue, but I used version 20130301.
I then went to the my CWM recovery menu and did a factory reset, cleared the cache and tried restoring to the backup I made before I flashed the ROM. After doing this I could not get past the HTC menu. After doing all of this I now cannot access the bootmenu, it instead goes straight to the recovery menu when I hold down the power and volume down button as one would do to access the bootmenu. Because I can't access the bootmenu, I can't use an RUU.
If anyone has any suggestions or ideas I would be very happy.:fingers-crossed:
I'll try to answer any questions people have.
CWM is more trouble than its worth. it doesnt have a boot to bootloader option like twrp? you are in a fix without the ability to access hboot
No it doesn't have the option sadly.
Curtis1973 said:
you are in a fix without the ability to access hboot
Click to expand...
Click to collapse
Yep that's pretty much jist of it.
whick kernel are you using ?
I'm using HELLBOY-2013-06-29-4.2
Managed to figure it out myself.:victory:
nostalgickitty said:
Managed to figure it out myself.:victory:
Click to expand...
Click to collapse
im curious what you did to get back in to hboot. it may be something users may need to learn how to do if they ever encounter this issue.
24339642 120
Curtis1973 said:
im curious what you did to get back in to hboot. it may be something users may need to learn how to do if they ever encounter this issue.
Click to expand...
Click to collapse
Honestly It's pretty embarrassing, and shows my inexperience at this, but the whole time I tried booting to hboot, my phone was plugged into my computer. Once I unplugged it I could boot into hboot no problem. I guess this would be helpful for new users to know.