Related
I have tried everything. Holding volume up and power, down and power, both and power
Holding the whole time, letting go at the vibrant screen
I even did i factory reset and it wont work
Does anyone else have this issue?
It is going to ultimately force me to get a replacment device
I was wondering if there was somehing i missed
Sent from my SGH-T959 using XDA App
hold both volumes and power until you see the contact screen for the second time.
Sent from my SGH-T959 using XDA App
Same problem here. Spent a day trying to get it to work. Finally gave up and used the one click root method to get into recovery. This is my second Vibrant, so it's not that I haven't done this correctly before. Very strange, but one click worked for me.
Sent from my SGH-T959 using XDA App
The one click doesn't do anything
It puts the update.zip on my internal storage then doesn't reboot or anything
Would it still work through adb?
Sent from my SGH-T959 using XDA App
I've spent several hours trying to get into recovery and download mode via the buttons. I've tried everything I've found on the forums, and pretty much concluded that the US Vibrant is seeing the same issue that Bell Canada and Aus Optus is with some phones not having the power button reboot functional for whatever reason. I'm going to return mine tomorrow for one that works. Hopefully I don't get any static about trying them out till I find one that works properly.
ADB works fine for me to reboot to recovery and download. I personally would use TGA_Gunman's root.
Hey guys. I just bought a Vibrant today and am having this same issue. No matter how many times I hold either volume button independently (or even together), I can't get into Fastboot, or I guess Download mode as it's called here. I'm coming from a Nexus One where it works everytime, so this is kind of weird. Launching RomManager and selecting to boot into recovery does work, but I don't want to rely on that.
Is the smart thing to go swap the physical phone?
I am having the same problem with my Vibrant. Anyone figure out how to get it into recovery?
kas21 said:
I am having the same problem with my Vibrant. Anyone figure out how to get it into recovery?
Click to expand...
Click to collapse
As unpleasant as it may seem to do so, it really behooves you who are having those issues, (as am I with my 3rd replacement!!!) Vibrant, it is absolutely worth your while to set up ADB, for numerous reasons. It solves both of those issues and allows so many other options. Once you do the installation of the SDK on your PC and install the right drivers, it is not at all difficult to use it to do many important things much easier.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
just download quick boot from the app store and u can reboot, recovery, or bootloader ur phone with this app
rdunn20 said:
just download quick boot from the app store and u can reboot, recovery, or bootloader ur phone with this app
Click to expand...
Click to collapse
he means boot rom and hes right just download it from app store and click install clockrecovery and after that click reboot in recovery and your done.
The problem with relying on adb, Quick Boot, and Rom Manager is what are you going to do when you flash and your phone won't boot? You won't be able to get into download or recovery mode and you'll be hosed. Take the phone back while you can and get one that works.
Exactly. I'm curious if there's a way around this though. What is it
that actually causes the phone to boot into recovery with the hardware keys and is it something that can be fixed/flashed?
I already exchanged once within the thirty days and I don't think the 30 days gets reset. Think I'm past the return period now.
Sent from my SGH-T959 using XDA App
shootr said:
The problem with relying on adb, Quick Boot, and Rom Manager is what are you going to do when you flash and your phone won't boot? You won't be able to get into download or recovery mode and you'll be hosed. Take the phone back while you can and get one that works.
Click to expand...
Click to collapse
I'm so glad you wrote that. This is exactly my feeling. In ideal solutions, ADB or even installing a terminal emulator onto the phone is great. But for any dev who dabbles with modifying their phone in any way, having access to recovery directly from the phone is an absolute must.
Im having the same problem but let me ask could it be because Avatar is in the sd card?...I keep reading (NOW) that the Root zip files should be copy to a SD without Avatar....
Gusgom said:
Im having the same problem but let me ask could it be because Avatar is in the sd card?...I keep reading (NOW) that the Root zip files should be copy to a SD without Avatar....
Click to expand...
Click to collapse
There are two "SD" cards, an internal and external. The external one is the on that the user can swap. It also contains the Avatar movie (if it is the one that came with the phone).
The update.zip file should be copied to the internal SD card. The one WITHOUT the Avatar movie.
I also cannot get my phone to boot into recovery using the buttons. I rooted using one-click.
It seems to be an issue with new/replacement Vibrants. I have a thread about it here: http://forum.xda-developers.com/showthread.php?t=764360
If anyone has a device like this and can pull a dump file from it and upload it, that would be fantastic! I'm not sure if this is a physical limiter or a software based one, but I'm pretty sure it's software based on experience and manufacture dates. Once we get a dump, I'm sure someone will be able to figure it out.
And to back what the others said, I was able to adb download no problem, but when the Odin flash hung, there was no way to get back in to download mode and I ended up having to exchange the phone. As soon as my next one gets here, I'll test and post a dump if someone else hasn't already.
johnny12times said:
And to back what the others said, I was able to adb download no problem, but when the Odin flash hung, there was no way to get back in to download mode and I ended up having to exchange the phone.
Click to expand...
Click to collapse
I had the same issue on a replacement Vibrant and this works for me to get into download mode (even after Odin hung and it looked 100% dead):
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
dex1701 said:
I had the same issue on a replacement Vibrant and this works for me to get into download mode (even after Odin hung and it looked 100% dead):
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
Excellent directions. Worked like a charm.
OMG! I seriously thought my Vibrant was trashed! Excellent directions for getting your Vibrant out of Boot loop and into Download mode:
1. pull everything out of phone (battery, SIM, SD card)
2. Plug in USB cable
3. Hold down both volume buttons
4. Insert battery while holding down volume buttons.
My phone went into Download mode easily at this point.
In my case, my phone got stuck in Boot loop while trying to use ROM Manager for a new ROM. Guess I used it wrong, I'll just stick with installing ROM's by way of Recovery mode. Anyway, my phone stayed in Download mode until I flashed it with ODIN. I just flashed it back to stock and started over. Here's the link:
http://forum.xda-developers.com/showthread.php?t=734475
I'm so glad I didn't have to exchange my phone, I feel bad for those that had to exchange thier phones, this is a nice workaround.
i try it went into downloading screen. Odin did not see my phone. What can i do now? Can anyone help.
I used Rom Manager to apply an update to my DasBamf 2.0-beta5, and the phone reset but did not into Clockwork. Instead it got stuck in a boot loop.
I thought nothing of it, held down the volume button and went into the bootloader. Turns out I left a radio update on the root of my SD Card, so no biggie, I plugged the SD Card into my pc, removed the radio update file. I put the card back into my phone and now I cannot get into Clockwork!
Every time I get to bootloader, click recovery, then it goes into clockwork for a second, says:
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Can't Mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
What should I do? I do not have any idea what the issue is here!
Uhhhh flash a new rom... It appears clockworkmod is still partially useable
Sent from my ADR6400L using XDA Premium App
I wish it were that simple. Clockwork is unusable. After the error message appears, the phone reboots into a boot loop with the White HTC Logo.
Load the stock rooted ruu through the bootloader than reflash can in the stock ruu than reupdate to gb
Sent from my ADR6400L using XDA App
Can you boot into your ROM?
If so, the just reflash CWR via Rom Manager.
If not, grab a root stock RUU and flash that via HBOOT. Then download Rom Manager from the market, then reflash CWR.
Only bad thing about the second option is that you will loose /data.
I *think* there is a way to flash CWR via adb, but I'd have to look it up.
I feel really stupid because I thought I had a grasp on this whole thing...I got rooted without any trouble!!!
BUt I am not sure what is up at this point. I took the advice of those above, and loaded the stock rooted RUU through HBOOT (http://forum.androidcentral.com/thu...8597-ruu-return-rooted-stock-leaked-ruus.html).
- Put zip on SD-root folder
- Rename to PG05IMG.zip
- Boot into HBOOT
- Press Vol Up To start update
- Reboot phone
- Boot loop (never goes past the white HTC screen before resetting)
But afterwards I still am stuck in a boot loop! When I boot to recovery I get into CWR, and can move through the menus, but the phone reboots after a second or two (not enough to restore a backup).
Am I doing something wrong?
Sounds to me like the RUU didn't take when flashed via HBOOT. Is S-ON?
Try reflashing that RUU again.
If that doesn't work, try downloading and flashing another RUU. If all else fails, get the unrooted stock RUU. You might have to reroot but you will have a function device.
Damn. I really only trust stuff posted by Jcase, but all of his links are broken!!!
http://forum.xda-developers.com/showthread.php?p=13921164
http://forum.xda-developers.com/showthread.php?t=1082114
I have an idea what it is, my phone did this before after I walked in and out of a walk in freezer... Blah blah
Go into hboot and find the selection that says system info.or something along those lines and if it says touch panel - fail or something along those lines then it will.never boot up
Sent from my ADR6400L using XDA Premium App
I think thats ok!
TOUCH PANEL-ATMELC12_20aaT
OS Ver.-1.12.605.6
Dang well we know it's not a hardware failure
I would just try to.boot it.up after flashing a ruu and don't touch it for awhile and see if its just taking forever to boot
Sent from my ADR6400L using XDA Premium App
Well multiupload is back up! I will try some other RUUs
Any tips to charge the battery again though? I am fearful that I may have depleted it too far at this point, and plugging it in sends it into a boot loop!
The best thing is to do a battery pull and plug it in right after you put the battery in
It shouldn't boot up... But who knows I could be wrong
>--The Game--<
I have loaded multiple RUUs in an attempt to fix this...no luck
I followed the Jcase to return to stock for rooted users - I am now stuck with S-ON, but it does not boot still. Just the same old White HTC Screen.
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.
Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.
I hope that fixes it, but if it doesn't...
Well, it comes down to a question that you need to ask your self...
Do you continue down the path of trying to fix this device?
Or
Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?
If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.
Let us know what you want to do.
barcodelinux said:
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.
Click to expand...
Click to collapse
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.
Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.
Click to expand...
Click to collapse
I will try this tonight. I think that my battery is dead at this point. I can get it to reset to HBOOT (S-ON). I can click recovery. The stock recovery opens, and then within 5 seconds the phone resets. From this point (until I pull the battery), it will boot loop to factory recovery. Is this due to a dead battery? Every time I plug in my phone to my wall AC Adapter, the phone actually turns on and boot loops. Because of this I have not been able recharge it.
I hope that fixes it, but if it doesn't...
Well, it comes down to a question that you need to ask your self...
Do you continue down the path of trying to fix this device?
Or
Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?
If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.
Let us know what you want to do.
Click to expand...
Click to collapse
I have a replacement in the mail at this point, but I am willing to experiment in the meantime so that anyone in the future can avoid my problems!
vypurr said:
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.
Click to expand...
Click to collapse
You are not the first one to say that. While using a GUI front end to CWR is handy, it doesn't have a great track record.
I have gotten away from using Rom Manager for anything except flashing CWR.
But then again, I make it a habit to wipe /system, /data, and /cache before flashing a new ROM. You can't do that from Rom Manager.
Anyways, back to the topic...
The battery being in a low charge state wouldn't make the phone reboot (I wouldn't think). In the past when my battery has died, the phone never rebooted...it just turned off. However, I have never had the phone boot when I plugged up my wall charger either. (My old OG Droid used to do that and it pissed me off)
Has anyone else had this happen? If not, that might suggest a hardware malfunction of some sort too.
Was this phone dropped or does it have any kind of water damage?
At this point, I think it is a hardware failure of some sort. And chasing a hardware failure with a software fix is kind of a fruitless endeavor.
I know the phone has been babied its entire life (except for many many roms).
I remember that the phone used to turn on when CWR was first put onto the TB, but it should not do that stock, and it was cleared up with recent CWR updates.
I am just going to cut my losses and get the replacement that Verizon has offered me. Maybe I can have a couple more break and just get the Galaxy S2 when it lands!
Well I am not alone!!!
http://www.droid-life.com/2011/05/2...ght-want-to-consider-reverting-back-to-froyo/
I rooted my phone the other day using super one click 2.3 and left it just rooted due to cwm in my rom manager app not showing my phone model for whatever odd reason. Tonight I did the most stupidest thing and decided to pick nexus 4G in rom manager and downloaded CM10 ICS rom from rom manager itself and as soon it finished downloading I pressed install with dalvik cache wipe checked and now my phone is just stuck on boot screen that say "GALAXY S 4G exclusively from T-Mobile"
I tried to hard reset by pressing home/vol up,down/power button but the screen just goes black for about 3 seconds then the same "GALAXY S 4G exclusively from T-Mobile" screen come on and it just stay there. I also tried to plug in the phone to my laptop but the phone is not recognized anymore and nothing happens.
This is the only phone I have and I am lost. I really need my phone back. What do I need to do?
please HELP:crying:
CyberGmonster said:
I rooted my phone the other day using super one click 2.3 and left it just rooted due to cwm in my rom manager app not showing my phone model for whatever odd reason. Tonight I did the most stupidest thing and decided to pick nexus 4G in rom manager and downloaded CM10 ICS rom from rom manager itself and as soon it finished downloading I pressed install with dalvik cache wipe checked and now my phone is just stuck on boot screen that say "GALAXY S 4G exclusively from T-Mobile"
I tried to hard reset by pressing home/vol up,down/power button but the screen just goes black for about 3 seconds then the same "GALAXY S 4G exclusively from T-Mobile" screen come on and it just stay there. I also tried to plug in the phone to my laptop but the phone is not recognized anymore and nothing happens.
This is the only phone I have and I am lost. I really need my phone back. What do I need to do?
please HELP:crying:
Click to expand...
Click to collapse
Okay, okay relax and stay calm first and foremost. I assure you, we've all been there (at least I have been lol). Needless to say, it sounds like you can fix this...which is good! I suggest you first head over to this thread: http://forum.xda-developers.com/showthread.php?t=954509 and download the toolbox. Once its downloaded, install the necessary drivers if you have not already. After that, you need to get your phone into download mode. There are a few ways to do this, and people prefer going about it in different ways...I'd suggest taking out your battery, and then popping it back in and holding the power on and volume up button at the same time and hopefully it will boot into download mode (it'll be yellow). If that doesn't work after a few minutes, remove the battery again, pop it in and try holding the power, the volume up and the little "arrow up" soft key at the bottom of the screen and hopefully this time it will go into DL mode. Once you're in DL mode, connect your phone to the computer and use the toolbox to flash to stock. This will bring your phone back to factory conditions and you'll be set to go. Be sure not to remove your phone while its flashing back to stock until you are given the green light. Good luck!
Xenoism said:
Okay, okay relax and stay calm first and foremost. I assure you, we've all been there (at least I have been lol). Needless to say, it sounds like you can fix this...which is good! I suggest you first head over to this thread: http://forum.xda-developers.com/showthread.php?t=954509 and download the toolbox. Once its downloaded, install the necessary drivers if you have not already. After that, you need to get your phone into download mode. There are a few ways to do this, and people prefer going about it in different ways...I'd suggest taking out your battery, and then popping it back in and holding the power on and volume up button at the same time, once your screen turns on, remove your finger from the power button and continue holding the volume up button, and hopefully it will boot into download mode (it'll be yellow). If that doesn't work after a few minutes, remove the battery again, pop it in and try holding the power, the volume up and the little "arrow up" soft key at the bottom of the screen, when the screen comes on, let go of the power button and hopefully this time it will go into DL mode. Once you're in DL mode, connect your phone to the computer and use the toolbox to flash to stock. This will bring your phone back to factory conditions and you'll be set to go. Be sure not to remove your phone while its flashing back to stock until you are given the green light. Good luck!
Click to expand...
Click to collapse
Thanks for trying to help, but is not working. I tried both options multiple times but it would not go into DL mode. I can't believe I did this to my only phone
CyberGmonster said:
Thanks for trying to help, but is not working. I tried both options multiple times but it would not go into DL mode. I can't believe I did this to my only phone
Click to expand...
Click to collapse
Relax, relax...I assure you. Everything will be fine. Your phone isn't dead. Getting into DL mode can be a pain, and honestly it took me a few tries my first time also. You just need to find the correct combo. Try with phone off, holding volume up and down at the same time and then plug in the usb until the phone boots up into DL (hopefully). If this doesn't work, report back. If it does, go through the steps in my last post.
Xenoism said:
Relax, relax...I assure you. Everything will be fine. Your phone isn't dead. Getting into DL mode can be a pain, and honestly it took me a few tries my first time also. You just need to find the correct combo. Try with phone off, holding volume up and down at the same time and then plug in the usb until the phone boots up into DL (hopefully). If this doesn't work, report back. If it does, go through the steps in my last post.
Click to expand...
Click to collapse
Another thing to try, pull battery, SIM card and SD Card. Then plug in USB to computer, plug in to phone, pop the battery in holding down volume keys (up and down) -- its a little tricky but you get the hang of it. It was only consistent way my phone would go into DL mode.
Same Problem
CyberGmonster said:
I rooted my phone the other day using super one click 2.3 and left it just rooted due to cwm in my rom manager app not showing my phone model for whatever odd reason. Tonight I did the most stupidest thing and decided to pick nexus 4G in rom manager and downloaded CM10 ICS rom from rom manager itself and as soon it finished downloading I pressed install with dalvik cache wipe checked and now my phone is just stuck on boot screen that say "GALAXY S 4G exclusively from T-Mobile"
I tried to hard reset by pressing home/vol up,down/power button but the screen just goes black for about 3 seconds then the same "GALAXY S 4G exclusively from T-Mobile" screen come on and it just stay there. I also tried to plug in the phone to my laptop but the phone is not recognized anymore and nothing happens.
This is the only phone I have and I am lost. I really need my phone back. What do I need to do?
please HELP:crying:
Click to expand...
Click to collapse
I have almost the same problem.
Did you ever get the phone to go into DL mode?
TIA
Wrong forum. Go to galaxy s 4G forum.
Sent from my SGH-T959 using xda app-developers app
gknitz said:
I have almost the same problem.
Did you ever get the phone to go into DL mode?
TIA
Click to expand...
Click to collapse
What exactly is your problem? Please list your device model and what ROM or stock android version you were using when issue began. Any other info you have would be helpful.
Paranoid, sitting in a deep sweat...
samsgun357 said:
What exactly is your problem? Please list your device model and what ROM or stock android version you were using when issue began. Any other info you have would be helpful.
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
i rooted with superoneclick .... it couldnt verify shell but it rooted.... then i put a kernel on called sms-t959v-kj6-v0.1.0unsigned-update. then i tried to flash a rom called SamsungSlim-T959-4.2.1.Beta.1-OFFICIAL and thats where everything failed.... its stuck at the rom boot.... the screen says semaphore..... PLEASE PLEASE HELP.... I FELL LIKE IM DYING LOL MY EMAIL IS carlosts2009 at gmail.com.. or text 856 2 4 4 101 8
Your problem is the kernel is for the t959v galaxy s 4g and the ROM is for t959 vibrant. You can fix it in Odin with the stock firmware but we need to figure out which device you have. Do you have a stock front facing camera?
Sent from my SCH-I535 using xda premium
samsgun357 said:
What exactly is your problem? Please list your device model and what ROM or stock android version you were using when issue began. Any other info you have would be helpful.
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
im using a samsung galaxy s 4g running on gingerbread (the latest version for this phone) I got the instructions for how to root my phone from youtube and everything was good until today when it just got stuck on the boot screen. how can I fix this. I need a professionals assistance for this.
This is the Samsung vibrant t959 (3g). It looks like you have the Samsung galaxy s 4g t959v. These are totally different phones, you need the galaxy s 4g forums, these files for the vibrant will not work on your phone. Find the correct forum on xda website and flash back to stock for the t959v
Sent from my SGH-T959 using Tapatalk 2
If someone helped you, hit the thanks button!
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
I'm special
bdpope88 said:
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
Click to expand...
Click to collapse
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
bdpope88 said:
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was a, to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
Click to expand...
Click to collapse
LOL. Well done sir.
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
TugboatTony said:
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
Click to expand...
Click to collapse
Are you saying volume up + power button does not restart your phone nor does any help? Check if your phone is detected in computer and if so you can issue and adb reboot command
also since there is no removable battery HTC added a reboot function press home vol down and power that should do the trick
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Vol up + Power was the key. I was thinking it was volume down. Thanks for all your help
TugboatTony said:
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Click to expand...
Click to collapse
Its volume up mate + power not volume down
pradeepvizz said:
Its volume up mate + power not volume down
Click to expand...
Click to collapse
Hi Do you have a HTC one max stock Rom I could use??
Thanks
mini88448 said:
Hi Do you have a HTC one max stock Rom I could use??
Thanks
Click to expand...
Click to collapse
There have been lots of request for this, ill upload a stock rooted ROM soon.
pradeepvizz said:
There have been lots of request for this, ill upload a stock rooted ROM soon.
Click to expand...
Click to collapse
OMG THANK YOU SO MUCH!!!
:victory::victory::victory:
Just wanted to point out I ran into this issue also (Stuck on white HTC boot screen) after wiping my ROM and Vol UP + Power did the trick for me also (and then Vol Down + Power to get back to the bootloader).
i need help, guys
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Sounds like you're flashing the wrong TWRP.
Sent from my Galaxy Nexus using Tapatalk
suieitori said:
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Click to expand...
Click to collapse
May I suggest following these instructions?
http://forum.xda-developers.com/showpost.php?p=51753483&postcount=129
If you're able to complete those instructions outlined in that post, this should set you up with the latest HBOOT, Radio and TWRP (Recovery) for the Verizon HTC One.
Make sure you read the post fully before you start, especially this part:
fastboot flash zip firmware.zip (Be sure it finishes saying 'successful', not 'please flush again immediately'. If it says the flush again, rerun the command)
If you succeed in getting that done, see if TWRP still causes the phone to reboot and get back to us.