Related
Hey folks, if any of you know me or have seen my posts, you know I only ASK questions when I'm in dire need. I've searched, and searched and haven't found the answers. So here are my questions:
I tried rooting my Sprint Hero (running 1.5) via Fresh Kitchen. I followed the steps, my phone rebooted. I had to take the battery out to get it to completely reload. However when I reloaded everything was exactly the same. I come from WinMo so I'm used to turning the phone back on and everything being a "Fresh" start. So I'm not sure if my phone was successfully rooted or not, and for some reason I can't find any info that gives a way to figure out if it has. So, how can I tell?
Also, if my phone has not been successfully rooted - I've recently switched to Ubuntu (yey) - and have been trying to follow these instructions to successfully root the phone ... with no success.
Any help is appreciated
One quick way I can think of is to try removing a system app that you don't want, maybe like Sprint Nascar or Amazon MP3. See this post here for how to do that. If you can remove a system app via adb, then you're rooted.
You could also just try rebooting into recovery. This will also show you if you have properly flashed a recovery image. Turn the phone off. Hold Home and then press Power. After a few seconds you should see the recovery console menu pop up instead of the regular HTC boot process. You can still reboot normally from here. Recovery is how you could wipe data and flash custom ROMs.
ok I just tried this (I did volume down, and held power), and this is what I see...
HERO XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009, 19:18:45
HBOOT
<VOL UP> FastBoot Mode
<BACK> Simlock
<HOME> Recovery
with 3 little android guys on skateboards
I pressed home, and got the HTC logo ... and the logo stayed on my screen until I took the battery out lol.
Looks like you don't have recovery then. Try rooting using THIS method....takes more steps, but its pretty much guaranteed to work unless you skip something or make a typo. And included in these steps are flashing a recovery image to your phone, then making a nandroid backup of your current setup.
chromiumleaf said:
Looks like you don't have recovery then. Try rooting using THIS method....takes more steps, but its pretty much guaranteed to work unless you skip something or make a typo. And included in these steps are flashing a recovery image to your phone, then making a nandroid backup of your current setup.
Click to expand...
Click to collapse
I'm not sure how to make this work on a linux OS, but I'll give it the good ol college try ... thanks!
Can a MOD lock/delete this thread I got it to work! Thank you Chromium leaf for all your help. I figured out that I was doing it correctly in linux. I have 1.5.2 NOT 1.6.2 which every set of instructions I found told me to type (slow moment).
I'm finally Rooted!!!! WHERE THOSE ROMS AT!
OK guys, Im not new to the android deal, or flashing, but im stuck here. I have a Sprint Hero, and I need to go back to stock. Problem is, the USB port is broken, and will only charge. So i cant enter ADB, and the phone wont boot past the HTC screen. Its rooted, and i still have root, and clockwork recovery. I cant seem to get any rom to flash though, it just hangs at the HTC screen, and I cant get the HBoot (version 1.47) to read anything. I tried renaming the extracted RUU from the sprint update to HERCIMG and it wont read it. So, anyone have any ideas???
Without usb or an s-off bootloader I think its impossible to go back to stock. Why do you need to?
can u get one of those USB SD card readers? (this way u can put ur SD card into ur computer USB port and transfer files onto it)
search around there is a HERCIMG from the ruu for HBOOT somewhere on here.
i looked real quick and found this, it may help.
moxlon69 said:
This isn't really the place for this, but these questions have already been covered, many many times..
Rooting instructions. I know this works on the latest official sprint, because I've done it successfully.
As far as not being able to RUU, some people have an issue running the RUU if they haven't ran HTC Sync. Try that and see if it works, and if not, follow this method.
HERCIMG-2.31.651.7.ZIP download it. it's the Sprint 2.31.651.7 executable but in signed zip format, for people who aren't running windows. Not sure who actually converted the executable to a signed zip, but props to you for helping those that can't run the regular RUU.
Rename the file to HERCIMG.zip and place it on the root of your SD card.
Power the phone off.
Press and hold your Volume Down button, and while still holding it press the power button to power your phone back up into HBoot mode.
HBoot should then automatically verify the zip file, and ask you if you would like
to flash it. Press your trackball to confirm the update (downgrade in this case),
or press your send button to cancel.
Once on 651.7 you would root as normal, but you should not have to RUU back to 651.7 just to root.
Click to expand...
Click to collapse
rodcpierce said:
OK guys, Im not new to the android deal, or flashing, but im stuck here. I have a Sprint Hero, and I need to go back to stock. Problem is, the USB port is broken, and will only charge. So i cant enter ADB, and the phone wont boot past the HTC screen. Its rooted, and i still have root, and clockwork recovery. I cant seem to get any rom to flash though, it just hangs at the HTC screen, and I cant get the HBoot (version 1.47) to read anything. I tried renaming the extracted RUU from the sprint update to HERCIMG and it wont read it. So, anyone have any ideas???
Click to expand...
Click to collapse
Just a thought, can you download the RUU onto the phone via dropbox or something similar?
Ok. I have an s off bootloader. I can't boot to any rom as it gets stuck at the htc screen. I have tried the above mentioned hercimg file (even though you cant open it, because it says the file is invalid, and I have downloaded it a number of times, so its not a download error) and hboot wont find it even after renaming. I can move files to the sd card via my computer. I have the adapter. I need to get back to something close to stock, so that i can activate the phone. I dont want to get the thread off topic though, just need help getting back there.
Check your computer's USB drivers. If you can charge it you should be able to use USB. Or use someone else's computer. Then running the ruu from HTC website will work just fine. This sounds more like the computers end then the phone. Ymmv.
®patience is a virtue©
If you are s off just flash a recovery from h boot. What bootloader version do you have?
Edit: also theres a link to an s off RUU in the links thread I started. Also, you never said why you wanted to unroot?
il, I dont even necessarilly need to unroot. But if people would please read the first post. It would help answer some of the questions.... I CAN FLASH ANY ROM, BUT NOTHING WILL BOOT PAST THE HTC SCREEN. It also says what bootloader version i have, its version 1.47. I have clockwork customer recovery version 2.5 I believe it is. HBOOT wont find any file, period. Including a recovery. And its not a computer issue, its with the USB. Trust me.
I used this when I RUU'd recently and it worked great. jasonmaloney put this up a while ago and this gem was in the middle of the thread. It broke root and I rerooted using Regaw's method this time.
H-boot should have no problem recognizing this.
Drunk, it wont read that either. It doesnt even recognize that there is a HERCIMG on the SD card. This phone is bunk. not even a week ago, it was booting AOSP rom fine, no issues. Then I went to turn it on the other day, and wont boot past the HTC screen. Not sure what the deal is with this POS. About ready to bounce it off the concrete here.
rodcpierce said:
il, I dont even necessarilly need to unroot. But if people would please read the first post. It would help answer some of the questions.... I CAN FLASH ANY ROM, BUT NOTHING WILL BOOT PAST THE HTC SCREEN. It also says what bootloader version i have, its version 1.47. I have clockwork customer recovery version 2.5 I believe it is. HBOOT wont find any file, period. Including a recovery. And its not a computer issue, its with the USB. Trust me.
Click to expand...
Click to collapse
Whoa, calm the F down. My phone isn't the broken one, it's yours. Anyway, I did read the OP, but it was real early, and I missed the 1.47. AFAIK hboot cannot fail IF you build the zip correctly. Pull out the SDcard and put this recovery zip on it, then flash from hboot. Do the device erase thing in fastboot before that. I just flashed it and it went fine. It's CWM 2.5.0.1. You will to rename it to "HERCIMG.zip". Also, were you using any other mods like FR or something? http://dl.dropbox.com/u/5669105/HERCIMG2501.zip
il, I have clockwork recovery 2.5. Ill try this though here in a minute and see what happens. This phone is just ticking me off something fierce.
Il, it wont find that either. I put the zip on the root of the SD, and renamed it to HERCIMG and HBOOT still doesnt recognize that there is a HERCIMG file on the SD
rodcpierce said:
Il, it wont find that either. I put the zip on the root of the SD, and renamed it to HERCIMG and HBOOT still doesnt recognize that there is a HERCIMG file on the SD
Click to expand...
Click to collapse
just to clarify, you named it HERCIMG.zip all caps and with .zip at the end? If so, maybe your card is bad or your reader in the phone is bad? Do you have another card you can try it on?
yes sir. HERCIMG.zip And its on the card, as when i boot into recovery, I can see the file there.
Man, if you can get into recovery you can fix it. Do a full wipe and flash a stable ROM, reboot, and then walk away from the phone for about 15 minutes.
Try the instructions at http://romrepo.info/wiki/index.php?title=Install_from_another_ROM
See, thats what I think too, but it wont do anything but boot to the HTC screen. I have tried quiet a few roms, and get the same thing. I just left for roughly 2 hours, came back and still stuck at the HTC boot screen. Im lost brother.
OK, just a quick update. Got it fixed with the help of laei1472. The recovery was botched, that was what was not letting me flash anything. Finally got it to boot one of AOSP's earlier roms (which was the last rom it had booted, before going haywire). Then we were trying to flash RA 1.7 through terminal, but it wouldnt find flash_image. Ended up finding a file to flash it as that version of AOSP was missing the flash_image file in /system/bin. Once we got that, then I was able to flash RA 1.7, and now can flash any rom I want too. What a pain in the butt experience. But happy the phone is back up and going. Thanks again laie1472.
good to hear. glad you got it fixed
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
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 my fellow friends in HTC Desire 626s Metro PCs land.
This is Isaiah speaking. I've run into a little misfortune here and I wanted to know if someone would be kind enough to help me out.
I have seemed to get myself in a little snag, were for some reason after I relock my phone, it won't reboot the system. What happens is, it boots right into download mode. So I unlocked it again and guess what. Everything booted normally.
Then I go to unlock it again, it jumps right back to download mode. I'm going bonkers over here, like Willy Wonka bonkers because i can't figure out why I can't relock my phone without it going right back to download mode. I flashed stock recovery through cmd, before I relocked it, that didn't work. All I did was root my phone. No debloated roms or anything. Just simply rooted my phone. I'm on Android 6.0.1. Somebody will you please help me get back to stock. Sigh, momma told there'd be days like this! Lol!!! I had to throw in a little humor.
I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.
Ace18o said:
I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.
Click to expand...
Click to collapse
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Ahh my bad, I was very tired last night.
s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.
Problem solved
IsaacGuti said:
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.
Click to expand...
Click to collapse
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:
s3llz said:
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:
Click to expand...
Click to collapse
By any chance, do you have the stock recovery link? I'm having the same issue :/
Sharkyzz said:
By any chance, do you have the stock recovery link? I'm having the same issue :/
Click to expand...
Click to collapse
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.
s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.