Related
Check out this link:
http://www.slashgear.com/htc-hero-update-confirmed-imminent-1852644/
Appears as though HTC are gonna address the lagginess expereinced by many (including myself) with an OTA update.
Those with root like me will not get the OTA update as ive read the firmware wont update on rooted phones. Im wondering whether people will put their chef hats on with the new update to create a rom based on it?
You could restore a backup from a point where you had not rooted your phone yet
It basically unroots itself that way.
ammurad said:
Check out this link:
http://www.slashgear.com/htc-hero-update-confirmed-imminent-1852644/
Appears as though HTC are gonna address the lagginess expereinced by many (including myself) with an OTA update.
Click to expand...
Click to collapse
That link makes no mention whatsoever that the update will be OTA - in fact, it says:
“HTC will be providing a software update for the HTC Hero, which will be available via the HTC website in the coming weeks.” HTC statement
Click to expand...
Click to collapse
Via the website almost certainly means download and update manually. Being rooted shouldn't stop you applying the update, though you will probably lose root in the process.
Note that Google pushed OTA updates out for the G1, and the reason they didn't work on most rooted phones was because the procedure used to root the phone specifically switched off the OTA functionality to avoid the phone getting an update and losing root.
Regards,
Dave
It was confirmed prior to release that the Hero would be incapable of receiving OTA updates.
Ok thats useful information. We can just hope now that the update will get rid of the lag.
Someone needs to change the thread topic to
Hero update Iminent, but noT if you have ROOT!
ghoonk said:
Someone needs to change the thread topic to
Hero update Iminent, but noT if you have ROOT!
Click to expand...
Click to collapse
I thought it was only OTA updates that rooted phones couldn't recieve.
Biffert said:
You could restore a backup from a point where you had not rooted your phone yet
It basically unroots itself that way.
Click to expand...
Click to collapse
correct me if i am wrong but even if you back up with nandroid before rooting , running the backup doesnt unroot your phone.
anyway, it is not a problem. all u have to do is just to flash the stock rom posted on this thread and then run the update if this is the case .
I don't think ROOTING is the problem. I think that some people, in the process of rooting, end up changing the recovery.img with test keys which the update may check against and prevent the update.
I updated mine using ADB and used fastboot, so I don't think I actually changed the recovery.img, so future updates will just see my phone as a 'normal' unbranded device (albeit with Superuser.apk and su.apk, and the HTC CIME)
After OTA update, We will get the Custom rom of Hero soon (Like in G1)
I just bought GNex, and I'm already a bit angry. I know what most of you will say, but I'd like an answer to something I couldn't find on the forum.
Basically, I booted the phone and thought I'll just update from it's stock firmware to 4.2.1, I go to update menu and system detects an update... to 4.1. No worries I think, maybe I have to do it one step at a time, so I download and restart. But mid way through the update I get a screen with a dead Droid and an exclamation mark over it. What is going on?
I've read threads about update, and how to rush the update and get it directly from google, but as far as I know, my device is a stock "maguro" with stock "yakju" soft (no additional letter here). Check for yourself, here's a screenshot:
http://i48.tinypic.com/257jaqc.png
What I am afraid of is that even if I root, and push the update it will still freeze during it.
Please advise, as I couldn't find an answer to fix this thing, and I would prefer not to be forced to root/unlock bootloader to do it if not necessary.
Thank you for your help.
Just found something peculiar - so my device is "maguro" (GSM), but the stock firmware it came with is 4.0.4 yakju version, build IMM76K.
I checked different firmwares, and it seems that build was only released for mysid devices (the CDMA/LTE for Verizon/Sprint). huh...
I doubt you'd have a CDMA /LTE rom successfully running on a GSM phone. That's usually when the device becomes a paperweight. I highly suggest efrants guides to updates, stickied at the top of the forum. I know i've heard that yakju is always a bit behind takju, also depending on locale. And i do believe updates are done incrementally. But if you're getting some unknown error in the ota, your primary option is to unlock and root, then DIY. Otherwise, it sounds like you wont be getting any updates. If you're concerned about losing data, there was a method for ICS unlocking without wipe, a vulnerability. Look for it, and read!
bodh said:
I doubt you'd have a CDMA /LTE rom successfully running on a GSM phone. That's usually when the device becomes a paperweight. I highly suggest efrants guides to updates, stickied at the top of the forum. I know i've heard that yakju is always a bit behind takju, also depending on locale. And i do believe updates are done incrementally. But if you're getting some unknown error in the ota, your primary option is to unlock and root, then DIY. Otherwise, it sounds like you wont be getting any updates. If you're concerned about losing data, there was a method for ICS unlocking without wipe, a vulnerability. Look for it, and read!
Click to expand...
Click to collapse
Thanks. Already done it, updated to latest takju version. I would suggest adding and information about errors with OTA, and directing people to efrants guide.
Who knows why, but sometimes the otas just fail. I've had it happen myself, even when i think i havent modified anything. Anyway, glad to hear about your success!
I'm posting a new thread because nothing I've found has come close to answering my questions, so I appreciate any of you bearing with me here.
I've been running a custom ROM originally downloaded from this http://forum.xda-developers.com/showthread.php?t=1910947 thread, using an older version than they currently show. I'd really like to post in that thread but since I just registered I cannot post in dev-forums.
I've been running a custom 4.1.1 Touchwiz ROM, rooted, modified PRL, TWRP, etc. for quite a comfy while now and everything has worked great. Stable, fast, all that good stuff. Info:
Baseband version
L710VPLF9
Build number
JRO03L.L710VPLBJ7
Kernel
LJ7 variant
Modem
LF9 (works better than anything I can find in my area, paired with custom PRL. 300MB roaming data cap for those of you interested....I racked up 16.5GB one month when I was tethering while roaming....got that letter [then got WiFi]).
So what I really want to know is why am I receiving notifications for an OTA update, and if I'm happy with how stable the build I'm working on is, should I even bother trying to "fix something that isn't broken"?
The OTA update popped up as a notification so I checked it out, and it's advertised as 157.6 MB. Has anyone in similar shoes see anything similar pop up? Is it a 4.1.2 update, and is it worth ****ing with? Or should I be happy with what I have? Is this a reflection on my marriage?
Happy to provide any other information needed...regarding the phone.
plantshrub said:
I'm posting a new thread because nothing I've found has come close to answering my questions, so I appreciate any of you bearing with me here.
I've been running a custom ROM originally downloaded from this http://forum.xda-developers.com/showthread.php?t=1910947 thread, using an older version than they currently show. I'd really like to post in that thread but since I just registered I cannot post in dev-forums.
I've been running a custom 4.1.1 Touchwiz ROM, rooted, modified PRL, TWRP, etc. for quite a comfy while now and everything has worked great. Stable, fast, all that good stuff. Info:
Baseband version
L710VPLF9
Build number
JRO03L.L710VPLBJ7
Kernel
LJ7 variant
Modem
LF9 (works better than anything I can find in my area, paired with custom PRL. 300MB roaming data cap for those of you interested....I racked up 16.5GB one month when I was tethering while roaming....got that letter [then got WiFi]).
So what I really want to know is why am I receiving notifications for an OTA update, and if I'm happy with how stable the build I'm working on is, should I even bother trying to "fix something that isn't broken"?
The OTA update popped up as a notification so I checked it out, and it's advertised as 157.6 MB. Has anyone in similar shoes see anything similar pop up? Is it a 4.1.2 update, and is it worth ****ing with? Or should I be happy with what I have? Is this a reflection on my marriage?
Happy to provide any other information needed...regarding the phone.
Click to expand...
Click to collapse
It's MB1. The newest OTA. As far as roaming, the new modem may help you. But you can also search the threads and install the modem seperatley from the ROM. If you don't want to see the notification for the update, the are a few ways to stop it. You can let it download and install, it will take you out to your custom recovery and fail. You can just reboot your system in the update notification will not come back. you can also freeze system update using Titanium Backup this should also stop the notification. and if you're looking for the latest and greatest, there are plenty of options out there for custom ROM's. There is a couple of MB1 ROM's already up and there is a bunch of MA6 ROM's up as well, which is the variation right before and MB1.
And to answer the question of why you are receiving the update, it is because the system update component of touchwiz, which is still active in your ROM. However it does use the stock recovery to install, so that is why It will fail when it boots out to your customer recovery.
Sent from my SPH-L710 using xda premium
adamdelozier said:
It's MB1. The newest OTA. As far as roaming, the new modem may help you. But you can also search the threads and install the modem seperatley from the ROM. If you don't want to see the notification for the update, the are a few ways to stop it. You can let it download and install, it will take you out to your custom recovery and fail. You can just reboot your system in the update notification will not come back. you can also freeze system update using Titanium Backup this should also stop the notification. and if you're looking for the latest and greatest, there are plenty of options out there for custom ROM's. There is a couple of MB1 ROM's already up and there is a bunch of MA6 ROM's up as well, which is the variation right before and MB1.
And to answer the question of why you are receiving the update, it is because the system update component of touchwiz, which is still active in your ROM. However it does use the stock recovery to install, so that is why It will fail when it boots out to your customer recovery.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Thank you for your timely reply, it was informative and appreciated. I have WiFi at work and home and almost everywhere else I go, or at least decent 3G speeds, so I'm not inclined to update the modem. I guess what I want to know is if MB1 or whatever the latest and greatest is really has any significant improvements over Jellybean builds. If you think any good custom ROMs are worth checking out, I'm happy for links and/or more input :good:
plantshrub said:
Thank you for your timely reply, it was informative and appreciated. I have WiFi at work and home and almost everywhere else I go, or at least decent 3G speeds, so I'm not inclined to update the modem. I guess what I want to know is if MB1 or whatever the latest and greatest is really has any significant improvements over Jellybean builds. If you think any good custom ROMs are worth checking out, I'm happy for links and/or more input :good:
Click to expand...
Click to collapse
This is what I am running right now... has just about everything.
http://forum.xda-developers.com/showthread.php?p=37149249
Sent from my SPH-L710 using xda premium
plantshrub said:
Thank you for your timely reply, it was informative and appreciated. I have WiFi at work and home and almost everywhere else I go, or at least decent 3G speeds, so I'm not inclined to update the modem. I guess what I want to know is if MB1 or whatever the latest and greatest is really has any significant improvements over Jellybean builds. If you think any good custom ROMs are worth checking out, I'm happy for links and/or more input :good:
Click to expand...
Click to collapse
I'll chime in here.
If you want to see the effect of the updated baseband on your 3G speeds, I'd say just flash the MB1 baseband and try it out. It's in the thread you originally posted, titled "MB1 Firmware/modem/baseband update." If you find it's slower than what you currently have, just flash the old baseband. All the old baseband files are located in the same post, just under the spoiler tag "OLD VERSIONS."
As far as upgrading your ROM, I typically am a fan of the "latest and greatest" things (as are a lot of people are here on XDA). But I understand your desire for stability (I just spent an hour this morning trying to fix mms on my phone, for the fourth time in two weeks). That's the great thing about Nandroid backups. If you flash a new ROM, realize it's not what you wanted, you can, in one easy step, return to what you had before. I'd say try out the MB1 Freeza ROM (v4.1.2), and if you really don't like the update, restore your nandroid of LJ7
Hope this helps!
http://imgur.com/EgzxWFI
I think this screenshot should have all of the relevant information. I would tried this sooner, but it was end of college, I got my first full time job, etc etc.
My main issue with this phone is that it does random "soft" resets where everything just comes down and it reboots to the lock screen. This is especially fun when I'm driving and using this as a GPS :laugh:. I'm pretty sure the kernel is involved somehow, but I honestly don't know.
I want to know:
1. What do you guys think would be the most efficient way for me to update both the ROM and Kernel?
2. Is there any way to do this without having to re-root?
3. Would I be better off just choosing a non-stock ROM in order to get to the latest version of the android OS more easily?
That's about it, pretty simple. Just some directions would be nice as I'm quite out of the loop. Thanks.
If you don't want to do the research or take the time to go through the trouble of reading through these forums, then the most efficient way will be to remain stock unrooted and update via the approved methods from your carrier and/or Samsung (OTA and/or Kies usually). All software versions from ICS on up (non international S3s are now officially on KitKat) have been covered extensively by now so I doubt anyone is going to entertain your direct request for information. There are many things you need to be aware of, such as but not limited to how the new bootloaders and KNOX, as well as how custom roms and kernels, are working together in the big picture of things.
NOTE: Regardless of which route you take, no one in this forum, including myself, is responsible should anything happen to your phone. Anything you do to your phone is at your own risk, including official updates from your carrier and Samsung.
xshadowinxbc said:
http://imgur.com/EgzxWFI
I think this screenshot should have all of the relevant information. I would tried this sooner, but it was end of college, I got my first full time job, etc etc.
My main issue with this phone is that it does random "soft" resets where everything just comes down and it reboots to the lock screen. This is especially fun when I'm driving and using this as a GPS :laugh:. I'm pretty sure the kernel is involved somehow, but I honestly don't know.
I want to know:
1. What do you guys think would be the most efficient way for me to update both the ROM and Kernel?
2. Is there any way to do this without having to re-root?
3. Would I be better off just choosing a non-stock ROM in order to get to the latest version of the android OS more easily?
That's about it, pretty simple. Just some directions would be nice as I'm quite out of the loop. Thanks.
Click to expand...
Click to collapse
You can get all the info you need here: http://forum.xda-developers.com/showthread.php?t=1725839
As for having to re-root, you won't if you flash a custom ROM. Getting the OTA (or Kies) update will require a re-root which can be easily done with Towelroot.
As for the "most efficient", just follow the ROM's OP instructions to a T - it''s usually straight forward and easy to follow.
BWolf56 said:
You can get all the info you need here: http://forum.xda-developers.com/showthread.php?t=1725839
As for having to re-root, you won't if you flash a custom ROM. Getting the OTA (or Kies) update will require a re-root which can be easily done with Towelroot.
As for the "most efficient", just follow the ROM's OP instructions to a T - it''s usually straight forward and easy to follow.
Click to expand...
Click to collapse
Thank you for the reply
Okay so basically the most (time) efficient way for me to update is to get some custom ROM. That's fine, all I need to work on my phone is a few programs nowadays. Namely Google maps and the phone (well and the browser). Is Kernel updating the same? What's one of the good kernels and roms these days for the purposes battery life?
The main reason I'm making this topic is I'm fine with just going out and following directions, but I'm updating from such an old version that I'm wondering if there are any "gotchas". Like I update it to this with my old kernel and the thing is suddenly bricked. That's really what I'm worried about.
xshadowinxbc said:
Thank you for the reply
Okay so basically the most (time) efficient way for me to update is to get some custom ROM. That's fine, all I need to work on my phone is a few programs nowadays. Namely Google maps and the phone (well and the browser). Is Kernel updating the same? What's one of the good kernels and roms these days for the purposes battery life?
The main reason I'm making this topic is I'm fine with just going out and following directions, but I'm updating from such an old version that I'm wondering if there are any "gotchas". Like I update it to this with my old kernel and the thing is suddenly bricked. That's really what I'm worried about.
Click to expand...
Click to collapse
Kernel will be overwritten in the flashing process. All you gotta do is make sure you recovery is up to date if you go the custom ROM way.
We don't make suggestions as for what ROM/kernel to use to avoid flaming and it also comes down to user preference. Although, I do suggest starting to look at some custom ROMs (most of them come with their own kernel but can also flash another one). It will most likely come down to AOSP vs TW (stock) base.
The closest to a suggestion I can make is to look at the top threads in the Dev section, those are the most "popular" ROMs/kernels.
Alright, looking around at the various threads in the development section I see that most of them look pretty simple to install. Just download the zip, reboot into clockwork and install after doing some resets.
I notice that some of these require a new bootloader/modem, though... I haven't seen those terms when I last did this. What are the general installation instructions for those; the same as custom roms? Can they brick your device (assuming that I even pick the one for my device)? I'll probably just install something that doesn't need me to update the bootloader/modem to make things simple.
For the most part, if you've updated to 4.3 you will be able to flash any available roms. The catch is once on 4.3, you cannot downgrade your firmware.
Firmware is updated either by ota or flashing with Odin.
I went ahead and got the Slimkat because the instructions for it were pretty easy. There are some unpleasant changes about it that I would like some assistance on, but I suppose that would go in the dev thread to ask about those. Thanks for the info, it helped give me some confidence about just trying it out. Like I said a little iffy about some of the things but overall I like. At least it hasn't randomly crashed on me yet, and getting all of my apps back was as easy as having TitaniumBackup extract them from my Nandroid backup.
So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc.
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Joshy8 said:
So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc. [emoji14]
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Click to expand...
Click to collapse
There's newer firmware out. Look in neo's 5.1 deodex thread. That os is also 5.1 (rom).
Sent from my HTC6535LVW using Tapatalk
LOL! So it is! I saw it last night and somehow I screwed up and linked to your thread. Hooray for tired long days.
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Thanks for the response bschram. It is appreciated.
I actually wiped my phone and installed 3.0.0 without updating the firmware. Phone still works fine, but I will be updating the firmware as soon as I am confident I know what I'm doing with firmware upgrades. I'm a bit more nervous about updating firmware as I don't want to break the phone.
I'm glad to hear that I don't have to do a full wipe, and I'll definitely be doing that going forward. I will say that 3.0.0 is way more reliable than 1.9.1 was.
Just to make sure I am doing things correctly.... I am not totally new to this. Coming from stock 5.0.2... with S-off/Bootloader Unlocked. Flash firmware from NEO's deodexed rom in fastboot, advanced wipe in TWRP, then flash any 5.1 rom that is compatible IC, Viper, ect.... Then we should be good to go?
Then when offical OTA arrives, wait until firmware is pulled then flash the same way? Just making sure I will doing things right..... Thanks in advance
bschram said:
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Click to expand...
Click to collapse
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
teckels said:
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
Click to expand...
Click to collapse
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
andybones said:
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
Click to expand...
Click to collapse
Is it a common thing or has it only happened to one or two people.
Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
I
Thiss I am not too sure of, but I don't think too many.
Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
Me and one or two others. I have my suspicions as to what caused it and the casual crack rom flasher likely won't fall victim to it.
Sent from my HTC6535LVW using Tapatalk