[Q] Basic steps from unlocked to Sprint updates - Sprint HTC One (M8)

I'm overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I'm a computer literate person, and I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"​
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions. I've also found step by step guides that each conflict with one another. One may have 5 steps and the other may have 12, and in one way or another they've always gone off the rails until they no longer seemed to apply to my use case.
If you can help, thank you.

Dr.Zee said:
I'm completely overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"​
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions.
If you can help, thank you.
Click to expand...
Click to collapse
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
No need to flash stock recovery if you run the RUU, only lock the bootloader.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.

dopy25 said:
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.
Click to expand...
Click to collapse
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?

Dr.Zee said:
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?
Click to expand...
Click to collapse
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.

dopy25 said:
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.
Click to expand...
Click to collapse
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.

Dr.Zee said:
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.
Click to expand...
Click to collapse
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.

dopy25 said:
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.
Click to expand...
Click to collapse
It's a patch that adds Harmon Kardon sound. Then I incorrectly remembered an app that enables Snapdragon audio (which is far superior to HK sound) but that's not firmware, you just need a rooted phone to be able to drop it into the system folder.

Related

[Q] HBOOT 1.16.0000, known ROMs to work?

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.

[Q] Trying to install the 4.3 OTA to a stock rom, stock recovery, but having issues

Hello all,
Firstly, I've got a (still unlocked) U.S. dev edition with S-On and Hboot 1.44.0000. I've been trying to install yesterday's OTA, but I can't seem to do it. The only changes I've made to my One since I got it were rooting it and installing TWRP in order to flash the MoDaCo toolkit. I understand that the stock recovery is needed to flash OTAs, and so I used fastboot to flash the stock recovery, but when I try to install the update, the progress bar in the recovery goes about 1/4 of the way and then it stops and displays the red triangle with exclamation mark. I'm not sure what I'm doing wrong, honestly.
I've seen varying advice aimed at other people also having difficulty suggesting I need to relock the bootloader (though as a dev edition, it was never locked, right?) or to get S-Off and then flash it somehow, so I'm not entirely sure what to do. I'd rather not resort to using a RUU as I will lose all of my data.
I didn't think a developer edition phone would be this difficult to deal with, as I've never had any problems flashing countless ROMs, kernels, etc with other android devices. I've never had an HTC phone though, so I've got no experience with S-On/Off, and to be honest I still don't understand what it is.
Anyway, how should I proceed? Thank you.
http://forum.xda-developers.com/showthread.php?t=2265618
Thank you for that, but I mentioned that I didn't want to use RUUs. There has to be a way to do this without losing my data.
1) Put your phone in s-off now that you have the 1.44 hboot, trust me is better for you.
2) Maybe you have a custom kernel.
For install OTA you need stock rom, stock recovery and stock kernel.
3) Maybe more info can help us
Deksloc said:
Hello all,
Firstly, I've got a (still unlocked) U.S. dev edition with S-On and Hboot 1.44.0000. I've been trying to install yesterday's OTA, but I can't seem to do it. The only changes I've made to my One since I got it were rooting it and installing TWRP in order to flash the MoDaCo toolkit. I understand that the stock recovery is needed to flash OTAs, and so I used fastboot to flash the stock recovery, but when I try to install the update, the progress bar in the recovery goes about 1/4 of the way and then it stops and displays the red triangle with exclamation mark. I'm not sure what I'm doing wrong, honestly.
I've seen varying advice aimed at other people also having difficulty suggesting I need to relock the bootloader (though as a dev edition, it was never locked, right?) or to get S-Off and then flash it somehow, so I'm not entirely sure what to do. I'd rather not resort to using a RUU as I will lose all of my data.
I didn't think a developer edition phone would be this difficult to deal with, as I've never had any problems flashing countless ROMs, kernels, etc with other android devices. I've never had an HTC phone though, so I've got no experience with S-On/Off, and to be honest I still don't understand what it is.
Anyway, how should I proceed? Thank you.
Click to expand...
Click to collapse
I'm having the exact same issues. I'm on HBOOT 1.44, S-On (I'd love to get S-Off, but revone keeps giving me error code -1...), and previously got the OTA's to work by flashing stock recovery, running the OTA, then reflashing TWRP. This one doesn't seem to work that way, though. If you figure anything out, or find the right stock recovery, please do share!

Hboot 1.44, ROM 4.3, Firmware is ??? What do I need to do?

Sorry for making one of these but I can't find the answer to my specific situation so I'm asking for some guidance: I'm S-ON btw
When 4.3 came out, I just wiped and flashed a custom 4.3 Rom like normal not realizing that I would need the whole new firmware to be fully functional. I can't delete system apps and xpsosed installer will never stick past a reboot and other misc stuff.
Then I tried flashing the new firmware over the top of the custom 4.3 ROM. But I kept getting a ERROR 99 or something, couldn't get it to work and gave up.
Now I'm on bad boys 4.3 rom and I have no idea what firmware I'm on cause I don't see it listed anywhere in the Rom.
Now from what I've read, it's advisable to be S-OFF for all future stuff so, what steps do I need to follow in order to gain S-OFF, completely update my phone to the new 4.3 firmware, radio etc... then be able to flash a 4.3 rom and then carry on with my usual root shenanigans like normal?
I have the 1.44 hboot (May 8) so if I read correctly, there is a way. I just need all the steps laid out in front of me cause I can't figure this one out.
MrDowntown12 said:
Sorry for making one of these but I can't find the answer to my specific situation so I'm asking for some guidance: I'm S-ON btw
When 4.3 came out, I just wiped and flashed a custom 4.3 Rom like normal not realizing that I would need the whole new firmware to be fully functional. I can't delete system apps and xpsosed installer will never stick past a reboot and other misc stuff.
Then I tried flashing the new firmware over the top of the custom 4.3 ROM. But I kept getting a ERROR 99 or something, couldn't get it to work and gave up.
Now I'm on bad boys 4.3 rom and I have no idea what firmware I'm on cause I don't see it listed anywhere in the Rom.
Now from what I've read, it's advisable to be S-OFF for all future stuff so, what steps do I need to follow in order to gain S-OFF, completely update my phone to the new 4.3 firmware, radio etc... then be able to flash a 4.3 rom and then carry on with my usual root shenanigans like normal?
I have the 1.44 hboot (May 8) so if I read correctly, there is a way. I just need all the steps laid out in front of me cause I can't figure this one out.
Click to expand...
Click to collapse
Hasoon2000's HTC ONE All-in-One Toolkit
It will guide you through this step by step
MrDowntown12 said:
Sorry for making one of these but I can't find the answer to my specific situation so I'm asking for some guidance: I'm S-ON btw
When 4.3 came out, I just wiped and flashed a custom 4.3 Rom like normal not realizing that I would need the whole new firmware to be fully functional. I can't delete system apps and xpsosed installer will never stick past a reboot and other misc stuff.
Then I tried flashing the new firmware over the top of the custom 4.3 ROM. But I kept getting a ERROR 99 or something, couldn't get it to work and gave up.
Now I'm on bad boys 4.3 rom and I have no idea what firmware I'm on cause I don't see it listed anywhere in the Rom.
Now from what I've read, it's advisable to be S-OFF for all future stuff so, what steps do I need to follow in order to gain S-OFF, completely update my phone to the new 4.3 firmware, radio etc... then be able to flash a 4.3 rom and then carry on with my usual root shenanigans like normal?
I have the 1.44 hboot (May 8) so if I read correctly, there is a way. I just need all the steps laid out in front of me cause I can't figure this one out.
Click to expand...
Click to collapse
Look HERE
bigdaddy619 said:
Look HERE
Click to expand...
Click to collapse
Ok thank you. So then at the end of those steps when I have achieved S-OFF, what's the next step? Cause won't I still be on old firmware?
MrDowntown12 said:
Ok thank you. So then at the end of those steps when I have achieved S-OFF, what's the next step? Cause won't I still be on old firmware?
Click to expand...
Click to collapse
Yes once you get s-off you can flash the firmware manually.

Just got this phone

Hello!
I just bought this phone. I have the HTC One HKE. I bought yesterday, and today I rooted it. I had no reason to wait.
So I was wondering, currently I'm on the Viper ROM 2.4.0, and I thought it would increase the performance but it has rather slightly hampered it. I want one that will increase the performance of the phone, so which ROM would you recommend? Also, please do make a kernel recommendation that goes along with it, too.
I prefer staying with Sense 6.0.
Not sure how you "slightly hampered" the performance of your phone by flashing Viper, other than the fact the version of Viper you flashed is outdated. I'm running Viper 3.2.1 with MassStash's Hypernova kernel and my phone runs great. To each his own, though. "Best ROM/kernel" threads are subjective at best because what works well for one person may not work well for another.
Magnum_Enforcer said:
Not sure how you "slightly hampered" the performance of your phone by flashing Viper, other than the fact the version of Viper you flashed is outdated. I'm running Viper 3.2.1 with MassStash's Hypernova kernel and my phone runs great. To each his own, though. "Best ROM/kernel" threads are subjective at best because what works well for one person may not work well for another.
Click to expand...
Click to collapse
I'm very well aware that this my rom is outdated, but I cannot seem to be able to return to stock to update the firmware in order to install the latest versions. When I do, my WiFi does not work and that's a real problem.
Can anyone direct me to the correct thread that explains how I can do this? Note that I have tried updating the firmware in many different ways - through the command prompt, and using the generic RUU update with replacing the rom.zip file. I do not know what I need to do first, I just relocked the device and had a little panic attack because I couldn't do anything else. I had to unlock it again using the HTC dev code.
Can somebody please tell me what I need to do to get the latest firmware? I'm on the HK device with firmware version 2.16.654.4
Take a look at the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
I tried to do this, as I previously stated. I tried to do it over fastboot. I tried using Generic RUU. Each time I get an error. At first it was error 99, but then I relocked the bootloader and got error 12 (signature verification failed).
Would you mind posting a link to the RUU you attempted to use? We were actually having a discussion in another thread about some similar issues folks were having.
I tried them all.
I tried the HK version, the non-HK version. I tried the ones with boot.img and the ones without. I even tried to download the entire image (1.6GB) and flash it with the program and that did not work either. I tried them all, believe me. I would not let something like that (wrong version) get in the way.
I have:
cidnum: SPCS_004
version-main: 2.16.654.4
I even tried running the SuperCID command, and that didn't do anything.
You won't be able to get SuperCID while S-on. My suggestion at this point would be to unlock your bootloader again, flash a stock rooted ROM and then get S-off with the Sunshine exploit. You can then update your firmware without having to mess with any of the RUU or FUU stuff.
Where could I find a stack rooted ROM that matches my version?
I looked them all up in the other thread and most of their versions are 1.xxx while my mainver is 2.16.xx
Amer28 said:
Where could I find a stack rooted ROM that matches my version?
I looked them all up in the other thread and most of their versions are 1.xxx while my mainver is 2.16.xx
Click to expand...
Click to collapse
Post #3 under "Old Downloads":
http://themikmik.com/showthread.php?16276-SPRINT-ROM-BeyondStockᵀᴹ-v1-2-0-amp-Stock-Rooted
Okay. Right now, I am on stock rooted. I am not quite sure how to proceed with the update. I have been going to the menu, and checking for an update but it says that no update is availible at this time.
Do I try running the RUU, or just wait for it to arrive?
I should also tell you that I am still on TWRP and unlocked. Should relock and install stock recovery as well?
Amer28 said:
Okay. Right now, I am on stock rooted. I am not quite sure how to proceed with the update. I have been going to the menu, and checking for an update but it says that no update is availible at this time.
Do I try running the RUU, or just wait for it to arrive?
I should also tell you that I am still on TWRP and unlocked. Should relock and install stock recovery as well?
Click to expand...
Click to collapse
You can go one of two routes. Either S-off and manually update your firmware, or install the stock Android system recovery, which will allow you to take the update.
So, I did it.
I'm currently on the latest firmware, running the latest Venom too with the WiFi working. I have root access.
You told me earlier that I should do sunshine s-off. I was wondering, why is that? I already have everything I wanted. What is the benefit of S-OFF, when I already have root?
I don't want to sound ignorant, but I really don't know. I feel like a big noob right now.
Amer28 said:
So, I did it.
I'm currently on the latest firmware, running the latest Venom too with the WiFi working. I have root access.
You told me earlier that I should do sunshine s-off. I was wondering, why is that? I already have everything I wanted. What is the benefit of S-OFF, when I already have root?
I don't want to sound ignorant, but I really don't know. I feel like a big noob right now.
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1680928

Finally Rooted My HTC One M7, Now What....

Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great. What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Thanks
AJHylton said:
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great.
Click to expand...
Click to collapse
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Click to expand...
Click to collapse
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
alray said:
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
Click to expand...
Click to collapse
I'd like to add - change recovery to TWRP as it's recomended for most ROMs out there
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
AJHylton said:
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
Click to expand...
Click to collapse
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
alray said:
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
Click to expand...
Click to collapse
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
AJHylton said:
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
Click to expand...
Click to collapse
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
alray said:
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
Click to expand...
Click to collapse
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
AJHylton said:
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
Click to expand...
Click to collapse
There is no RUU for 7.19.401.30 but there is one for 7.19.401.22 which can be used on your phone if needed in the future. :good:

Categories

Resources