I was just going to flash ARHD 3.1 GE which is 4.3 based.
Currently i'm unlocked/s-off (thanks to revone) with hboot 1.44 and RUU 1.29.401.16.
Do I even have to update firmware or does 1.29 based fw work with 4.3 correctly?
Basically i'm confused with these firmware packages: http://forum.xda-developers.com/showthread.php?t=2182823
Is flashing a 2.24.401.12 based firmware going to update hboot too? Does this one break touch in recoveries too?
Why the custom firmwares based on 2.17.401.1 RUU and why aren't there 2.24.401.12 based custom firmwares?
Hopefully someone can answer at least some of my questions :angel:
Thanks
_saiko said:
I was just going to flash ARHD 3.1 GE which is 4.3 based.
Currently i'm unlocked/s-off (thanks to revone) with hboot 1.44 and RUU 1.29.401.16.
Do I even have to update firmware or does 1.29 based fw work with 4.3 correctly?
Basically i'm confused with these firmware packages: http://forum.xda-developers.com/showthread.php?t=2182823
Is flashing a 2.24.401.12 based firmware going to update hboot too? Does this one break touch in recoveries too?
Why the custom firmwares based on 2.17.401.1 RUU and why aren't there 2.24.401.12 based custom firmwares?
Hopefully someone can answer at least some of my questions :angel:
Thanks
Click to expand...
Click to collapse
Sounds like your a noob, so don't upgrade your hboot.
Sent from my One using xda app-developers app
gee thanks, you answered everything
I want to keep hboot 1.44, so it's fairly a simple question whether the 2.24 based firmware updates hboot as well or not.
That is my main question.
Tw1tchy said:
Sounds like your a noob, so don't upgrade your hboot.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
That was so rude, even if he is a noob, I think he has the right to find information and in this case, ask for it.
To be honest, I would like the answer to this too.
_saiko said:
gee thanks, you answered everything
I want to keep hboot 1.44, so it's fairly a simple question whether the 2.24 based firmware updates hboot as well or not.
That is my main question.
Click to expand...
Click to collapse
Yes the firmware will update the hboot. It may also update your radio and other hidden partitions.
I would recommend having s-off if your looking to upgrade your firmware. If you don't s-off you have to find the firmware corresponding with your CID. Most of it the time you have to run a RUU to upgrade so back up. Lastly S-OFF only works on hboot 1.44 so if your looking to s-off in the past (assuming you haven't already) don't upgrade because there is no downgrade method yet.
Sent from my One using xda app-developers app
Guys,
Go here: http://forum.xda-developers.com/showthread.php?t=2316726
Read the guide, and flash the 3.06/2.17 combo file if you can (S-off helps). Will give you the great updated touch drivers, and the GE 3.06 firmware. Sneakyghost did an excellent job with this guide, it will really help you out!
And if i'm S-OFF and on 1.44 HBOOT. Does it worth me upgrading ? What will be the benefits of new firmware / hbott ?
Im already s-off on 1.44 using revone, so what would happen with s-off status if I were to flash the 3.06/2.17 firmware from snakyghost?
Would it remain s-off?
Also something caught my eye, is the hboot from snakyghost a modified version and would reverting to s-on while having it brick the device?
r3v0Lut10n said:
And if i'm S-OFF and on 1.44 HBOOT. Does it worth me upgrading ? What will be the benefits of new firmware / hbott ?
Click to expand...
Click to collapse
Sirs please if you could give an answer Id be grateful
_saiko said:
Im already s-off on 1.44 using revone, so what would happen with s-off status if I were to flash the 3.06/2.17 firmware from snakyghost?
Would it remain s-off?
Also something caught my eye, is the hboot from snakyghost a modified version and would reverting to s-on while having it brick the device?
Click to expand...
Click to collapse
You will not lose s-off if you flash it just don't s-on with that firmware
Flashing firmware need not be a harrowing experience. As long as you read the guides carefully and follow the instructions to the letter, you will be fine. I have probably flashed at least 5-6 firmware packages on my One since getting it.
In general, once you're s-off, it's good to be on the most recent firmware because of various bug fixes like touch sensitivity. And, it would seem to be best to be on a matching firmware/rom base.
Once you start doing this stuff, however, forget about going back to s-on. You can do it if you're careful, but it's a bad idea. One mistake could leave you with a brick or crippled phone.
Again, to emphasize: Read very carefully, follow the instructions exactly, and you'll be safe.
Thank you Sirs
Usually i'd go and test things myself before asking, but in this case a wrong choice is not an option
Related
Alright, so my friend has an AT&T One and it had 1.26.502.10 firmware (like mine), but he had some camera issues... He decided to do all the modding (root, s-off, etc...) and upgraded to 4.2.2 firmware 2.24. His camera issues continue, and he plans on returning to 4.1.2 with the available RUU that returns the phone to 1.26.502.12. He is s-off, supercid, unlocked bootloader, rooted, running twrp 2.6.0.1 and is on stock rooted 2.24.401.1 Rom. I thought of just using that RUU to return him to fully stock, but since it has all the mods I'm not really sure if I should take another approach or other steps. Please help me out here, I don't wanna brick his phone (even though he's taking it to be replaced). Thanks in advanced!
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Just run the RUU, as he's S-OFF there should be no issues
jerrycoffman45 said:
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Click to expand...
Click to collapse
Yes, that's the very file I have. Thanks! Will run it now! Thanks for the quick reply!
EddyOS said:
Just run the RUU, as he's S-OFF there should be no issues
Click to expand...
Click to collapse
Will do, thanks for ur quick reply!
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
EddyOS said:
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
Click to expand...
Click to collapse
Hmm, will I get a kind of error during the RUU process that might possibly brick the device or will it warn me before the RUU process starts? Can I and should I just flash the 1.44 RUU from fastboot before starting the RUU? The phone's on 2.24 right now with the modded 1.54 hboot (I know he first has to flash the original, but can/should he flash the 1.44 instead?).
EDIT: As far as I've read till now, the ones having errors were converted to Google Edition with GE hboot and all... I did read about 2 people (one with 2.17 and the other with 2.24 like my friend's phone) both on 1.54 hboot and it worked for both of em. I'm just gonna go ahead and flash the RUU on my friend's phone and hope for the best
Hey gals,
I want to ask a noobish question:
I'v done S-OFF to my US Developer Edition device.
Hboot now 1.44
android 4.1.2
I'd like to know, if i would like to flash ViperOne rom that have 4.2.2 base, do i need to update the hboot or someting else?
Thanks
oksagi said:
Hey gals,
I want to ask a noobish question:
I'v done S-OFF to my US Developer Edition device.
Hboot now 1.44
android 4.1.2
I'd like to know, if i would like to flash ViperOne rom that have 4.2.2 base, do i need to update the hboot or someting else?
Thanks
Click to expand...
Click to collapse
You Can update Hboot boot via a firmware update (which I recommend if you are still on the original 4.12 firmware, as there have been some touch driver updates that really helped the capacitive buttons, look here for a great guide and firmware packages: http://forum.xda-developers.com/showthread.php?t=2316726 ), but you don't Have to update Hboot to flash Viper 2.1, it will work fine either way
dgtiii said:
You Can update Hboot boot via a firmware update (which I recommend if you are still on the original 4.12 firmware, as there have been some touch driver updates that really helped the capacitive buttons, look here for a great guide and firmware packages: http://forum.xda-developers.com/showthread.php?t=2316726 ), but you don't Have to update Hboot not flash Viper 2.1, it will work fine either way
Click to expand...
Click to collapse
Thanks for reply,
As i know there is no new HBOOT for DEVELOPER EDITION. maybe i'm wrong?
Or i need just to take a latest HBOOT and flash it?
Will i still have S-OFF?
oksagi said:
Thanks for reply,
As i know there is no new HBOOT for DEVELOPER EDITION. maybe i'm wrong?
Or i need just to take a latest HBOOT and flash it?
Will i still have S-OFF?
Click to expand...
Click to collapse
It would be a good idea to update your firmware/Hboot to the 2.24 (4.22) version, so it matches the rom and you get the touch fixes I talked about. It's a good idea, but you do not have to, it's up to you. Hboot will change to 1.54, but you will stay S-off, no worries. Read that thread I linked, and I recommend this firmware https://mega.co.nz/#!nZoVXKpD!Iki5KkvxxhL9jZgJkegv_iHLbp0eHQALxAz5Nc50_rc from that thread if that's what you want to do. If that's the route you go, first update the firmware/Hboot, then flash the rom, then any custom kernels if desired
dgtiii said:
It would be a good idea to update your firmware/Hboot to the 2.24 (4.22) version, so it matches the rom and you get the touch fixes I talked about. It's a good idea, but you do not have to, it's up to you. Hboot will change to 1.54, but you will stay S-off, no worries. Read that thread I linked, and I recommend this firmware https://mega.co.nz/#!nZoVXKpD!Iki5KkvxxhL9jZgJkegv_iHLbp0eHQALxAz5Nc50_rc from that thread if that's what you want to do. If that's the route you go, first update the firmware/Hboot, then flash the rom, then any custom kernels if desired
Click to expand...
Click to collapse
is this firmware good for developer edition?
oksagi said:
is this firmware good for developer edition?
Click to expand...
Click to collapse
Yes! It is fine, and your phone will work better with the new touch drivers. I am not sure what the CID of the Developer's edition is, you might want to check that. Will definitely flash if Super CID (fastboot oem writecid 11111111), worked for me.
Look, before you flash firmware, you better read that guide I linked you to at the very least, I mean it. This is pretty routine, non-scary stuff, but you are S-off, and that means something. Read the thread, make sure you understand what you're doing, and I'm here to help. But I'm not trying to or going to convince you to do anything, read and decide for yourself, ok? I'm telling you it will work, but you have to decide and be comfortable
dgtiii said:
Yes! It is fine, and your phone will work better with the new touch drivers. I am not sure what the CID of the Developer's edition is, you might want to check that. Will definitely flash if Super CID (fastboot oem writecid 11111111), worked for me.
Look, before you flash firmware, you better read that guide I linked you to at the very least, I mean it. This is pretty routine, non-scary stuff, but you are S-off, and that means something. Read the thread, make sure you understand what you're doing, and I'm here to help. But I'm not trying to or going to convince you to do anything, read and decide for yourself, ok? I'm telling you it will work, but you have to decide and be comfortable
Click to expand...
Click to collapse
do i need to upgrade only HBOOT or the firmware too?
oksagi said:
do i need to upgrade only HBOOT or the firmware too?
Click to expand...
Click to collapse
You don't "need" to update Hboot at all, but it will update to 1.54 with the firmware update. In my opinion, you " want" to update the firmware to: get the new, much improved touch drivers, be on the same firmware as your rom (ViperOne 2.1), and get whatever other updates are in the new firmware
oksagi said:
Hey gals,
I want to ask a noobish question:
I'v done S-OFF to my US Developer Edition device.
Hboot now 1.44
android 4.1.2
I'd like to know, if i would like to flash ViperOne rom that have 4.2.2 base, do i need to update the hboot or someting else?
Thanks
Click to expand...
Click to collapse
ViperOne will run just fine on the stock US Dev Ed firmware!
You do not NEED to upgrade the firmware, unless you want the updated touch screen drivers.
guyd said:
ViperOne will run just fine on the stock US Dev Ed firmware!
You do not NEED to upgrade the firmware, unless you want the updated touch screen drivers.
Click to expand...
Click to collapse
Can you please explain what is the problem with touch s on old hboot?
oksagi said:
Can you please explain what is the problem with touch s on old hboot?
Click to expand...
Click to collapse
The H-Boot has nothing to do with the touch screen.
The touch screen drivers were updated in the 2.17 and 2.24 firmware release.
Many people feel that the touch screen is more responsive with the updated drivers/firmware.
You do not NEED to update the firmware to run a 4.2.2 ROM. It will run fine on the older firmware.
I ran ViperOne on the older firmware up until very recently. No problems.
oksagi said:
Can you please explain what is the problem with touch s on old hboot?
Click to expand...
Click to collapse
Oksagi,
I told you yesterday, you don't Need to flash anything to run Viper, I thought that was clear, your Hboot is fine. If you Want to update your firmware, I gave you links to a very good guide, and to the firmware you should use, IF YOU WANT. Again, you are fine on your Hboot, go ahead and flash Viper, I think you will love it, I do. I think updating firmware may be too much for you at this point. Good luck sir....
Sorry For my newbie-ness but what advantages has S-OFF and what can i do with it ?
Hi All,
I have the M7 UL with a CID of HTC__001, it has hboot 1.44 s-off and I want to know if I really need to update the firmware/radio at all? I believe the current firmware is that of the 1.29.401.1 and since this was from the time of the Android 4.1.2 ROM and I am running a custom 4.3 ROM, I'm not sure what to do. I'm, not actually having any problems, so is it really necessary?
If so, do I need to upgrade hboot as well or can I get newer firmware/radio while keeping hboot 1.44 ?
beartiger said:
Hi All,
I have the M7 UL with a CID of HTC__001, it has hboot 1.44 s-off and I want to know if I really need to update the firmware/radio at all? I believe the current firmware is that of the 1.29.401.1 and since this was from the time of the Android 4.1.2 ROM and I am running a custom 4.3 ROM, I'm not sure what to do. I'm, not actually having any problems, so is it really necessary?
If so, do I need to upgrade hboot as well or can I get newer firmware/radio while keeping hboot 1.44 ?
Click to expand...
Click to collapse
At this point in time, you don't NEED to upgrade firmware, but there COULD be benefits such as the updated touchscreen drivers.
And since you're s-off, you can flash new firmware(s) including updated hboot, and still be able to downgrade anytime you choose.
Updating firmware or hboot will not change your s-off status, and therefore allow you to downgrade at your choice.
Sent from my HTC One using xda app-developers app
Ive got a quick question regarding this, is firmware ROM dependent - i.e does it matter if im on the 4.3 Sense ROM or the 4.3 Play ROM to flash the 4.3 Firmware?
TheOozyMan said:
Ive got a quick question regarding this, is firmware ROM dependent - i.e does it matter if im on the 4.3 Sense ROM or the 4.3 Play ROM to flash the 4.3 Firmware?
Click to expand...
Click to collapse
Nope. Like I said, currently the ROMs are firmware independent. This could change in the future, but for now it doesn't matter.
Sent from my HTC One using xda app-developers app
Thanks again for the help, I have another question about firmware flashing. I want to flash the latest firmware.zip on my HTC one and I'm already S-OFF. Can I just do this in TWRP and can I do it anytime or do I need to do it before I flash a ROM?
TheOozyMan said:
Thanks again for the help, I have another question about firmware flashing. I want to flash the latest firmware.zip on my HTC one and I'm already S-OFF. Can I just do this in TWRP and can I do it anytime or do I need to do it before I flash a ROM?
Click to expand...
Click to collapse
Firmware needs to be flashed in fastboot.
"fastboot oem rebootRUU"
"fastboot flash zip firmware.zip"
"fastboot flash zip firmware.zip"
(Yes, twice)
Be sure to check an make sure everything was successful.
"fastboot reboot"
Sent from my HTC One using XDA Premium 4 mobile app
Thanks, but I read somewhere that you need to flash firmware and then flash a ROM? Is that true?
Also whats the worst thing that could happen if I messed something up, could I just restore a nandroid?
TheOozyMan said:
Thanks, but I read somewhere that you need to flash firmware and then flash a ROM? Is that true?
Also whats the worst thing that could happen if I messed something up, could I just restore a nandroid?
Click to expand...
Click to collapse
The worst thing that could happen is a brick-- but that's unlikely.
Nandroids don't backup/restore firmware.
I'd recommend NOT updating hboot.img, or sbl??.img when updating firmware.
Only include these in firmware.zip: android-info.txt, adsp.img, radio.img, rcdata.img, tp_SYN3302.img, rpm.img and tz.img.
These get you (in order) the DSP, radio, radio config data, touch pad driver, and some misc stuff (rpm and tz).
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
docdoc518 said:
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
Click to expand...
Click to collapse
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
n1234d said:
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
docdoc518 said:
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
Click to expand...
Click to collapse
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
so as long as the you are s-off, you can ruu to any version even if you are at 1.54 hboot?
n1234d said:
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
EddyOS said:
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
Click to expand...
Click to collapse
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
docdoc518 said:
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
Click to expand...
Click to collapse
Follow what eddy says, he's the man @eddy, how does the hboot version make a difference??
Sent from my iPod touch using Tapatalk
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
EddyOS said:
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
Click to expand...
Click to collapse
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
You should be fine on that HBOOT, just try it and if it works it works! If not, you'll get an error and then you just following the second post in the GPe conversion thread
docdoc518 said:
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
Click to expand...
Click to collapse
Yep, go ahead and try, if it gives you an error, post back.
AFAIK, the dev edition BS_US001 gets OTAs the quickest, so you could keep it at that. SuperCID will allow you to flash any RUU/OTA, even of a different region/MID/CID
Nope, you're not being a pain We're all trying to learn and help here
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
docdoc518 said:
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
Click to expand...
Click to collapse
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
EddyOS said:
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
Click to expand...
Click to collapse
Newbie move I suppose :angel: haha
I've been rooting and flashing ROMs on my Androids since the G1/Dream believe it or not, but with every new phone/manufacturer there's always new terminology and steps to be taken so I feel like I start over every single time, which honestly isn't much of a bad thing, keeps things exciting (even though HTC made the G1 but that was what feels like ages ago now)
Thanks again guys, it's hard not to feel intimidated but it's been an extremely pleasant experience learning from you. This is why xda is by far the best site you can find for these things.
Cheers
Hi to everybody. I am planning to buy an used M7 with 1.55 Hboot.
So I was planning to Unlock, Root and then S-Off with Rumrunner.
But when I do this how can I update the phone to Lollipop stock to flash a custom rom like Viper (I've red that I can't flash it if I am not in Lollipop stock)?
Or have I to do every OTA Updates, upgrade to stock Lollipop, than do Unlock, Root and S-Off by Sunshine?
I really do not understand, it's very difficult to find this information, I've red lots of posts but I am still confused!
Thank's a lot!
HarryCustom said:
Hi to everybody. I am planning to buy an used M7 with 1.55 Hboot.
So I was planning to Unlock, Root and then S-Off with Rumrunner.
But when I do this how can I update the phone to Lollipop stock to flash a custom rom like Viper (I've red that I can't flash it if I am not in Lollipop stock)?
Or have I to do every OTA Updates, upgrade to stock Lollipop, than do Unlock, Root and S-Off by Sunshine?
I really do not understand, it's very difficult to find this information, I've red lots of posts but I am still confused!
Thank's a lot!
Click to expand...
Click to collapse
You should definitively try to s-off for free on hboot 1.55, better not to update the phone until you have achieved s-off.
Once s-off, you'll be able to update to anything you want using a ruu for example. Newer roms doesn't really requires lollipop OS but the firmware update that comes with it (7.xx.xxx.x)
You'll then update the firmware to a 7.xx.xxx.x version using a firmware.zip file or a full ruu.zip. Ask help when ready to flash the firmware to be sure you flash the right one as you can brick your phone if not done properly.
Also note that you don't need s-off to update your phone and flash a rom but its a good idea to achieve it now before updating. Its always easier to recover a bricked phone when its s-off but also remember its also easier to brick a s-off phone if you flash the wrong file so do not hesitate to ask questions before flashing, especially when flashing firmware files.
alray said:
Also note that you don't need s-off to update your phone and flash a rom but its a good idea to achieve it now before updating. Its always easier to recover a bricked phone when its s-off but also remember its also easier to brick a s-off phone if you flash the wrong file so do not hesitate to ask questions before flashing, especially when flashing firmware files.
Click to expand...
Click to collapse
Thank you very much I think the phone is an HTC One M7 801e "U" version, so as I understand well, after S-Off, I have to find the right RUU, flash it and than flash my favourite rom!