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/
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 unlocked my phone with the htc method. I had root, and superuser. titanium backup worked fine. I made a nandroid backup before I started messing with ROMS. I decided to flash infected's ROM first. Everything seemed to be going ok. It rebooted, and I got the cool beats animation. Then I got the htc splashscreen. then it just flipped back and forth between them for a half hour or so. something was obviously wrong. I tried rebooting the phone: same results. I can get into bootloader, both by holding volume down while powering up, and through the command prompt, via adb. I have a nandroid backup through twrp recovery, so no problem, right? well, it didn't work. So now, I can boot into the bootloader screen, but nothing else. I tried flashing a different ROM, but to no avail. Eventually, I noticed that I had htc sync running while I did all this. Did that wreck me? Any ideas what I can do now? I just tried to restore my nadroid backup again, without htc sync running, but all I get is a white htc screen. Please help me unbrick my phone!!!
whenever I try to flash ANY other rom, I get to the part where I have to use fastboot to flash the boot.img, and it says "sending boot" and just stays there forever.
Tried flashinf recovery.img, and the same thing happens. "sending recovery" and screen pause
God I hope someone smarter than me feels generous enough to help here...
Are you on windows? Did you install htc drivers?
Sent from my PG86100 using XDA App
I am on windows 7, and I have the htc drivers installed. Like I said, I successfully completed the htc unlock method. I had no problems until I tried to flash a rom
So you hold volume down and power to enter fastboot. Select fastboot by hitting power again. Then plugin usb and it should say fastboot usb. Then what command do you type after that?
Sent from my PG86100 using XDA App
now it wont even go into hboot. not with vol down and power, or through command prompt. before, it was going into hboot just fine, and I was using fastboot flash boot boot.img to flash the rom, but everything froze
now when I plug it in and use the command prompt to enter adb reboot bootloader, it just says device not found. holding power and vol does nothing
Hmmm.. Not sure why you can't get into fastboot but your using the wrong command. You want to type fastboot boot recovery.img. Recovery being the name of the recovery image in your folder.
Sent from my PG86100 using XDA App
thanks. I'll try that if I can get back into the bootloader
What you did works for that only installs the kernel. Then you need to flash the rom. I never did it that way nor do I use twrp
Sent from my PG86100 using XDA App
I did flash the rom.zip from twrp recovery. when it rebooted, it started to work, then just went into a boot loop. then I started trying to fix it, now it wont even come on
For now, I'm hoping that the battery just discharged during the process. I'm gonna let it charge for a few hours, and see what happens. I'm afraid that I might have done a battery pull in the middle of the process, though. When I first flashed the InfectedROM, the phone rebooted and got stuck in a loop between the beats graphics, and the htc quietly brilliant screen. it just kept going from one to the other. It went on for quite a while, and eventually, I think I pulled the battery to stop it. However, I was still able to get into the bootloader after this. I tried to reflash the rom, and a couple of others to no avail. When I decided to try to reflash recovery.img, is when it hit the fan, so to speak. after that, I was unable to boot into fastboot, or even get adb to recognize that there was a device there at all. Man, I hope letting the battery charge works. Like a moron, I don't have any insurance on my phone.
when I plug it in, windows intermittently makes the gong noise that something is connecting or disconnecting, and windows explorer briefly recognizes that a removeable drive is present, but I can't get the thing to charge, or turn on at all, and adb refuses to recognize that it connected, so I still cant manually put it into fastboot
well, I left the phone plugged in for about 7 hours. I hooked it up to the computer and once again tried to get into bootloader through adb. The computer said that the "daemon was started successfully" then goes right back to device not found. I guess Im screwed if no one else knows any tricks or ideas..
izzy spun said:
well, I left the phone plugged in for about 7 hours. I hooked it up to the computer and once again tried to get into bootloader through adb. The computer said that the "daemon was started successfully" then goes right back to device not found. I guess Im screwed if no one else knows any tricks or ideas..
Click to expand...
Click to collapse
Pull the battery
Wait 2 minutes.
Put battery back in.
Hold down Vol - and power.
Do not be connected to anything. And are you SURE your battery is good?
PM me if you see this and I dont answer.
I pulled the battery and waited. I even grabbed the battery out of my girl's evo3d. I can get into bootloader via the vol down, and power, but it stopas and asks if I want to update. If I say no, it just reboots to the htc screen. If I say yes, it says updating, then says press power to reboot. Then it goes directly to the htc screen and freezes. While it's in the htc screen, I can use command prompt to get it back into bootloader via the "adb reboot bootloader" command, but I can't get to my recovery menu. I was going to mount usb storage, and put another rom on the sd card, then re-flash, but it won't allow me to get to recovery
izzy spun said:
I pulled the battery and waited. I even grabbed the battery out of my girl's evo3d. I can get into bootloader via the vol down, and power, but it stopas and asks if I want to update. If I say no, it just reboots to the htc screen. If I say yes, it says updating, then says press power to reboot. Then it goes directly to the htc screen and freezes. While it's in the htc screen, I can use command prompt to get it back into bootloader via the "adb reboot bootloader" command, but I can't get to my recovery menu. I was going to mount usb storage, and put another rom on the sd card, then re-flash, but it won't allow me to get to recovery
Click to expand...
Click to collapse
Ok, soundslike you have a "PG86IMG.ZIP" on the root of your SD card. Dont worry, just swap cards with your old lady but put the ROM on it first.
You wont be able to do anything until you swap Sd cards or otherwise delete the PG86IMG.zip.
when I use command prompt to enter bootloader, I get the opening menu: bootloader, reboot, reboot booloader, and power down. If I press power to choose booloader rather than fastboot, the phone immediately goes back to asking me if I want to update, and no matter what I choose, the results are the same. it reboots to the htc screen
So I just used Bootmanager for the first time. I was having alot of issues so I rebooted and now it sits at the splash screen and it isn't going into the bootloader. Kind of freaked out.
What do I do to fix this?
Thanks.
are you s-on or s-off?
I'm S-off on 1.49
edit: sorry, I meant 1.40
If u can get to recovery, go to install zip and find the boot manager folder, look in there for a phone Rom folder, their will be an update.zip, flash it and reboot.
I can't get to the recovery. It wont even boot to the spash screen unless it's plugged in.
Pull the battery, put it back in, hold vol down and power, what happens?
Well if it's unplugged it wont do anything. But, if it's plugged in, it goes to the splash screen.
Plugged into what, ac power or USB to comp? Try taking out the sd card and then try vol down and power.
Either the usb to computer or AC. It does it for both.
Took out the sd, no change.
I haven't seen a prob like this, without hboot you'd never see the splash screen, it has to be there. Maybe leave the battery out for a few minutes then try holding vol down+power. If you can get to hboot then you're good but with no hboot your not so good.
Hmm, so my red charging led is blinking now while the phone is off, wasn't doing that before, any idea on what that means?
I know that when I drain my battery all the way till it shuts off, it won't charge and I get the blinking red led. I have to put in a spare battery and let the other sit for a few hours befor it'll charge.
What's it do when u just press power? Just goes to the white HTC screen and stays?
Yeah it does that, I'm wondering if there is something wrong with my vol down.
Does it feel like it "clicks"? Take the case off and try to press vol down+power.
edit..Lol, just tried it without the case and its not as easy as I thought.
It does click, I tried it without the case, it was working earlier today though. The last time I had it on, I was rebooting into recovery and the screen went black and just sat there, so I did a battery bull and that is where I am now, Would something have happened if I did a battery pull in that state?
I wouldn't think so... I've had to pull it in situations like that, generally you just don't want to pull the battery during an ruu update or a pg86img update, when its writing to certain partitions. What recovery are you using and what Rom did you try to flash with boot manager?
I'm using TWRP 2.0 and my phones rom was on mean rom. I put ics playground on slot 1 and was having alot of issues getting the phone to wake up and random freezes and crashes. I attempted to boot back to my phones rom but it wasn't doing it. So I attempted to flash Chads AnthaX ICS playground kernel and bootmanager crashed. so I decided I would just boot into recovery and do flash the update zip for bootmanager.
That is everything I did
brenstar said:
It does click, I tried it without the case, it was working earlier today though. The last time I had it on, I was rebooting into recovery and the screen went black and just sat there, so I did a battery bull and that is where I am now, Would something have happened if I did a battery pull in that state?
Click to expand...
Click to collapse
It just sounds like something weird happened to your recovery partition. If you pull out the battery and put it back in, then plug a usb cable into your computer. Do not turn it on. Run the command "adb reboot bootloader" (from your computer). that should turn on the phone and put it into the bootloader. From there, redownload your custom recovery of choice to your computer. Make sure you have a .img file. Type in "fastboot flash recovery [NAMEOFRECOVERYIMAGE].img". Now run your custom recovery and restore the update.zip for your ROM.
~co~
I'd be very surprised if your phone is broken. Sounds like an easy fix and I wish I could help more. You really can't do anything without getting to the hboot screen. No ruu, no turning s-on to re downgrade, no loading a recovery from fastboot.... I'm trying to think, maybe somebody else will jump in here and teach both of us somethin.
I know that a couple of other ppl had prob with a certain release of playground and twistedumbrella fixed them right up. Maybe you could hit him up. He's way more pro than I am.
My Amaze has been off for about a week or two and now it wont even power on.
If I press and hold the power button I get no indication that it is doing anything. However, if I press the buttons on the bottom of the screen I get a slight vibration indication that it is indeed getting power to it. Tried booting into recovery with no luck.
Any thoughts?
What recovery are you using? I know most recoveries don't support charging while off. I suggest 4EXT but you will need to charge the battery externally first in order to flash it. Good luck.
do you have an external battery charger to charge the battery out of the phone?
did you try to charge the battery ?
Here's an interesting update.
Was able to plug it in USB and using ADB restart into recovery. From recovery I hit restart and the phone booted up like normal.
BUT, about 5-10 seconds in Android it reboots again back to the black screen with the vibrating buttons. Had to run back to work so I wasn't able to play around with it anymore than that.
BiznessMan said:
Here's an interesting update.
Was able to plug it in USB and using ADB restart into recovery. From recovery I hit restart and the phone booted up like normal.
BUT, about 5-10 seconds in Android it reboots again back to the black screen with the vibrating buttons. Had to run back to work so I wasn't able to play around with it anymore than that.
Click to expand...
Click to collapse
if your running a custom rom maybe it got corrupted somehow, happens to my phone often due to the fact im trying to find a way around to cloning one rom to another phone, try to reset your phone back to stock by flashing a ruu stock rom or a different rom, flash 4EXT and wipe everything from the phone (including sd card) don't forget to check and realign the partitions and then toggle usb mode and put the rom on the sdcard and flash it , hope that helps
Ninjistix said:
if your running a custom rom maybe it got corrupted somehow, happens to my phone often due to the fact im trying to find a way around to cloning one rom to another phone, try to reset your phone back to stock by flashing a ruu stock rom or a different rom, flash 4EXT and wipe everything from the phone (including sd card) don't forget to check and realign the partitions and then toggle usb mode and put the rom on the sdcard and flash it , hope that helps
Click to expand...
Click to collapse
Thanks for the reply but I can't even get it to recognize via USB anymore
Buttons still vibrate, screen is still black. I can't get anything to work on it
BiznessMan said:
Thanks for the reply but I can't even get it to recognize via USB anymore
Buttons still vibrate, screen is still black. I can't get anything to work on it
Click to expand...
Click to collapse
Battery pull, hold volume down(or is it up? I work on too many android phones..) and power button and it should boot into bootloader. From there reboot into recovery. Flash a custom rom of your choice after doing a full wipe. Problem should be solved unless there is a hardware issue, at which point it must have been dropped, battery issue, etc..
What it really seems like is your battery doesn't have enough juice to sustain power, (I get bootloops when my battery goes really low and I try turning it on). Just let it charge a bit and if the battery isn't holding its charge, then time for a new battery
Sent from my Amaze using xda app-developers app
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.