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.
Related
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 ?
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
Hi, I was wondering if there was going to be an RUU for 4.03.651.2 firmware. I tried to take the update with an outdated version of TWRP, and I would like to go back to stock and reroot. I have tried and failed to gain S-Off with Revone and moonshine. I am unsure of what to do. My phone is not recognized by ADB in recovery, so I cannot use the S-Off workaround to flash an old RUU. Any suggestions/responses are appreciated.
Thanks,
Vobeyo
Vobeyo said:
Hi, I was wondering if there was going to be an RUU for 4.03.651.2 firmware. I tried to take the update with an outdated version of TWRP, and I would like to go back to stock and reroot. I have tried and failed to gain S-Off with Revone and moonshine. I am unsure of what to do. My phone is not recognized by ADB in recovery, so I cannot use the S-Off workaround to flash an old RUU. Any suggestions/responses are appreciated.
Thanks,
Vobeyo
Click to expand...
Click to collapse
there should be in the future but we still dont even have a 1.31 RUU yet.. only 1.29
P.Mobile said:
there should be in the future but we still dont even have a 1.31 RUU yet.. only 1.29
Click to expand...
Click to collapse
Hmm... I just assumed that there wouldn't be an RUU for 1.31. Do you know of any way to gain S-Off so that I can flash the 1.29 RUU?
RUU
This can be very frustrating, I know.
I used Moonshine to achieve S-OFF, yesterday. Reason was because I managed to delete almost everything, I still don't know exactly what happened. However, if I remember correctly, you need S-On in order to run a stock RUU. There are several threads that pretty much will walk you thru the steps needed to flash the RUU. I was on them yesterday.
Good luck.
retiredtrebor said:
This can be very frustrating, I know.
I used Moonshine to achieve S-OFF, yesterday. Reason was because I managed to delete almost everything, I still don't know exactly what happened. However, if I remember correctly, you need S-On in order to run a stock RUU. There are several threads that pretty much will walk you thru the steps needed to flash the RUU. I was on them yesterday.
Good luck.
Click to expand...
Click to collapse
You don't need S-Off or S-On to run the RUU, but the bootloader has to be locked (or relocked). Believe that I read that HTC was going to not release RUUs any more because they didn't want others to tear them apart, etc. But don't quote me on that one...
From my understanding, S-Off is required to flash an RUU for a firmware version that does not match the version you are currently on. Could you please refer me to one of these threads? I would appreciate it very much.
Vobeyo said:
From my understanding, S-Off is required to flash an RUU for a firmware version that does not match the version you are currently on. Could you please refer me to one of these threads? I would appreciate it very much.
Click to expand...
Click to collapse
I've also heard the same however how can I gain S-Off without mounting the internal storage? Or ADB? I can't get either to work.
Sirricharic said:
I've also heard the same however how can I gain S-Off without mounting the internal storage? Or ADB? I can't get either to work.
Click to expand...
Click to collapse
I believe that if you have a custom recovery installed, you can use the workaround by accessing the terminal from the recovery, type the command, and then lock the bootloader. I am not completely sure on that, though.
If your on 4.3 there is no RUU and no s-off exploit at this time. This is why it's always recommended to root/s-off before you update.
Sent from my HTCONE using xda app-developers app
Vobeyo said:
From my understanding, S-Off is required to flash an RUU for a firmware version that does not match the version you are currently on. Could you please refer me to one of these threads? I would appreciate it very much.
Click to expand...
Click to collapse
Here's one of the links: http://forum.xda-developers.com/showthread.php?t=2251800
Check in the Sprint HTC One Forums, the first two sub-forums both have info you're looking for.
retiredtrebor said:
Here's one of the links: http://forum.xda-developers.com/showthread.php?t=2251800
Check in the Sprint HTC One Forums, the first two sub-forums both have info you're looking for.
Click to expand...
Click to collapse
If you updated your phone to latest sprint 4.3 that's it you cannot instal RUU any more
s-on s-off not gonna help you
you can download naked drivers for htc one http://dl.xda-developers.com/attachd...river_0.72.zip but first delate/uninstal all htc/syn drivers
and jus push any 4.3 rooted rom to your phone and install g-luck
Don't know if this will help you or not, just stumbled across it a couple of minutes ago.
http://forum.xda-developers.com/showthread.php?t=2236418
retiredtrebor said:
Here's one of the links: http://forum.xda-developers.com/showthread.php?t=2251800
Check in the Sprint HTC One Forums, the first two sub-forums both have info you're looking for.
Click to expand...
Click to collapse
Thanks. I will look into this as soon as time permits.
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...
Hello,
I wanted to S-OFF my HTC One M7 and it looks like my last hope is use SunShine in the end.
Since I receive the following message when SunShine runs on my phone, I would like to receive some help to figure out what is the stock kernel I have to flash in order to run SunShine.
At the moment I use Elemental X kernel, as shown in the signature below, but I have not been able to find a kernel to meet the requirements. By the way, I have a rooted and unlocked phone, and I wouldn't like to come back to stock if possible.
Thanks
fbcyborg said:
Hello,
I wanted to S-OFF my HTC One M7 and it looks like my last hope is use SunShine in the end.
Since I receive the following message when SunShine runs on my phone, I would like to receive some help to figure out what is the stock kernel I have to flash in order to run SunShine.
At the moment I use Elemental X kernel, as shown in the signature below, but I have not been able to find a kernel to meet the requirements. By the way, I have a rooted and unlocked phone, and I wouldn't like to come back to stock if possible.
Thanks
Click to expand...
Click to collapse
1) do a nandroid backup in TWRP
2) install maximusHD, this one: http://llabtoofer.com/2014/12/02/htc-one-maximushd-46-0-0/
3) sunshine s-off
4) restore you nandroid backup
Hi!
Thanks a lot for your hint!
And what about doing as explained here instead? I mean where it says about "Step-by-step procedure before attempting to S-OFF (with the universal Rumrunner version for international variants)".
It doen't say anything about the hboot version. That should work I guess, without wiping anything by the way.
fbcyborg said:
Hi!
Thanks a lot for your hint!
And what about doing as explained here instead? I mean where it says about "Step-by-step procedure before attempting to S-OFF (with the universal Rumrunner version for international variants)".
It doen't say anything about the hboot version. That should work I guess, without wiping anything by the way.
Click to expand...
Click to collapse
rumrunner only works on hboot 1.54 and lower
clsA said:
rumrunner only works on hboot 1.54 and lower
Click to expand...
Click to collapse
OK, thank you.
So, I could flash a ROM having such hboot and then try rumrunner. If yes, can you suggest me some rom to flash? There's lot of stuff here in the forum, I get confused to be honest.
fbcyborg said:
OK, thank you.
So, I could flash a ROM having such hboot and then try rumrunner. If yes, can you suggest me some rom to flash? There's lot of stuff here in the forum, I get confused to be honest.
Click to expand...
Click to collapse
nope, you cant back flash your HBOOT at all unless you are already s-off, I see in your signature your on 1.57, sunshine is the only way to s-off your device, really the only way - (people still ask after saying this if there is another way), you also need as close to stock as possible to use sunshine.
I succeeded using Sunshine in the end, flashing a stock kernel (boot.img) extacted by a stock ROM.