Related
I have successfully custom flashed Sense 3.0 with 2.3 gingerbread for my incredible S phone. It only took 3 long days. I am very happy but what now? I want this to be my permanent ROM. Is there anything else that I am recommended to do now? I was reading about how you can make your phone almost like a stock phone meaning S-OFF and Unroot. Not too sure if that is necessary. What do you guys think?
please provide more info..
what Custom Rom are you on and how did you flash Sense 3.0.
there's a lot of threads hear and your initial details really don't provide much useful information.
I am on Virtuous Unity 1.27.0 Sense 3.0 based on Pyramid, I flashed it through 4EXTRecovery_v2.1.0_RC1_vivo.
I also had to flash a radio file to my ROM afterwards. I did that through the SDK software. Instructions from here: http://wiki.cyanogenmod.com/wiki/HTC_Incredible_S:_FAQ Here is a list of Radio files for your specific provider/region : http://forum.xda-developers.com/showpost.php?p=12870734&postcount=1
I S-OFF'd my phone through Alpha RevX..there is also a you tube tutorial on how to do it. If anyone has anymore questions on how to do it then msg me!
So now what is left to do?????? Any other procedures? Besides flashing more Roms!
saying the custom rom, radio, cwm would have been enough information. anyways i see that you're new so it's all good.
so the question is, What do you want to do with your phone. after customizing it, are you okay with performance? no bugs? What do YOU want to do with your phone?
I want to permanantly make it my OS. Is that possible? I posted all of that because when I was figuring out how to do this I found that other peoples solutions helped me out alot tee hee
guys I think this belongs in "General"
IncredibleSlover said:
I want to permanantly make it my OS. Is that possible? I posted all of that because when I was figuring out how to do this I found that other peoples solutions helped me out alot tee hee
Click to expand...
Click to collapse
What do you mean 'permanently make it my OS'? That ROM will stay on your phone as long as you want it, until you decide you want to flash a different one. There's no need to go trying to lock it down again after flashing it, that's a pointless exercise.
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Awesome thanks for the reply
hussainmushahid said:
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Click to expand...
Click to collapse
Hi, I need the S-ON. everywhere let me just advise'll update RUU, but I did and I still have the S-OFF. You know how to solve it? I need back guarantee.
thank you very much.
exnerjan said:
Hi, I need the S-ON. everywhere let me just advise'll update RUU, but I did and I still have the S-OFF. You know how to solve it? I need back guarantee.
thank you very much.
Click to expand...
Click to collapse
you need to go S-ON again? you used alpharevx? If so, just flash the whole official RUU and you will be S-ON again since it would also flash the bootloader.
hussainmushahid said:
you need to go S-ON again? you used alpharevx? If so, just flash the whole official RUU and you will be S-ON again since it would also flash the bootloader.
Click to expand...
Click to collapse
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
doctorsax said:
What do you mean 'permanently make it my OS'? That ROM will stay on your phone as long as you want it, until you decide you want to flash a different one. There's no need to go trying to lock it down again after flashing it, that's a pointless exercise.
Click to expand...
Click to collapse
Awesome man, thats what I wanted to hear
hussainmushahid said:
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Click to expand...
Click to collapse
You mean I wont be able to recover my old settings if I have restored it?
I dont care really if I cant. Is it because I am now 2.3 gingerbread????
Well it doesnt matter because I love this new ROM and will be keeping it forever
uh oh this is bad. no more warranty for my phone :s
tpbklake said:
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
Click to expand...
Click to collapse
and know how to do it to the S-ON? Please.
tpbklake said:
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
Click to expand...
Click to collapse
I haven't tried it myself so I guess you're true, when I flashed the stock RUU I flashed it without the bootloader file (unzip,delete,zip) as stated in a thread regarding keeping S-OFF when installing stock RUU. A guy has found the solution to going S-ON again in his thread in the general discussion section.
hussainmushahid said:
I haven't tried it myself so I guess you're true, when I flashed the stock RUU I flashed it without the bootloader file (unzip,delete,zip) as stated in a thread regarding keeping S-OFF when installing stock RUU. A guy has found the solution to going S-ON again in his thread in the general discussion section.
Click to expand...
Click to collapse
Yes I saw that this morning. Basically AlphaRevX has a special HBOOT you can 'downgrade' with that you must flash and then using the special HBOOT you can flash an official HTC HBOOT. End result is S-OFF and you have a standard HTC HBOOT.
Sorry if this has been asked but i did search first...
I have a new (optus) IS,
GB 2.3.3
HBOOT 1.16.0000
ROM 2.34.980.1
I want soff and root but alpharevx will not work with 1.16.0000
Can i get soff and root or do i have to wait until alpahrevx gets updated?
Ueee said:
Sorry if this has been asked but i did search first...
I have a new (optus) IS,
GB 2.3.3
HBOOT 1.16.0000
ROM 2.34.980.1
I want soff and root but alpharevx will not work with 1.16.0000
Can i get soff and root or do i have to wait until alpahrevx gets updated?
Click to expand...
Click to collapse
Here is a tool that is in the Development thread you could try. It may not work with your HBOOT 1.16.0000, but it's worth a shot, right?
http://forum.xda-developers.com/showthread.php?t=1245904
Go to revolutionary.io. You can s-off your device there.
Sent from my HTC Incredible S using XDA App
Ueee said:
Sorry if this has been asked but i did search first...
I have a new (optus) IS,
GB 2.3.3
HBOOT 1.16.0000
ROM 2.34.980.1
I want soff and root but alpharevx will not work with 1.16.0000
Can i get soff and root or do i have to wait until alpahrevx gets updated?
Click to expand...
Click to collapse
ste1164 said:
Go to revolutionary.io. You can s-off your device there.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Although OP did mention alpharevx, the alpharevx site now redirects you to the revolutionary.io site. On their documentation wiki, they state:
HTC Incredible S (vivo) 1.09.0000 and 1.13.0000
So apparently he has a newer hboot version.
Sorry for the confusion, but to clarify i did try revolutionary, but got to it from an alpharevx link, hence the confusion.
I got the same problem here, new IS from Virgin mobile in early this month..... no clue at all....
omg, can we please get a method to get it working? After hours of research and rooting and videos, I then noticed that I had to get "S-OFF", but now I can't do it because the 1.16 version is out.
I'm new to these forums, just basically want to find out an answer, if anyone wants to say something email me on [email protected] as I may not check but I will try to visit and check on it. I'm so excited to root it an install cyanogenmod.
I've got Incredible S on virgin mobile unlocked.
Bump!!!
Every day atleast twice a day I keep looking back at the revolutionary site to see if they have updated anything yet. I'm not sure, but apparently can I goldcard (changing my HBOOT) then I will be able to root... or..? cause it's on 1.16 which is not able to be rooted yet apparently.
Not too sure. So damn impatient!
Ueee said:
Sorry for the confusion, but to clarify i did try revolutionary, but got to it from an alpharevx link, hence the confusion.
Click to expand...
Click to collapse
Hi, Ueee..
Did you have any sms delayed and
miss call problem for the 2.34.980.1 optus rom?
ansg86 said:
Hi, Ueee..
Did you have any sms delayed and
miss call problem for the 2.34.980.1 optus rom?
Click to expand...
Click to collapse
Also, what is your radio version?
ansg86 said:
Hi, Ueee..
Did you have any sms delayed and
miss call problem for the 2.34.980.1 optus rom?
Click to expand...
Click to collapse
No sms or missed call problems at all
neo-X said:
Also, what is your radio version?
Click to expand...
Click to collapse
Radio version is 20.2810.30.085au
Ueee said:
Radio version is 20.2810.30.085au
Click to expand...
Click to collapse
Looks like they pushed a fix out with a new radio and base software. Good news!
Now just gotta get the optus rom on my phone and update it.
As for rooting your version, looks like your stuck until revolutionary release an update.
Does anyone know if it is a purely a radio problem? If not, if I restore the stock rom (nandroid) would it be possible to flash a custom kernel without screwing up my phone?
Tartarus1 said:
Does anyone know if it is a purely a radio problem? If not, if I restore the stock rom (nandroid) would it be possible to flash a custom kernel without screwing up my phone?
Click to expand...
Click to collapse
It seems as thought it's both radio and software problem.
Neo-X did you try loading the old Optus rom and then allow the OTA upgrade? Did it work?
I bought mine for mobicity then alpharexed it and using ARHD at present.
i guess installing the optus rom then OTA will remove the root.....
tzuyang said:
Neo-X did you try loading the old Optus rom and then allow the OTA upgrade? Did it work?
I bought mine for mobicity then alpharexed it and using ARHD at present.
i guess installing the optus rom then OTA will remove the root.....
Click to expand...
Click to collapse
No i didn't try it. I just sent it back in to downgrade because i'm giving the phone to a family member and need it working 100%. Yes it will but i would have thought that if you use revolutionary before you do anything that not even an ruu will touch hboot and you will be s-off no matter what.
humm
i think this is more of a sense problem than anything as i have had the missed calls/delayed sms on the HTC sensation Incrediable s and wild fire s
on all of them turning them to 2g only fixes the problem
this is causing me to switch away from htc for now as it kiils the smartphone experience
So is anyone able to answer my question?
I have HBOOT 1.16.0000 and have S-ON
I want to make it S-OFF, but revoloutionary.io only does 1.09.0000 and 1.13.0000
Can I get S-OFF so I can root? Thanks
jakeyo said:
So is anyone able to answer my question?
I have HBOOT 1.16.0000 and have S-ON
I want to make it S-OFF, but revoloutionary.io only does 1.09.0000 and 1.13.0000
Can I get S-OFF so I can root? Thanks
Click to expand...
Click to collapse
Does not look like you can for now. You will have to wait for revolutionary.
Hi all,
I'm having issues trying to restore the latest Telstra RUU and I'm hoping someone will be able to give me a hand with this.
I originally unlocked the bootloader, flashed a CWM recovery, custom ICS ROM, and all was working fine.
I've decided to go back to stock Telstra release but every time I try running the RUU I get an error message saying ERROR [140]: BOOTLOADER VERSION ERROR.
From what I've read, this relates to the bootloader being newer then that included in the RUU. I'm not sure how accurate this is though so if someone could confirm, that would be great. If I do need to downgrade the bootloader, where do I get it from?
The RUU's I've tried flashing are from here: http://www.filefactory.com/f/002b74e0f4775869/
- RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_34.06.701020.02_release_231121_signed.exe
- RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed.exe
Neither of these work and both show the same error as indicated above.
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0029
eMMC-boot
Mar 15 2012, 17:16:42
If anyone can provide any assistance getting this phone back to stock Telstra release it would be greatly appreciated. I've been working on it for almost 6-8 hours now and seem to be going around in circles.
Thank you! :good:
You need to relock your boot loader to run an ruu
Sent from my HTC PH39100 using xda premium
Sorry, I forgot to mention that. The bootloader has been relocked.
What hboot do you have currently?
Sent from my HTC PH39100 using xda premium
As above, HBOOT-1.85.0029.
I've managed to flash Velocity² "Nightly Build 5" which is as close to stock as I can get for the time being. Phone is working fine.
I can't seem to find any information at all regarding updating the HBOOT though, and what small information I do come across, it doesn't make a whole lot of sense. I don't even know if 1.85.0029 is the latest. Whether I need to upgrade/downgrade it before the RUU will work which some information I've found seems to suggest.
You shouldn't have to change the hboot to be able to run the ruu. Did you unlock your bootloader again to flash the new Rom?
Sent from my HTC PH39100 using xda premium
I did unlock the bootloader again to flash the new rom, only becasue the RUU wouldn't flash. I've tried flashing the RUU with the bootloader locked and unlocked even though I know it needs to be locked. I've tried flashing the RUU while using both a GB rom and an ICS rom - just incase it makes it difference - it didn't.
I've never had this much trouble flashing an RUU before - it's ridiculous.
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
kgs1992 said:
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
Click to expand...
Click to collapse
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Nucleotide said:
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Click to expand...
Click to collapse
Main version is the software number.
The one you see in Settings > About > Software Information.
The number should be on the RUU that you downloaded, it's the first set of numbers. for example: 3.25.841.4
How did you go with this, I am in the exact same boat. I want to sell my phone but not with this rom.
I was never able to install the stock Telstra RUU. Could never figure it out. After countless hours and at one stage thinking I'd bricked it, I gave up. I ended up sticking with this ROM (http://forum.xda-developers.com/showthread.php?t=1653317) which hasn't been too bad really.
I would still really love to restore it to factory but in all honesty I don't think it will ever happen.
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
androidlurv said:
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
Click to expand...
Click to collapse
That would be awesome. Very interested to know how you get on. :good:
Nucleotide said:
That would be awesome. Very interested to know how you get on. :good:
Click to expand...
Click to collapse
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Drunkllamajr said:
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Click to expand...
Click to collapse
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Nucleotide said:
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Click to expand...
Click to collapse
Same here I'm now running Holics 1.3 very similar to stock with some nice addons etc
just s-off and then use that RUU
I can't find the RUU's any more. They have gone from File Factory. I've pretty much given up on trying to restore this to factory. I can't even find up to date information on how to S-OFF - and from memory it's got to be done via hardware hack of some sort? Not real keen on that idea.
That said, I'm looking at flashing CyanogenMod 10 4.1.2 ROM which I'd be more then happy with.
RUU
You might be looking for this http://forum.xda-developers.com/showthread.php?t=2094150&highlight=ruu. I was having the same problem and what I did was find the exact/the same version of the RUU and the version of my phone.
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 ?
Can anyone point me in the right direction to either get s-off for HBOOT 1.55 or a tutorial or video on how to downgrade back to a version of HBOOT that I can run S-OFF on. I did the Sprint OTA 4.3 and need a little help.
I'm sorry to say it, but you can't s-off when on 1.55, nor can you downgrade. I found that out for myself.
I also did the OTA 4.3 upgrade with S-off on Hboot 1.44.
I now am on Hboot 1.55 and can unlock/lock my bootloader using the unlock code.bin I saved from HTCdev.
I cant believe I thought S-off was the same as unlocked bootloader....
Now im stuck with 4.3 BOO
How did you guys lose your s-off? I did the 4.3 OTA when I had s-off already, and I didn't lose mine
Sent from my HTCONE using XDA Premium 4 mobile app
I was downgrading and upgrading and some things went wrong. I was stuck in recovery. Through the process of getting back to stock I guess I messed up.
At least I heard that the Devs are working on 1.55 : )
I found this but, its For ATT, and I don't really know if it would work.
http://forum.xda-developers.com/showthread.php?t=2394155
So if anyone knows if a nandroid backup will restore everything, even hboot 1.55 to 1.44, I would love a link so I can download yours since I upgraded to windows 8.1 with a fresh install before backing up mine...
Also, if I have S-ON, which I cant tell except for the fact that I cant downgrade, why can I lock/unlock my bootloader?
doragu said:
I was downgrading and upgrading and some things went wrong. I was stuck in recovery. Through the process of getting back to stock I guess I messed up.
At least I heard that the Devs are working on 1.55 : )
I found this but, its For ATT, and I don't really know if it would work.
http://forum.xda-developers.com/showthread.php?t=2394155
So if anyone knows if a nandroid backup will restore everything, even hboot 1.55 to 1.44, I would love a link so I can download yours since I upgraded to windows 8.1 with a fresh install before backing up mine...
Also, if I have S-ON, which I cant tell except for the fact that I cant downgrade, why can I lock/unlock my bootloader?
Click to expand...
Click to collapse
No a nandroid does not contain the hboot. Sorry but you'll have to wait till some dev manages to s-off the newest hboot. You don't seem to know what s-off really means so don't worry, I'm sure you'll never need it.
Anyway here's a quote for you to read
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Click to expand...
Click to collapse
Thank you for better explaining that to me.
But why am I still allowed to flash TWRP recovery, and OMJ's Deodexed 3.04...ROM if the security is suppose to block it?
Guess I should of read more. SGS2 was too simple
doragu said:
Thank you for better explaining that to me.
But why am I still allowed to flash TWRP recovery, and OMJ's Deodexed 3.04...ROM if the security is suppose to block it?
Guess I should of read more. SGS2 was too simple
Click to expand...
Click to collapse
Flashing recovery and ROM, doesn't need you to be s-off, but flashing a firmware does
Sent from my HTCONE using Tapatalk 4
elvisypi said:
Flashing recovery and ROM, doesn't need you to be s-off, but flashing a firmware does
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
Okay so as I understand it. When a developer says need to be s-off to flash a rom they do mean it ? or is it some special firmware you are talking about. I had s-off and lost it because I didn't do my research. I'm very disgusted with my self now i'm on H-Boot 1.55 and stuck... also I heard the devs are working on this h-boot to get s-off. Can anyone tell me if this is true?
I was able to flash the viperone rom with S-On without any issues. well may be couple at&t apps which i erased but other than that-Lokks okay for now.
intramorph said:
Okay so as I understand it. When a developer says need to be s-off to flash a rom they do mean it ? or is it some special firmware you are talking about. I had s-off and lost it because I didn't do my research. I'm very disgusted with my self now i'm on H-Boot 1.55 and stuck... also I heard the devs are working on this h-boot to get s-off. Can anyone tell me if this is true?
I was able to flash the viperone rom with S-On without any issues. well may be couple at&t apps which i erased but other than that-Lokks okay for now.
Click to expand...
Click to collapse
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
tkoreaper said:
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
Click to expand...
Click to collapse
I appreciate that however I had s-off and now can't get it back due to my been n00b. So yeah it's a little disappointing
Does this mean I won't be able to get the 4.3 OTA?
tkoreaper said:
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
Click to expand...
Click to collapse
Worst pile of misinformation ever. You do not need s-off to flash a boot animation, however you do need it for important things like downgrading your hboot.
Sent from my HTCONE using xda app-developers app
tkoreaper said:
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
Click to expand...
Click to collapse
And the ability to S-Off to go back to stock unrooted the properly official way. That's all I use it for lol
Konfuzion said:
Worst pile of misinformation ever. You do not need s-off to flash a boot animation, however you do need it for important things like downgrading your hboot.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Oh really? Are you sure about that? Explain to me how we never had custom boot animations until we achieved S-OFF and also explain to me why everything I've read on the topic has been wrong. There was no reason for you to be rude about it. A quick Google search tells you all that you need to know: http://android-revolution-hd.blogspot.com/2013/06/do-we-really-need-s-off.html
With S-OFF you can:
Flash in fastboot original parts of the firmware like: Trust Zone (tz.img), Resource Power Manager (rpm.img), Advanced Digital Signal Processor (adsp.img), bootloader (hboot.img), Radio Config Data (rcdata.img), Splash Screen and others, very often device specific firmware like Consumer IR (cir.img) for the television remote controller in HTC One.
Flash in fastboot custom parts of the firmware above, however I've never seen in my life anyone compiling custom rpm.img or tz.img. I've seen custom bootloaders and Splash Screens only. You can also flash modified radio.img but there is rarely anyone out there who does this.
Use more advanced fastboot commands, for example you can change the CID (Carrier ID) of your device or even MID (Model ID). And this one is the most important one in the context of this article.
Reset the Tampered flag, so your device does not show up as "Relocked" if you relock your bootloader.
Click to expand...
Click to collapse
You can also refer yourself to a thread that I started back when we got S-OFF... Take a look at one of the first things mentioned: http://forum.xda-developers.com/showthread.php?t=2314705
tkoreaper said:
Oh really? Are you sure about that? Explain to me how we never had custom boot animations until we achieved S-OFF and also explain to me why everything I've read on the topic has been wrong. There was no reason for you to be rude about it. A quick Google search tells you all that you need to know: http://android-revolution-hd.blogspot.com/2013/06/do-we-really-need-s-off.html
You can also refer yourself to a thread that I started back when we got S-OFF... Take a look at one of the first things mentioned: http://forum.xda-developers.com/showthread.php?t=2314705
Click to expand...
Click to collapse
Le sigh.....
Maybe I slightly misread your post. You said main thing is "boot screens" you mean splash screens maybe? If so yes you do need s-off, however you don't need s-off to flash custom boot animations. Most importantly flashing a splash screen is not the main reason someone would need s-off, and I am sure the many users of this forum who have flashed a 4.3 based GSM Rom on their CDMA device and don't have s-off would agree.
Last but not least I was in no shape or form rude, even if you did mean to flash splash screens it's still total misinformation that isn't the most important reason to have s-off, it's to save your butt when your in a pickle.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Le sigh.....
Maybe I slightly misread your post. You said main thing is "boot screens" you mean splash screens maybe? If so yes you do need s-off, however you don't need s-off to flash custom boot animations. Most importantly flashing a splash screen is not the main reason someone would need s-off, and I am sure the many users of this forum who have flashed a 4.3 based GSM Rom on their CDMA device and don't have s-off would agree.
Last but not least I was in no shape or form rude, even if you did mean to flash splash screens it's still total misinformation that isn't the most important reason to have s-off, it's to save your butt when your in a pickle.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
And that's why I said "as far as ROMs are concerned..."
Of course S-OFF is used for more important things, but the person's question was about S-OFF in regards to ROMs. And what is a ROM going to do with S-OFF? I answered that question.
tkoreaper said:
And that's why I said "as far as ROMs are concerned..."
Of course S-OFF is used for more important things, but the person's question was about S-OFF in regards to ROMs. And what is a ROM going to do with S-OFF? I answered that question.
Click to expand...
Click to collapse
Ok, sounds fair. Just a misunderstanding
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Ok, sounds fair. Just a misunderstanding
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Okay guys I didn't need to start a war. Is there anything I can do or anyone I can pay to get s-off If I'm on hboot 1.55 at&t?
I really need my s-off back ^^
intramorph said:
Okay guys I didn't need to start a war. Is there anything I can do or anyone I can pay to get s-off If I'm on hboot 1.55 at&t?
I really need my s-off back ^^
Click to expand...
Click to collapse
As of now there it's nothing you can do, this might change in the future.
Sent from my HTCONE using xda app-developers app
Kernel
Konfuzion said:
As of now there it's nothing you can do, this might change in the future.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
So with s-on can I still flash kernel and radio??? My biggest concern is that I won't be able to flash the kernel I want and the radio also when there's an official update how can I get that with custom rom I stalled? I rly miss having s-off rly does anyone know of a paid site who can do that for me?