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.
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.
As the title states guys, I have no idea what RUU I should download or even if one is available ... Like I said, I'm in the UK and I bought the phone sim free from Carphone Warehouse and I am on Tesco.
Cheers in advance
AllAboutTheCore said:
As the title states guys, I have no idea what RUU I should download or even if one is available ... Like I said, I'm in the UK and I bought the phone sim free from Carphone Warehouse and I am on Tesco.
Cheers in advance
Click to expand...
Click to collapse
HAve you been here ??
http://forum.xda-developers.com/showthread.php?t=2224752
Download this one
http://www.androidrevolution.nl/downloader/download.php?file=One_2.17.401.1_odexed.zip
If you need a guide, follow this
http://forum.xda-developers.com/showthread.php?t=2265618&highlight=back+to+stock
Hope this helps, do it by the numbers and you'll be fine.
Bare in mind that you cannot at the moment relock your device to a warranty perfect state, it will sat relocked, simple as that and they will know that you unlocked it.
dladz said:
HAve you been here ??
http://forum.xda-developers.com/showthread.php?t=2224752
Download this one
http://www.androidrevolution.nl/downloader/download.php?file=One_2.17.401.1_odexed.zip
If you need a guide, follow this
http://forum.xda-developers.com/showthread.php?t=2265618&highlight=back+to+stock
Hope this helps, do it by the numbers and you'll be fine.
Bare in mind that you cannot at the moment relock your device to a warranty perfect state, it will sat relocked, simple as that and they will know that you unlocked it.
Click to expand...
Click to collapse
Cheers dude ... I did look at that a bit ago when I was trying to find it but I want the actual stock if poss from HTC. My current software version is 1.29.401.13, is that an OTA or is that the version of an RUU I need? I looked on the HTCDev site but I couldn't find anything under my operator but then I don't know if I can just flash a generic UK RUU or Europe or what lol, bit more to it on this phone than on my previous Xperia Ray.
The one listed should be fine m8, just know that you can't relock your phone properly.
the one i downloaded to keep for my sim free UK is RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe from this thread: http://forum.xda-developers.com/showthread.php?p=39588860
restore that and it should prompt to update to whatever the latest version is once you boot up
Cheers guys, I'll download the suggested files and have a butchers lol
IINexusII said:
the one i downloaded to keep for my sim free UK is RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe from this thread: http://forum.xda-developers.com/showthread.php?p=39588860
restore that and it should prompt to update to whatever the latest version is once you boot up
Click to expand...
Click to collapse
Hi I have been following this thread, I read the instructions and it says you have to fastboot oem lock and then flash the RUU.
When you have gone through this process do you have to go through the process of unlocking the device via HTC id token again should you want to unlock, root and flash a recovery?
maxal said:
Hi I have been following this thread, I read the instructions and it says you have to fastboot oem lock and then flash the RUU.
When you have gone through this process do you have to go through the process of unlocking the device via HTC id token again should you want to unlock, root and flash a recovery?
Click to expand...
Click to collapse
yes you do
IINexusII said:
the one i downloaded to keep for my sim free UK is RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe from this thread: http://forum.xda-developers.com/showthread.php?p=39588860
restore that and it should prompt to update to whatever the latest version is once you boot up
Click to expand...
Click to collapse
OP is on 1.29.401.13 so that RUU is next to useless without S-OFF...
EddyOS said:
OP is on 1.29.401.13 so that RUU is next to useless without S-OFF...
Click to expand...
Click to collapse
Any idea what one I need mate or is it not available? Tbh, I did try and restore using all the Europe versions on the link and I always got an error telling me it wasn't the correct RUU ... Why is it so hard to restore a One compared to say, Sony. When I had an Xperia Ray it was so easy to do, software direct from Sony to restore to stock, yet HTC have nothing simple when it comes to restoring ... It's blagging my head just trying to find any files to go back to stock.
AllAboutTheCore said:
Any idea what one I need mate or is it not available? Tbh, I did try and restore using all the Europe versions on the link and I always got an error telling me it wasn't the correct RUU ... Why is it so hard to restore a One compared to say, Sony. When I had an Xperia Ray it was so easy to do, software direct from Sony to restore to stock, yet HTC have nothing simple when it comes to restoring ... It's blagging my head just trying to find any files to go back to stock.
Click to expand...
Click to collapse
HTC have never publicly released their RUUs, no idea why. You will need to use mike1986's 'stock' ROM to go back to stock or use one of the Nandroids posted in the Nandroid/RUU thread which is 1.29.401.13 or higher
Cheers for all the help guys, I think I'll just leave it unrooted and stock, at least until there is a stock RUU that is the same as the version I'm currently on, I could use the one from Android Revolution but correct me if I'm wrong but isn't that the leaked 4.2.2 whereas I want an RUU for my curren version but if it's not available then I'll just wait and hope it appears at some point ... Maybe I'll take the plunge then when I have all the bits I need lol.
AllAboutTheCore said:
Cheers for all the help guys, I think I'll just leave it unrooted and stock, at least until there is a stock RUU that is the same as the version I'm currently on, I could use the one from Android Revolution but correct me if I'm wrong but isn't that the leaked 4.2.2 whereas I want an RUU for my curren version but if it's not available then I'll just wait and hope it appears at some point ... Maybe I'll take the plunge then when I have all the bits I need lol.
Click to expand...
Click to collapse
There isn't an RUU for 1.29.401.13, 1.28.401.7 is the latest one to leak
EddyOS said:
There isn't an RUU for 1.29.401.13, 1.28.401.7 is the latest one to leak
Click to expand...
Click to collapse
I am in the same boat as you.. My rom is also 1.29.401.13 and i can not find the RUU for it.. So someone correct me if I am wring please.
From what I understand is that in order to use the RUU , you must have the same 1.29.401.13 RUU for this 1.29.401.13.. if you have any other RUU it will not work.. is this correct?
so if there is no 1.29.401.13 out.. then is it only to just use the android revolution 10.1 rom or the stock rom .4.2.2 ?
thanks for anyone who will clarify this .. as I am really lost
mojolive said:
I am in the same boat as you.. My rom is also 1.29.401.13 and i can not find the RUU for it.. So someone correct me if I am wring please.
From what I understand is that in order to use the RUU , you must have the same 1.29.401.13 RUU for this 1.29.401.13.. if you have any other RUU it will not work.. is this correct?
so if there is no 1.29.401.13 out.. then is it only to just use the android revolution 10.1 rom or the stock rom .4.2.2 ?
thanks for anyone who will clarify this .. as I am really lost
Click to expand...
Click to collapse
You have to have 1.29.401.13 or higher, e.g. 1.29.401.16 would work if available, same for 2.17.401.1
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 ?
I take it my One on Hboot 1.54 is stuffed atm for and recoveries/rom flashing?
htcdev unlocked bootloader - only to find i cant really go any further!!!!
You can flash anything the same as anyone else, you just don't have an RUU available to go back to stock if required so make sure that you make a backup before doing anything else
EddyOS said:
You can flash anything the same as anyone else, you just don't have an RUU available to go back to stock if required so make sure that you make a backup before doing anything else
Click to expand...
Click to collapse
hmm now this has perked me up a bit! I must be reading it wrong, not a noob at this flashed my sensation a LOT! but this seems to be a different kettle of fish!
Is TWRP the recovery of choice for this?( I notice from your sig you are on stock recovery? are you on stock ROM also?)
ty
Over the weekend i took my T-Mobile HTC One and made it into a GPe unit.
It made my Hboot 1.54 as well. I was able to use HTC Dev to unlock it and put TWRP on it. Monday in fact i did that and yesterday and today i have been playing around with GPe radios and T-Mobile radios..
JayIce11 said:
hmm now this has perked me up a bit! I must be reading it wrong, not a noob at this flashed my sensation a LOT! but this seems to be a different kettle of fish!
Is TWRP the recovery of choice for this?( I notice from your sig you are on stock recovery? are you on stock ROM also?)
ty
Click to expand...
Click to collapse
I'm 100% stock, don't really need a custom ROM these days, but I did make sure I got S-OFF before doing anything else!
I've always been a fan of CWM but TWRP seems to be the recovery of choice these days so give them both a go and see for yourself! Then get your ROM and flash away (oo-er!)
JayIce11 said:
hmm now this has perked me up a bit! I must be reading it wrong, not a noob at this flashed my sensation a LOT! but this seems to be a different kettle of fish!
Is TWRP the recovery of choice for this?( I notice from your sig you are on stock recovery? are you on stock ROM also?)
ty
Click to expand...
Click to collapse
you can get s-off on 1.54 also. Just send off to fonefunshop. Very quick service.