Hey can someone Pm me the stock (or a better one) Swype apk extracted from the ota update. I don't want to OTA update cause I hear it sucks battery on older phones. I unrooted my evo to get the speaker replaced and the next morning my laptop died (mother board) and it won't be back from getting repaired till latter next week :-( I was using unrevoked. Or can you tell me where the phone downloads the OTA to so I can extract it without updating.
Sent from my PC36100 using XDA App
smokinbanger said:
Hey can someone Pm me the stock (or a better one) Swype apk extracted from the ota update. I don't want to OTA update cause I hear it sucks battery on older phones. I unrooted my evo to get the speaker replaced and the next morning my laptop died (mother board) and it won't be back from getting repaired till latter next week :-( I was using unrevoked. Or can you tell me where the phone downloads the OTA to so I can extract it without updating.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Wrong section. You can download the OTA from XDA, there's a link if you search.
I'll just leave this here...
Swype letter to XDA said:
While we at Swype are obligated to protect our intellectual property, we also feel that the enthusiast community is valuable to the long-term success of our business. With that in mind we’d like to offer some rules for posting content related to Swype here on the XDA-developers forum.
The overriding principle behind our policy is that distributing Swype in any way which would allow its use without a license is a violation of our terms of service and our intellectual property rights. This includes the use of features for which the user does not hold a valid license. Therefore the following situations are NOT allowed:
Distribution of Swype standalone APKs in any form;
Inclusion of Swype in ROMs where the Swype licensing mechanisms have been stripped;
The addition of features, such as the voice input button, to devices where the user does not hold a license or appropriate rights for these features – this includes the distribution of additional languages; and
Any other use of Swype that infringes any third party copyrights or other intellectual property rights or violating any third party terms of service.
The following, however, are allowed by Swype (assuming you have all other required third party rights):
Inclusion of Swype in ROMs for devices which come with Swype preinstalled, where:
the version of Swype matches the version distributed with the device
all licensing mechanisms remain intact, and
where the user is not infringing on any third party copyrights or other intellectual property rights or violating any third party (e.g., a device manufacturer or carrier) terms of service;
The use of MetaMorph(R) to modify graphical elements in any licensed installation of Swype.
Thank you for your understanding and cooperation in making sure our intellectual property and that of third parties is protected, while still allowing those who love to customize their devices in such awesome ways the liberty to do so. Swype reserves all of its rights.
Click to expand...
Click to collapse
Please keep in mind that you can always register for the BETA at http://beta.swype.com. The rules above apply only to the redistribution of Swype APKs. A valid BETA license allows you to use the latest BETA version from beta.swype.com on any supported Android device.
smokinbanger said:
Hey can someone Pm me the stock (or a better one) Swype apk extracted from the ota update. I don't want to OTA update cause I hear it sucks battery on older phones. I unrooted my evo to get the speaker replaced and the next morning my laptop died (mother board) and it won't be back from getting repaired till latter next week :-( I was using unrevoked. Or can you tell me where the phone downloads the OTA to so I can extract it without updating.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Oh jeez, someone is gonna get banned
He's not gonna get banned for asking for swype...
The latest update doesn't suck battery on older devices. The older x.30.xxx.x updates did. No reason not to flash.
Sent from my PC36100 using XDA App
Nothing wrong with asking, but there is an easier method than trying to use the ota, and wont risk getting anyone in trouble for warez. Swype is legal on our phones. You can download nearly any rom based off of 3.70, rip it open and push the apk and lib to your phone. OP, do a little more reading, bro. I saw a thread just earlier talking about where to put the apk and the lib files.
Ok guys. So remember my computer is dead. And Swype is part of the OTA so maybe I should ask how can I do it from my unrooted phone. I can't root till I get my puter back. And anyone got a download link to the OTA file? How bout someone just rip up an OTA for me and get me some pieces out of it named swim or something like that. Oh and are OTA's banned too cause they contain it? Is everyone supplying them gonna get clipped. Like hello! Sprint/ HTC redistributes it for this phone! Is that license enough? Um did anyone say sell or buy?
Sent from my PC36100 using XDA App
Not happening on an unrooted phone. Not without the update. The lib file goes in a /system folder...which you can only write to with root.
tejasrichard said:
Not happening on an unrooted phone. Not without the update. The lib file goes in a /system folder...which you can only write to with root.
Click to expand...
Click to collapse
Ok that's what I was afraid of. What's MetaMorph? That sounds cool. Also does the OTA version have the voice input button?
Sent from my PC36100 using XDA App
mattykinsx said:
After the 3.70 OTA? Also, requesting the Swype apk that came with the 3.70 OTA?
Click to expand...
Click to collapse
Yup after the 3.70 OTA. Another member asked for it, I told him to PM me cuz I was gonna give it to him, & a mod issued me a warning saying asking for Swype via PM is the same as doing it openly in the forums and its grounds for getting banned.
EVO on Tapatalk
Just as an fyi, as long as your phone is rooted you don't need a computer to do the work.
I downloaded the ota, extracted the zip contents, used root explorer to mount /system rw, moved the library to /system/lib, remounted /system as ro and installed the OTA apk.
That's all there is to it and swype runs fine on cm 6.1.2 wimax alpha 2.
Cheers,
Swyped on my CM'D Evo using tapatalk!
All it takes is thirty seconds worth of searching on google to find the apk...
Neatchee:
I tried to get the current beta and swype didn't work at all other than as a traditional keyboard. Swype tells you to install the ota version.
Yes, I'm in the beta program.
Swyped on my CM'D Evo using tapatalk!
smokinbanger said:
Ok guys. So remember my computer is dead. And Swype is part of the OTA so maybe I should ask how can I do it from my unrooted phone. I can't root till I get my puter back. And anyone got a download link to the OTA file? How bout someone just rip up an OTA for me and get me some pieces out of it named swim or something like that. Oh and are OTA's banned too cause they contain it? Is everyone supplying them gonna get clipped. Like hello! Sprint/ HTC redistributes it for this phone! Is that license enough? Um did anyone say sell or buy?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The reason we can't post the APK by itself is because it will work on any phone, whether or not it's licensed for use on it. Basically, it's piracy. If I post it here, what's to stop an LG Optimus owner from downloading it and putting it on their phone? On top of that, one of the rules said it has to be the same version, so even if someone with a different phone already has Swype, it'd be a different version and therefore would break the rule.
It's not cause we're so "by the book". It's just that you have to respect the rules of the people who put time into it. They're nice enough to let us modify it and put it into our ROMs at all. Notice how they said don't POST them here. They never said "we'll come after you if you extract it from the OTA yourself!".
Ummm I think everyone is making this wayyyyy too complicated. He's unrooted, doesn't have a computer to do it, doesn't mind using the OTA update....
Go to Settings >> System Update >> Firmware update
Unless you're not getting any connection on your phone, I don't know why anybody else didn't suggest it. Also if you're afraid about rooting it again, and most rooting methods cover the newest hboots now too.
edit: misread, sorry. I'm pretty sure you can download the OTA SOMEWHERE on this forum, just use the search. As far as extracting it without a computer, I'm sure it's possible but very difficult.
adamantypants said:
Ummm I think everyone is making this wayyyyy too complicated. He's unrooted, doesn't have a computer to do it, doesn't mind using the OTA update....
Go to Settings >> System Update >> Firmware update
Unless you're not getting any connection on your phone, I don't know why anybody else didn't suggest it. Also if you're afraid about rooting it again, and most rooting methods cover the newest hboots now too.
edit: misread, sorry. I'm pretty sure you can download the OTA SOMEWHERE on this forum, just use the search. As far as extracting it without a computer, I'm sure it's possible but very difficult.
Click to expand...
Click to collapse
I know you misunderstood, but it's worth a mention that Unrevoked works for all Evos now. Any hboot and radio and hardware revision.
All the ones who have said that asking for or sharing the apk are correct. Swype cannot be distributed in any way other than by cooking it into roms. Don't ask in open forums or via pm, you will get a warning and/or banned if repeat offender.
BTW, you posted in the wrong section. I am moving this (and closing it) to Q&A.
@OP,
This is your first and last warning. I would read this thread and try to follow their advise.
Thread closed and moved.
Related
Hey guys, I just read in a local newspaper that there is a security flaw in the android web browser. It allows hackers to access files stored on the SD card. Does this call for an AntiVirus software?
Sent from my HTC Wildfire using XDA App
It's true. I also read an article where they said rooting is illegal. What about that?
And you think antivirus-software will block that? I don't think so.
Android is open source, be happy they're telling Google the bugs in Android so they can fix it. It's better than hackers find the bug and Google doesn't know of it.
Hmm.. so should I be worried about this flaw or not? According to the article, seems like its quite serious..
Sent from my HTC Wildfire using XDA App
Read this article..has to do with the USSD...good thing i got backups..lol
http://news.yahoo.com/blogs/technol...security-flaw-wipe-phone-click-010830893.html
Its been around for a while now, its easily solveable, don't click on a link you don't know, pretty much how you would react on a pc if you had a random email with a link in it. I'm not sure if by dialling a code on a wildfire you can wipe the phone though someone correct me if i'm wrong.
It can happen on my s2 but i highly doubt it will, i suspect this is a leaked story to help promote the iphone 5 a little to the uneducated.
No need for antivirus as the way it works is you click the link with the malicious code in and it tells the phone to dial a code which then wipes the phone so unless your anntivirus can detect the code in a url it won't help.
Sent from my GT-I9100 using Tapatalk 2
The flaw was patched sometime back in August IIRC, but thanks to slow updates it's still unpatched on a majority of phones.
My One S with 4.0.4 Sense 4.1 has the issue. I thought those tel: links from the browser was a feature, not a security risk!
They are a feature, it's just that some phones can be wiped with no prompt by dialling a code so its also a possibility that some idiot can add that certain dialling code into a link. Shouldn't affect most of us xda'ers though and even if it did most of us wipe our phones on a regular basis anyway and know all about the importance of backups, its just a minor setback in my eyes.
Sent from my GT-I9100 using Tapatalk 2
here's some more information on the issue: It's Not Just Samsung Phones: How to Check If Your Android Device Is Vulnerable to The Remote Wipe Hack
eventcom said:
here's some more information on the issue: It's Not Just Samsung Phones: How to Check If Your Android Device Is Vulnerable to The Remote Wipe Hack
Click to expand...
Click to collapse
lol mine is indeed vulnerable !
I think my phone is vulnerable, but I don't think that code works, I think it may be a Samsung code to factory reset, which HTC doesn't have. Other codes like IMEI, INFO and CHECKIN work, but not the factory reset one, I don't think.
Edit:
Also don't have root so I can't make a backup. If we had S-OFF, I would root, but don't want to void my warranty, with no way of turning back.
usaff22 said:
I think my phone is vulnerable, but I don't think that code works
Click to expand...
Click to collapse
did you notice there's a link to check @ the Lifehacker article
Everyone seems to always suggest downloading titanium backup and freezing everything instead of just deleting it. Why? We have plenty of evidence of the apps that it is safe to get rid of and the ones that ya better not. So why does it seem that people are worried about deleting them. I am not a NASCAR fan and I don't see myself becoming one so why not just get rid of the app completely? Am I missing something?
Safe from what I have been told and read to delete are :
Blockbuster
Kindle
Amazon mp3
NOVA
Sprint TV
NASCAR
Sprint Football
Sprint Hotspot
Sprint Navigation
Personal preference, if you don't want them, delete away.
I would say from your list that you are right as long as you have a nandroid backup to restore. I have had my Evo start acting weird after I uninstalled some bloat ware so I restored the nandroid and just froze the apps instead. After CM7 final came out I dropped the stock rom, still have a backup, installed the Cyan goodness and have no plans of going back other than install new radio updates. The main benefit to uninstalling them is to free up space. The choice is yours.
Why waste time deleting them? They are installed to /system, so freeing that up doesn't free up the /data partition.
strung said:
Why waste time deleting them? They are installed to /system, so freeing that up doesn't free up the /data partition.
Click to expand...
Click to collapse
I'm confused , elaborate for me please.
Everyone is not experienced at flashing and tinkering with their devices. Think about it. A lot of people do things to their devices and when they've messed something up, they post here looking for help without stating what they have already done. Telling people to freeze the stuff they don't want is just a safeguard. Those of us who are a bit more experienced will go beyond TB. I hope that made sense.
posting & replying via the XDA Premium app.
Everyone is not experienced at flashing and tinkering with their devices. Think about it. A lot of people do things to their devices and when they've messed something up, they post here looking for help without stating what they have already done. Telling people to freeze the stuff they don't want is just a safeguard. Those of us who are a bit more experienced will go beyond TB. I hope that made sense.
Click to expand...
Click to collapse
That was all I was trying to get across was that if you are new to rooting and deleting/changing system files then you are better off just freezing the apps. It is normally safe but most people try to change something before they realize what they are doing, and don't have or know of a way to fix it. If a person wants to uninstall an app by all means go ahead that is one of the main reason for rooting your phone. It also makes it a lot easier to help them fix it if they know what they did.
Smurph82 said:
That was all I was trying to get across was that if you are new to rooting and deleting/changing system files then you are better off just freezing the apps. It is normally safe but most people try to change something before they realize what they are doing, and don't have or know of a way to fix it. If a person wants to uninstall an app by all means go ahead that is one of the main reason for rooting your phone. It also makes it a lot easier to help them fix it if they know what they did.
Click to expand...
Click to collapse
I understand. Thank you for your reply and enjoy the rest of your day...
posting & replying via the XDA Premium app.
I've also heard people use the reasoning that if you uninstall system apps you cannot accept an ota, so they freeze them. This way if they want to update, they can just defrost and accept.
I don't understand wanting to accept an OTA, but I also don't understand staying on the stock rom when there are so many great devs making awesome roms.
But people like what they like, I guess you can't knock that.
Hey there are 3 different people from NC in this thread.
I've also heard people use the reasoning that if you uninstall system apps you cannot accept an ota, so they freeze them. This way if they want to update, they can just defrost and accept.
I don't understand wanting to accept an OTA, but I also don't understand staying on the stock rom when there are so many great devs making awesome roms.
Click to expand...
Click to collapse
I thought about staying with the stock rom at first then I saw what I am missing. I love running CM7 and I have tried others. The main thing for me is that I'm now running Android 2.3.3 which has several features that I wanted and got tired of waiting on Sprint. Don't get me wrong I will stay with Sprint and they have one of the better update records but when Android 2.4 is coming fast and I am stuck on 2.2 with 2.3.3 what seems to be everywhere else. I can't stand that. I only hope that the HTC Evo 3D will get rooted because I plan on getting it as soon as it comes out. I was the first person at the Greensboro Besy Buy that got the Evo 4g and I will do it again.
Smurph82 said:
Hey there are 3 different people from NC in this thread.
Click to expand...
Click to collapse
I'm actually from Orlando, Florida and I moved to NC a year ago, however, I will be moving back to Orlando in about a week...LOL...I was getting the "evil eye" for being bold enough to strut around wearing a University of Miami shirt in the land of Hoyas, Tar Heels, Blue Devils and Wolfpacks....
posting & replying via the XDA Premium app.
At least you are still in the ACC.
LOL...That's true..
posting & replying via the XDA Premium app.
haha i came from the droid x now im on cm 7, have you checked out the cm7 update to use a bluetooth mouse and have a mouse pointer on the screen with hdmi miorroring? its awesome. i have a blutooth mouse and keyboard hooked up to my evo and the phone is connected to the tv.. i actually use this now instead of my comp
keejung said:
haha i came from the droid x now im on cm 7, have you checked out the cm7 update to use a bluetooth mouse and have a mouse pointer on the screen with hdmi miorroring? its awesome. i have a blutooth mouse and keyboard hooked up to my evo and the phone is connected to the tv.. i actually use this now instead of my comp
Click to expand...
Click to collapse
WTF??????????
well, you see the question above.. i really canÄt understand why it is missing . And besides, is anyone able to upload an apk of the music app?
Couldn't you just download it from the market? I mean, if you flashed gapps, then you have the market so you can just get it there.
Sent from my Galaxy Nexus using XDA App
wiiplayer94 said:
well, you see the question above.. i really canÄt understand why it is missing . And besides, is anyone able to upload an apk of the music app?
Click to expand...
Click to collapse
Dunno why it's not included, my guess is that Google might have the answer to that or whoever put together the gApps zip file.
And as to your second question:
Maybe try the search function? ...or Google it?
I'm a nice guy today, so I did the footwork for you...
gMusic APK
Certain ROMS (codename android being one of them) are adhering more strictly to Google's policy regarding Gapps and have removed music, maps etc so the zip won't contain them. Other zips on the other hand will.
Sent from my Galaxy Nexus using XDA App
Because it's not officially available in all markets, so including them with an internationally-available gapps package circumvents Google's regional restrictions. If it's available in your market, you can just get it from the marketplace anyways.
killyouridols said:
Certain ROMS (codename android being one of them) are adhering more strictly to Google's policy regarding Gapps and have removed music, maps etc so the zip won't contain them. Other zips on the other hand will.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
If they were adhering to Google's policy, they wouldn't be packaging Google Apps at all. You are not allowed to redistribute them, in or out of a rom. You are allowed to back them up from your own personal device. Thats it.
http://wiki.cyanogenmod.com/wiki/What_is_CyanogenMod
Until version 4.1.11.1, CyanogenMod included several proprietary apps such as Gmail, Maps & the Android Market, which are included with stock versions of Android, but are not licensed for distribution with 'custom' firmwares, such as CyanogenMod. Legally, Cyanogen was not allowed to include these apps in CyanogenMod.
Google sent Cyanogen a Cease and Desist letter demanding he stop distribution of these apps and Cyanogen ceased all development until a solution could be found.
The reactions of many CyanogenMod users was predictably hostile, with some claiming that Google's legal threats hurt their own interests and violated their informal corporate motto to "Do No Evil". After extensive media coverage (PC World, The Register, The Inquirer, Ars Technica, The H, ZDNet, Gigaom, and eWeek) and a statement from Google clarifying its position Google and Cyanogen negotiated an agreement in which Cyanogen could continue development on his firmware as long as he did not include Google's proprietary "Google Experience" components.
To work around the licensing issues, it was further agreed that the proprietary Google apps may be backed-up from the stock firmware on the device and then re-installed onto CyanogenMod releases without infringing copyrights.
Click to expand...
Click to collapse
adrynalyne said:
If they were adhering to Google's policy, they wouldn't be packaging Google Apps at all. You are not allowed to redistribute them, in or out of a rom. You are allowed to back them up from your own personal device. Thats it.
http://wiki.cyanogenmod.com/wiki/What_is_CyanogenMod
Click to expand...
Click to collapse
Ah, my mistake. Apologies. I was under the impression certain Gapps were OK for distribution, just not all. So Gapps are not strictly legally allowed to distributed ?
Sent from my Galaxy Nexus using XDA App
killyouridols said:
Ah, my mistake. Apologies. I was under the impression certain Gapps were OK for distribution, just not all. So Gapps are not strictly legally allowed to distributed ?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Correct. While even CM uses Google Apps packages, they will never admit that they are the ones that put them together
I am not saying that I don't do the same, just explaining that Google is within their right to bring our world crashing down around us if they felt so inclined.
The "legal" thing to do is to use a script to backup your current Google Apps so that you can move them to your own rom. Amon Ra recovery does (or used to) do this and I think CM has a script somewhere as well.
adrynalyne said:
Correct. While even CM uses Google Apps packages, they will never admit that they are the ones that put them together
I am not saying that I don't do the same, just explaining that Google is within their right to bring our world crashing down around us if they felt so inclined.
The "legal" thing to do is to use a script to backup your current Google Apps so that you can move them to your own rom. Amon Ra recovery does (or used to) do this and I think CM has a script somewhere as well.
Click to expand...
Click to collapse
Ah. OK. Good info that. I back up all apps regardless on a regular basis, but as a matter of course I download the Gapps from within the rom thread for the sake of a 'clean install'. Might as well use my backups now then
Sent from my Galaxy Nexus using XDA App
Please go to POST 56 for updated information. I will update the OP over the weekend. Thanks!
As many of you already know, with our recent official Jelly Bean release came a new, updated flash counter. With ICS we were able to either just root via the root66 method and not trip the counter, or we could just use Chainfire's Triangle Away app to reset it. This is no longer the case. Now, with JB, unless our firmware meets a very strict set of conditions, it will trip the counter every time you reboot the device. If you simply just flash the root66 firmware, and do nothing else beyond that, you will not raise your count. But then, whats the point of rooting???
DON'T PANIC!
We can still zero it out for Warranty returns! The biggest issues arise when you want to utilize certain apps and/or services such as All Share Cast, Media Hub and other Samsung apps. For example, if you have purchased the $100 equipment, the All Share Cast Hub, it will not work! Additionally, DRM protected content may not play anymore. (Probably just applies to DRM protected media you got from Samsung, but this needs verification). For example, if you got to download the Avengers a couple of months ago, it will not play, even though it is perfectly legal to do so!
So are we able to get around this? Yes and No, for the moment. There are at least 2 separate detections going on. One is done post-boot, using the SysScope app. If you remove this from /system/app/ you will be able to install a custom recovery, and probably also a kernel and another modem without tripping the counter! I have yet to see any negative side effects from removing this app, so until I find more info proving otherwise, I suggest backing it up and deleting it. Hopefully Chainfire will decide to update Triangle Away to counter the updated detection. He may not though. Please read what he has to say about it here.
This does not solve the whole problem though. There is still another method Samsung coded in to detect if your system has been modified. I am not sure yet what is responsible fot this. But if you were to simply deodex your rom, it will begin tripping the counter at boot again! (It may not be the deodexing that is trigging it though, I believe it is also scanning for any processes that are running with root privledges that should not be there, and it may also have to do with busybox). Either way, if you are running pretty much any kind of custom rom, it will retrip the counter at bootup. This method is different in that it happens during boot, not after, and it does not look at recovery, and probably not at kernel or modem either. It appears to look specifically at the system partition for anything not stock. I am trying to narrow this down.
Because the other 2nd part seems to happen during bootup, I think that Chainfire's paid version may be able to help here. If you purchase it on the Play Store, it will have enabled the ability to Auto run at boot. Since SysScope is now removed, I dont think any detections are running post-boot anymore, meaning Auto run from Triangle Away should work. I do not have the paid version to test with right now. But I will try and test this soon.
I am fairly certain that the rest of the detection process is running either from the kernel, or from a completely separate partition. It is going to require quite a few flashes and test to narrow it down for sure. So if you guys will report your experiences with it, particularly on different kernels, I would be greatly appreciative.
As I find and/or remember more about this, I will update it here. If anyone has any other information about this, please do post it here! Any help, tips, info, etc that you can provide can be very helpful!
I hope this all made sense to you guys! I will go back and clarify some stuff a little later, but Ive got a 6 year old kid going stir crazy waiting on me to be done with this! I wanted to go ahead and get something up though to get the conversation started! I will also post some links to some information later on.
In the meantime, you can Odin back to ICS build UVALJ4, and then flash your roms from there...yes even the JB ones! I hate saying that after suggesting to Odin flash the JB update, but if you have anything not working because of this, it may be your best option temporarily.
Otherwise, delete SysScope from /system/app! And keep Triangle Away handy!
I will continue doing a lot of testing and trying to investigate this problem. But I do appreciate any help that you guys can give!
Hopefully, with a little luck we can figure this out! :highfive:
I think that pretty much covers it...
I know that if you triangle away, and reboot to download mode, the counter's zero... if you boot into recovery and then boot into download mode the counter's still zero...
It gets triggered when you boot into the actual rom... I wonder if you odin to JB... then actually flash down to an ICS rom, does the counter get reset on boot?
scifan said:
I think that pretty much covers it...
I know that if you triangle away, and reboot to download mode, the counter's zero... if you boot into recovery and then boot into download mode the counter's still zero...
It gets triggered when you boot into the actual rom... I wonder if you odin to JB... then actually flash down to an ICS rom, does the counter get reset on boot?
Click to expand...
Click to collapse
That's SysScope running after booting up. Flashing an ics rom over a fully updated JB will most likely also trip the counter due to the 2nd part of the device check which runs during boot. Worth trying though.
Sent from my SGH-T999 using xda app-developers app
Also need to find out if its the deodexing that triggers it, or something like busybox.
Sent from my SGH-T999 using xda app-developers app
Good info. And nice write up so your saying if we odin root66 ics we are ok to say flash gs3r7.zip to jb and the new custom rom detection wont be present?
Sent from my SGH-T999 using xda app-developers app
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...
Okay, here was the progenitor post, that may give clues if the old (ICS) way no longer works:
http://forum.xda-developers.com/showpost.php?p=28953690&postcount=67
and the resultant manual method, which I verified worked on TMO (ICS):
http://forum.xda-developers.com/showthread.php?t=1781471
1Shotwonder said:
Good info. And nice write up so your saying if we odin root66 ics we are ok to say flash gs3r7.zip to jb and the new custom rom detection wont be present?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Yes that is correct. I cannot guarantee you wont have any other bugs. Doing it this way you are essentially running half ics half jb. If you have no need of samsung services like media hub or all share cast, id go full jb. Otherwise id go with the ics UVALJ4 firmware and a jb rom.
wideasleep1 said:
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...
Click to expand...
Click to collapse
That would be great! Thanks!
Sent from my SGH-T999 using xda app-developers app
Good job Doc... :thumbup::thumbup::thumbup:
Sent from my SGH-T999 using Tapatalk 2
Doc, I'd be more than happy to help out with this. Just shoot me a PM about where you are heading and I can see what I can do. I'm not adverse to getting in deep, so that is a non-issue.
My initial thoughts are to take a pretty simple approach and, for lack of a better few words, do a side-by-side of the new JB and the recent leaks and see what is different. Obviously it is a bit harder than than but we could breakdown the /system/apps, then move on the each partition scheme and see what the differences are and why they are different. Then start crossing off things like apps, 2boot check, something buried in on of the other partitions, ....
Really Samsung? God this crap is really starting to piss me off. Love how manufacturers don't want be enjoying my device.
On a more positive note, can't Samsung deny claims for just the CPU?
Sent from my SGH-T999 using Tapatalk 2
only thing that bothers me is the avengers movie not playing in any of the players on the GS3R7 rom. ( I have tried to reset the counter and still does not play the movie... any ideas? It does work on stock jb root66 though). Other than that I dont use any other samsung apps. The other issue I have come across is with Root Explorer when trying to modify the build.prop for GW I can edit the build.prop but it will not save the changes I believe this to be an issue with the sdcard now being sdcard0 but I am not 100% any one have a way around this or know the fix?
wideasleep1 said:
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...
Okay, here was the progenitor post, that may give clues if the old (ICS) way no longer works:
http://forum.xda-developers.com/showpost.php?p=28953690&postcount=67
and the resultant manual method, which I verified worked on TMO (ICS):
http://forum.xda-developers.com/showthread.php?t=1781471
Click to expand...
Click to collapse
Thanks for looking those back up. Ill be checking them out later on today.
Woodrube said:
Doc, I'd be more than happy to help out with this. Just shoot me a PM about where you are heading and I can see what I can do. I'm not adverse to getting in deep, so that is a non-issue.
My initial thoughts are to take a pretty simple approach and, for lack of a better few words, do a side-by-side of the new JB and the recent leaks and see what is different. Obviously it is a bit harder than than but we could breakdown the /system/apps, then move on the each partition scheme and see what the differences are and why they are different. Then start crossing off things like apps, 2boot check, something buried in on of the other partitions, ....
Click to expand...
Click to collapse
sounds good man! Kinda have a feeling ill be needing help on this one! Ill shoot you a pm later on. Gotta get going for now, but wanted to respond real quick.
1Shotwonder said:
only thing that bothers me is the avengers movie not playing in any of the players on the GS3R7 rom. ( I have tried to reset the counter and still does not play the movie... any ideas? It does work on stock jb root66 though). Other than that I dont use any other samsung apps. The other issue I have come across is with Root Explorer when trying to modify the build.prop for GW I can edit the build.prop but it will not save the changes I believe this to be an issue with the sdcard now being sdcard0 but I am not 100% any one have a way around this or know the fix?
Click to expand...
Click to collapse
Its another thing I've got to figure out. If its just breaking Samsung related/downloaded stuff, or is it screwing with DRM altogether.
As to your other issue, wallets included with jb now so I assumed it wouldn't require a 'fix'. But it sounds more like a superuser problem with root explorer. Download chainfires cwm supersu from his thread and flash it. See if that helps. Not going to be related to this stuff though.
Sent from my SGH-T999 using xda app-developers app
Does reverting back to ics roll back the flash counter? I am really liking JB TW maybe time for a change lol
Sent from my SGH-T999 using xda premium
Unfortunately I doesn't work that way. Would be sweet if it did, then all we'd have to do is roll back and we'd be good. Plus we could figure out the trigger and remedy it.
md1008 said:
Does reverting back to ics roll back the flash counter? I am really liking JB TW maybe time for a change lol
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If I'm not mistaken, you should be able to revert to ICS then use triangleaway and your counter will stay at 0.
Sent from my SGH-T999 using Tapatalk 2
Woodrube said:
Unfortunately I doesn't work that way. Would be sweet if it did, then all we'd have to do is roll back and we'd be good. Plus we could figure out the trigger and remedy it.
Click to expand...
Click to collapse
Triangle away, boot to recovery, then flash ICS on your phone...
Well my counter is stuck at 1 lol
What exactly trips the counter? I've seen multiple answers for the question but I figured ide ask here since there are so many knowledgeable people here
Sent from my SGH-T999 using xda premium
So ive been reading this and from what i can gather, it seems that samsung (or T-Mobile) placed a new apk file into the system directory (or maybe a lib file?) and that if you root your device, every time you reboot your phone, it will +1 to the flash counter?
Has anyone asked any ATT, Sprint or Verizon users if their flash counter goes up with root after each reboot as well? If it doesnt, we could probably do a system file comparison between the two to isolate the file(s) which are causing the incremental flash counter at boot.
That's what I was saying earlier about comparing official and leak and seeing the differences. Sprint is the only one that has had official so not sure if that would work for us. Think we need to differentiate between Samsung and TMo and see where the "fault" lies.
Woodrube said:
That's what I was saying earlier about comparing official and leak and seeing the differences. Sprint is the only one that has had official so not sure if that would work for us. Think we need to differentiate between Samsung and TMo and see where the "fault" lies.
Click to expand...
Click to collapse
That sounds like a good idea. I'll download one of the leaks and see if anything is obvious. It may also be a new line of code inside an apk or lib file as well. Making things a bit more difficult. As im comparing them i will check the size of each APK as well as if new code is added to them it should increase the size of the compiled apk. And i have my computer set up to show individual bytes of data.
So yes basically I know things on xda are supposedly safe in terms of security and roms. But have there ever been a case of a Rom having something like a keystroke logger or any type of hack to gather information or gain access to your personal stuff? And if it had never happened on xda maybe from one of the other sites?
I suppose I'm just trying to address how safe custom roms are I have been using various ones recently so I do trust them some what of course and I assume if a roms been on xda for months and has many posts it's been checked but I still wonder if someone was clever they could wait for the right moment to strike if you know what I mean. Thanks.
Yea, in a way, you are trusting that the devs have no added anything sinister to their custom ROMs. But in the time I've been here (a long time!) I haven't seen anything like this added to any ROMs. You could always do a full scan of the ROM before flashing it to be sure.
the_scotsman said:
Yea, in a way, you are trusting that the devs have no added anything sinister to their custom ROMs. But in the time I've been here (a long time!) I haven't seen anything like this added to any ROMs. You could always do a full scan of the ROM before flashing it to be sure.
Click to expand...
Click to collapse
What would you scan it with though? Pc viruses and malware different to mobile no? And anyway surely a clever hacker would make there own hack etc. And maybe they just add it to the update add well . Anyway good to hear no ones reported one yet!
Well I will try a pc scanner...phone scanners seem to just check.apk's so that's useless...done some full scans all the same just for the hell off it. Guess I don't have any money anyway so I'm safe . But like I say if they are clever they will write their own code so the scanners won't find it .
Still no one reported ok that's given me more confidence...a bit :s ...
Only thing I new of was start of the year I had a xperia z ultra and the mostly only way to gain root at the time was to use kingo root. It wasn't a XDA developed root tool is was from a Chinese website and it was suspect as it took your phone details like imei number. Not sure what happened in the end. But if you get a phone and you trust the recognised devs you should be OK.
Golly, I sho hope not!
:good::good::good:
How about as of late and the security involved when you have a rooted phone? I have not been able to locate any substantial info concerning the legitimacy of or about the claim. Do I need to UN root my phone after the new flash or no? Or, am I way of base here and obviously don't fully understand the weekness of having a rooted phone? In other words, a rooted phone is just as safe as a non rooted phone?
Thanks in advance
Edit
Randy L said:
How about as of late and the security involved when you have a rooted phone? I have not been able to locate any substantial info concerning the legitimacy of or about the claim. Do I need to UN root my phone after the new flash or no? Or, am I way of base here and obviously don't fully understand the weekness of having a rooted phone? In other words, a rooted phone is just as safe as a non rooted phone?
Thanks in advance
Click to expand...
Click to collapse
No, a rooted phone is not as secure as an unrooted phone. You've opened up access to the system when you rooted, and therefore made it vulnerable.
Not that an unrooted phone is completely secure either, but with root access, a malicious app could do much damage.
What would you suggest since I plan to flash a newer, stable ROM with a newer radio binary? I need to ensure my phone is locked up right as possibly allowable without over taxing the system.
Thanks again
Randy L said:
What would you suggest since I plan to flash a newer, stable ROM with a newer radio binary? I need to ensure my phone is locked up right as possibly allowable without over taxing the system.
Thanks again
Click to expand...
Click to collapse
It's all a trust and common sense game. If you flash a rom you are putting the trust in others hands. No way around that. As for keeping it locked down. Your best bet would be to stay on stock. Root is a security hole and that's why Google is starting to allow apps to check for root and if found disable the app or features of the app.
Luckily most of our ROMS don't come from people stand to gain anything from that info and are probably like-minded when it comes to how we want our phones to work.
To answer some of these questions, it might help to fully understand what we're talking about.
What kind of security issues face an Android phone?
Well, for one, there are network-level attacks. This are fake cell towers (sometimes called Stingrays) that can collect the sort of data a cell tower might be able to collect, your location, your messages, and your data.
A third-party ROM or a rooted phone is not intrinsically more vulnerable to this. In fact, there are some apps that help detect this kind of attack, and those apps will generally require root access. This kind of attack is less likely to be a random skiddie, and more likely to be the police or a government.
Another kind of attack is a malicious app. Think of it like a trojan horse, something you willingly let into your phone, and it has a secret malicious payload. Maybe it's a browser that actually skims all your activity to sell to marketers. Maybe it's a widget that shows a neat clock on your lock screen, but it actually collects all of your contacts so they can be spammed later.
Since this would be an app that you've willingly downloaded, a third-party ROM doesn't make you much more susceptible, but granting this app Root could make it much more damaging, since it could hide itself from uninstallation or even modify other apps to do bad things.
Note, though, that certain third-party ROMs and apps that require root can help protect against this. If you download an app, and it says it needs permissions that don't make sense (why does a clock app need access to my camera, or my contact list?), that should be a red flag to not install it. But some ROMs actually let you revoke/block individual permissions., so if a baddie app was trying to access stuff it shouldn't, you can stop that from happening.
But there's a slightly more insidious kind of malicious app. Imagine third-party app that accesses Twitter, or Snapchat, or Instagram. Now this app actually saves all of the things you're doing elsewhere before it punts them off to the service you're trying to access. This app could be appearing to function completely honestly, hoarding your Snaps and your snapchat password, until one day they decide to leak all your snaps, or upload all the images you sent to your private Instagram to a public site.
You're not intrinsically more vulnerable to this kind of attack with a third-party ROM or a rooted phone. These apps will likely be come from a non-Play store source, which can happen even stock/unrooted. An app like this with root access can do more bad stuff, but their wheelhouse is in doing bad things with the data you've already willingly given them, so it's moot.
Then there's the issue you seem to be most worried about, which is malware baked into a ROM. This is by far the biggest danger in terms of risk, because it could be doing all sorts of nasty stuff relatively invisibly. What prevents someone from doing this, though? Well, for one, with an open source project, everyone can see the code. If there is something flagrantly wrong, it could be spotted by other people. It's possible to try to hide it, though, and some smaller ROMs don't attract a ton of eyeballs, so not that many people might be looking.
Then again, plenty of major ROMs could have the same thing going on, just in very clever or subtle ways. Look at how pervasive the Heartbleed issue was, and that was in code that tons of very smart people had the chance to look over.
Third-party ROMs do present more danger in this regard. What do we consider third-party, though? Major carriers lay tons of extra code on top of vanilla Android. And plenty of them may be doing unseemly things with your data, either for marketing reasons or at the behest of someone like the NSA. In that case, you're best but would be to stick strictly to AOSP ROMs, but even then, it's not a sure thing.
Truth be told, the best thing you can do for security is just pay attention to what you're letting onto your phone, and what you're letting those apps do. Your choice of ROM and root status is a part of it, but being generally aware is by far the most important thing.