[Q] post/pre OTA explaination? - G2 and Desire Z Q&A, Help & Troubleshooting

Could someone explain or point me in the direction of an explanation for how installing a custom rom affected automatic updates, as well as the difference between pre and post ota, and why we can't install a pure clean android 2.2 installation in our phones. I am relatively new to this, but did alot of iPhone hacking before.. I've already rooted, S-OFF and flashed a few different roms having my phone 2 weeks and new to android hope someone can explain, thanks :_)

When you flash a custom ROM, you will no longer get the automatic updates OTA. Either you will have to revert to the stock ROM for the update, or the ROM developer will have to incorporate the OTA update changes into the ROM.
There are a few ROMs that attempt to give you a plain vanilla Android experience. But in my opinion, Cyanogen is one of the best mixes of plain Android with lots of extra features.

Okay that makes sense, I'm currently using a villian rom with no sense, is it worth my while installing cyanogen? and if so will i go with RC4 of wait for the stable release?

jakbjak said:
Could someone explain or point me in the direction of an explanation for how installing a custom rom affected automatic updates, as well as the difference between pre and post ota, and why we can't install a pure clean android 2.2 installation in our phones. I am relatively new to this, but did alot of iPhone hacking before.. I've already rooted, S-OFF and flashed a few different roms having my phone 2 weeks and new to android hope someone can explain, thanks :_)
Click to expand...
Click to collapse
Well, the reason for many semi-bricks from trying to downgrade to original stock rom pre- or post-OTA was the fact that hboot was hacked, and not truly "S-OFF." If you search the dev section you will find the S-OFF, SIM unlock, SuperCID guide that will give you true S-OFF. I recommend reading that--it helped elucidate why semi-bricks were showing up. Once this is done, it should be easy to flash a rooted, stock ROM when the OTAs start showing up and get the update that way, or just wait for it appear in the forums (which is usually sooner than the OTA gets pushed out, anyhow).

So the S-OFF I have isn't complete? Not that I need a sim unlock as I bought the phone off contract, but it's worth my while getting the true S-OFF? Thanks for all ye're help, there are so many people talking about these things in every section it's hard to pull a search of a simple explanation,

jakbjak said:
So the S-OFF I have isn't complete? Not that I need a sim unlock as I bought the phone off contract, but it's worth my while getting the true S-OFF? Thanks for all ye're help, there are so many people talking about these things in every section it's hard to pull a search of a simple explanation,
Click to expand...
Click to collapse
Yes, the previous S-OFF was via an engineering version of HBOOT, which was set to report S-OFF. But the security setting is actually held in the radio, and was still S-ON.
The new, "true" S-OFF (via gfree) is a lot safer than the old method, e.g. much less prone to a brick if you flash the wrong thing (e.g. an older RUU than the ROM you're running).

Related

[WARNING] Do not flash a new official RUU/ROM/OTA if you have root and/or S-OFF

DO NOT FLASH A NEW RUU OR OFFICIAL ROM IMAGE UNLESS YOU *REALLY* KNOW WHAT YOU ARE DOING !
Sorry for shouting, but this is very important. Thanks to the mods for making this sticky.
The latest official RUU that has been released - http://forum.xda-developers.com/showthread.php?t=870369 - has been found to break the existing methods of rooting and getting full S-OFF.
This shouldn't be a big suprise, because when HTC saw that the amazing devs on XDA had cracked the existing security, we should expect them to put something even tougher in later releases.
So flashing any later release, whether that's an official RUU or just the ROM image (PC10IMG.zip) is a very dangerous thing to do until it has been fully tested and "cleared" by the devs here. i.e. your previously rooted and S-OFF'd phone might lose root and go back to S-ON, and be unable to be rooted and S-OFF'd again.
It's of course fine if your phone came with a particular ROM release to flash that *exact same* release back onto the phone if you want to return to stock. What I'm referring to is flashing a brand new release that isn't the one that came with your phone.
It's fine to flash custom ROMs of course, because those have already been tested out. In general, it's probably best to steer very clear of new official releases, and wait till the devs have pulled them apart and put any cool new stuff into a custom ROM. Then you know it'll be safe to flash.
Currently I don't think it's entirely clear what just flashing a new *radio* on its own will do, as opposed to the entire ROM/RUU. That's still being worked on. But steer clear of even that if you're not sure what you're doing or dont' want to take any chances of losing root/S-OFF.
Thanks for reading
Thanks for the heads up.
I flashed the ROM you mentioned.
For those who want to try:
Just remember to get REAL S-OFF using gfree before flashing it.
This provide you a medicine for regret. You can get back to WWE ROM using WWE RUU and root/recover your old ROM.
What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.
androidtoy09 said:
What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.
Click to expand...
Click to collapse
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.
steviewevie said:
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.
Click to expand...
Click to collapse
Ok, thanks for clearing it up. So, RUU is pretty much similar to the method RIM uses to flash its OS on the Blackberries.
Im a little confused here.. So just to clear some things up i hope someone will answer these questions i have.
I have the software on my Desire Z that it came with (1.34.405.5), which i've rooted, S-off'ed and installed another kernel for OC porpuses. This is working fine, but lets say that i wanted to try another rom .. After some time i decide to go back to the stock software and then update to the newest software, would that be a problem? And has HTC released some newer software than the one iam using?
If you flashed back to stock, that would be fine. But if you flashed a new official update (e.g OTA), then you run the risk of installing something that you can't root/S-OFF.
It is best to steer clear of any official upgrades until they've been checked by the devs here and been given the all-clear.
Given that the phone came with certain areas write-protected, and the devs managed to crack that, we should be expecting HTC to release an even more secure update.
Yes, there is a new ROM out, at the moment for Egypt, that seems to have increased security. It would not be a suprise if HTC rolled out similar security as an OTA update for all existing ROMs. Right now there is something in that Egypt ROM (probably the hboot, at the minimum) which mean existing permanent root and S-OFF methods fail. It may be this is easily cracked again, or maybe it will take some time, who knows.
Bottom line - don't apply any official updates to your phone if it is rooted/S-OFF or you plan to root/S-OFF.
Sent from my HTC Desire Z
perm-rooted g2 stock tmobile rom s-off
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.
blitz69 said:
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.
Click to expand...
Click to collapse
The trouble is, HTC/T-Mobile don't want you to root and/or S-OFF your phone, because it's a lot easier to end up bricking the phone if you don't know what you're doing. They put greatly increased security on the G2/DZ/DHD when they came out, in order to help prevent this.
Now this security has been cracked, we can expect HTC/T-Mobile to try and increase security even further (e.g. closing loopholes that let our current methods of root/S-OFF work) in future updates.
So if you accept any future OTA, you run a high risk of accepting something that will lock you out of root and S-OFF, at least temporarily, and possibly permanently (depending on how good a solution they come up with).
If you are not bothered about root/S-OFF, then that's fine of course.
This doesn't mean that you necessarily have to switch to a custom ROM to get updates though. If you stay with the stock ROM (and I'm still on a stock ROM too right now), then just do not accept the update when an OTA comes out, and keep checking these forums to see when the devs say that they can root/S-OFF with the new version. When they say it's ok then you know you can apply the update and still get root/S-OFF.
This already happened with the G2. Very soon after release, but after rooting had been achieved, there was an OTA. Most people here decided to wait until the OTA had been looked at, and sure enough there was a small adjustment needed to the rooting method. But of course this OTA was before HTC had a chance to respond to the cracking of the security, so as I said, any future updates may well require a lot more time and effort from the devs to investigate and crack again.
Ok. Thank you very much
Will this muff up my phone if I factory reset it by using the Power+Volume Down option?
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
What do you mean with gfree?
Is my waranty broken When i execute radio s-off?
Is it possible to make it radio s-on?
Yes,warranty is broken,but with the new gfree method
you can go back to S-ON:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
ericjosepi said:
Will this muff up my phone if I factory reset it by using the Power+Volume Down option?
Click to expand...
Click to collapse
If you do a factory reset then I think you'll lose root, but you can get it back again easily enough. The issue for this thread is flashing new updated stuff from HTC etc.
Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
You might still need that backup, e.g. if you don't know what your old CID was and you want to un-do that bit too. I would keep it.
Sorry I don't think I understand your last question though, or why you say the uberroot method (I'm personally not keen on that name, it's just the usual method using Visionary/rage with gfree, not a new method) doesn't work.
Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
If you are only interested in permanent root you only need radio S-OFF and then it is sufficient to use
# ./gfree -s off
instead of
# ./gfree -f
in the following commands.
And gfree can now also be used to set radio S-ON by using the "-s on" option and to change the CID back to the original value be using i.e. "-c T-MOB010" if you want or have to go back.
Click to expand...
Click to collapse
But for CID (you mean SuperCid right?) I need the backup?
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Thanks for the advice, I will stick myself with the current rom for a while
Ganii said:
Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
But for CID (you mean SuperCid right?) I need the backup?
Click to expand...
Click to collapse
Yes, I mean to go from your SuperCID back to your regular CID. You might not know what your original CID was.
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
Yes, if you flash a stock ROM then it won't affect your S-OFF and CID status (or SIM unlock). These are stored in your radio configuration partition, and not in any of the partitions which are overwritten by the ROM flash.

[Q] stock update S-OFF phone

I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Kokuyo said:
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Click to expand...
Click to collapse
Why did you root your phone? There is no need to update your phone to the latest OTA update if you are wanting to install custom ROMs.
Because I was testing custom mods and wanted to go back to stock?
Kokuyo said:
Because I was testing custom mods and wanted to go back to stock?
Click to expand...
Click to collapse
ahhh, I thought you had just rooted it. I updated the day after I received my new phone. I had problems with bluetooth (music wouldn't resume after ending phone calls) and wound up here on the XDA forums looking for answers. I ended up rooting my phone, installing CM6 and now CM7 and never looked back. There is no bluetooth switching problems using CM builds so I'm happy.
Found this:
http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
Thanks, that looks interesting. Now the only question: Do I need my original CID? And if so, how do I find it now that the CID has been changed by gfree?
That link is about a procedure to restore the stock G2 ROM. Since you seem to have a DZ ROM, I'm not sure if you want to flash a G2 ROM (though the other bits might be useful).
The 1.72 OTA update has been rootable for some time now, so you can safely accept the update if you want. But it might be easier just to flash the 1.72 ROM in its entireity (you can get it from the dev forum).
With SuperCID and S-OFF you should have no problems flashing 1.72.
steviewevie said:
With SuperCID and S-OFF you should have no problems flashing 1.72.
Click to expand...
Click to collapse
Really? Then I don't quite understand the stickied warning thread that says to never, ever attempt that.
Anyhow, I gave the Virtuous mod another go. Since it has sense and 1.72 I'm thinking of testing this one out a bit more, before I go flashing stock.
Thanks for the replies, though.

[Q] No OTA updates available after debranding and downgrading

Hi guys, I've been searching the forum for a while but I still can't find a solution/reason for what it's happening to my DZ, which I bought from England and vodafone branded.
Soon after the first configuration I upgraded to 1.72 as suggested, but I couldn't know that rooting was then no more possible. I didn't want to be stuck on a vodafone branded and only-english rom, so I debranded succesfully my DZ by downgrading to a stock htc 1.34 rom (RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed), obtaining then permroot + superCID.
Now my rom speaks italian (as I wanted) and is rooted, but if I check manually for updates, I get only a message telling me that the phone is updated and there are no new upgrades available.
I tried to:
- look for updates before rooting and with s-on (CID vodap_001), waiting even for 1 week
- put back the gold card I used to downgrade and then checking for OTA
- check for updates with root, superCID and s-off
Is there any reason for that?
How can I update again to 2.2.1 (1.72 & 1.83)?
ps: I prefer a stock rom for the moment instead of a custom rom
Any help/opinion is appreciated!
There won't be any OTA updates once you've rooted and de-branded. And if there are, do not accept them, as they will either fail or possibly unroot/brick your phone.
Your option will to be to find a rooted, stock ROM that comes with the latest OTA software package already installed. Check the dev section, they have a list of ROMs. You may not be able to find the exact specific ROM you've currently got, but there are many choices that can come close.
First of all, thanks for prompt answering martonikaj.
I thought I could receive and install ota updates since there was a stock rom with superCID in my devide.. which is different from having a custom rom like Virtuos.
What about users telling they had downgraded-debranded-rooted their DZ and can receive and install successfully OTA updates??
Flashing a rooted stock rom implies wiping everything.. and I prefer to avoid that.
There's a rooted 1.82 stock ROM at : http://forum.xda-developers.com/showthread.php?t=960149 . Really if you're going to make that huge version jump you should do a wipe. Back up your stuff with Titanium backup first
Rixan said:
First of all, thanks for prompt answering martonikaj.
I thought I could receive and install ota updates since there was a stock rom with superCID in my devide.. which is different from having a custom rom like Virtuos.
What about users telling they had downgraded-debranded-rooted their DZ and can receive and install successfully OTA updates??
Flashing a rooted stock rom implies wiping everything.. and I prefer to avoid that.
Click to expand...
Click to collapse
Sorry but in all my times rooting and modding devices, applying OTA updates has never been something that works with rooted devices.
Unfortunately, yes, if you want to upgrade to the rooted version of the latest OTA ROM, you're gonna have to wipe everything and start from fresh with the new ROM.
Same here
Hi,
The same thing is exactly happening to me. My phone keeps telling me that there is not update but the software number is 1.34, which from what I've read is an older firmware. Shouldn't my phone be able to detect the update?
The question isnt whether rooted is better, but why our phones are not receiving any ota. Granting that stock rom is not better, the problem is there is no notification at all that there is an update.
FYI, I have flashed an official rue version but still has s-off. :-D I don't know if having s-off would prevent the phone from finding an update.
Think about it this way people: when you mod your phone by rooting, it's like cutting the imbillical cord with your carrier/manufacturer's update servers. Don't worry about why, just have that mentality as it will make all your lives easier. If you rooted, why would you want a stock rom that limits you?
If you want stock with sense, go for GingerSense, Vitruous, etc..
If you want stock w/o sense, go for any of the other pre-rooted G2 roms.
I really don't understand why people would complain about OTA updates when you can backup and update to a rom of your choice whenever you want. Plus, if you don't like it, you can revert! Something you cannot do with a stock OTA update.
/rant
Sent from my Virtuous Desire Z 1.0.2 using XDA App

When is the best time to S-off?

Newb Alert!
Hi I'm currently running stock android 2.2.1 (build 1.72.405.3) on an unbranded DHD in the UK (I'm on Orange if that matters) I'm getting frustrated with the wait for 2.3 to be released here so I want to install the official RUU that was released a little while back.
I understand that to do this my phone will still be "official" ish, and that the only real difference between this way and OTA is that I'll lose my apps etc. which I can handle.
I want to be able to try some custom roms (in the future) but then be able to return the phone to stock - I believe this is possible? Am I better off downgrading now and doing S-off / eng-off, clockwork recovery, root etc? Or will I be fine to downgrade from 2.3 to 1.32 in the future to do everything I'll need for custom ROMS?
Or am I a muppet and have things totally wrong?
Any help appreciated,
Grim.
Ps. I've read the sticky in the Development forum, and tried searching the forum to find answers but have found it difficult as the terms I'm searching for are really generic - for this forum at least.
grimbola said:
I want to be able to try some custom roms (in the future) but then be able to return the phone to stock - I believe this is possible? Am I better off downgrading now and doing S-off / eng-off, clockwork recovery, root etc? Or will I be fine to downgrade from 2.3 to 1.32 in the future to do everything I'll need for custom ROMS?
Click to expand...
Click to collapse
Simple answer: Do it NOW!!!
Yes you can always go back to stock.
Much easier to do everything now.
Even if you only do root and S-OFF, you will be protected should the OTA update arrive in the sense that you won't need to downgrade again. But in for a penny and all that, go for the lot now and start exploring the greatness of Android and Sense (if you like that).
grimbola said:
Newb Alert!
Hi I'm currently running stock android 2.2.1 (build 1.72.405.3) on an unbranded DHD in the UK (I'm on Orange if that matters) I'm getting frustrated with the wait for 2.3 to be released here so I want to install the official RUU that was released a little while back.
I understand that to do this my phone will still be "official" ish, and that the only real difference between this way and OTA is that I'll lose my apps etc. which I can handle.
I want to be able to try some custom roms (in the future) but then be able to return the phone to stock - I believe this is possible? Am I better off downgrading now and doing S-off / eng-off, clockwork recovery, root etc? Or will I be fine to downgrade from 2.3 to 1.32 in the future to do everything I'll need for custom ROMS?
Or am I a muppet and have things totally wrong?
Any help appreciated,
Grim.
Ps. I've read the sticky in the Development forum, and tried searching the forum to find answers but have found it difficult as the of yerms I'm searching for are really generic - for this forum at least.
Click to expand...
Click to collapse
hi grim..
not neccesary you are going to lose your apk´s...
you can install "titanium backup" and do a backup of your apk´s, your system and your data (dialer, missed calls, wifi passwords...on sd-card\titaniumbackup) and then when you has installed your new gingerbread rom you can restore it.
download it from android market..
and finally say to you step by step what should to do:
1ºDOWNGRADE proccess from 1.72xx to 1.32xx wee off. ru
2ºroot with visionary Rxx
3º s-off eng-off+SUPERCID
4ºinstall ROM MANAGER from market and then flash a CWM recovery (lastest)
5ºDOWNLOAD the gingerbread rom, copy, paste to sd card root,
6ºDO FULL WIPE in recovery (factory reset, data, dalvik)
7ºFLASH the new rom and ENJOY
Mr_JMM said:
Simple answer: Do it NOW!!!
Click to expand...
Click to collapse
WIN!!!!!!
Hi grimbola
You can do anything, anywhere, and anyhow on your Desire HD (But make sure you know what you are doing. Lol.) It all depends on your risk appetite.
only follow the guides, it sounds more difficult than it is.
I did it as an unexperienced user 3 weeks ago and the master plan was, to read the guides
Hi guys,
Thanks for all the speedy replies! I read them last week, but have only now have the time to reply.
I did it! I downgraded to 1.36 (?) then ran the tool on my pc to do radio S-off then also ran the other tool to Eng S-off - I followed jkoljo's posts (from the sticky roll-up thread over on the development forum). I've now installed the official 2.3. It was a little scary at times, but easy as pie!
The only issue I had was that I don't think I backed up my apps correctly (I used Astro file browser to do it) as they have not all been restored, however this is no great pain!
I'm now thinking that I might try installing a custom ROM, maybe Leedroid? I'm after something that is like the stock rom - i.e. Sense based (at least to start with) but has more bells and whistles - any suggestions are welcome!
Once again many thanks for your replies,
Grim.

re-exploring rooting, flashing, and so on

Just wanted to make a post about re-exploring the whole rooting and custom ROM nature of Android.
I used to be fairly active when I was using my Desire HD back in the day (which remains one of my all time favorite devices). I was making splash screens, boot animations, discovering my own tweaks and stuff, which are probably around here in the Desire HD section somewhere, inclusing a bootloader, splash flash, radio flasher and all sorts.
And then it seemed to me that most of the reasons people were rooting for, were starting to becoming irrelevant, as more of those features were being built in etc. For my phones after the HD, I used a custom recovery at most, but never bothered to root, or install a different rom. Not to mention one of the more important banking apps I used refuses to work with root. Even now, I find my self exploring, tweaking, and then removing root. It seems to leave things as I set them whilst letting me run the phone normally.
I've been on the HTC10 for a few weeks now and a few issues with it have forced me to consider alternative ROMS as a way of fixing these or getting more out of the phone than is already possible. I unlocked the bootloader fine, but I dont think I will bother with S-OFF.
Last time I tried to install a custom rom to a phone with S-ON, you had to install the ROM first, and then go back into the bootloader and flash the roms boot.img seperatley. Apparently that step isnt necessary anymore, it takes care of it all during the installation process.
I'm glad I started to get into it all again, and I will be keeping an eye on new or interesting roms and seeing what becomes of them. Open to suggestions too
S-off isn't as much of a necessity as it used to be with some of the older HTC phones. It still has its usefulness, though. As far as ROM flashing goes, you can flash a ROM on the 10 without having to flash the boot.img separately, as you stated.
Sent from my HTC 10
The process is how I remember it on my old Desire HD, which I dug out recently. For whatever reason it cannot be changed to ENG-HBOOT or S-OFF (I think the bootloader is too recent or it was when HTC decided to start locking bootloaders, or something along those lines) it is bootloader unlocked, but S-ON RL (not sure what the RL means ... re-locked?) I updated the recovery to 4EXT since apparently no one seems to like CWM/Rom Manager these days, and I reflashed a more stable rom to it, which needed the boot.img flashed in fastboot.
S-OFF and ENG-HBOOT was fun for things like custom splash screens and so on, buts its nice that it isnt necessary for ROM flashing.
I was debating whether to bother with S-OFF, but in the end I'm glad I did if only to have the latest radio firmware. A bit terrifying to be a big step closer to bricking, though.
Everyone seems to be using TWRP recovery now, by the way.
Also, might want to give LeeDroid ROM a shot. Have been very impressed with how many kinks he's worked out.
The only finance app I know of that won't run on a rooted device is Android Pay. There's a workaround for this, though: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 Can't imagine not having root!
pixelvisions said:
I was debating whether to bother with S-OFF, but in the end I'm glad I did if only to have the latest radio firmware. A bit terrifying to be a big step closer to bricking, though.
Everyone seems to be using TWRP recovery now, by the way.
Also, might want to give LeeDroid ROM a shot. Have been very impressed with how many kinks he's worked out.
The only finance app I know of that won't run on a rooted device is Android Pay. There's a workaround for this, though: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 Can't imagine not having root!
Click to expand...
Click to collapse
Yeah I know it's opens up a lot of avenues for things, the app is Barclays, I'm in the UK so it may differ from what you have if you're elsewhere. They did ALOT of work to make it pretty unusable if you're rooted, and it won't even load at all with xposed and root cloak installed. A few do work, such as Nationwide.
I am on Maximus HD (LlabTooFeRs ROM), which is easier because OTA updates etc. I used to use LeeDroid a lot back on my Desire HD. I'll try a variety of roms when I can find the time.
HTC10 is pretty stable for now though. My main problem (just for fun really) is figuring out how to radio s-off and eng s-off my old desire HD. The cid is ORANG001, but the phone itself accepts any sim as it's been unlocked. Beyond that, I cannot downgrade the bootloader, the phone is rooted, bootloader unlocked, the sd card for it is a gold card, although I may try another. It just seems to not want to do anything.
silegeek said:
Yeah I know it's opens up a lot of avenues for things, the app is Barclays, I'm in the UK so it may differ from what you have if you're elsewhere.
Click to expand...
Click to collapse
Ah, I see -- a lot of frustration with that app on these forums!
pixelvisions said:
Ah, I see -- a lot of frustration with that app on these forums!
Click to expand...
Click to collapse
Yeah I noticed that! :laugh:
silegeek said:
Yeah I noticed that! :laugh:
Click to expand...
Click to collapse
Hey there. Just something to try out, if you want a bunch of tweaks build into the ROM, would be Viper10. It's really amazing and comes with OTA updates as well.
S-OFF would be needed in case you'll leave your HTC 10 on a custom ROM instead of reverting to stock, to be able to flash the latest no wipe firmware zips if need occurs as a result of incompatibility with your Custom ROM's base.
Sent from my HTC 10 using XDA Labs

Categories

Resources