Deleted.
Out of curiosity could this potentially lead to helping unlock the bootloader? Or anything else for that matter? I'm not the most smartest at knowing things of this nature so it never hurts to ask, right? Thanks in advance.
DELTED
Seconded.
Looking into trying to help with the kernel modules. Hopefully we can get something figured out
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Seconded.
Looking into trying to help with the kernel modules. Hopefully we can get something figured out
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is amazing the amount of time that you guys must spend tearing apart our phones in order to fix things that shouldn't be broken in the first place. Thanks for all the effort.
Ahhhh! S&#t! Surge in the house! I was gonna say get this info over to the s4 forum but looks like it got there! I miss my mdk s4 but due to my clumsy @$$, I had to send it in for a insurance claim. so I sold the one sent to me and got the note 3. You devs CAN'T be thanked enough for what yall do but I don't mind trying! THANK YOU! THANK YOU!
THANK YOU!
Sent from my SM-N900V using xda app-developers app
Yes at least something to hope for its been kinda quite here lately on note 3 Verizon forums
Sent from my SM-N900V using Tapatalk
<reserved for more dragons>
Seems like the cast of a highly anticipated movie is getting revealed one by one.
I'm thrilled to see some progress going on considering how heart-broken I've been with those locked threads and scams.
Let's hope this isn't another one of those.
I have to ask though, what exactly is Qfuse? Is there any easy explanation for it?
404 ERROR said:
Seems like the cast of a highly anticipated movie is getting revealed one by one.
I'm thrilled to see some progress going on considering how heart-broken I've been with those locked threads and scams.
Let's hope this isn't another one of those.
I have to ask though, what exactly is Qfuse? Is there any easy explanation for it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28464645
Just putting this out there and I don't know anything about this type of dump/log. But would it be beneficial to get the same tree from a Dev Ed phone. Just an idea cause in my mind that makes sense to compare the two to see if that leads any where.
Sent from my SCH-I535 using Tapatalk
want to help
ryanbg said:
Too long to explain how I got this. It's from my device. Hopefully this attracts the right attention. This is my biggest discovery yet. It's all out of order too, and I'm not going to put it into order because I'm lazy. Thanks @Surge1223 as always
As far as I can tell, this would be the device tree source.
Pastebin dump
Click to expand...
Click to collapse
I'll admit that im not a dev, but id like to post my version of the same file to see if they're any different bith my knox being 0x1.
Where did you find this gold mine?
pimpmaneaton said:
Just putting this out there and I don't know anything about this type of dump/log. But would it be beneficial to get the same tree from a Dev Ed phone. Just an idea cause in my mind that makes sense to compare the two to see if that leads any where.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
orangewaldo said:
I'll admit that im not a dev, but id like to post my version of the same file to see if they're any different bith my knox being 0x1.
Where did you find this gold mine?
Click to expand...
Click to collapse
This is a generic source file for MSM8974, this isn't what the fuses are actually set to. You can check what fuses are blown (or most) with viewmem. The file just shows us all the possible registers/addresses, and how they are setup.
ryanbg said:
As far as I can tell, this would be the device tree source.
Click to expand...
Click to collapse
Ryan, that pastebin in truncated because of the size limit for free pastebin.
Can you please upload file where we can get the whole thing, possibly on github?
Second, can you please consider moving this thread to "Hardware Hacking General" as
this is useful for a whole range of Qualcomm MSM8974 based devices.
For even more info about Qfuses, look here: "Qfuses in the MSM8960".
E:V:A said:
Ryan, that pastebin in truncated because of the size limit for free pastebin.
Can you please upload file where we can get the whole thing, possibly on github?
Second, can you please consider moving this thread to "Hardware Hacking General" as
this is useful for a whole range of Qualcomm MSM8974 based devices.
For even more info about Qfuses, look here: "Qfuses in the MSM8960".
Click to expand...
Click to collapse
I believe I already started a thread in Hardware Hacking, I think it just fell to the back already. I actually have the whole register map, the problem is it was split into SEVERAL chunks. It will take me quite a bit of time to piece it all back together. The dump I posted here is actually like 4-5 different files I pieced together since the tool I used to carve it out of a memory dump didn't recognize it at one contiguous file. I slapped all of them together out of order and uploaded it because I was so excited. I will be out of town this weekend, but I will start putting the puzzle pieces together (there might be like 100 different files.)
I know longer have the memory dump (I wasn't aware of it's significance at the time,) but I do have all the files I pulled out of it.
file disassembly and heartbleed exploit
Let me know of any files that would help if they are disassembled amd decompiled.
Also I have the heartbleed exploit. I wonder if we installed a openssl version that is affected. Infect the phone with a root kit like virus and do a mem dump. If we could grab something juicy.
This is a good read about the qfuse
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Related
Okay, so someone from Samsung is going to be callig me soon. I assume it's related to #NeverAgain.
What would you guys want to know, or tell, samsung?
If I agree (maybe even if I do not) I will ask them.
EDIT - UPDATE:
Okay, I have finished the call. I hit on every topic from this thread/my twitter. I am very limited with what I can say RIGHT NOW though. I do feel that (& hopefully) shortly a lot of good will come from all of this.
I am NOT willing to throw my hands in the air and yell "hooray," but the Olive Branch is absolutely extended and this has the potential to be a huge win for the community, and Samsung.
I do feel this is less a PR move and more that our collective voice was heard. I really hope that is the case anyway. Still a little ways to go.... but I have to applaud them for their efforts so far, even though everything else they've done to this point has been a let down in my eyes.
I hate I solicited your Q's, and am unable to give answers... just wanted to let you guys know what I could say, and that I left the call a bit optimistic, hope that helps some.
Why the lack of support for us vibrant owners? What did we do besides buy millions of your phones?
You will need to be as clear as possible... hard to yell lack of support when froyo and source are available now. Granted it was slow and done terribly.. both the misleading deadlines AND the lack of an OTA.
Gingerbread or at least 2.2.1
Sent from my SGH-T959 using XDA App
s15274n said:
You will need to be as clear as possible... hard to yell lack of support when froyo and source are available now. Granted it was slow and done terribly.. both the misleading deadlines AND the lack of an OTA.
Click to expand...
Click to collapse
Ok. Why the delay on froyo? Also why not an OTA update? Just seemed like the threw us a bone to shut us up with the kies update?
Tell them we need an easy way to get our problems through.. Some type out forum or a public way to brainstorm ideas.. Maybe you can get a job out of this..
Rfs has to go.. It cripples the device.. Ext4 has been proven a better file system.. An aosp build that we choose to flash if wanted.. Maybe through kies.. A metal back we can buy to give our phones that weight we always wanted..
Awesome, plese keep the good ideas going...
How about a definitive answer on the choice of rfs over ext4?
I know we have ext4 on our own, but im just curious as to why they made the decision in the first place.
Anything else? Call is happening shortly.
why don't we have the drivers source? Also will we be getting gingerbread?
Sent from my SGH-T959 using XDA App
neotoky said:
why don't we have the drivers source? Also will we be getting gingerbread?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, driver source was on my list, though I think I know the answer.
I'll report back. Keep adding.
neotoky said:
why don't we have the drivers source? Also will we be getting gingerbread?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think that's the question most people are gonna want an answer to. Something tells me they aren't going to be able to tell you much, but Ill hold out hope.
We at XDA are a completely different type of customer. We like good specs, but we also like to be able to tinker with our phones. Currently, HTC is the most XDA friendly. If Samsung gave us the tools we needed, wed have no reason to switch up phones. We already have some of the best hardware, we just want great software to go with it.
Ask them if they are in a service business and not just a hardware business any more. As soon as they started provided hardware that needs updates, they need to provide those updates to keep their customers happy.
Also ask them if they are planning on inviting the XDA developers to their development tree so that we don't have to get leaked source code but can get it straight from Samsung. Maybe if we sign a waver that we take responsibility for our own actions. To be adults.
Also ask if they are going to allow critical feedback on their website of their devices and not censor them to only accept good feedback?
please tell these Nazis to make an option for the incoming call volume delay. it drives me nuts
OP updated. Sorry but I was asked to not share a lot of what we discussed, and I will listen to that demand.
I will say I feel like this is a potentially great thing. Here is hoping that all parties can find a mutual ground and we will all benefit.
s15274n said:
OP updated. Sorry but I was asked to not share a lot of what we discussed, and I will listen to that demand.
I will say I feel like this is a potentially great thing. Here is hoping that all parties can find a mutual ground and we will all benefit.
Click to expand...
Click to collapse
I understand that you can't reveal anything, but Id say if the guy that spearheaded the NeverAgain campaign is satisfied with the conversation, things should be much brighter in the future.
I see that SGS variants are the first Android devices that brought Samsung a major success in smartphone battles, and obviously they were not ready to deal with all sorts of demands. I am happy to see them reaching out to their customers and to see a work in progress.
thegreatcity said:
... if the guy that spearheaded the NeverAgain campaign is satisfied with the conversation, things should be much brighter in the future.
Click to expand...
Click to collapse
I'm cautiously optimistic. This could easily dissolve into nothing, or it could be a genuine game changer. The ball is in Samsung's court, but others will have a large impact on the outcome too (no names).
s15274n said:
OP updated. Sorry but I was asked to not share a lot of what we discussed, and I will listen to that demand.
I will say I feel like this is a potentially great thing. Here is hoping that all parties can find a mutual ground and we will all benefit.
Click to expand...
Click to collapse
Ok since they have chosen you to discuss....... That is nice of them,
BUT, WHEN is this going to happen? This is the third or forth iteration of "Dangling the carrot" telling us something wonderful is coming........
Did you ask about the time line ?
Why bother to root the 3VO or any phone?
How does Sprint update? If Sprint can update and change "stuff" in the rom like the clock or whatever, or even change the system from 2.2 to 2.3 how do they do it?
Is there some code in the front end of the install, that allows this update without root?
I suggest find this part of any update that Sprint uses; and then just run this section of code on any/every new rom that any developer wants to run...
I remember looking at some old games and programs, and being able to find the lost "code keys" that were actually on the cd's in hidden files.... type those into the program when they started, and bam.... no "key" on the box needed.
Anyway, if Sprint can do it without "root" why bother to root - just find the hidden lines!
This might seem simple, or maybe obsurd, or just outside the "box".... but seriously - what if?
The hell?
Drugs are bad mmkay?
Hmmm. Ok go ahead and get on that
Sent from my PG86100 using XDA Premium App
Hmmmm perhaps you don't get it...
i.e. if sprint can 're-rom" our locked phones... why can't we?
Que....?
I goes something like this.
Take the firmware, zip it up, take that zip, encrypt it with a private key. Push this OTA to the device.
The device will read the OTA update, check to see if the decryption key succeeds and then flash the device.
You're confusing headers in unsigned roms with hash checks in encrypted roms.
In simplest forms this is a header
Start>Rom1
You can change Rom1 to Rom2
Start>Rom2
That's a header.
Encryption is a little bit harder.
For simplicity sake let's just say the encryption key was +5 and decryption key was -5.
If your rom contained simply this.
Hello
Your file would be
Mjqqt
Send that to the phone it'll derive that into Hello
Now unless you know the encryption/decryption key how would you know that Mjqqt was Hello? It's not gonna be as simple as -5/+5 or anything like that.
Play with PGP and you'll see that the word Hello could be something like this
390tu904ugriojwG#GvrgerfdojeGO#J)94g39141Hb9ohbrG$#!Tjodsdfobadvscnleojgireig340909g3098409riorgkenR)#dgro0gJ#$)!0rejg!#GJ!!JRGH!#$G9je10ojgreojer1
You make it sound so simple. Too bad these phones are locked with strong modern encryption... The only way to install an update like htc/sprint can is it is signed with the correct private key, which only they have.
Because we don't have the private key to sign the update. There, no more questions on this thread.
Sent from my PG86100 using XDA App
Stephanie95 said:
Hmmmm perhaps you don't get it...
i.e. if sprint can 're-rom" our locked phones... why can't we?
Click to expand...
Click to collapse
Here, let me explain... it's like this. You go to work, but you can't go beyond your department. Sprint/HTC owns the office building, so they go in and out, with their key. You on the other hand, can only go where they let you go. Now if we some how find a little crack in the wall some where, we might be able to get in and then do as we please. We might even be able to change the locks so they can't get in unless we let them.
AssassinsLament said:
Here, let me explain... it's like this. You go to work, but you can't go beyond your department. Sprint/HTC owns the office building, so they go in and out, with their key. You on the other hand, can only go where they let you go. Now if we some how find a little crack in the wall some where, we might be able to get in and then do as we please. We might even be able to change the locks so they can't get in unless we let them.
Click to expand...
Click to collapse
Ok what about a "key-gen" ? i.e.
Is there an "encryption-gen"?
Can we delete this thread? Its taking up precious bandwidth from the internet.
Sent from my encrypted EVO 3d with ultra-secret decoder keys
Stephanie95 said:
Ok what about a "key-gen" ? i.e.
Is there an "encryption-gen"?
Click to expand...
Click to collapse
I know that not everyone is knowledgeable on every subject, but instead of asking here, you can do some Google searches about public private key encryption.
Sent from my PG86100 using XDA App
nealwheels said:
Can we delete this thread? Its taking up precious bandwidth from the internet.
Sent from my encrypted EVO 3d with ultra-secret decoder keys
Click to expand...
Click to collapse
Hmmmm... this takes up bandwidth- from what? Crysis2 takes up tons of bandwidth and "they" can get away with it... this is just a bit of typing once ever 5 min... lol
Have some fun and think outside the BOX!
i.e. both Sprint and HTC have this code and the phones don't need to be unlocked to install a new ROM
lol
swatspyder said:
I know that not everyone is knowledgeable on every subject, but instead of asking here, you can do some Google searches about public private key encryption.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Ya I will - but I was hoping the genius of the developers could hack something quickly... I don't know what I'm doing, other than "Brain-Storming"
Brainstorming is a good first step to get over "the wall"
I get my 3VO monday
Stephanie95 said:
Ok what about a "key-gen" ? i.e.
Is there an "encryption-gen"?
Click to expand...
Click to collapse
I see what the OP is trying to say there is like a master program code that opens the door for the OTA to get pushed through.
I really would rather wait for a good program to come back such as unrevoked 3 and then AMON other then that im sure sprint has hidden there tracks really well because if they didn't this would be known world wide by now
There is no keygen for such a thing . There waiting on HTC to do a update to unlock the phone which should be soon.
reaper24 said:
There is no keygen for such a thing . There waiting on HTC to do a update to unlock the phone which should be soon.
Click to expand...
Click to collapse
ok cool
does every phone have it's specific type of encryption?
I imagine they all have different "code-keys"
But, I wonder if anyone knows how the EVO was encrypted, or any of the older phones? Would that help?
I'm really pulling for the developers to come up with a "simlpe root" for the
3VO!
Using the computer to open files and "push stuff in a shell with pc3600.exe.zip.whatever.something.newfile... wasn't easy when I got my EVO when it was released(with "s-on"). lol
Alright, honestly we just need to wait for HTC to release a update...
Its been 24 hours and already some people are thirsty to root this bad boy...
Give it time
Stephanie95 said:
ok cool
does every phone have it's specific type of encryption?
I imagine they all have different "code-keys"
But, I wonder if anyone knows how the EVO was encrypted, or any of the older phones? Would that help?
I'm really pulling for the developers to come up with a "simlpe root" for the
3VO!
Using the computer to open files and "push stuff in a shell with pc3600.exe.zip.whatever.something.newfile... wasn't easy when I got my EVO when it was released(with "s-on"). lol
Click to expand...
Click to collapse
Htc really locked this sucker down from what I remember then enough people started *****in and HTC CEO said it will not be locked down with that crazy encryption which would take year or more to break.
From what I know and read were waiting on them to unlock us and the devs to build stuff along with a easy root
Stephanie95 said:
I get my 3VO monday
Click to expand...
Click to collapse
Please, buy an iphone.
Oh, and never post in the Developer section again. OKTHANKSBYE
http://www.verizonwireless.com/dam/support/pdf/system_update/galaxys4.pdf
I woke up this morning and on my phone was a request to update from Verizon, it was an official update.
I haven't seen anything anywhere and I can't believe that I am one of the first on XDA to get this;
I go first!
Lol :laugh:
Lol, spam is spam!
Sent from my SCH-I545 using Tapatalk
No offense, but you are a little late to the party. The update has been out for a week now.
See these threads:
http://forum.xda-developers.com/showthread.php?t=2731099 - Thread created on first rollouts
http://forum.xda-developers.com/showthread.php?t=2658480 - Discussion thread
The only nice thing is that VZW finally released info on the update.
Omega360 said:
No offense, but you are a little late to the party. The update has been out for a week now.
See these threads:
http://forum.xda-developers.com/showthread.php?t=2731099 - Thread created on first rollouts
http://forum.xda-developers.com/showthread.php?t=2658480 - Discussion thread
The only nice thing is that VZW finally released info on the update.
Click to expand...
Click to collapse
I didn't think I was the first but I haven't been following lately so I didn't see anything. How do you get rid of that constant nag?
What is so exciting about an update that essentially kills write permissions to the SD card and adds more bloat? Not being sarcastic. Just do not see the benefit. S4 seems fine, pre update.
JMO
rushless said:
What is so exciting about an update that essentially kills write permissions to the SD card and adds more bloat? Not being sarcastic. Just do not see the benefit. S4 seems fine, pre update.
JMO
Click to expand...
Click to collapse
Didn't add more bloat. Please explain in detail what bloat you are talking about. Most bloat can be turned off. As a matter of fact, one of the best parts of the update is the ability to disable bloat from the app drawer. Also, 4.4 added the framework for Tap to Pay. There are plenty of reasons to update. Kit Kat runs better for me and has features I find very useful.
Sent from my SCH-I545 using XDA Premium 4 mobile app
MedleHed said:
Didn't add more bloat. Please explain in detail what bloat you are talking about. Most bloat can be turned off. As a matter of fact, one of the best parts of the update is the ability to disable bloat from the app drawer. Also, 4.4 added the framework for Tap to Pay. There are plenty of reasons to update. Kit Kat runs better for me and has features I find very useful.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe you can disable KNOX(crap) without root. There are probably a few other verizon apps that cannot be disabled without root.
Knox? I haven't had a problem with it... It does nothing on my phone. Can you please explain what your problem is with Knox?
Sent from my SCH-I545 using XDA Premium 4 mobile app
You CAN disable knox....The only thing I wish I could disable that u can't is the stupid security update notifications
Sent from my SCH-I545 using xda app-developers app
It's not that it's a bad update by any means, 4.4 code has a lot of efficiencies over 4.3, but with as long as the wait was i guess people over hyped it and expected more new end-user features.
Sent from my SCH-I545 using XDA Premium 4 mobile app
My phone didn't show the update till a few hours ago. At first I was semi excited, then I remembered I still plan on rooting the crap out of the thing..... Verizon and their slow nonsense don't sit well with me sometimes.
D3Seeker said:
My phone didn't show the update till a few hours ago. At first I was semi excited, then I remembered I still plan on rooting the crap out of the thing..... Verizon and their slow nonsense don't sit well with me sometimes.
Click to expand...
Click to collapse
If you want the update and be rooted, go here --> http://forum.xda-developers.com/showthread.php?t=2726868
rushless said:
What is so exciting about an update that essentially kills write permissions to the SD card and adds more bloat? Not being sarcastic. Just do not see the benefit. S4 seems fine, pre update.
JMO
Click to expand...
Click to collapse
Honestly, the SD card "issue" is so overblown its not funny. It doesn't kill write permissions... what it does do, is make it so that apps don't have the right to go willy nilly across you card, to folders it shouldn't have permission to (unless you agree that a random app you download should have the ability to muck with other programs folders).
I made the jump on my phone more than a month ago, and my day to day impacts are NILL. Poweramp still plays all my music just fine, and not one program has had a FC or any other issue. In fact, had i not read articles from other people about the sky falling, i would have never known anyway....
Divine_Madcat said:
Honestly, the SD card "issue" is so overblown its not funny.
Click to expand...
Click to collapse
It's an unexpected, undocumented change. That you don't run applications which get broken doesn't mean that others aren't hurt by it.
Google is the new Microsoft - they think because they're successful they can do no wrong, but in reality they're clueless about a lot of things. Big enough to not care, and it's the users who get hurt.
Adding *nix permissions to a vfat volume is the right thing to do (short of requiring a modern file system on an SD card), but they're doing it wrong by not phasing it in so apps can accommodate the change.
Well, fill me in. What broke? What app needs to write willy nilly to folders it shouldn't be in that is now no longer working?
For all the moaning people give, i seem to have trouble finding REAL problems...
Divine_Madcat said:
Well, fill me in. What broke? What app needs to write willy nilly to folders it shouldn't be in that is now no longer working?
For all the moaning people give, i seem to have trouble finding REAL problems...
Click to expand...
Click to collapse
Subsonic is one example. Here's a detailed explanation with another example.
Your Google-fu is weak.
mike.s said:
Subsonic is one example. Here's a detailed explanation with another example.
Your Google-fu is weak.
Click to expand...
Click to collapse
At the end of the thread, its reported fixed, and your other article is from 2012 and has nothing to do with any of this.
Keep trying....
As it is.. apps may write to any folder they own, and may read from every folder. Unless the app is badly written, this change should honestly be a non issue.
Divine_Madcat said:
Honestly, the SD card "issue" is so overblown its not funny.
Click to expand...
Click to collapse
I agree 100%
Divine_Madcat said:
At the end of the thread, its reported fixed, and your other article is from 2012 and has nothing to do with any of this.
Keep trying....
As it is.. apps may write to any folder they own, and may read from every folder. Unless the app is badly written, this change should honestly be a non issue.
Click to expand...
Click to collapse
LOL. It was "fixed" by manually changing things in the application, fortunately the app had a setting where the storage path can be configured by the user, many don't. KitKat broke something which worked before because it introduced new restrictions with no prior warning to developers.
The linked article is about this issue, exactly. You didn't read the comments, did you? Or try searching ? The change has been around for a while (back to Honeycomb), but manufacturers worked around it for most devices. Now Google seems to be enforcing it as a requirement with KitKat (or Samsung decided to not do the work-around anymore, we'll see). Maybe it's not causing you problems, but it is causing problems for people.
Hi,
OK, so i finally got my TS yesterday, big surprise, was not expecting it.
Now, please forgive me, I am sure you are sick of users like me, but I don't know where to start.
I wanted to know how to get the play store, so I visited the Omate website > community > that led me here.
I have read many posts in these forums and now I am confused. I have no clue about this stuff and I need some clear clarifications and advice. Please pretend you are explaining to a 5 year old child.
1. I get the impression after reading posts here that the TS with stock everything is very unsafe. I have the non-dev edition. Is this true?
2. If so, I understand I have to install a patch. Is there a clear simple guide how to do this?
3. You then recommend I install a custom ROM.
3a. What do I gain by doing this?
3b. Which ROM do you recommended?
3c. Is there a clear simple guide on how to do this?
4. I also read that the BT is broken! Is this true? Does this mean I will not be able to connect a headset?
5. Icing on the cake, it is not water resistant and I cannot swim with it. How about heavy rainfall? If I am out on my bike, do I need to worry about rain?
Once again, please forgive me, this is way out of my comfort zone, I have never done anything like this before. I just wanted a watch that I could use as a phone and check my emails at times when my normal phone was not an option and "way back when" I had no idea it was going to be such a long, complicated and disaster plagued process.
Thank you in advance for sharing your time, it is appreciated.
-B
2100 1/8 TrueSmart (non-dev)
My watch is still on custom but I'll try to help you...
As I said I don't have it yet and all I know is from my Android experience on phones.
First, you'll need to root your device
* I'll post a link in a min *
Then find on Google "play store", download and open it.
Download all apps you need...
I would definitely recommend to flash custom ROM or patch developed by Loki.
Go to Omate section on XDA and ready first few threads by Loki, you'll get all when you read that...
Here are the links...
You have all instructions in OP (opening post - first post)
http://forum.xda-developers.com/showthread.php?p=9944525 - how to use flashing tool for TS
http://forum.xda-developers.com/showthread.php?p=51808413 - root Omate with this tool
http://forum.xda-developers.com/showthread.php?p=52253528 - ROM by Loki.
it's only custom ROM that'll work on 2100 version.
Patched and secured...
Sent from my C6903 using Tapatalk
I never had a problem with rain with my Motoactv, so I figure this should be fine as well. I've worn it in the rain a few times with no issues. Granted I haven't worn it in the rain with rain pelting on it for like a 45 minute period or anything, but I don't let things like rain or washing my hands get in the way. That being said, I can't say for sure if you could have it exposed to heavy rain while riding your bike for extended periods of time. Rain can come down pretty hard sometimes, and that with the speed that you're traveling at could cause water ingress. I kind of take the safe approach for mine though. It took a long time to get and I do like how it functions, so I really don't want to break it.
Thanks
Thank you both for your swift response.
funky0308 thank you for your guidance, I will walk through your steps and give it a go. So does this mean that it is unsafe at stock and I don't really have an option but to root it? If I want it secure that is.
speedyink, glad to know it can at least handle splashes
Examining and playing with it today, I came to pretty much the conclusion you described, so I am not going to worry too much about it, but I will not take the p*ss.
Thank you both again.
funky0308 said:
My watch is still on custom but I'll try to help you...
http://forum.xda-developers.com/showthread.php?p=9944525 - how to use flashing tool for TS
Click to expand...
Click to collapse
Your first link goes to a post for a TPU Case for a Nexus S
BD111 said:
Your first link goes to a post for a TPU Case for a Nexus S
Click to expand...
Click to collapse
Haha...really don't know why...
Well....Tapatalk...
Anyway...
Try this one
http://forum.xda-developers.com/showthread.php?p=47090665
And yeah...you have to install/flash recovery (TWRP) to flash ROM or patch.
Usually that means you have to root it first to flash/install recovery.
You need recovery because you can't flash zip files without it...
Maybe it's different on TS, maybe you can flash only TWRP without rooting device first - I'm not sure...
But TWRP and Loki ROM is something you must have.
Or at least Loki patch and Dees_Troy ROM (for bluetooth tethering)
http://forum.xda-developers.com/showthread.php?p=51455564
After you set everything and flash ROM and patch, check this thread and install (you also have this app on market) best companion app for TS.
http://forum.xda-developers.com/showthread.php?p=1735788
Sent from my C6903 using Tapatalk
Be careful even about exposing the TrueSmart to casual splashes. Many owners have reported their watches died from very light exposure to water, others have had better luck. It seems to depend of how it was assembled. There are several possible points of ingress: speaker grill, antennae ports, buttons, gaskets.
It was never really IP67 tested nor certified anyway.
Some seem to work OK for things like ocean kayaking, but you can't tell until you have tried and then it is likely it will die.
Do not expect a warranty replacement, in any case. It has happened, but don't expect it.
Sent from my Nexus 5 using Tapatalk
OK, I was planning to follow the steps and root it tonight, however I am not sure I need to.
I have the 2100 1/8 not the 1900, does that mean I do not have the same security flaws?
Here are the details from my TS:
Baseband Version
MOLY.MR8.W1315.MD.WG.MP.V4,2013/08/14 18:16
Kernel Version
3.4.5
Omate Version
OUI 2.1
Custom Build Version
Omate_TrueSmart_20140328.182336_V2.0
Is my TS safe?
Thanks
4284226 10
trent999 said:
Be careful even about exposing the TrueSmart to casual splashes. Many owners have reported their watches died from very light exposure to water, others have had better luck. It seems to depend of how it was assembled. There are several possible points of ingress: speaker grill, antennae ports, buttons, gaskets.
It was never really IP67 tested nor certified anyway.
Some seem to work OK for things like ocean kayaking, but you can't tell until you have tried and then it is likely it will die.
Do not expect a warranty replacement, in any case. It has happened, but don't expect it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
OK, thanks for the heads-up trent999 :good:
You do still have all the security flaws, even with the latest version of the 2100 firmware. They did not correct t ANY of the problems that Lokifish discovered and reported to them with fixes last year. They do not seem to either care or understand, I am not sure which. Probably both. EnSec patch by Lokifish will take care of most of the problems and correctly root the phone, but I cannot help you with selecting the version or installing. You can handle it though, with info available here on xda in other threads.
Sent from my Nexus 7 using Tapatalk
trent999 said:
You do still have all the security flaws, even with the latest version of the 2100 firmware. They did not correct t ANY of the problems that Lokifish discovered and reported to them with fixes last year. They do not seem to either care or understand, I am not sure which. Probably both. EnSec patch by Lokifish will take care of most of the problems and correctly root the phone, but I cannot help you with selecting the version or installing. You can handle it though, with info available here on xda in other threads.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Really? Wow! This company is starting to sound like a real joke. Lying in their promotional campaigns, ignoring known security flaws and practicing ignorance as a customer service model, I am really starting to wish I didn't bother.
Have they made any attempt to acknowledge Lokifish's discoveries? If so, have they give the xda community (or anyone else for that matter) any indication as to what they plan to do about it?
Yes. They officially support and encourage the installation of Lokifish's EnSec patch.
That involved no effort on their part, so, of course.
Sent from my Nexus 5 using Tapatalk
trent999 said:
Yes. They officially support and encourage the installation of Lokifish's EnSec patch.
That involved no effort on their part, so, of course.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
They really need to make it very clear to all of their customers that this problem needs patching. Thanks for the info.
Hi guys, figured I'd dive into this thread instead of starting another.
I've also just received my watch, 1/8/2100. I've read through the thread, followed links around in circles to empty repositories and posts that link to yet more posts that I just don't understand, I'm completely lost.
Is there anywhere a simple step by step, download this [link to actual download], run this [name of app], do this [instructions].. Something that doesn't rely on prior knowledge of how to do all this stuff.
Basically I have my expensive paper weight and I'd really prefer not to turn it into an expensive broken paperweight by using the wrong tools :-/
Sorry for being so dense, I just don't get it. Thanks.
No. Your 1/8/2100 may not be compatible with the patch - or anything else here for the TS. I also have a latest batch 1/8/2100 and the firmware is different to previous batches. You can root it but I've held off on patching and ROMing.
Sent from my LG-V500 using XDA Free mobile app
LeighR said:
No. Your 1/8/2100 may not be compatible with the patch - or anything else here for the TS. I also have a latest batch 1/8/2100 and the firmware is different to previous batches. You can root it but I've held off on patching and ROMing.
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Ah.. And seeing any further development has stalled due to lack of source code.. my expensive paperweight will likely remain an expensive paperweight. Isn't that just grand...
Thanks mate.
Next stupid question. There are about 6 clock faces to choose from, but my admittedly hasty back of a napkin math seems to indicate there should be 26 (one for every $5K above $900K)... Is this another thing that just didn't happen, or is it something we were supposed to get from the o-store or..?
http://www.xperiablog.net/2015/08/0...ty-fix-heading-to-xperia-z-series-this-month/
This is to confirm Sony will be pushing out an update to protect their Z series phones first from this Stagefreight problem that involves hacking our Androids with simply MMS. The issue is for us is that we still haven't had Lollipop to our phones for this long. Will this patch update may even take Verizon to do a hell a lot longer before they could even give us our deserved update? Because this is a serious issue that must be addressed.
I've also attached a screenshot from the analysis app for my Z3v, and we're definitely vulnerable...
Sent from my D6708 using XDA Free mobile app
we are ****ed
Watch vzw give us a patch without 5.1...
Old news Vzw is a terrible carrier
Not only stagefright but now certifi-gate, and certifi-gate you need to update the whole OS to fix it, so maybe we will finally get Lollipop, but wouldn't hold your breath.
I feel like a duck sitting on a pond surrounded by hunters, being a sitting duck I don't like.
SO LETS SEE HOW VZW PROTECTS THEIR NETWORK NOW!
Will VZW patch or will VZW not?
The quick fix solutions I have found so far in credits to Android Authority is to either download Textra for your messaging app, or disable auto downloading of MMS attachments on your messaging app.
To do that on our phones, go to stock Messaging app, Settings, then scroll down to uncheck Auto MMS Retrieval.
GigaSPX said:
The quick fix solutions I have found so far in credits to Android Authority is to either download Textra for your messaging app, or disable auto downloading of MMS attachments on your messaging app.
To do that on our phones, go to stock Messaging app, Settings, then scroll down to uncheck Auto MMS Retrieval.
Click to expand...
Click to collapse
Good tip, did that yesterday to mine and my wife's phone after reading the exploit news.
Be careful, any MMS can have the exploit attached.
Forgot to add, I disabled "Hangouts" too, I think it is affected too.
I was on my phone and went to xda news and saw the pushbullet article. I click on comments and get a redirection with a mess of ads and a android message talking about being infected....wth xda!!!
1linuxfreak said:
Not only stagefright but now certifi-gate, and certifi-gate you need to update the whole OS to fix it, so maybe we will finally get Lollipop, but wouldn't hold your breath.
I feel like a duck sitting on a pond surrounded by hunters, being a sitting duck I don't like.
SO LETS SEE HOW VZW PROTECTS THEIR NETWORK NOW!
Will VZW patch or will VZW not?
Click to expand...
Click to collapse
Where are you reading that you need to update the whole OS to patch Certifi-gate? Read this article, particularly the quote from the google spokesperson. http://www.zdnet.com/article/androcertifi-gate-remote-access-security-hole-malware-seen-in-the-wild/
BladeRunner said:
Where are you reading that you need to update the whole OS to patch Certifi-gate? Read this article, particularly the quote from the google spokesperson. http://www.zdnet.com/article/androcertifi-gate-remote-access-security-hole-malware-seen-in-the-wild/
Click to expand...
Click to collapse
Took you long enough to try and disprove me.
Do some reading you will find it. It is a problem with a layer in the OS, I had the information before the Black Hat conference.
1linuxfreak said:
Took you long enough to try and disprove me.
Do some reading you will find it. It is a problem with a layer in the OS, I had the information before the Black Hat conference.
Click to expand...
Click to collapse
I did read, couldn't find anything to support what you are saying but did find what I linked. If you have something else feel free to share with the rest of us. Kind of a moot point to me really as I am on my Nexus 6, which apparently isn't vulnerable.
That's okay I'm fine with being right don't have to prove it to you.
1linuxfreak said:
That's okay I'm fine with being right don't have to prove it to you.
Click to expand...
Click to collapse
you have something against sharing with the community?
BladeRunner said:
you have something against sharing with the community?
Click to expand...
Click to collapse
Your name is "community"?
Pleasure to meet you Community.
If you have Nexus 6 and are not at risk, are you just here to gloat and point fingers at us and laugh? Not very friendly.
1linuxfreak said:
Your name is "community"?
Pleasure to meet you Community.
If you have Nexus 6 and are not at risk, are you just here to gloat and point fingers at us and laugh? Not very friendly.
Click to expand...
Click to collapse
Who's pointing fingers and laughing? There is a community of users here that could benefit from the information you have if you'd share it. I only asked where you got your information from as the information I had seemed to imply something different.
BladeRunner said:
Who's pointing fingers and laughing? There is a community of users here that could benefit from the information you have if you'd share it. I only asked where you got your information from as the information I had seemed to imply something different.
Click to expand...
Click to collapse
If you know as much as you imply you would already know what I know and there would be no need for further discussion.
So as far as you are concerned the scare is over. Patches are out everything is fine. At least with your Nexus 6.
I will not post up something that is available on the inter web and you can find yourself. LAZY! Wait you may not get it right so here --
"Android-based mobile devices are under threat from yet another major security vulnerability and this time a simple download patch won’t fix it. Making smartphones and tablets safe against the new 'bug', dubbed Certifi-gate, will reportedly require a rewrite of the underlying software, leaving most mobile devices vulnerable until a new operating system version is released." -- there copy and paste this into your browsers search window or highlight and right click and do "Search Google" for this. Wait here -- https://www.google.com/search?q=certifi-gate+requires+a+OS+rewite&ie=utf-8&oe=utf-8#q=certifi-gate+requires+a+OS+rewrite
since you can't do it yourself.
Please go away now troll.
1linuxfreak said:
If you know as much as you imply you would already know what I know and there would be no need for further discussion.
So as far as you are concerned the scare is over. Patches are out everything is fine. At least with your Nexus 6.
I will not post up something that is available on the inter web and you can find yourself. LAZY! Wait you may not get it right so here --
"Android-based mobile devices are under threat from yet another major security vulnerability and this time a simple download patch won’t fix it. Making smartphones and tablets safe against the new 'bug', dubbed Certifi-gate, will reportedly require a rewrite of the underlying software, leaving most mobile devices vulnerable until a new operating system version is released." -- there copy and paste this into your browsers search window or highlight and right click and do "Search Google" for this. Wait here -- https://www.google.com/search?q=certifi-gate+requires+a+OS+rewite&ie=utf-8&oe=utf-8#q=certifi-gate+requires+a+OS+rewrite
since you can't do it yourself.
Please go away now troll.
Click to expand...
Click to collapse
wow, I really feel that was completely uncalled for.
BladeRunner said:
wow, I really feel that was completely uncalled for.
Click to expand...
Click to collapse
Really bro and what you did to me was kosher? Alrighty then!
Should have left it alone, I all but begged you to drop it.
So now I am wrong for sharing, really?
1linuxfreak said:
Really bro and what you did to me was kosher? Alrighty then!
Should have left it alone, I all but begged you to drop it.
So now I am wrong for sharing, really?
Click to expand...
Click to collapse
WHT, exactly, did I "do to you"? Wrong for sharing? Absolutely not. It's what I wanted from the beginning. Wrong for personally attacking by calling me lazy and a troll. Absolutely, I am neither, thank you very much.
This thread was on its way down the list but I just had to wake it up......