Related
Hi!
I've got a Nexus One with HBOOT 0.33 and S-OFF. I guess it's a developer version. I'm wondering if anyone with S-OFF tried updating to HBOOT 0.35 and if their phones remained S-OFF or of they lost it. Not sure about updating just yet, but my boot partition has some bad blocks, so I guess I could benefit from it. Please let me know.
wrong section
Sorry, mods, please move this to the correct sub-forum.
I have S-ON since I updated to 0.35, but I still can flash ROMs etc.. whats the difference between S-ON and S-OFF if I still can flash ROMs and the AMON_RA Recovery still works?
[email protected] said:
I have S-ON since I updated to 0.35, but I still can flash ROMs etc.. whats the difference between S-ON and S-OFF if I still can flash ROMs and the AMON_RA Recovery still works?
Click to expand...
Click to collapse
You can relock the bootloader.
Not sure about "wrong section". My personal advise: If you haven't realized or felt the need for S-OFF its not really important, devices have a short life time, make sure you don't waste too much time on this subject as it is really for system developers.
Warranty theoretically expires by unlocking the boot loader, as for real life I haven't heard yet of a single "rejection" by HTC due an unlocked boot loader.. except if you brick your screen by dropping the device etc.
Hope this helps.
Well, I guess I'm just proud of having an S-OFF version of the phone, but no real use for it. I'll leave it for now, I guess and will let you know the result if I do update it.
completely pointless, however I think I'd feel the same ;-)
(Now sitting at a real keyboard, easier to type)
RunTimeWorld is correct, these devices do have a short life time, so it would be a shame to wast it on waiting for an answer/explanation of a small thing like S-OFF on a Nexus One. However, I figured it like this: Seeing as I can run Kang-o-Rama with IR's kernel properly on my current HBOOT/Radio config, I'm not changing it until I need to. I see that my phone frequently is checking (and finding) the HBOOT update, but we'll just see when CM7 is closer to release. All that 0.35 would profit me would be a smaller recovery partition but a larger boot partition. If I need to flash a larger kernel, I'll definitely switch.
Mine remained S-OFF after updating to .35
Rusty! said:
Mine remained S-OFF after updating to .35
Click to expand...
Click to collapse
Sounds reassuring.
Exactly how did you update to 0.35? Using the official zip file downloaded from the Google servers or through the Korean OTA/RUU?
Via the recent 2 part OTA update (not Korean).
Aha, so I guess I'll just try it then.
Success
Here's the result, for you other Nexus One owners with S-OFF. Like i said, it's pretty much only for personal pride, but it's still nice to see my phone didn't loose it's "Developer phone" status when upgrading the HBOOT.
I believe the 'developer' ones say "ENG S-OFF", not "SHIP S-OFF"... ours are freaks and probably just a mistake by HTC.
Well, I guess you could be right. Mine was bought second hand in late May 2010 from a person who's mother (the actual previous owner) works for the Swedish telecommunication company Ericsson. One can only guess that she got it at some Google event or something similar. Anyway, I'm quite pleased to have something special.
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk
I know.. I have spoken to him.
jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.
katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome
no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..
Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.
Hopefully it works for him I couldn't help.
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.
jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.
I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.
globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
surgehtc said:
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
Click to expand...
Click to collapse
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
majmoz said:
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
Click to expand...
Click to collapse
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
surgehtc said:
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
Click to expand...
Click to collapse
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
majmoz said:
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
Click to expand...
Click to collapse
I did get it from the verizon section.
But I have no custom recovery and no fastboot
I can't adb sideload either.
What should I do?
Huge amount of frustration with trying to deal with my phone
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
F0rZ3r0 said:
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
Click to expand...
Click to collapse
Flashing RUU requires locked bootloader.
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
F0rZ3r0 said:
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
Click to expand...
Click to collapse
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Alright, doing this now. I'm a lot calmer today, so I can do this.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
F0rZ3r0 said:
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
Click to expand...
Click to collapse
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Sloth said:
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Click to expand...
Click to collapse
My apologies for the swearing, was angry at the time.
Also, my hboot version seems to be 3.18. Not sure what to do in order to be able to flash firmware. My OS version seems to be 2.16.651.4 as well if that helps.
What would I have to do in order to install a ROM and how?
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
dopy25 said:
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
Click to expand...
Click to collapse
I believe I'm S-OFF.
F0rZ3r0 said:
I believe I'm S-OFF.
Click to expand...
Click to collapse
look in bootloader it will tell you if you are s-off or s-on.
Sloth said:
look in bootloader it will tell you if you are s-off or s-on.
Click to expand...
Click to collapse
Never mind, S-ON.
F0rZ3r0 said:
Never mind, S-ON.
Click to expand...
Click to collapse
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Sloth said:
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Click to expand...
Click to collapse
Umm...I don't have anything called SDK :/
What do I do then?
F0rZ3r0 said:
Umm...I don't have anything called SDK :/
What do I do then?
Click to expand...
Click to collapse
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Sloth said:
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Click to expand...
Click to collapse
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
F0rZ3r0 said:
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
Click to expand...
Click to collapse
Should only be a few seconds.
Sloth said:
Should only be a few seconds.
Click to expand...
Click to collapse
Not sure what the issue here is then. As I write this, it is still sending. I'm not sure what the issue is...
Check PM.