Hey guys,
I'll apologize in advance, since I'm sure I'm not the only one who's had this problem. I did try to use the search function, google, you name it. Didn't really come across any results that reflected my problem.
That all being said...
Tonight, my phone "died." I've been running Venom Viper XL for sometime now with no issues other than a pretty quick battery drain.
I was logging into 4square to check in tonight and I was getting a GPS error and a Wi-Fi disabled pop up. So I go into settings and check the Location stuff, turn the Google crap back on. Go back into 4square, same thing. I go back to the location settings, they were off again. Turned them back on. Saw that my wi-fi was enabled but "disconnected" so I disabled/enabled. Then my phone drops to the Viper XL splash screen. Tried to hold the power button to recycle it. HTC screen comes up, then to the Viper XL splash and stops. I tried a hard factory reset (volume down + power), same thing.
I can't get to anything. I plug it into my pc, can't get to anything.
I'm not sure what version of the Venom ROM I'm running. As far as I know, I haven't updated it in several months, even though something came out in September.
Am I stuck?
Firstly, volume down plus power isn't a factory reset, it's a hard reset. A factory reset is a very different thing. Have you tried flashing the ROM again or restoring a backup?
Sent from my Evita
timmaaa said:
Firstly, volume down plus power isn't a factory reset, it's a hard reset. A factory reset is a very different thing. Have you tried flashing the ROM again or restoring a backup?
Sent from my Evita
Click to expand...
Click to collapse
I just now was able to get into recovery. I'm running a back up and will go from there.
Thank you for responding though.
Ok, cool. In future you should probably exhaust possible options before creating a new thread though.
Sent from my Evita
timmaaa said:
Ok, cool. In future you should probably exhaust possible options before creating a new thread though.
Sent from my Evita
Click to expand...
Click to collapse
Like I said... I searched for a couple hours, so I thought I had. I can see how nearly every thread in here is pretty much started with "Search more." I didn't want to be one of those guys.
For anyone else reading that may have a similar issue:
As long as your phone turns on, you should be able to get to the bootloader. My problem was ignorance on this part, I didn't think I was able to.
1. Hold the power button + volume down until you get into the bootloader. I found that if I held these down, release when the screen went blank, then immediately pushed them down and held them, it got me into the bootloader.
2. Boot into recovery.
3. Take a back up of your stuff.
4. Re-install your ROM. If you don't have a copy of your ROM saved on your phone, plug your phone into your computer and mount your storage. This should make your phone storage available to your PC. Copy your ROM over to your phone, re-install.
5. Reboot. Though my phone was stuck in a restart loop after this. I initially did a reflash with the latest version of Viper XL without wiping. I went back into recovery and did a new install with a wipe. Problem solved.
6. Once you're sure your phone is back up and running, reboot into recovery and do a restore of your data from the back up you made earlier.
7. Enjoy having a phone again.
BigJanko said:
1. Hold the power button + volume down until you get into the bootloader. I found that if I held these down, release when the screen went blank, then immediately pushed them down and held them, it got me into the bootloader.
Click to expand...
Click to collapse
So many people are confused about how to get into bootloader. The main reason is that vol down needs to be held and not at any point released, until you get into bootloader. But the power button actually has to be released. The easiest way to accomplish this is:
- If the screen is on at all, hold both the power button and vol down until the capacitive buttons flash several times and the screen turns off. Once the screen is off, release the power button but keep holding vol down until you are in bootloader.
- If the screen is still black (or phone was powered off to begin with) simply keep holding vol down, and press the power button for a few seconds, then release it. But again, always holding vol down until the bootloader comes up.
If the phone boots normally, or goes to the boot splash, its almost always because you pressed vol down too late, or let go of it too early. As long as the screen comes on, failure to get into bootloader is almost always due to this user error.
People will often say "Press power and vol down" for bootloader. But this isn't really a complete and accurate description. And likely the reason why a lot of folks get confused.
Aside from this failure to get into bootloader, the remainder of your issue would have been easily solved if you had just originally had a nandroid on your phone. Recovering would have been as easy as:
1) Bootloader
2) Boot recovery
3) Restore nandroid
4) Keep on trucking
I'm surprised how so many people lately seem to be the practice of flashing ROMs or other mods without first making a nandroid backup. This to me is just a fundamental step in the process, and good basic practice. Failure to do so either signifies lack of knowledge, or doing mods in a careless fashion. Either way, its not good.
If you don't want the nandroid taking up all the space on the SD, I can understand that. In that case, have one on your PC that can be easily moved to your phone's SD in case of an emergency.
hi i was using my htc one x with viper xl but now i reset my system extsd cache everything .now when my device is on it shows me viper xl image alone so please kindly help me with this
kknaveenkk24 said:
hi i was using my htc one x with viper xl but now i reset my system extsd cache everything .now when my device is on it shows me viper xl image alone so please kindly help me with this
Click to expand...
Click to collapse
I think you have erased system and data partition too if u have done this you must have to flash viper Rom again
Related
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Dharkaron said:
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Click to expand...
Click to collapse
i tried and did not work
natienn said:
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Click to expand...
Click to collapse
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
andonnguyen said:
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
Click to expand...
Click to collapse
how do you flash to the original theme? do you know of any links? thanks
Start holding the Home button before you press the Power button.
jashsu said:
Start holding the Home button before you press the Power button.
Click to expand...
Click to collapse
i tried that in different time lentghs from 10 seconds holdin both to 2 minutes, of course pressing the home key 1 sec before the power and holding both
Same problem
Need to bump this thread as I'm having the same issue. Have a HTC Dream with CyanogenMod-5.0.7-DS, trying to go to 5.0.8, but cannot get into Recovery Mode.
Yes, I am completely powering the phone off, holding Home just prior to pressing & holding Power. I keep both depressed for a few minutes and no joy, just sits at the G1 splash screen. I can remove the battery and press Power to bring the phone up normally. Have even dropped to the console, switched to root and issued "reboot recovery". The phone restarts and sits at the G1 splash screen as well.
Can anyone offer advice on how to restore my Recovery Mode? Many thanks...
You can try to reflash (or flash another) recovery with adb, fastboot or in terminal. Btw this thread is in wrong section. It should be in Q & A section.
You could even flash a recovery image from within your rom...you said you could boot the phone normally correct?
So drop into terminal and flash it if you don't want to mess with adb.
The Amon Ra 1.7 Recovery thread has the commands you need to flash through terminal...
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
yutsoku said:
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
Click to expand...
Click to collapse
Why would you need to reroot it, just flash a new recovery through fastboot.
fastboot flash recovery <name>.img
misread, yeah he could do that too but it would be easier to reroot if he knows how to do that... instead of learning a whole new method.
You're right though, that would be better.
Update
I am able to fastboot by holding the camera button in and powering on. It sounds like I just need to do the Amon Ra Recovery procedure in order to restore my recovery partition. I assume that I'll need to re-root, but I'm sure there are instructions there for that as well.
Thanks for all the quick replies!
So here's what I found....
I had the exact same problem, but first a little history then how I fixed it.
I purchased an 8GB MicroSD card so I could use Apps2SD and was quite pleased with the ability to do so. Until my battery life dropped to 5mins. It was already down from when I bought it last year.
The battery was severely screwed on my. If I used ANYTHING for more than 5 mins, it would die and would NOT boot up. Oh I could pres the power button and it would try to boot but then die somewhere in the boot process. That is until I plugged it into some charger (car or wall) and then it would boot, showing anywhere from 70 to 90% battery life.
After much research I found that it was the battery and so ordered a replacement off eBay from Hong Kong. $3.96 shipped to my door. Works great, and I am incredibly thankful for that.
So just prior to getting the battery I had done an upgrade to 5.0.8 with the vain hopes that it might help limp along but to no avail. The battery was gone.
Ok, so in comes the new battery. Great! I'll just reflash the ROM to make sure there are no lingering issues and we'll be good to go! Little did I realize that I did an 'upgrade' from CM Updater and when I booted into Recovery I flashed th zip file that was there....which was 5.0.7. DOH! No biggie, everything was working so I didn't worry too much.
Then I installed Clockwork's ROM Manager 1.8.x. A few days later there was an update, so I updated to 2.0.1.3. So I updated that. It went fine.
Few days later, and a few more apps re-installed, the system was running slow.
Apps2SD was greyed out. Huh?
Checked the card....Ubuntu was only mounting it Read Only. And the old swap partition, which I thought I had deleted, was still there. Dammt. But this s a side story I think.
So I wanted to reflash but there was no way I could do it because I could not get into Recovery mode. Ugh.
ROM manager had an update to 2.0.1.4. Ok, maybe that'll work. Nope. It said it updated fine but stuck at G1 logo like many others.
Doing some googling around I saw that it was a ROM Manager issue and that you should flash back down to 1.4.x. Well, since I knew it was working at 1.8.x I decided to reflash to 2.0.0.3. I could get into recovery mode now!
While this kinda solves one issue....I'll have to go into another thread to figure out the Read Only problem so I can re-partition my card again.
Thread closed. Please post questions in the Questions and Answers forums and not in the development forum.
My phone never updated to the 2.2.1 I am still stuck on the 2.2. I called t mobile, but they didn't do much to help. Anyone know how to help?
Sent from my HTC Glacier using XDA App
Did you try *#*#checkin#*#* ?
Sent from my HTC Glacier using XDA App
joeman55 said:
My phone never updated to the 2.2.1 I am still stuck on the 2.2. I called t mobile, but they didn't do much to help. Anyone know how to help?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Method 1 - Update.zip
http://www.filedropper.com/update2
1. Put the file on the root of your sdcard and rename it to update.zip.
2. Turn off your phone.
3. Remove the battery.
4. Reinstall the battery.
5. Hold volume down + power until you get to a white screen.
6. Use the volume rocker to highlight FASTBOOT and press power to select.
7. Use the volume rocker highlight RECOVERY and press power to select. If you see an exclamation point instead of the blue menu, you might have to press volume up or down to get into the blue recovery menu.
8. Use the volume rocker to highlight and press power to select APPLY SDCARD UPDATE.ZIP.
9. DON'T TOUCH IT UNTIL IT'S DONE AND REBOOTS ON ITS OWN.
10. You should now be in 2.2.1 with all of your data preserved.
Method 2 - pd15img.zip
This procedure will completely erase ALL of your data but it is guaranteed to work.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
1. Put the file on the root of your sdcard and rename it to pd15img.zip.
2. Turn off your phone.
3. Remove the battery.
4. Reinstall the battery.
5. Hold volume down + power until you get to a white screen.
6. Let the phone "detect" the update. You might have to use the volume rocker to highlight the option and press the power button to select.
7. When the phone is ready, use the volume rocker to highlight and power button to select BEGIN UPDATE.
8. DON'T TOUCH IT UNTIL IT'S DONE AND REBOOTS ON ITS OWN. THIS MIGHT TAKE A WHILE.
9. You will now be on a clean install of Android 2.2.1. Enjoy.
Thank you Phateless!
I've just bricked my phone this afternoon, and been looking for some noob way for recovering it.
It is all because I rooted this phone and might delete some critical apks that caused my phone lost its desktop/main screen.
Doesn't PD15img kill WiFi?
If you read the How To Root. . . thread carefully you will see that PD15img is only partially 2.2.1 and more has to be added to get a full install of 2.2.1 with working WiFi.
After waiting more than a week for an automatic update after I got my phone, I tried the PD15img thing without reading all of the posts and only too late discovered that my WiFi didn't work and a lot more had to be done to get it back. And it appears that PD15img can't be undone. I had decided to take the phone back for an exchange but. . .
That very night TMo did an automatic update from my incomplete 2.2.1 to real 2.2.1, which fixed the problem.
I didn't get the phone from TMo directly and I never gave them my IMEI. I wonder if the automatic update was just luck or PD15img had something to do with it.
Thank you.. My phone hasn't been rooted yet, but I'll give that a try. I hope it's a full update.. That'd suck if my wifi didn't work...
Sent from my HTC Glacier using XDA App
raphael888 said:
Thank you Phateless!
I've just bricked my phone this afternoon, and been looking for some noob way for recovering it.
It is all because I rooted this phone and might delete some critical apks that caused my phone lost its desktop/main screen.
Click to expand...
Click to collapse
Glad I could help!
ecdy said:
If you read the How To Root. . . thread carefully you will see that PD15img is only partially 2.2.1 and more has to be added to get a full install of 2.2.1 with working WiFi.
After waiting more than a week for an automatic update after I got my phone, I tried the PD15img thing without reading all of the posts and only too late discovered that my WiFi didn't work and a lot more had to be done to get it back. And it appears that PD15img can't be undone. I had decided to take the phone back for an exchange but. . .
That very night TMo did an automatic update from my incomplete 2.2.1 to real 2.2.1, which fixed the problem.
I didn't get the phone from TMo directly and I never gave them my IMEI. I wonder if the automatic update was just luck or PD15img had something to do with it.
Click to expand...
Click to collapse
You're thinking of the OLD pd15img.zip that was part of the procedure to undo the OTA update. The one I linked to is the NEW one posted by Football that completely restores to 2.2.1 without issue. NEW radio, NEW SPL, NEW software.
I tested it on two different phones and everything worked perfectly.
You were thinking of this method.
http://forum.xda-developers.com/showthread.php?t=832642
I posted the file from this one. Ignore the part about gfree.
http://forum.xda-developers.com/showthread.php?t=863899
raphael888 said:
Thank you Phateless!
I've just bricked my phone this afternoon, and been looking for some noob way for recovering it.
It is all because I rooted this phone and might delete some critical apks that caused my phone lost its desktop/main screen.
Click to expand...
Click to collapse
If all you did was delete the wrong APK and it can be restored by flashing a stock image, it certainly is not bricked by any means.
TeeJay3800 said:
If all you did was delete the wrong APK and it can be restored by flashing a stock image, it certainly is not bricked by any means.
Click to expand...
Click to collapse
People definitely use that term way too loosely on xda... lol
NRGZ28 said:
People definitely use that term way too loosely on xda... lol
Click to expand...
Click to collapse
Most people don't know what brick even is they do something wrong and think they bricked it lol I remember in HD2 forum someone did BINFS format and didn't flash rom manually thought he bricked it cause he had no rom installed and only stuck on bootloader. So told him to just flash using LeoCustomRRU as he could do task29 and flash.
BTW NRGZ28 thanks for cooking NRG roms bro loved your 6.5.X work specially the whole 29XXX base as it was most stable and fast to bad HD2 is stolen.
ForceUpdate
I would check out these instructions
----> http://forum.xda-developers.com/showthread.php?t=843428
Hmmmm, NRG creeping around in a android thread....
Phateless said:
Method 1 - Update.zip
http://db.tt/oDkWb2k
1. Put the file on the root of your sdcard and rename it to update.zip.
2. Turn off your phone.
3. Remove the battery.
4. Reinstall the battery.
5. Hold volume down + power until you get to a white screen.
6. Use the volume rocker to highlight FASTBOOT and press power to select.
7. Use the volume rocker highlight RECOVERY and press power to select. If you see an exclamation point instead of the blue menu, you might have to press volume up or down to get into the blue recovery menu.
8. Use the volume rocker to highlight and press power to select APPLY SDCARD UPDATE.ZIP.
9. DON'T TOUCH IT UNTIL IT'S DONE AND REBOOTS ON ITS OWN.
10. You should now be in 2.2.1 with all of your data preserved.
Method 2 - pd15img.zip
This procedure will completely erase ALL of your data but it is guaranteed to work.
http://db.tt/peYZBi5
1. Put the file on the root of your sdcard and rename it to pd15img.zip.
2. Turn off your phone.
3. Remove the battery.
4. Reinstall the battery.
5. Hold volume down + power until you get to a white screen.
6. Let the phone "detect" the update. You might have to use the volume rocker to highlight the option and press the power button to select.
7. When the phone is ready, use the volume rocker to highlight and power button to select BEGIN UPDATE.
8. DON'T TOUCH IT UNTIL IT'S DONE AND REBOOTS ON ITS OWN. THIS MIGHT TAKE A WHILE.
9. You will now be on a clean install of Android 2.2.1. Enjoy.
Click to expand...
Click to collapse
I followed the guide you gave me since i was using an obsolete one and it worked perfectly. My phone says its on 2.2.1 but it doesnt feel like i am.... i remember after my update the market app was completely different, it has this half circle kind of look to it where it featured some popular apps. this version of 2.2.1 doesnt have that. is there any specific reason for that or am i missing something?
thanks again for your help!
The market update itself was a separate update "just to the market app" than 2.2.1. I had to force 2.2.1 on my phone early on; market came later. You should be able to find it in the apps/themes section, or just give it time and it should update itself.
Great post but I really need help.
I guess my phone is from some other batch or ... who know these chinese these days.
Anyways my menu is just different from described.
as folllows:
HBOOT screen
FASTBOOT (gets me to FASTBOOT screen)
RECOVERY (just give triangle makeing out with exclamation point)
FACTORY RESET
SIMLOCK
IMAGE CRC
FASTBOOT sreen
BOOTLOADER (gets me back to HBOOT screen)
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Don't really want to go with pd15img.zip route to preserve data. (So far)
Thanks
btw - I'm on Simple Mobile so no OTA for me
kb-evo said:
Great post but I really need help.
I guess my phone is from some other batch or ... who know these chinese these days.
Anyways my menu is just different from described.
as folllows:
HBOOT screen
FASTBOOT (gets me to FASTBOOT screen)
RECOVERY (just give triangle makeing out with exclamation point)
FACTORY RESET
SIMLOCK
IMAGE CRC
FASTBOOT sreen
BOOTLOADER (gets me back to HBOOT screen)
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Don't really want to go with pd15img.zip route to preserve data. (So far)
Thanks
btw - I'm on Simple Mobile so no OTA for me
Click to expand...
Click to collapse
I don't quite understand your issue here? Is it that you get stuck at the recovery screen with a triangle? Did you read step 7 of the previous posts clearly?
7. Use the volume rocker highlight RECOVERY and press power to select. If you see an exclamation point instead of the blue menu, you might have to press volume up or down to get into the blue recovery menu.
Ok, maybe this time it will post.
Thanks for your answer Genocaust
I'm noob so I'm trying everything that comes to my mind several times before bugging good people.
Somehow my menus seems to be different than expected. Anyways, right after hboot my first screen has following options:
* FASTBOOT
* RECOVERY
* FACTORY RESET
* SIMLOCK
* IMAGE CRC
Clicking on recovery gets me triangle/exclamation screen after several tries i managed to get blue menu by pressing VolumeUP and POWER simultaneously (just up or down does nothing at all).
there is apply update.zip but when clicked returns yellow message:
E:Can't open /cache/recovery/command
Invalid operation
and goes black and not responsive.
After waiting for say 20 min decided to pull battery. (phone works, still 2.2)
Tried above few times. Downloaded update file yet another time, even changed file name using file manager on the phone (i know).
I will appreciate any suggestions. I guess next step is pd15img.zip which I wanted to avoid or stay on 2.2
Phone is few days old and all stock
Thanks again
I need help getting the wife's phone out of safe mode. I rooted the phone and its on a stock rooted 2.2.1 rom and if you do a restart it loads the the boot loader screen and I can pick recovery and then restart but it still boots in to safe mode says it in the bottom left corner. She has apps and stuff on there so trying to get everything back but not really sure how to get this fixed. Also have pulled the battery out and still no luck going to safe mode. I guess if I can't get it fixed can I install a factory stock rom back on it to fix this? I know if I do she will lose everything. Just need the best option to get this fixed.
Thanks
"Safe mode"???? I've never heard of that.
Yeah it the bottom left corner of the phone it says safe mode it says it down near the home icon and over top off the circle with the up arrow. It looks like it may only load mainly core apps and some others but not all kind of like a windows pc in safe mode. And like I said I've pulled the battery out and rebooted and still says it and also from the boot loader screen picked recovery and then restart and once booted it still says it in the bottom left corner.
I gotta ask... Are you sure this is an Inspire?
Yes this is a inspire. I'm at work and once I get home I will use my inspire and take a pic of the screen with it saying it and upload it here. Mine I just got and haven't rooted it yet still a little unsure on the new way so you may see some questions from me on it a little later.
I have seen people stuck in safe mode . The guy was stuck in hboot and would not boot up. somehow he managed to boot it up but he said it was in safe mode. he was going to flash the gingerbread ruu, but havent gotten an update.
you posted in the thread gene it was titled bricked.
as to the question isse here. you might have to flash a new rom, though not ideal. But google does a good job of backing up apps/settings
I'll be damned:
http://www.technipages.com/htc-hero-start-in-safe-mode.html
This seems more applicable to the Inspire:
http://www.myvusers.com/forums/htc-thunderbolt/7426-safe-mode-htc-thunderbolt-adr6400.html
I'll try and see if one of these works. I think I read some where about the hero and tried it but may not have. So will give it a shot.
Thanks
sreadesjr said:
I'll try and see if one of these works. I think I read some where about the hero and tried it but may not have. So will give it a shot.
Thanks
Click to expand...
Click to collapse
Apparently the hero has a "hard" menu key. The Inspire does not so you have to ue a different "hard" key. I tried it and the thunderbolt method works for the Inspire (using VOL "hard" key).
It was mentioned over on #liberatedAria that you may have a stuck VOL-UP key so it goes into safe mode every time you boot.
Ok thanks Gene I'll try it for the thunderbolt method. Like you said the key maybe stuck. So when you powered back on you held power and vol up key and it turned safe mode off for you then? Just checking cause not sure if vol down does any thing or you always use the up vol.
sreadesjr said:
Ok thanks Gene I'll try it for the thunderbolt method. Like you said the key maybe stuck. So when you powered back on you held power and vol up key and it turned safe mode off for you then? Just checking cause not sure if vol down does any thing or you always use the up vol.
Click to expand...
Click to collapse
No, I just rebooted. That's why we thought the key might be stuck.
yeah I think it is the vol key stuck as soon as you try to turn phone on it just goes to hboot screen. Sense I do believe the volume key is stuck does anyone know how hard it would be to fix this problem? I'm sure I can order a new volume button on ebay but not sure that will fix the problem. I need to get it fixed so I can get it back to factory rom so I then can take it back to AT&T cause I do have insurance on the phone but don't believe they will take it back cause of it loading to the hboot screen menu.
Can anyone give me any suggestions on what to do to get this fixed? And would it be possible to use the stock rom or stock exe file to put it back to stock form to take it back to AT&T to get it repaired or can I repair this problem myself by ordering a new volume key off ebay.
You should try gene pooles s-on tool in the Dev section. Since you have insurance I would just have it replaced
Hi, i've got a big problem...
After a system crash i pull-out the battery and then pull-in to reset the device.
after that now when i turn on the telephone it remain stucked on the white screen with htc logo. tryed to factory reset but remain stucked after i press on it.
my htc has original rom. no modification. what can i do? i don't really want to spend 3 weeksfor htc assistance.
Thanks
Semi-bricked phone E:Can't mount /cache/recovery/command
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log
For everyone who Bricked their phone - Help prevent the others
[Guide] How to brick your Desire S
Have i to flash a stock rom? how can i do without remove warranty? in the case it does'nt work i have to take it to htc center
You probobly fried your EMMC chip when you removed your battery.
it would be best to return it in for repair.
I think you may have same problem with me before. No choice but to bring it to repair.
Sent from my HTC Desire S using XDA App
It was s-off before? Can you boot 2 recovery?
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
chris5s said:
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Same problem as topic poster, i,ve been messing a lot with custom roms on win 6.5 phones, but I havn´t done anything fancy on my Desire S , as to rooting or custom roms. (work phone!) Now I´m just curious as how I get a recovery going, when the PC doesent recognice the device when USB connected.
The eng-off file (mine is ON) with the .bat file cant connect to phone, and maybe im better off sending it to repair, but my pride wants me to solve it myself.
-Damn phone just went AWOL last night after an marked Angry Birds update, rebooted it a couple of times, because of a lot of process errors, and then all dead. (white HTC screen on -until morning)
Have the latest FOTA (DK, Nordic)
ROM: SAGA PVT SHIP S-ON RL
Hboot: 0,98.0002
Radio: 3805.06.02.03_M
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
psudo said:
Same problem as topic poster ....
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
Click to expand...
Click to collapse
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
chris5s said:
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
Click to expand...
Click to collapse
"ROM on SDcard": what format would that be in? RUU.exe or?
I can get into recovery menu (HBOOT) but chosing recovery option results in "a green recycle icon with an arrow on black background" screen, a few seconds then it virbrates 6-8 times, and then fades to black, so to speak!
Factory reset option: Locks the HBOOT screen and nothing but a battery pull, will change that.
I MAY have pulled the battery and not left it out for the 30 sec bricking danger senario, that I wasn´t aware of, until resently.
So the diag. is that is probably bricked!
Thanks for the reply
/Psudo
Rom on sdcard would have to be *.zip to be flashable. If you're unrooted + stock then you won't have Clockwork recovery or similar.
Tough that factory reset doesn't give any joy. These devices.....
Looking like masonry then, unless someone else can help.
Peace
Sent from my HTC Desire S using xda premium
surprisingly i got the same issue yesterday after i installed proxuser's official htc rom. Everything started fine went through setup so i assume it's not because of the rom because i don't think the phone would've started up in the first place. Anyway i am about to try and install some different roms and have also copied a backup over from my other desire s.
Will let you guys know if it worked.
Running CM 10.1, 06/08 Nightly
I did search the threads and google, but could not find any posts about a phone that works normally except for download and recovery.
Problems:
1. Can't boot into recovery (via apps, power menu, or manually). It gets to the boot logo, and then blank screen and resets. It will keep resetting trying to go into recovery (a battery pull will put it back to normal).
2. Can't stay in download mode. When I put the phone in download mode, it turns off after a couple seconds. I can't ODIN it if it keeps turning off.
3. Power button doesn't work properly (sometimes it works, most of the times it doesn't). Example: I press the power button to close the screen. No response. A few minutes later I might press it, and the screen will close, but come back on and this time with power menu. I took out the button to verify that it wasn't stuck, and tried pressing the actual button inside the phone with the stick. I can feel it click, but it still has the same problems. Pretty sure it's not a stuck button.
What's working:
-Everything else. If I let the phone boot normally, it loads perfectly fine and into cyanogenmod. No issues with voice/data, any apps, or instability. No battery issue. No lag. No crashes. The only issue is with the power button, and my inability to boot into recovery or go into download mode.
History:
-I was experiencing a random reboot problem (and power button issue) from an earlier nightly, and I waited a couple months for a more stable version. The CWM recovery for some reason only worked sometimes. When I did get it to work, I flashed RC5 (format and wipe data, dalvik, cache, factory reset, etc.), which fixed my reboot problem, but not my power button.
-I came across this thread: at plus.google(.com)104277415207525128383/posts/iAVpVPYqMtM and updated the radio, even though the RC5 fixed my random reboot.
-I did try flashing CWM, TWRP, and Stock recoveries (the latest ones, and from CWM/EZ recovery apps), but have not tried CWM Touch. It doesn't seem to matter, it won't boot into recovery.
Perceived Solution:
-I have a plan with Best Buy - I am considering smashing the phone and getting it replaced with a refurb, but would like to avoid that if possible.
Anyone have any ideas? I am okay with the phone as is, but I would like to be able to update CM or to another ROM in the future
Thanks for helping me out!
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
phospholipid1 said:
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
Click to expand...
Click to collapse
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
DarkMenace said:
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
Click to expand...
Click to collapse
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
phospholipid1 said:
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
Click to expand...
Click to collapse
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Thanks for responding, guys
rellomar said:
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
Click to expand...
Click to collapse
Yes, I did. This brings me back into download mode, at which the phone just turns off.
BadUsername said:
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the commands; they ended up just shutting the phone off.
Yeah, I did ponder the idea that even though the power button "clicked," it might not necessarily be working. I google searched "galaxy s 3 broken power button" and there was a video with a description where the guy mentioned something about the circuit always being switched "on"
But his phone experienced different symptoms than mine (because the circuit was always switched on, the phone actually restarted itself while in normal operation. This hasn't happened to me).
Is there an app for me to definitely determine which buttons are being registered as they are pressed? Similar to programs that tell you what buttons you're pressing on your keyboard.
I would take it back to Best Buy, but I just don't want to give them any reason to say it was my own fault since I rooted and put a custom ROM on it.
Haha, I'll dunk it in salt water in favor of smashing it
Thanks again for your suggestions and ideas :cyclops: