Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks
Related
...Brick an *UNROOTED* G1...?!
I attempted a soft factory reset (which I have done on many occasions previously successfully) but on this occasion I've run into the bootloop. Hitting Camera+Power button results in bootloop also.
One thing to mention is I removed my SD card before running the factory reset?
I've tried leaving the battery out over night and trying again in the morning.
I've tried placing the SD card back in and booting up the phone.
I've tried holding Home+Power to get into recovery but results in bootloop
I've tried holding Camera+Power to get into Bootloader but results in bootloop.
Any suggestions please?
Thanks!
No, this should not happen. With Bootloop do you mean there is just the G1 logo and nothing else, or does it get past the logo and reboots then?
Another thought, has this phone ever been rooted and unrooted again?
If you are still under warranty and the phone is completely stock, I'd return it.
Nope. Phone has never been rooted then unrooted.
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Warranty is only for a single year, right? So then that's not an option.
Thanks for suggestions.
Jignesh Sutar said:
Warranty is only for a single year, right? So then that's not an option.
Click to expand...
Click to collapse
Depends on where you are: http://www.htc.com/www/support/warranty.html
It looks like you phone either fails to boot, thus tries to boot recovery (box picture is the background of the recovery) and then reboots (best case, i guess) or the boot to recovery flag is set, recovery fails, reboot (you might seriously be screwed).
You are sure that you can't enter the bootloader? Also try Back+PowerOn. That would make things alot more easy.
How long does it stay with the box picture? Long enough to get adb connected? If yes you could try "adb shell reboot bootloader".
Tried all combinations of buttons to try get into bootloader or recovery, nothing!
Definitely no chance of being able to ADB, the phone switches off very quickly...
Also, have ensured the battery is fully charged, in case that has an impact?
I really looks like you are the first all stock bricked guy I ever heard of.
The boot recovery flag seems to be set for some reason (is this set during a normal hardreset?) as all boottime commands are ignored.
The recovery fails improperly (sounds strange, but if it failed properly, you would end up in bootloader or your system).
-> That really looks like a brick...
Options:
- Warrenty
- JTAG
- perhaps someone else has another idea / sees something I missed...
Good luck with it.
Jignesh Sutar said:
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Click to expand...
Click to collapse
What where you flashing? It probably had a radio and something got copied incorrectly into the staging area of ram.. if the radio passes recovery's validation but not the current radios validation you can get stuck.. this shouldn't be possible but I've seen it before.. my bet is a bit error at the wrong point in time.
First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
I haven't touched my Rogers G1 rom, it is as stock as they come. One day the battery died, so I plugged the phone to charge and also tried to start it up.
My problem started after that.
I will try to restart the phone and it'll get stuck on boot screen - where it says HTC or sometimes even just the Rogers screen.
Only solution is to take battery out, do hard reset.
I've searched the forums but everybody else asks regarding modded roms and not stock.
Any idea how I could resolve this issue without flashing new roms? Or is that my only way out?
Thanks.
Did you apply Rogers mandatory 911 update that was released about a year ago? You can check by booting into fastboot mode (hold the camera button while powering it on). If your radio version is 3.22.26.17 you have the update. Rogers locked down fastboot in this latest update and the only way to root it is through the ROM. If you don't have this update I can walk you though the steps to root your phone though fastboot.
Just checked and it does have the update.
Should I just go ahead and flash new roms?
I keep having the same issue as before.
With the latest update Rogers locked down fastboot so it is useless. So, I don't believe that there is any way to flash a new ROM without first booting into your existing ROM.
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
JiggyNS said:
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
Click to expand...
Click to collapse
I'm not completely sure, but usually you need to be able to get into the rom to root. Maybe there is another way.
6 hours later and i got nowhere...
I rooted phone, flashed new cyanogen rom, setup amon ra's recovery but I didn't do new radio since my current is one of the newer ones.
The booting goes nowhere as soon as the rogers logo shows at the beginning of boot up.
Would a new radio help? Could that be the issue?
edit:
The phone rebooted properly and now I have a working fone!
Wait, how did you root the phone without getting into the ROM?
beav_35 said:
Wait, how did you root the phone without getting into the ROM?
Click to expand...
Click to collapse
I used the Androot method, copied onto sd card, launched file via file manager app on phone and it rooted the phone. This is how I remember anyways - I fiddled with the phone for good part of the afternoon so my memory is all over the place with the specifics.
I used this site for rooting.
I thought you said in the op that you couldn't boot into the ROM (got stuck on boot screen). So, what was the problem in the first place? (or how did you fix the ROM?)
Sorry I guess I wasn't clear enough in op.
The only way I could get to use the phone was to do a hard reset and let the phone boot up from there, however if I ever wanted to turn the phone off or restart the phone it would get stuck on the next boot up.
I was able to flash the rom by constantly hard reseting the phone every time I needed to put files onto the memory card.
I've been having trouble with my Vibrant and with T-Mobile in limbo I picked up a N1 off ebay to hold me over. This thing is driving me insane!
The phone came with CM7 installed on it, but the person that shipped it to me didn't erase any of there stuff so I figured I would flash a fresh image on the phone to take care of things. I've flashed my Vibrant a dozen or so times and never had an issue. Flashed the N1 and it comes up with an X made of 4 different colored lines and a little lock at the bottom. I know some roms take a while to load so I let it sit for an hour. Nothing.
Since I've been trying everything I can find out how to recover the phone including all of the guides on the wiki. I'm at my wits end at this point. I can't get into clockwork at all on the phone. It gets stuck in the bootloader and if I select recovery it just takes me back.
I've got droid explorer running, and the phone shows up, but it doesn't show anything on the phone, no folders or files and won't let me load anything on to it. (it says it is, but then stays blank) I have no clue what to do at this point short of taking a sledge hammer to it. (obviously I'm posting this as I consider that to be plan B)
I don't need anything special, I just want a working phone. Is that really so much to ask for?
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
danger-rat said:
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
Click to expand...
Click to collapse
I'm sure I haven't, just what I found in the wiki
I tried the PASSIMG.ZIP and it failed
I tried Amon_Ra's Recovery and the only way I can get it to do anything is to tell it to flash in droid explorer and it just reboots and gets stuck. Now nothing is showing up file wise in droid explorer and I can't transfer the image onto the root.
When I could get into clockwork I tried flashing different roms but it would just go to a screen with the clockwork logo and get stuck.
amolji said:
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Click to expand...
Click to collapse
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
n25philly said:
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
Click to expand...
Click to collapse
in the bootloader I think (dont take my rookie rooting words too serious) theres a hard reset menu under recovery. it will take you to another x and press volume up and power for the menu to pop up.
try fastboot a recovery image (either Amon Ra or CWM) and see if you can get back to recovery after that.
Well I'm assuming you already have a custom recovery since it came with CM and you've, as you said, flashed it (what exactly do you mean by that by the way? flashed another rom?). So all I can recommend is that you wipe a few times and try flashing a few different roms and hopefully one will boot. Not the best advice in the world but its always worked for me before and my N1 and my DEXT before hand when I've messed them up!
You still did not say what you flashed to your phone.
Anyways follow the restore to stock guide.
I don't know what this Droid manager thing is but don't use it. Install the sdk.....
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.