Related
Help me please.
I had a HTC Dream I guess, flashed it with wrong ROM, which was made for HTC Hero.
From then on, the phone just doesn't work
1. I tried the recovery mode and reboot mode (Home + Power), (Home + Back) as well as Home + Camera. Nothing Works. It's still stuck at the startup screen <Black background shows white text says G1 T-Mobile.>
2. I tried pulling out the battery and put it back and tried to power it up. I retried the above step. Still the same.
3. I tried pulling out the SD Card as well and tried to power it up and retried the step # 1. Still the same.
I did try searching for similar posts but there are way too many and I have been digging them for the past 4 hours but couldn't find anything useful
Guys, Please share if anyone has any idea.
Thanks in advance
Steven
If home+power and camera+power don't work your phone is bricked.
also, post this in Q&A. this is either gonna get locked or moved.
and yes you are bricked.
You may not be bricked if you did not flash special spl or new radio, however, you will probably need fastboot/adb method.
Try searching, this has been addressed many times. Also try posting in right place next time too, although it will be a while since you've been a member since 2006 but this is your first post.
M..N said:
If home+power and camera+power don't work your phone is bricked.
Click to expand...
Click to collapse
What he said, but flashing a theme shouldnt brick your phone, only flashing an SPL or radio or something along those lines typically.
Please help, I was uninstalling some applications from my HTC PURE and had to restart the phone, when it was rebooting it hung at the ATT screen and there was small red text in the bottom left screen.
I had previously installed HardSPL 1.83 but relocked it via instructions in 2nd post because I'm still deciding if I wanna keep the phone and didn't wanna do anything for warrenty reasons.
I have the stock ROM and never installed anything except the HardSPL and the revert.
Please help me, I have tried to load the ATT Pure Stock/Shipped ROM I found here but everytime I try to in the bootloader mode it says either "no image file" or hangs at loading depending what I've tried to name the file. Also I've tried to run customruu.exe to install the stock ROM and also tried to install HardSPL 1.83 but it hangs at 0% and eventually wants to do recovery on the PC.
How do I fix this problem, and preferabbly get it back stock. I do have a warrenty, well unless I violated it by installing HardSPL then doing the revert.
Thanks
viper2g1 said:
Please help, I was uninstalling some applications from my HTC PURE and had to restart the phone, when it was rebooting it hung at the ATT screen and there was small red text in the bottom left screen.
I had previously installed HardSPL 1.83 but relocked it via instructions in 2nd post because I'm still deciding if I wanna keep the phone and didn't wanna do anything for warrenty reasons.
I have the stock ROM and never installed anything except the HardSPL and the revert.
Please help me, I have tried to load the ATT Pure Stock/Shipped ROM I found here but everytime I try to in the bootloader mode it says either "no image file" or hangs at loading depending what I've tried to name the file. Also I've tried to run customruu.exe to install the stock ROM and also tried to install HardSPL 1.83 but it hangs at 0% and eventually wants to do recovery on the PC.
How do I fix this problem, and preferabbly get it back stock. I do have a warrenty, well unless I violated it by installing HardSPL then doing the revert.
Thanks
Click to expand...
Click to collapse
Of course you hard reset?
Make sure your SD card is formatted to Fat32 and you may mant to try a different card, 2gb - 4gb.
What does your SPL say now in bootloader mode?
Yes I tried a hard reset. I can try another sd card the one I used was fat32 and 2gb. I believe it says 1.33 can't look now but I know it's not the same as an untouched pure.
Help!
You are not the only one who is having this issue. I am frustrated beyond frustrated. How are other people flashing their out of the box ATT Pures using the same exact steps but I can't? It's making no sense.
1. I turn off firewalls.
2. I've tried both usb and sd card boot, didnt work
3. I installed the enablerapi cab
Nothing works and I am having the same problem you are having...it stays on 0% forever and it doesnt even prompt me saying there is an error it just sits on 0% until I unplug it...
Help!
themasterhook2000 said:
You are not the only one who is having this issue. I am frustrated beyond frustrated. How are other people flashing their out of the box ATT Pures using the same exact steps but I can't? It's making no sense.
1. I turn off firewalls.
2. I've tried both usb and sd card boot, didnt work
3. I installed the enablerapi cab
Nothing works and I am having the same problem you are having...it stays on 0% forever and it doesnt even prompt me saying there is an error it just sits on 0% until I unplug it...
Help!
Click to expand...
Click to collapse
Are you trying to HSPL or flash a ROM?
Well
According to what i've read, you have to do Hard SPL before you flash a rom, so i've been trying to HardSPL and it doesn't work! I even tried to skip the step and just flash the rom and it doesnt work..
Now, I also have an ATT Tilt to and I JUST flashed a rom 30 mins ago, so it has nothing to do with firewalls or anything as far as my computer goes, I think its the phone, so what can I do?
How to flash HSPL.
themasterhook2000 said:
According to what i've read, you have to do Hard SPL before you flash a rom, so i've been trying to HardSPL and it doesn't work! I even tried to skip the step and just flash the rom and it doesnt work..
Now, I also have an ATT Tilt to and I JUST flashed a rom 30 mins ago, so it has nothing to do with firewalls or anything as far as my computer goes, I think its the phone, so what can I do?
Click to expand...
Click to collapse
Its a good thing flashing the ROM didn't work, you'd be bricked.
For flashing HSPL, it seems that newer phones are having an issue.
Something may have been changed that is preventing the unlocker from working.
Do the following;
1. Hard Reset
Instructions:
- Soft reset with stylus
- Hold Vol up & Vol dwn simultaneously until white screen appears
- Following screen prompts, Press Vol up to confirm.
2. Go to bootloader mode.
Instructions:
- Turn off your device using the power button
- When the device is turned off, simultaneously press the Vol dwn + Power button
- Your device will startup in Bootloader mode
Should say SPL: 1.33 or something.
3. Sync your phone to your PC.
4. Install enablerapinew.cab
5. Unzip both Topaz_CustomRUU_v1.1.zip & SPL_183.zip to the same folder
6. Run the CustomRUU.exe
This process should install HSPL and now when you enter bootloader mode you should see something like SPL: 1.83 Olinex.
If so, you're ready to start flashing custom ROMs.
If not, please report all errors to the HSPL thread or PM Olipro.
**I take no responsibility for any loss of data or functionality of your device.**
See, the problem with your instructions are...
1. You cannot soft reset with the stylus, I don't see a button anywhere on the phone ( ATT PURE not Diamond 2 )
2. Holding Vol up & Vol down simultaneously until white screen appears doesn't work. The only thing that works is when I hold Vol Down and the screen with the colors come up, not a white screen.
So i'm still lost. Thanks for your help regardless. I just really want to flash a new rom so I can stop using this stupid slow ATT rom.
So basically you are messing with your Pure and don't know how to soft reset?
Remove the stylus and in the groove for the stylus is a red dot, that is the red reset button. Insert the tip of the stylus in the red dot and push. Now the Pure will soft reset.
Probably should familiarize yourself with the device before you finish turning it into a brick!
Oh wow. That is so hidden.
On my Touch Pro 2 its right there on the side where you can see it, with words.
Anyway, Thank you very much, i'll try that.
Still, what about the Up and Down button volume button function so I can go into bootloader mode?
themasterhook2000 said:
On my Touch Pro 2 its right there on the side where you can see it, with words.
Anyway, Thank you very much, i'll try that.
Still, what about the Up and Down button volume button function so I can go into bootloader mode?
Click to expand...
Click to collapse
Now that you found the soft reset button.... follow my procedures.
Note- you have to hold the keys IMMEDIATELY after soft reset before the boot screen appears.
Ok.
Bruce Inman said:
Now that you found the soft reset button.... follow my procedures.
Note- you have to hold the keys IMMEDIATELY after soft reset before the boot screen appears.
Click to expand...
Click to collapse
Didn't work, I re-did the steps you listed 3 times over to make sure I was correct and the same results. I guess ATT has found a way to stop their phones from being unlocked.
Thank you for your help regardless.
themasterhook2000 said:
Didn't work, I re-did the steps you listed 3 times over to make sure I was correct and the same results. I guess ATT has found a way to stop their phones from being unlocked.
Thank you for your help regardless.
Click to expand...
Click to collapse
You should probably post over in the HSPL thread.
You'll get more help over there. There are many others having similar issues and there may be a fix over there.
FYI, when you get to the tri colored screen, that is where it shows what SPL you have currently.
Updating rom freeze
Hi, I don't post much if at all, normally you guys have it right on the button, this is my 3rd phone to run custom roms on but for some reason it just freezes on the "Updating ROM image on your PDA Phone..." screen and doesn't continue past, on my last 2 phones active sync worked well with updating to custom roms,seems like my Pure produces the same error after the attempt, its a communication error "ERROR [262] : UPDATE ERROR", now recovering from the error is not a issue, we all have familiarity in that area but I was wondering if it could be something as simple as the cable that was sent with my phone or if its possible to flash rom through sd card as opposed to using active sync?
drearystate said:
Hi, I don't post much if at all, normally you guys have it right on the button, this is my 3rd phone to run custom roms on but for some reason it just freezes on the "Updating ROM image on your PDA Phone..." screen and doesn't continue past, on my last 2 phones active sync worked well with updating to custom roms,seems like my Pure produces the same error after the attempt, its a communication error "ERROR [262] : UPDATE ERROR", now recovering from the error is not a issue, we all have familiarity in that area but I was wondering if it could be something as simple as the cable that was sent with my phone or if its possible to flash rom through sd card as opposed to using active sync?
Click to expand...
Click to collapse
Yes, you can flash through storage card, just rename the .nbh to TOPAIMG.nbh, Put in root of storage card and enter bootloader mode.
You have HSPL'd, right?
Bruce Inman said:
Yes, you can flash through storage card, just rename the .nbh to TOPAIMG.nbh, Put in root of storage card and enter bootloader mode.
You have HSPL'd, right?
Click to expand...
Click to collapse
I was just going through the thread. I have the same issue. i have place topaimg.nbh in the root of storage card and entered bootloade mode, it shows loading and is stuck at 0%.
HSPL is 1.83. Went through entire thread of HSPL but unfortunately didn't find any solution.
arun.ramachandra said:
I was just going through the thread. I have the same issue. i have place topaimg.nbh in the root of storage card and entered bootloade mode, it shows loading and is stuck at 0%.
HSPL is 1.83. Went through entire thread of HSPL but unfortunately didn't find any solution.
Click to expand...
Click to collapse
Just to confirm, you have to name it exactly "TOPAIMG.nbh".
With all of the people that have tried all methods and still can't flash, something must have changed in the stock SPL.
Hello people
Hello, did anybody found the way to flash HTC PURE , I have the same problem 0%
Thanks
same problems here
i have same problem with pure to.
coldun187 said:
Hello, did anybody found the way to flash HTC PURE , I have the same problem 0%
Thanks
Click to expand...
Click to collapse
From HTC site (HTC Pure support):
What is a Soft Reset and how is it performed?
A soft reset basically resets the memory structure in the handheld. This recovers the device from memory conflicts, corrupted system service chains (mainly due to attempting hacks), memory leaks, and system lockups due to the “Fatal Exception” program errors. Removing the battery from the device while it is still powered on is NOT a soft reset and can actually damage the device.
A Soft Reset is performed by:
Remove the Battery cover and the Stylus from the device.
Insert the tip of the stylus into the Reset hole located at the entry point of the stylus silo.
The device will reboot.
For the past few months I've been flashing separate Energy Roms onto my tilt 2. I finally found one that I liked and stuck with it for the past few weeks, which was the Dinik Glass Energy rom.
Everything was running great until last night when I was watching a video on You tube and everything froze up. I pulled the battery out and turned the phone back on and now it keeps going to the boot loader screen....
I've tried re flashing different roms to see if that would work but I've gotten nothing out of it.
If anyone could let me know of anything that i could possibly do to try and fix this I would be highly appreciative of it.
I dont know what may have caused the problem but in your situation i would have tried to do task29, flash radio and then flash a new ROM. this is normally how i flash my roms but task29 may remove somethin that may be causing the problem. if you have already done so, sorry for wasting 5 secs of your life ... let me know if it worked
Can you show me where I can dl task 29 at?
I had the same thing happen to my tilt2 last week!
Use task 29,
dont freak out when it only shows the screen that says touch pro 2.
Enter into bootloader and run ruu from there, it will fix everything.
Dont flash with sd card in or it will happen again.
I had to clear my sd card and reload it! good luck.
one more thing after task 29 do not disconnect from usb until you load next rom, that is what worked for me best.
hope it helps
I used the RUU and i tried reloading the ROM but it still starts in boot loader screen every time.
Should I just hit the hard reset?
you have nothing to loose by a hard reset at this point ... IF that works.
If I hard reset it will I have to flash a hard spl again?
Ok i noticed that yoy are pritty confused about the terminolog, so here is some help:
1. Task 29 - delets your rom of the phone so your phone become practicly unuseble.
2. HardSpl - "Unocks" (allowes) the phone for flashing custom made roms - i.e. all roms and ro preform Task 29.
3. Hard rest - reinstalls allready flashed rom.
4. Soft reset restart the phone - on/of
5. BOOTLOADER - allowes you to flash without activesync and from Sd card.
When any problem turns on with phene i usually check to see if there is any connection running. I discovered that too much internet over phone makes a phone buggy dissregarding the rom.
You dont have to hardspl phone again, once you did is enough.
Okay well here is the problem then... every time I turn the phone on it goes straight to bootloader. The only button I press to turn the phone on is the main power button. I've ran the custom RUU twice now. I've tried flashing a new rom onto the phone via sd card but it still turns on in bootloader mode. I'm nearly freaking out now because I'm led to believe I've got a bricked piece of $hit.
I hate sounding like a noob but if there is some way someone could run a step by step process to me that works I might through some $$ via pay pal.
Joe Mustard said:
Okay well here is the problem then... every time I turn the phone on it goes straight to bootloader. The only button I press to turn the phone on is the main power button. I've ran the custom RUU twice now. I've tried flashing a new rom onto the phone via sd card but it still turns on in bootloader mode. I'm nearly freaking out now because I'm led to believe I've got a bricked piece of $hit.
I hate sounding like a noob but if there is some way someone could run a step by step process to me that works I might through some $$ via pay pal.
Click to expand...
Click to collapse
I had the same problem with a phone about a month ago. I was able to flash the stock rom and it would boot up then put on the stock SPL and relock the phone. Sometimes I was able to take the battery out and get it to boot but even with the stock ROM I was getting the bootloader at startup. So once I reloaded the stock ROM and relocked it, I returned it and got a replacement.
Sorry, nothing I did every resolved the problem.
good luck.
I agree with taking everything back to stock
flash stock rom
do a spl relock
and start over...
oh, and dont forget about radios! idk if that could be part of the problem tho
I never changed the radio's so I should be good to go then, just the stock rom?
Try this :
- Enter bootloader
- Connect USB cable so "serial" in the bootloader changed to "USB"
- Perform Task29
- Reset
- If the phone enters bootloader skip this step. If not, hold volume down key while resetting (push the reset switch with stylus). The phone will enter bootloader.
- Flash a stock ROM. Download it from HTC website if you don't have one.
- Reboot.
Ow, the stock ROM also contains Radio. So Flashing with stock ROM will flash your radio also.
gabmurillo said:
I had the same problem with a phone about a month ago. I was able to flash the stock rom and it would boot up then put on the stock SPL and relock the phone. Sometimes I was able to take the battery out and get it to boot but even with the stock ROM I was getting the bootloader at startup. So once I reloaded the stock ROM and relocked it, I returned it and got a replacement.
Sorry, nothing I did every resolved the problem.
good luck.
Click to expand...
Click to collapse
When you returned your phone and got a replacement was your phone starting in boot loader?
If so how did the workers at the ATT store react to that so I know what to expect?
shadixs said:
Try this :
- Enter bootloader
- Connect USB cable so "serial" in the bootloader changed to "USB"
- Perform Task29
- Reset
- If the phone enters bootloader skip this step. If not, hold volume down key while resetting (push the reset switch with stylus). The phone will enter bootloader.
- Flash a stock ROM. Download it from HTC website if you don't have one.
- Reboot.
Ow, the stock ROM also contains Radio. So Flashing with stock ROM will flash your radio also.
Click to expand...
Click to collapse
How would you recommend that I flash the stock ROM back on?
I'm kind of confused because I've always flashed with my SD card, how do I do it through my USB? Could you give me a step by step?
Well, those steps I wrote are basically "step-by-step how to flash from usb".
Allow me to clear it:
- Enter bootloader -> Hold volume down button while pushing the reset switch
- Connect USB cable to your computer. and wait until the "serial" word in the bootloader changed to "USB"
- Perform Task29, download task29 and unzip it. run ROMUpdateUtility.exe. Follow the instruction.
- Reset/reboot. well, the phone will reboot itself after task29 is completed
- If the phone enters bootloader skip this step. If not, hold volume down key while resetting (push the reset switch with stylus). The phone will enter bootloader. Connect the usb cable again to your computer (if you disconnect it.) and wait until the word "serial" changed to "usb" again.
- Flash a stock ROM. Download it from HTC website if you don't have one. Just run the exe file you downloaded and follow the wizard.
- Reboot.
I reccomend you to flash with stock ROM because Stock ROMs are "Guaranteed to work(at least by HTC )" and contains radio that may be the cause of your problem. there's no need to flash to stock SPL, yet.
I was stuck in bootloader...
You can find task 29 here. I always do this before flashing.
After task 29, make sure USB is still plugged in and enter bootloader by holding Volume Down key while hitting the reset button. You should see USB on the bottom of the bootloader screen.
Now you should be able to flash the NRG ROM by running the RUU in the same folder as your ROM (rhodium.nbh file).
If this doesn't help, search the entire forum for "stuck in bootloader." I did this and it saved me the hassle of the warranty process.
Before
[/URL]
Joe Mustard said:
Can you show me where I can dl task 29 at?
Click to expand...
Click to collapse
Joe Mustard said:
When you returned your phone and got a replacement was your phone starting in boot loader?
If so how did the workers at the ATT store react to that so I know what to expect?
Click to expand...
Click to collapse
I was able to get it to boot to the ROM by removing the battery several times and reinserting, powering on until it boot. I am on TMobile and called them and they sent me a new phone and returned the old through the mail after expalining the problem. So never went into the store.
good luck.
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??
brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.
Hello everyone. In my attempt to experiment with custom ROMS yesterday, I seem to have sort of soft bricked my phone. When I install the stock OS, it installs fine, and I can start the phone. However, after it boots up, there are no apps. Just the clock at the top, the background, and the menu button in the bottom center (but pressing this button doesn't do anything). I can pull down the top menu and go to settings, but I don’t have access to anything else. Furthermore, after a couple minutes, the phone restarts itself. After this first restart, when its gets done booting, there is simply an empty black screen. The only way to get to the state mentioned before is to boot into bootloader, turn the phone off, and then turn it back on.
I’m wholly lost and out of ideas on how to go about troubleshooting this. Here is what I did yesterday to get to this point:
1. Unlocked the bootloader.
2. Flashed the latest Viper rom. It didn’t work; after booting up the phone was forever stuck on the Viper splash screen.
3. Flashed the stock Sprint HTC One rom. Again, after booting up the phone was forever stuck on the HTC splash screen.
4. Used TWRP to format all the data.
5. Flashed the stock Sprint HTC One rom again. This time it worked just fine. At this point, I thought I had discovered a valid method for fixing my soft bricked phone, so I decided to experiment with Viper and Android Revolutions roms to see if I could get them to work. I followed the process of installing a custom rom, getting stuck on the splash screen, formatting the data, then reinstalling the stock rom 3 times. On all three times the stock rom worked when I installed it. However, on the 4th iteration of this cycle, I reached the state I described above.
I tried using the RUU utility, but it doesn’t work (I get a signature verification error). I can enter bootloader and recovery without issue.
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
jclark11 said:
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
Click to expand...
Click to collapse
Do you mean you have had the same blank screen problam as well? Or RUU wouldn't work for you?
I'm pretty sure i relocked the bootloader when I tried doing the RUU, but I will definitely try again. Unfortunately, I'm on a trip at the moment, so I'm not sure when I'll be able to look at it again (hopefully Saturday or Tuesday).