need assistance please - Verizon HTC One (M9)

I unlocked with sunshine, got twrp going, tried to flash supersu, but when i rebooted phone just hung at verizon screen. I have recovery, download mode, just no OS. Any advice is greatly appreciated.

mikelikesbikes said:
I unlocked with sunshine, got twrp going, tried to flash supersu, but when i rebooted phone just hung at verizon screen. I have recovery, download mode, just no OS. Any advice is greatly appreciated.
Click to expand...
Click to collapse
Flash supersu 2.65 and nothing else to root.
Sent from my XT1575 using Tapatalk

dottat said:
Flash supersu 2.65 and nothing else to root.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
You are right again. I see now what I did, I flashed the LP .apk causing it to hang on the Verizon screen. Downloaded the MM .apk on the laptop, put it on an SD card, put it in my phone, flashed it and it booted right up. I must just be rusty or something.
Another question though, is the RUU what's used to unbrick? Do I need a special version of fastboot cause I couldn't flash one the other day when I tried.
Sent from my HTC6535LVW using XDA-Developers mobile app

mikelikesbikes said:
You are right again. I see now what I did, I flashed the LP .apk causing it to hang on the Verizon screen. Downloaded the MM .apk on the laptop, put it on an SD card, put it in my phone, flashed it and it booted right up. I must just be rusty or something.
Another question though, is the RUU what's used to unbrick? Do I need a special version of fastboot cause I couldn't flash one the other day when I tried.
Sent from my HTC6535LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
I always use htc_fastboot. I have it posted in a couple of my threads around here. It knows how to handle the split system chunks.
Sent from my XT1575 using Tapatalk

How did you get recovery? It's not copying over in download mode. I just get "waiting for device".

dragonrazorz said:
How did you get recovery? It's not copying over in download mode. I just get "waiting for device".
Click to expand...
Click to collapse
Probably either driver issue if on windows, permission issue if on linux (run as root or fix udev rules), bad usb cable, or potentially wonky usb port. In that order.

jcase said:
Probably either driver issue if on windows, permission issue if on linux (run as root or fix udev rules), bad usb cable, or potentially wonky usb port. In that order.
Click to expand...
Click to collapse
I overlooked the HTC Drivers. I can boot to twrp now. I went and installed the supersu zip for root, but now im stuck on verizon boot...

dragonrazorz said:
I overlooked the HTC Drivers. I can boot to twrp now. I went and installed the supersu zip for root, but now im stuck on verizon boot...
Click to expand...
Click to collapse
Which supersu did you flash?

Okay, I was doing all of this last night about 4am. That was probably my whole issue because I somehow had "BETA-SuperSU-v2.48" downloaded. Then I downloaded and flashed the latest 2.71 and that boot looped longer than I though it should. I download 2.64 and I'm up and running.
Thank you!

Related

Bricked or not bricked?

I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Were you using CM7 before your phone started bootlooping?
Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?
Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.
teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk
Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button

Major problems! Phone completely bricked nothing is fixing! Please help

I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.
I tried to boot again but was freezing at the HTC boot screen.
I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)
Ive tried everything from flashing RUU to new HBOOTS, nothing is working.
Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.
Im two seconds away from smashing this with a sledgehammer.
I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Yes, when i go to install it, it does a few things.
It p****s the zip
bypasses the bootload
and freezes at boot saying updating and at the bottom is says can not roll back hboot version.
Its been at this screen for about 45 minutes THIS TIME
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide
The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.
________________________________
Easy as 3.1415926536
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
sjpritch25 said:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
Click to expand...
Click to collapse
I did??
Sent from Kangdemnation
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
this is what it should look like.
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
Lol I think he had just looked at your contact picture. They look very similar at a glance
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
CondemnedSoul said:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
Click to expand...
Click to collapse
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.
My phone recognizes it in fastboot but not adb.
I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The download links in this do not work or else id try that too.
Try it
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
flydoug9 said:
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
Click to expand...
Click to collapse
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
TheValk said:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
Click to expand...
Click to collapse
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.
Have you tried doing anything in fast boot like wiping data and cache?
Sent from my Incredible 2 using xda premium

[Q] Help to fix my phone

I used a video to unroot my phone and now it will not come out of boot mode, I turn it on it acts like it is booting up but never does just stays in the same position. and when I try to go into fastboot mode I get an error, it shows an android laying down and a red triangle over him how do I fix this? PLEASE HELP
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
I will try this, but I am not sure that the computer is reading the phone, I can get odin to work but it is not helping I tried putting stock files using odin but same thing. when i tried cmd and fastboot devices it brings up nothing
when I plug my phone in my computer does not recognize it, now what do I do?
Zepius said:
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
pamelak38 said:
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
Click to expand...
Click to collapse
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
pamelak38 said:
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
Click to expand...
Click to collapse
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
pamelak38 said:
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
Click to expand...
Click to collapse
Lte radio? Anyway if your connection is ok I'd say it's not an issue.
Good you figured it out.
Sent from my Galaxy Nexus using Tapatalk 2
still cant get into recovery mode
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
pamelak38 said:
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
Click to expand...
Click to collapse
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
pamelak38 said:
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
Click to expand...
Click to collapse
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes I have root, now what do I need to do?
pamelak38 said:
Yes I have root, now what do I need to do?
Click to expand...
Click to collapse
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I got it back to stock and locked, THANK YOU so much you are awesome!!!!

[Q] Bricked GNex?

I was doing a lot websurfing and the phone got hot but didn't think much of it. Then my screen imagine became distorted and a loud noise came out of the speaker. I had never seen it before. I figured the phone crashed. The power button didn't work, so I removed the battery and put it back in. Now the phone can't get past the "Google" screen (which blurs after a few moments). My phone is unlocked and rooted. It's been so long since I've flashed my phone that I don't know if the usb debugging is turned on and here's where my problem lays. I can't get the phone to be recognized by any of my computers. I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Anyone have any ideas on how to fix this?
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Man_Utd said:
I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Click to expand...
Click to collapse
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
savagehax said:
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can boot into CWM, but there is no option to flash or wipe. All I see is one line of text. That's it.
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
I think it is bettER to uninstall the drivers you have already, and try another USB port. Did you try that as well?
Download the galaxy Nexus toolkit and that will apply the stock image vai google. You can restore your phone from scratch back to stock.
Sent from my Galaxy Nexus using Tapatalk 2
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I figured out why my computer couldn't see the phone. The USB cable was bad. It charged the phone, so I assumed it worked. Tried another cable and now the computer sees the device. Stupid cable!
So, I got going using fastboot but now I have another problem. I can connect to the phone and my computer sees it, but when I try a flash command like "fastboot flash bootloader bootloader.img", I get "Failed (status read failed (Too many links))". I've been doing some reading and see this is not a good thing.
I haven't tried Odin, because I read in another post by efrant, not to use Odin if I'm getting the "Failed (status..."
I probably have a hardware issue, right? Any suggestions?
Thanks to everyone for their input!!!
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Man_Utd said:
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Click to expand...
Click to collapse
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
ahmadallica said:
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
Click to expand...
Click to collapse
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Man_Utd said:
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Click to expand...
Click to collapse
Well, I searched for that error and found this thread. I checked it quickly and there are many suggestions up there to solve the issue like changing the cable, ports, and so on. So please take some time to read through it and try the various solutions so hopefully this error will be solved
I too have had issues with cables. Never that same error but I've had read and write errors. I've resorted to using a 3yr old Motorola Droid power cable because it seems to be built the best. I've also had success using different ports and computers.
Also instead of updating the drivers to the newest try deleting the device out if device manager and rebooting and then installing the device new. That has fixed a "hardware component ID" error I had
Sent from my Nexus 7 using Tapatalk HD

[HOW-TO] Guide to Debloated, S-OFF'd, Rooted HTC One with Wireless Tether Support

I'm writing this short little post to give an idea of a good starting point for the HTC One as it stands right now. There are a lot of threads and they get out-of-date quickly (just as this one will). I just picked-up my new HTC One on Tuesday of last week from a Verizon store. This just gives a fresh idea of what can be done to get started on it.
Obviously you're running these instructions at your own risk. I'm not responsible for you bricking or otherwise damaging your phone. Doing these things may (will) void your warranty and may prevent you from being able to return your phone. Run these things at your own risk.
AN IMPORTANT PUBLIC SERVICE MESSAGE: When you get your phone out-of-the-box, it's probably going to offer you an OTA update. I recommend that you do not accept an OTAs as this usually makes this process even harder than it has to be. Verizon hates having us enjoy our devices!
First, let me describe my goals here:
Unlock the bootloader and obtain S-OFF
Install a custom recovery (CWM)
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
Get wireless tether working without jumping through tons of hoops.
I'll go through the list and just describe what I did:
Unlock the bootloader and obtain S-OFF
This was fairly straightforward. Rumrunner has an excellent package that does this very easily. I checked my phone's ROM version and saw that I was running 1.10.605.15. I grabbed the Rumrunner package from here for that level.
In looking over the requirements for Rumrunner, it wanted 32-bit Linux and I run 64-bit. The easiest way to solve this problem for me was to just boot to a Xubuntu 12.10 32-bit ISO that I had on my system. If you have it burned, just boot to it. If you don't (like me), use grub2 (if you have it) and boot the ISO directly. Either way, get yourself into a live environment.
Once the ISO was booted, I got it on the network and installed adb and fastboot from the Ubuntu repositories (after I did apt-get update, of course). Connect the phone via USB and enable USB debugging:
Go to Settings -> About -> Software Information -> More
Tap the Build number field 7 times
Back up to the Settings screen again and you'll now see Developer options
Enable USB Debugging under the developer options
Verify that you can see the device on your system using adb (this should result in a device being listed by serial number):
Code:
sudo adb devices
Follow these instructions for executing Rumrunner. It worked perfectly as described. Once complete, the phone was unlocked and S-OFF with a stock ROM.
Keep the live environment up as it will just make life easier to do the next steps.
Install a custom recovery (CWM)
I pretty much always use CWM if I can. I saw that there were no issues with doing that on this phone (like there are on other phones like the Rezound). I grabbed version 6.0.4.7 of CWM (non-touch) for the HTC One from here. If I recall correctly, the device is booted back into the stock ROM at this point. Make sure your device is still connected USB and has USB debugging enabled.
Reboot into the bootloader from the command prompt:
Code:
sudo adb reboot bootloader
Once the phone comes up, it should be at the Fastboot screen (it should actually show Fastboot USB). Verify that you can see your phone with fastboot (should get your device serial number again):
Code:
sudo fastboot devices
Now you can flash CWM recovery using this command from the directory where you stored the CWM file you downloaded (such as the one I provided a link to):
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.7-m7vzw.img
After the flash is successful, reboot back into the bootloader:
Code:
sudo fastboot reboot-bootloader
Now you can choose BOOTLOADER and then RECOVERY to get access to CWM. If you really want to, you can take a backup of the stock ROM at this point. I did not because I thought it was a waste of space. I just booted back into the stock ROM and disabled USB debugging so I could stick a real ROM on the system.
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
I really wanted to give this HTC Sense 5.0 a run. I've used Sense before and it wasn't awful. This seemed less annoying than previous versions (plus, there are some nice camera features which are important to me). For that reason, I selected the stock 2.10.605.1 rooted, deodexed, debloated ROM from this thread. I also opted to do the firmware upgrade at the same time, so I grabbed the firmware for the 2.10.605.1 as well.
The instructions in this thread are easy to follow so just use those. Just a note though: Flash the firmware and ROM at the same time if you're going to do firmware at all. Instructions are in the second post on that thread.
Once the ROM was up, I did my typical setup of accounts and such. The last thing I needed was Wireless Tether support.
Get wireless tether working without jumping through tons of hoops.
I don't particularly care how I get wireless tethering (infrastructure mode) as long as it works on my phone reliably. I first tried the stock tethering as this sometimes works because the authors of "stock" ROMs sneak hacks into their ROMs. It did not work. I then tried messing around with the WiFi Tether TrevE Mod that I saw recommend a few times but this didn't pan out on the 2.10.605.1 ROM (I temporarily went to 1.10.605.15 and it worked; I went back to 2.10.605.1 when someone recommended the solution below):
http://forum.xda-developers.com/showthread.php?t=2576548
I flashed this package onto my system and, without a problem, built-in wireless tether started working. I've seen no problems.
Getting my one today. I guess I will give this a go tonight. Thanks. Anything else to look for? Thanks.
Sent from my HTC Rezound.
Rumrunner worked perfectly fine for me on Ubuntu 12.1 64 bit both times I ran it. I would try it first before downloading s 32 bit distro if 64 bit is already installed.
Sent from my HTC6500LVW using Tapatalk
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
onthehole said:
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
Click to expand...
Click to collapse
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks.
No problem.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
No problem.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
onthehole said:
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
Click to expand...
Click to collapse
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
onthehole said:
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
Click to expand...
Click to collapse
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
onthehole said:
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
Click to expand...
Click to collapse
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
will do. thanks.
onthehole said:
will do. thanks.
Click to expand...
Click to collapse
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
onthehole said:
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
Click to expand...
Click to collapse
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
disconnecktie said:
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
onthehole said:
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
Click to expand...
Click to collapse
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
disconnecktie said:
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
understood. I will flash fresh if things aren't up to par.

Categories

Resources