Hi,
I just sent my One S to Vodafone because of the chipping issue (it wasn't very much but if they change it it would be nice) and I expect to get a new flashed phone back from them.
At the moment I have (or more had) the Virtuos 1.4.0 Rom installed because I kinda like the Sense look&feel more than the AOSP way but I wanted to have the 3-dot menu mod.
As the Mod is now available for odexed 1.78 ROMs and the Virtuos ROM isn't updated I'm thinking about keeping the stock ROM, clean it in parts with the ROM Cleaner and then apply the Mod (and maybe some other also) to still get OTA Updates.
My Question now is: What does the phone need to get the OTA Updates?
Somewhere I read that it would need the default recovery, is this true? and what else does it need? I want to have CWM to make nandroids etc. - would it be necessary to unlock the bootloader, flash CWM and reflash the default recovery if there are OTAs?
Also I'm thinking about changing the phone from a branded Vodafone one to the default HTC Eu version like this. Does this make it possible to receive OTA from HTC after flashing an RUU and what do I have to consider?
With an official ruu (eg. EU) you should always get updates. Although devs update moreoften.
Sent from my HTC One S using XDA
Eumaniac said:
With an official ruu (eg. EU) you should always get updates. Although devs update moreoften.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Thank you for the answer!
But what can you modify and still get OTA Updates? I'm thinking as said about if the CWM as Recovery etc. affects the "OTA-Ability"
You need stock recovery, Stock ROM, All the stock bloatware. you may even need re locked bootloader.
its easier to run an RUU or wait for ROM devs to include the update into the ROM
azzledazzle said:
You need stock recovery, Stock ROM, All the stock bloatware. you may even need re locked bootloader.
its easier to run an RUU or wait for ROM devs to include the update into the ROM
Click to expand...
Click to collapse
Okay, so no chance to modify it a little bit without affecting the OTA ability
I have a nandroid of the default ROM so then I think I should be able to make an OTA by restoring the nandroid, flashing the signed stock recovery and then give it a try?! - As said the Phone is brandet so flashing a RUU would be a little bit more riskier
Mh... I'll just try it when the net OTA is there
My Problem now just is that the Virtuos ROM isn't up to date and every other ROM doesn't fit my needs
The MoDaCo is very "*****y" (doesn't want to boot sometimes) and misses the "Facebook for HTC Sense" and "Twitter for HTC Sense" apps...
Oh and if somebody is interested:
I got my phone changed without any discussion from Vodafone. They just sent me a new one and the delivery boy took my old back to Vodafone.
you could certainly try the Nandroid way ! lots have people have successfully done it this way
Related
But is it now too late to return to Gingerbread original.Because i cant find anything on the HTC site directing to firmware updates.
And another question is it still possible to root your sensation when you have flashed to ICS 4.0
If you flash it the fully official way, assuming you didn't unlock bootloader and get S-Off: Not possible through normal means. Only if you can get S-Off there are some risky tricks to downgrade which I personally wouldn't prefer. About rooting a fully stock ICS. According to some, the most recent SuperUser versions are working.
How does the stock version feels in comparison to GB?
It just feels smother, I did had to wait for it to settle down but now its working fine.
being on a rooted phone i didn't want to wait and do all sorts of changes to get the ota working so i flashed ardh. It's my first custom rom untill now i have been using stock roms.
Glad to hear it's an improvement.
Hey, i am new to rooting, actually the whole android intact. I decided to get a HTC ONE X after having the iPhone for a while. I have watched some videos on rooting and i think i have all that down with boot loader and stuff. I just have a few questions about other stuff regarding rooting the phone with customer ROM's.....
1) if i have a custom rom, and i get an OTA update, will that brick my phone if i do decide to update it? I know that it will take root off... but will it brick it if i just update without doing anything with custom rom?
2)Do custom roms (the one I'm looking at is the cyanogen mod for HTC ONE X) kill the battery more then normal?
3) How do you go back to stock rom if you no longer want the rom.... is it as easy as just going to the reboot screen and selecting stock rom? is the stock rom already on there or do i have to put it on there?
4) If wanted, how easy is it to un-root phone?
5) and just personal opinion, what is the best jellybean Custom rom out right now for HTC one X?
Thank you all so much!!
1 - You can't OTA update with a custom rom. Anyway, the custom roms (Sense based) are further updates than the AT&T updates.
2 - When I used CM10, it had quite a bit of wakelock but it's dependent on each phone as well. Many have great battery life.
3 - RUU
4 - When you RUU, you relock your bootloader and it brings it back to stock. Only difference is now in the bootloader, it says re-locked, not locked.
5 - CM10 is pretty good so far, but I'm a fan of AOKP.
1. The OTAs are pulled by software on the phone. Custom ROMs don't have this software and don't pull, so no need to worry.
2. Depends. Keep in mind the current JB ROMs are still a work in progress. CM10 does still have wakelocks, but its getting better.
3. Already said above. Just relock your bootloader and RUU.
4. Easy to unroot. Easy to relock. But once you unlock your bootloader your phone will never say LOCKED again. I honestly have never had an issue with it with warranty repair, but please don't be an asshat and flash a ROM for the wrong One X and then complain to AT&T.
5. Personal preference. The great things about custom ROMs is you can try a bunch out and find the one that you like. I used AOKP a while back and liked it. CM10 is pretty cool but I just had it for a few days as they work out the wakelock issues. Also check out some of the ICS ROMs. CleanROM is pretty solid as well and gives great performance. Don't necessarily limit yourself. That's the beauty of it.
On going back to stock rom, you dont necessarily need to use the ruu. After you get your phone rooted, unlocked, and a recovery for flashing your custom roms, then just make sure before you flash your first rom that you (from recovery) select factory reset (will erase all user data such as 3rd party apps and such) then perform a backup, also in recovery. Now,you have a safe stock rooted rom backup. Go flash any of the roms in this forum and at anytime you can always just go restore your stock rom back
I think i'm getting overwhelmed with all the reading I'm doing and need a little help clear out the confusion in my brain
I'm rooted
I have SUPER CID
I have S-OFF
Custom Recovery (TWRP)
On a custom ROM (chameleon OS)
Never updated to JB OTA
Does my phone need to update to JB before I begin to flash any other Custom ROM? I know these roms provide Android 4.1/4.2+ but does my phone need the OFFICIAL JB update for it to work good? I see a lot of people installing the stock RUU and getting the update - I guess my main question is - is it necessary to downgrade back to stock, update, re-root,unlock, install new ROM again with my phone now having JB thru OTA?
If so - what are the PROS of doing this?
If not - is my phone going to be okay installing ROMs with my phone never being updated.
Thanks!
Short answer: no.
Long answer: no, because you're wiping cache and data the phone is a blank slate. You could go back to Cupcake or skip forward to Jelly Bean 4.3... If you managed to break into Google Inc and get the data for that.
Sent from my HTC One S using xda premium
Normaly no.
But I've seen situations with previous devices that a certain min hboot/firmware is required.
Like if your firmware is gb any jb/ics Rom might not work. just an example!!
Just look what base the Rom is made from. Test if it works. If not update you're firmware to min required or same as base of rom. Test it again.
Always check op of rom. Or ask the dev.
Verstuurd van mijn HTC One S met Tapatalk
since you're s off, any ROM will work.
Real187, on some other HTC devices (eg.Flyer), you had to match your hboot to the ROM, but so far for the One S, this hasn't mattered (for the average user).
The only "firmware" partitions you might consider messing with is the radio, but that won't affect if the ROM boots.
to answer your question, the pros of ota are none to negligible. No ones sure if the other partitions it updates are beneficial.
Thx for the replies! I was worried about this as I see a lot of people trying to downgrade and bricking their phones while doing the process.
I have a TmoUS HTC One S, and I unlocked bootloader, rooted my phone and flashed Pacman 22.3 on my phone. I like the rom, but it has slowed my phone and made it quite buggy. It soft-resets at least once a day and randomly gets stuck on lock-screen and I have to wait a couple minutes to try again. Anyway, those are just a couple of my annoying bugs that I don't want to deal with anymore. I'd like to just go back to the stock rom, but as I've found out, I can't restore from a previous backup.
As I'm relatively new to smart-phones, rooting, installing roms. I need a straightforward tutorial on how to flash the stock rom. I've read through the xda forums but cant seem to find exactly what I'm looking for. Any help would be greatly appreciated. And I apologize in advance if this wasn't the correct thread to post in.
PS - Not sure if this make any difference, but I have CWM installed as my recovery.
bizeekizay said:
I have a TmoUS HTC One S, and I unlocked bootloader, rooted my phone and flashed Pacman 22.3 on my phone. I like the rom, but it has slowed my phone and made it quite buggy. It soft-resets at least once a day and randomly gets stuck on lock-screen and I have to wait a couple minutes to try again. Anyway, those are just a couple of my annoying bugs that I don't want to deal with anymore. I'd like to just go back to the stock rom, but as I've found out, I can't restore from a previous backup.
As I'm relatively new to smart-phones, rooting, installing roms. I need a straightforward tutorial on how to flash the stock rom. I've read through the xda forums but cant seem to find exactly what I'm looking for. Any help would be greatly appreciated. And I apologize in advance if this wasn't the correct thread to post in.
PS - Not sure if this make any difference, but I have CWM installed as my recovery.
Click to expand...
Click to collapse
make backup first
change cid back to original (if needed)
flash stock jb recovery (extract from ruu or ota, or google it on xda)
flash latest tmous jb ruu. (latest ota is also availible in ruu form)
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!