Guys, lets ask for moto maxx forum proper way is here http://forum.xda-developers.com/showthread.php?t=1660354
Every member should do. Will be better for turbo and maxx.
Done. I made first tracks back before the phone came out. Subsequently I've gotten a few post quotes seconding it. If nothing else I think they should rename this one Moto Maxx XT1225 and then the problem will go away. See us Maxx owners being the generous, kind, handsome, and amazingly good lovers we are we would be willing to allow the Turbo owners to remain without complaint. Its just the kind of people we are.
krabman said:
Done. I made first tracks back before the phone came out. Subsequently I've gotten a few post quotes seconding it. If nothing else I think they should rename this one Moto Maxx XT1225 and then the problem will go away. See us Maxx owners being the generous, kind, handsome, and amazingly good lovers we are we would be willing to allow the Turbo owners to remain without complaint. Its just the kind of people we are.
Click to expand...
Click to collapse
I know you meant it to be funny but that was one of the most ridiculous things I've heard in a while.
The development is wildly different for these devices and it makes total sense to at the very least make separate development subgroups.
krabman said:
Done. I made first tracks back before the phone came out. Subsequently I've gotten a few post quotes seconding it. If nothing else I think they should rename this one Moto Maxx XT1225 and then the problem will go away. See us Maxx owners being the generous, kind, handsome, and amazingly good lovers we are we would be willing to allow the Turbo owners to remain without complaint. Its just the kind of people we are.
Click to expand...
Click to collapse
Hope more people ask, for adms looking for us.
adrynalyne said:
I know you meant it to be funny but that was one of the most ridiculous things I've heard in a while.
The development is wildly different for these devices and it makes total sense to at the very least make separate development subgroups.
Click to expand...
Click to collapse
You would have known I said exactly that on the thread that came before the one where we last crossed paths (about the same subject which is why I mentioned you might want to peruse what had already been previously discussed before you continued) but I'm guessing you did not. In fact even then it wasn't the first time I said it. lol And yes, it was humor. See I have already been on a multi device forum section with devices which varied more in their development than they do here and there was far less cries for a split. I mean hugely less. For an old man like me these sort of things are both interesting and humorous. I apologize for trying to inject some humor into it, I know it was weak but I had hoped to keep the mood propped up to a more upbeat place.
krabman said:
You would have known I said exactly that on the thread that came before the one where we last crossed paths (about the same subject which is why I mentioned you might want to peruse what had already been previously discussed before you continued) but I'm guessing you did not. In fact even then it wasn't the first time I said it. lol And yes, it was humor. See I have already been on a multi device forum section with devices which varied more in their development than they do here and there was far less cries for a split. I mean hugely less. For an old man like me these sort of things are both interesting and humorous. I apologize for trying to inject some humor into it, I know it was weak but I had hoped to keep the mood propped up to a more upbeat place.
Click to expand...
Click to collapse
Show me one forum that has flashing/modding methods this dissimilar please that has combined forums.
You go on about cries for a split, I've never been on a forum that has had this many cries against a split, especially one that makes total sense.
Thats just it, most are not crying against a split, they are just tired of crying about it period. The moderators have seen this and reported it to admin several times, I know that the thing has been requested in the proper place because I and others have already done so and posted that they did so here. There is no question that admin has seen this and evidently deems for whatever reason that they do not want to split these off into separate forums. I and many other people have also asked for a split of development if they are not willing to make separate sections already and this has also been seen by admin. As I already suggested several times people should go to the proper thread and make their voices heard about this and maybe we get some action, maybe not.
As to showing you I'm not going to spoon feed you something which I already told you, it becomes irksome to repeat something over and over to someone who is not listening. Outside of this everyone under the sun knows that once the bootloader gets unlocked on the Turbo the development can be nearly completely shared with the Maxx. Yes, developers for the Moto X and other devices have already confirmed this for the stupid people like me which are lucky to get something to recompile. The thing here is you are not like me, you know more about working with this stuff than I ever will so it begs the question... Why am I telling you something you must already know?
krabman said:
Thats just it, most are not crying against a split, they are just tired of crying about it period. The moderators have seen this and reported it to admin several times, I know that the thing has been requested in the proper place because I and others have already done so and posted that they did so here. There is no question that admin has seen this and evidently deems for whatever reason that they do not want to split these off into separate forums. I and many other people have also asked for a split of development if they are not willing to make separate sections already and this has also been seen by admin. As I already suggested several times people should go to the proper thread and make their voices heard about this and maybe we get some action, maybe not.
As to showing you I'm not going to spoon feed you something which I already told you, it becomes irksome to repeat something over and over to someone who is not listening. Outside of this everyone under the sun knows that once the bootloader gets unlocked on the Turbo the development can be nearly completely shared with the Maxx. Yes, developers for the Moto X and other devices have already confirmed this for the stupid people like me which are lucky to get something to recompile. The thing here is you are not like me, you know more about working with this stuff than I ever will so it begs the question... Why am I telling you something you must already know?
Click to expand...
Click to collapse
So you can't show me one. It is true, I knew you couldn't.
Nope, asked and answered, you have already been told by me exactly which forum. You are going to have to actually pay attention and read what people are saying or continue being ignorant, your choice.
krabman said:
Nope, asked and answered, you have already been told by me exactly which forum. You are going to have to actually pay attention and read what people are saying or continue being ignorant, your choice.
Click to expand...
Click to collapse
Edit:
I don't want to argue anymore, and withdraw my statements. The point is, until such a time (might) appear, the development is far too dissimilar for it to make sense as a combined forum. I am sorry you disagree, but its true.
Keep the same main forums, divide the development forums.
Exactly, you want to talk but you don't listen. All you hear is blah blah blah because the only thing important enough for you to listen to is your own voice. You were already told by me exactly which forum here on XDA the last time we traded posts. I'll give you a hint the devices have different SOCs, ram, screen, that help? I was just there five minutes ago because I still have that phone which nowadays is not normal since one of my kids or grand kids usually takes them off my hands when I upgrade.
You want to know which phone all you have to do is actually read what someone said and a quick search will give you your answer which you were already told in plain English. The forum section exists, the development is in fact far more different. Sorry man, the truth is out there and you cant BS your way out of it. Good night.
krabman said:
Exactly, you want to talk but you don't listen. All you hear is blah blah blah because the only thing important enough for you to listen to is your own voice. You were already told by me exactly which forum here on XDA the last time we traded posts. I'll give you a hint the devices have different SOCs, ram, screen, that help? I was just there five minutes ago because I still have that phone which nowadays is not normal since one of my kids or grand kids usually takes them off my hands when I upgrade.
You want to know which phone all you have to do is actually read what someone said and a quick search will give you your answer which you were already told in plain English. The forum section exists, the development is in fact far more different. Sorry man, the truth is out there and you cant BS your way out of it. Good night.
Click to expand...
Click to collapse
It took you 30 minutes to reply? How did you not notice I retracted my previous comment for the sake of stopping an argument?
adrynalyne said:
It took you 30 minutes to reply? How did you not notice I retracted my previous comment for the sake of stopping an argument?
Click to expand...
Click to collapse
It was easy, I started to respond but I got a phone call and finished up after. I should have quoted you so your whole blah blah comment could not disappear, my bad. At any rate, it appears we are done now. Good evening.
Hope more people help, droid turbo users should do too
The complication is there is a U.S Moto Maxx, the XT1250 which has the same FCC ID as the Droid Turbo XT1254. Sold by U.S. regional CDMA/LTE carriers The two phones are identical in every way, except for Verizon bloatware. Oh, and the XT1250 has bootloader that can be unlocked, phone can be rooted, and XT1250 will run on Verizon network with a Verizon SIM card. But Verizon Droid Turbo customers don't want to hear about that. Put fingers in their ears "La, la, la. I can't hear you."
ChazzMatt said:
The complication is there is a U.S Moto Maxx, the XT1250 which has the same FCC ID as the Droid Turbo XT1254. Sold by U.S. regional CDMA/LTE carriers The two phones are identical in every way, except for Verizon bloatware. Oh, and the XT1250 has bootloader that can be unlocked, phone can be rooted, and XT1250 will run on Verizon network with a Verizon SIM card. But Verizon Droid Turbo customers don't want to hear about that. Put fingers in their ears "La, la, la. I can't hear you."
Click to expand...
Click to collapse
Good grief, it has nothing to do with that.
It has to do with the fact that we have entirely dissimilar development and flashing methods now. Entirely.Different. Therefore it should be separated. Does the 1225 need to flash images for mods? How about the 1250? How about WP? No? Ok then, it doesn't matter how similar or the same the internals are here.
This is not some ego trip and it doesn't matter one iota what the FCC ID says. The methods are different and there is no denying it. Not a little different, very, very different. You are so big on pointing out FCC IDs that you have missed the point entirely. This would cut down on confusion.
adrynalyne said:
Good grief, it has nothing to do with that.
It has to do with the fact that we have entirely dissimilar development and flashing methods now. Entirely.Different. Therefore it should be separated. Does the 1225 need to flash images for mods? How about the 1250? How about WP? No? Ok then, it doesn't matter how similar or the same the internals are here.
This is not some ego trip and it doesn't matter one iota what the FCC ID says. The methods are different and there is no denying it. Not a little different, very, very different. You are so big on pointing out FCC IDs that you have missed the point entirely. This would cut down on confusion.
Click to expand...
Click to collapse
I agree the flashing methods are different. But before you (or others) were trying to say Moto Maxx and Droid Turbo were totally different phones, which was a LIE. The FCC ID of the XT1250/XT1254 proves that Moto Maxx model and Droid Turbo are identical in hardware, and anyone who says differently knows nothing about phones. Or at least ignorant about a an important technical area of phones. Seriously. There is so many legal ramifications to that FCC ID -- including the ADA law. So, it does matter what the FCC ID says. The XT1250 will even run on Verizon LTE.
Yes, developmentally they are different and we can continue the discussion from there. Because in a way the XT1250 is the "developer's" version of the XT1254. Already has bootloader that can be unlocked.
ChazzMatt said:
I agree the flashing methods are different. But before you (or others) were trying to say Moto Maxx and Droid Turbo were totally different phones, which was a LIE. The FCC ID of the XT1250/XT1254proves they are identical in hardware, and anyone who says differently knows nothing about phones. Seriously. There is so many legal ramifications to that FCC ID. So, it does matter what the FCC ID says. The XT1250 will even run on Verizon LTE.
Yes, developmentally they are different and we can continue the discussion from there. Because in a way the XT1250 is the "developer's" version of the XT1254. Already has bootloader that can be unlocked.
Click to expand...
Click to collapse
Lets fast forward to the present and stop living in the past. It doesn't matter what anyone said about them being totally different phones (and I never said that. Feel free to point it out if you can). This thread is not about any perceived differences in the phones internally. It shouldn't even have been brought up.
Related
To people that troll the forum... shut up if you arent helping with dev...
Especially dont be rude and drive them away... They are our only hope until moto releases an unlock bootloader - if ever
P.S I know this isnt dev related... But I hope the post can be here for a bit so people can see this.
Link below... CellZealot pointed out we arent very warm to people just trying to help.... Lets not be like that....
http://www.mydroidworld.com/forums/android-hacks/6511-moto-atrix-4g.html#post58112
Hopefully, "Recognized Developer" status will help with this, since it will allow said developers to partially police their own threads (yay the ability to close your own thread until you're ready to say more!). But that's still several weeks away.
Sogarth said:
Hopefully, "Recognized Developer" status will help with this, since it will allow said developers to partially police their own threads (yay the ability to close your own thread until you're ready to say more!). But that's still several weeks away.
Click to expand...
Click to collapse
+1. Can't come quickly enough
It really does astound me the amount if hatred and misinformation being spread around about this device, and a lot of it comes from people who don't even own one, or used it for a day and returned it. Very sad indeed. I agree with Sogarth, though
+1 So many people just spew out things not fully understanding, or make statements because they made changes to their device that they don't fully understand. My viewpoint is if you are going to make a change to your device, you should know what the change you are making is and the consequences of such. If you modify your software by modding files know that updates released by the manufacturer will not work on your device unless you put it back to factory.
Quite a few people here state moto is intentionally bricking their device because they can't install the update over their mods. It's problematic because it breeds misinformation as well as hatred/flamewars on the boards
Ririal said:
It really does astound me the amount if hatred and misinformation being spread around about this device, and a lot of it comes from people who don't even own one, or used it for a day and returned it. Very sad indeed. I agree with Sogarth, though
Click to expand...
Click to collapse
+1. Without Dev's, this device is just another "one year wonder" (if even in my use). We need to attract Devs, not push them away.
naturefreak85 said:
+1 So many people just spew out things not fully understanding, or make statements because they made changes to their device that they don't fully understand. My viewpoint is if you are going to make a change to your device, you should know what the change you are making is and the consequences of such. If you modify your software by modding files know that updates released by the manufacturer will not work on your device unless you put it back to factory.
Quite a few people here state moto is intentionally bricking their device because they can't install the update over their mods. It's problematic because it breeds misinformation as well as hatred/flamewars on the boards
Click to expand...
Click to collapse
For some reason this reminded me of an article on Engadget that was posted a while back:
http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking/
I'm always amazed at how many people manage to fudge up their phones and don't take responsibility for it, or try and blame the developer. I think there was a flare up last night because an Android blog posted something in a similar vein stating CyanogenMod was "ruining" a bunch of phones.
Going back to the Nexus One, I've always been amazed by how people talk to the devs here. They have much thicker skin than I do, thankfully. Haha.
Gr8Danes said:
+1. Without Dev's, this device is just another "one year wonder" (if even in my use). We need to attract Devs, not push them away.
Click to expand...
Click to collapse
Sigh... We really need devs badly for the atrix
That was one of the things I remembered reading a while back and it stuck with me, I remembered from my time working for Apple how people would **** up their phones jailbreaking it because they thought it would always be "one click and done". My girlfriend has an iPhone and wants to jailbreak it so she can do "cool things" with it. But she has no idea what the cool things she can do are. Nor the consequences that can happen should she mindlessly update her phone. Even I am sometimes skeptical of hacking my device until I know I can revert back.
As was said in Spiderman "With Great Power Comes Great Responsibility"
In the end what people have to remember is that as Devs software gets cracked not because everyone asks for it to be done, but it's Because they can. Back in the day whenever someone would ask "Why are you bothering with this" the response was always "Why? Because I can." Users of the mods have to remember this and know that things don't always "Just work" you have to know what you are doing. Part of the reason I'm teaching myself bit by bit how to mod so I can take part properly in the Dev Community.
KaLiBLeeK said:
For some reason this reminded me of an article on Engadget that was posted a while back:
http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking/
I'm always amazed at how many people manage to fudge up their phones and don't take responsibility for it, or try and blame the developer. I think there was a flare up last night because an Android blog posted something in a similar vein stating CyanogenMod was "ruining" a bunch of phones.
Going back to the Nexus One, I've always been amazed by how people talk to the devs here. They have much thicker skin than I do, thankfully. Haha.
Click to expand...
Click to collapse
naturefreak85 said:
In the end what people have to remember is that as Devs software gets cracked not because everyone asks for it to be done, but it's Because they can. Back in the day whenever someone would ask "Why are you bothering with this" the response was always "Why? Because I can." Users of the mods have to remember this and know that things don't always "Just work" you have to know what you are doing. Part of the reason I'm teaching myself bit by bit how to mod so I can take part properly in the Dev Community.
Click to expand...
Click to collapse
I remember that DEVS are doing this because they can, but now we have also some stimulus for the brave one(s) who'd crack the security issues that are preventing from flashing new kernels etc.
I also agree that if somebody is doing something with device like rooting, hacking Webtop or anything else should know what are they doing. I think that it'd be much more 'secure' - less number of bricked phones. But there are a lot of people that just want oneclick for everything, because the dont want/cant go into the command line, flashing or extraordinary instructions - its too complicated for them.
Moving this to general as not android development
This hole controversy over the past few days over P3droids post
http://www.mydroidworld.com/forums/...rooting-manufacturers-carriers.html#post65013
When i first read this i was stunned, i unloaded a lot of frustration out in another thread but that didn't do anything other than make me feel better, temporarily. I have another year with the Droid X and don't want to just put up with it until i can upgrade. I've enjoyed my Droid X very much and would like it to continue that way but the development on it seems to be dieing. I still see there being much more to do to the device, considering Gingerbread leak was just released and rooted. I don't know how many people flashed the leak but i have... and it makes a huge difference in performance. I am no dev or anything, the most knowledge i have on this concept is rooting, flashing roms, and sbf'ing when something goes wrong. So i just want an idea of what everyone else is doing now that P3droid has said what he had to say. Do you believe it?
This is my question ...why would someone who had this info release a "leak" of the rom they can track down? And still have links up for d/l?
If that was me id advice people not to upgrade to GB and wait for an official release then figure out how to root it... just how they figured out how to root the nexus s g2 mt4g atrix thunderbolt ...its possible ..
Now this is all a "he said she said"thing case ... no evidence no links no emails from Verizon or Motorola ...I understand the tethering and data thing but the root is garbage in my opinion ...it clearly voids warranty so you really think Motorola would be upset if you voided your warranty and have to buy a new phone? Less likely ...just my two cents
And just read where its posted in..
"News and Rumors" .....
That's all I gotta say
Sent from my DROID2 using XDA Premium App
I agree with 100% jeezy. I understand why Verizon would be upset about the tethering, but we all do pay for UNLIMITED data. Verizon is just upset that we found a loophole instead of paying for their wireless tethering. And it is a little fishy that P3droid will be the one person to give us a leak and then immdiately tell us this information. I did take a peak at his twitter the night that he posted that information and aparently he was drunk...hmm.... No disrepect to P3Droid, he may be telling the truth about all of this but we can't tust anyone anymore, especially after the recent rumor that someone cracked the bootloader.
And there is 70 views on this thread already and only 2 votes. Please people, we want everyones input on this topic. Obviously other people are curious too if there are already 70 views lol. If you want to comment and give your opinion, thats great too, but all i ask is if you make those 2 clicks to vote.
The final decision is to stop spamming and trolling about that topic. There is no solid evidence, links, Official ANYTHING for that matter and quite frankly, and I speak for a lot of senior members and those with common sense, I think we all want to stop hearing about it.
There are four posts in this thread, three of them are yours (OP). No one is posting because this is old and dead news on XDA. I doubt this thread will even get to a page two.
Well now someone has their panties in a bunch. The idea for this thread was the poll. Your exactly right in that there is no solid evidence on the topic... Which is the point of the poll. If there were solid evidence, then the topic would be dead. So instead of trashing a thread with your useless information, go make another thread on switching the 3g icon to 4g. Talk about pointless Ben
sdicker89 said:
Well now someone has their panties in a bunch. The idea for this thread was the poll. Your exactly right in that there is no solid evidence on the topic... Which is the point of the poll. If there were solid evidence, then the topic would be dead. So instead of trashing a thread with your useless information, go make another thread on switching the 3g icon to 4g. Talk about pointless Ben
Click to expand...
Click to collapse
Lol!!!
Sent from my DROID2 using XDA Premium App
sdicker89 said:
This hole controversy over the past few days over P3droids post
http://www.mydroidworld.com/forums/...rooting-manufacturers-carriers.html#post65013
When i first read this i was stunned, i unloaded a lot of frustration out in another thread but that didn't do anything other than make me feel better, temporarily. I have another year with the Droid X and don't want to just put up with it until i can upgrade. I've enjoyed my Droid X very much and would like it to continue that way but the development on it seems to be dieing. I still see there being much more to do to the device, considering Gingerbread leak was just released and rooted. I don't know how many people flashed the leak but i have... and it makes a huge difference in performance. I am no dev or anything, the most knowledge i have on this concept is rooting, flashing roms, and sbf'ing when something goes wrong. So i just want an idea of what everyone else is doing now that P3droid has said what he had to say. Do you believe it?
Click to expand...
Click to collapse
Umm.. Does anyone with a real brain cell believe it? Seriously stop spamming with this useless garbage. This isn't true. Not one shred of any evidence, stop spamming.
sdicker89 said:
Well now someone has their panties in a bunch. The idea for this thread was the poll. Your exactly right in that there is no solid evidence on the topic... Which is the point of the poll. If there were solid evidence, then the topic would be dead. So instead of trashing a thread with your useless information, go make another thread on switching the 3g icon to 4g. Talk about pointless Ben
Click to expand...
Click to collapse
No this is a waste of space. The poll is meaningless as it is not true. Seriously how in the world can you believe this? If someone honestly truely believes this and not just from a fear campaign I pity them. Verizon and Motorola are coming off saying they don't care if your Zoom is rooted they will upgrade it anyways. Also every Verizon rep I have talked to have no clue what I was talking about and the most recent one went a step farther and claimed it would probably have been a breach of contract on their end.
sdicker89 said:
And there is 70 views on this thread already and only 2 votes. Please people, we want everyones input on this topic. Obviously other people are curious too if there are already 70 views lol. If you want to comment and give your opinion, thats great too, but all i ask is if you make those 2 clicks to vote.
Click to expand...
Click to collapse
Then give an option to say this is bull**** I bet that hit counter will light up like christmas lol...
Bring it on Big Red. Ill have the legal team from Cydia make you their B%$# just like Apple
If it is true it's bullsh#t. If it's a rumor, that's sh#tty too. I hope it's not real, or at least something that never actually happens to us. I don't like the idea of being forced to go back to stock. And why? What was the main reason I got out of all the reading I did? Wireless tether. I don't even use it.
I own my hardware not Verizon.
I haven't changed the code for the baseband which is what interacts with their system.
My user experience is just that, mine.
Isn't a forum an open place for discussion? If you're not interested in the discussion why even read the thread or waste your time commenting on it?
Whatever, regardless if the rumor is true or not I for one am not changing my ways. I will do whatever I want with my phone until Verizon gives me the boot, at which time I will just flash to cricket and enjoy the reduction in my bill.
Sent from my DROIDX using XDA App
Sorry for the wall of text. I started typing and next thing I knew I wrote a novel.
Honestly, until I see some news on it, it's just a rumor. I did not upgrade to GB because I would rather wait for some development, but the bottom line is that this is just a rumor.
People have beat the whys, ifs, and hows into the ground so there is no reason for me to talk about them.
If you're so concerned that you have to make multiple threads, polls, and cry to your mother, SBF back to stock and enjoy your stock ROM as best you can. If you were on GB and this is true, VZW already has your MEID so you're ****ed one way or the other. So the only thing I can say is just chill out, crack open a beer, go to work, watch some baseball, jerk off... whatever you do in your spare time that relaxes you. If this whole thing is going to happen it's going to happen and worrying about it won't solve anything. You're already screwed on your current phone if everything P3 said goes down.
Most people here know there are certain risks involved when they mod there phones so if this all goes down, I'll just buy a new one and deal with the wenching from my wife. **** happens; deal with it.
--------------------------------------------------------
Finally, just some food for thought:
I've been using custom ROMs since the days of WinMo 6.5. Unfortunately, my first phone was not hacked due to lack of interest. I think it was the Samsung SCH-i760. While it was not hacked, people were sending this $600 phone bricked under a warranty replacement. I'm sure not as many as the Droid X's being sent back from complete noobies coming here and bricking their phones, but I digress.
Warranty replacements due to tampering are nothing new; it's been going on for YEARS, even prior to Smart Phones. In fact, I remember people warranty replacing their RAZRs trying to get rid of the Verizon UI.
Whatever happens, happens. Just go with it.
Honestly if everything is true and we will be no longer be able to make our droid Phones OUR droid phones I'm just going to get a plan with a cheap carrier and use this as a multimedia device and leo it mine.
Sent from my DROIDX using XDA Premium App
tech_head said:
I own my hardware not Verizon.
I haven't changed the code for the baseband which is what interacts with their system.
My user experience is just that, mine.
Click to expand...
Click to collapse
You are very correct. You can do whatever you want with your device and Verizon cannot do anything to your device about it. HOWEVER, they can do whatever they want with THEIR service. As stated in the terms of service that EVERYONE here agreed to, in section 2 part d of reasons they can terminate or suspend your service, if you " modify your device from its manufacturer's specifications" they have the right to stop providing you service.
So yes you can modify your device to hell and back but they DO NOT have to give you service for it. So all of you can stop saying Verizon had to tell you something or can't do this. THEY ALREADY TOLD US.
Message from kennethpenn regarding the issue at hand. Please read.
Ok I watched the following go down last night; Epinter edited his ICS rom leak posting from full of info and a download link, to " .. " and only that at 5:22 PM PST. This was followed by a few people commenting at the end of the thread "what happened/where are you?" to which Epinter replied (thumps up) "still here". That was about 8pm PST, and as of right now 6 am PST the following day, all of Epinters posts from the past 4 days have been deleted until the 7th.
Was Motorola employee information leaked in the leak we've been using?
Lets discuss, because now the record is gone. At the end of the thread 6 hours ago someone mentioned that a sanitized version will be coming, but I couldn't verify if that was either true, or even the problem to begin with.
Is Epinter in trouble with the notoriously stupid and arrogant Motorola?
If there was ever a company to forgot the rule of the internet, that once it's on the internet it's out there forever, it would be Motorola. I can verify for a FACT that Motorola watches this forum. I have spoken to nvidia executives, when they were toting development atrixes in summer of 2011, they WATCH xda, and occasionally use it; I have in the flesh verified this, they aren't morons and they know their resources. I think we might have stepped on some toes here, because Motorola is wickedly insecure about their IP, look at their recent lawsuits and blatent tech-grab acquisition by Google. They want us to buy their damn Razr M on Verizon, and not the continued usage of our phones, just look at the locking down of bootloaders, followed by waving $100 Verizon vouchers followed by killing ICS. It's like their not just giving us the middle finger, their trying to pry into our wallet, because we (everyone here at XDA) all need smartphones, why does Motorola have to make this such a painful experience...
Figured something like this would happen. Not a Dev so I kept out of the discussion but it seems that some entity with some parts in the file objected to its presence on XDA and it had to be taken down. I hope this doesn't mean the end to dev on this as I would love to have my atrix back.
Hopefully it will surface in the underground and be available to underground atrix network.
their trying to pry into our wallet
Click to expand...
Click to collapse
who do they think they are? the Gov't?
crashingout said:
Ok I watched the following go down last night; Epinter edited his ICS rom leak posting from full of info and a download link, to " .. " and only that at 5:22 PM PST. This was followed by a few people commenting at the end of the thread "what happened/where are you?" to which Epinter replied (thumps up) "still here". That was about 8pm PST, and as of right now 6 am PST the following day, all of Epinters posts from the past 4 days have been deleted until the 7th.
Was Motorola employee information leaked in the leak we've been using?
Lets discuss, because now the record is gone. At the end of the thread 6 hours ago someone mentioned that a sanitized version will be coming, but I couldn't verify if that was either true, or even the problem to begin with.
Is Epinter in trouble with the notoriously stupid and arrogant Motorola?
If there was ever a company to forgot the rule of the internet, that once it's on the internet it's out there forever, it would be Motorola. I can verify for a FACT that Motorola watches this forum. I have spoken to nvidia executives, when they were toting development atrixes in summer of 2011, they WATCH xda, and occasionally use it; I have in the flesh verified this, they aren't morons and they know their resources. I think we might have stepped on some toes here, because Motorola is wickedly insecure about their IP, look at their recent lawsuits and blatent tech-grab acquisition by Google. They want us to buy their damn Razr M on Verizon, and not the continued usage of our phones, just look at the locking down of bootloaders, followed by waving $100 Verizon vouchers followed by killing ICS. It's like their not just giving us the middle finger, their trying to pry into our wallet, because we (everyone here at XDA) all need smartphones, why does Motorola have to make this such a painful experience...
Click to expand...
Click to collapse
I think the question is more "why are the Motorola managers [excluding Googlers] so hell-bent on not thinking with their heads".
rthomas10 said:
Figured something like this would happen. Not a Dev so I kept out of the discussion but it seems that some entity with some parts in the file objected to its presence on XDA and it had to be taken down. I hope this doesn't mean the end to dev on this as I would love to have my atrix back.
Hopefully it will surface in the underground and be available to underground atrix network.
Click to expand...
Click to collapse
But if you look at other Motorola Sections on XDA, non of them had their ICS leaks thread deleted. This smells fishy.
Sent from that Atrix.
Morons! They think we are stupid and live inside a bubble.
Maybe Nvidia is hell bent agenst leeks, that would explain why there wernt any leeks for the other tega 2 phones.
IM_back! said:
Maybe Nvidia is hell bent agenst leeks, that would explain why there wernt any leeks for the other tega 2 phones.
Click to expand...
Click to collapse
There were. For both the LG Optimus 2X and the Galaxy R.
Sent from that Atrix.
Veyr strange.
Anyone has a mirror to the leak before it gets deleted ? Thanks !
I think we are not going to win this war. I'm interested in the lg nexus. Looks promising.
Sent from my MB860 using xda app-developers app
tatperson said:
There were. For both the LG Optimus 2X and the Galaxy R.
Sent from that Atrix.
Click to expand...
Click to collapse
Ok I missed that, maybe its the coumpany that made the fp reader, or any other component, i doubt that its moto since they usaly dont go this beserk over a leek.
So the plot thickens!
Anyone has a mirror to the leak before it gets deleted ? Thanks !
Click to expand...
Click to collapse
It's the internet. By now there are hundreds of copies of that leak floating around. I wouldn't be surprised to find it on torrent.
IM_back! said:
Ok I missed that, maybe its the coumpany that made the fp reader, or any other component, i doubt that its moto since they usaly dont go this beserk over a leek.
Click to expand...
Click to collapse
Usually a leak happens of an unofficial build that is going to be released officially at some point. This leak made moto look particularly bad because it was a partially finished update that they canned, most likely to get people to upgrade their phones. I find it hard to believe that moto didn't have EVERYTHING to do with the thread being deleted. We need to hope that our xda devs aren't in any real (aka legal) trouble over this.
crashingout said:
I can verify for a FACT that Motorola watches this forum. I have spoken to nvidia executives, when they were toting development atrixes in summer of 2011, they WATCH xda, and occasionally use it;
Click to expand...
Click to collapse
If you want me I can find you many posts on XDA threads submitted by very active members with very high number of 'Thanks' that were adamant Motorola didn't read comments on XDA, as if it was a degrading act. I have always suspected these members actually work in the benefit of companies, yes these people can represent multiple companies at same time because these people are actually employed by companies you and I never heard about before. Similar companies have previously been exposed after tweet followers scandal.
Let me summarise Motorola in a short sentence or two. Mexican Drug Cartels conduct business with their customers more professionally than Motorola ever did. Mexican Drug Cartels are brutal to disloyalty whereas Motorola's core business is based on disloyalty.
when in doubt, torrent. go look for it people. it's never gonna go away, since it has already been outed.
That Motorola...
CSharpHeaven said:
Let me summarise Motorola in a short sentence or two. Mexican Drug Cartels conduct business with their customers more professionally than Motorola ever did. Mexican Drug Cartels are brutal to disloyalty whereas Motorola's core business is based on disloyalty.
Click to expand...
Click to collapse
Reckon that!!
Guys : if for any reason, the development for that rom is banned from xda (which I doubt...you know, democratic freedom), I will be coming up with a forum to host the devs work and discussion right away, if needed.
It would be nice to know what's going on so nobody else gets in trouble. Hiding what is going on, removing threads and deleting leaked ROMs is not the way of XDA.
DannyBiker said:
Guys : if for any reason, the development for that rom is banned from xda (which I doubt...you know, democratic freedom), I will be coming up with a forum to host the devs work and discussion right away, if needed.
Click to expand...
Click to collapse
I really hope we don't have to go that far. but thanks for your offer!
Sir_Brizz said:
It would be nice to know what's going on so nobody else gets in trouble. Hiding what is going on, removing threads and deleting leaked ROMs is not the way of XDA.
Click to expand...
Click to collapse
Don't blame xda here. Judging by how abrupt and quick this was, I don't think they were asked politely. I'm betting the involved parties got a C&D from motorola. That's why you're not seeing anyone involved in this posting more details.
I have been browsing the droid turbo forums ever since I upgraded my gfs phone for vday and I am getting very confused to why the droid maxx xt is mixed in with the turbo topics.
I saw a root method for the maxx that does not work for the turbo, someone could easily end up downloading it and trying it, in the process brick their phone :'(
I was just hoping the mods would do some clean up of the threads and topics, etc. If there's a reason the maxx is mixed in please let me know, I'll greatly appreciate it
THANK YOU!!!!
Sent from my LGG3 using the original tapatalk pro!
117micc said:
I have been browsing the droid turbo forums ever since I upgraded my gfs phone for vday and I am getting very confused to why the droid maxx xt is mixed in with the turbo topics.
I saw a root method for the maxx that does not work for the turbo, someone could easily end up downloading it and trying it, in the process brick their phone :'(
I was just hoping the mods would do some clean up of the threads and topics, etc. If there's a reason the maxx is mixed in please let me know, I'll greatly appreciate it
THANK YOU!!!!
Sent from my LGG3 using the original tapatalk pro!
Click to expand...
Click to collapse
If you read before u download anything it wouldnt be a problem. The main reason they keep it all mixed together is i guess because they are identical in devices just one has an unlockable bootloader. Many people tried to get this to be changed so they are not mixed together but no luck.
I think will better have area for maxx, because turbo dont have unlocked bootloader or Lollipop yet.
117micc said:
I have been browsing the droid turbo forums ever since I upgraded my gfs phone for vday and I am getting very confused to why the droid maxx xt is mixed in with the turbo topics.
I saw a root method for the maxx that does not work for the turbo, someone could easily end up downloading it and trying it, in the process brick their phone :'(
I was just hoping the mods would do some clean up of the threads and topics, etc. If there's a reason the maxx is mixed in please let me know, I'll greatly appreciate it
THANK YOU!!!!
Sent from my LGG3 using the original tapatalk pro!
Click to expand...
Click to collapse
Agreed! Separate forums would be very helpful.
Not droid maxx but Moto Maxx
Don't know that separation will not add more duplicity along with segregation, but might be helpful. What would be reasonable is if people started referring to the device designations like what always has to be done on Sammy devices across regions/carriers/bands. If the XT1225, XT1250, and XT1254 designations were used more people would likely stop coming to this forum looking for the Droid Maxx, Droid Razr Maxx, et al, as well as it help determine whether packages, methods, firmwares, ROMs (wishful thinking), and other schemes work across the devices or to what degree.
if nothing else Moto Maxx needs to be added to the forum title obviously, and preferably the three models be added to the forum somehow or at least thread titles/compatibility.
I know the FCC ID would be more specific to use but not as readily identifiable to most.
The Turbo and Maxx need separate forums. They are now testing different versions of android. This forum is becomming a maxx forum with little for the turbo.
Sent from my Droid Turbo using Tapatalk
donsmith1964 said:
The Turbo and Maxx need separate forums. They are now testing different versions of android. This forum is becomming a maxx forum with little for the turbo.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
I agree 100%. The only drawback is if the forums do separate this place will be even more boring because of lack of development. Either way the separation needs to happen.
Another vote for separation.
Sent from my XT1254
yes, please.
There are a few threads on this already. My own thoughts are that separating the development sections would be enough. I suppose I have this opinion partly because I like to believe that people have functional brains and may actually bother to read a little before they flash. I also think that separating these completely would reduce the number of posters for both devices to the benefit of neither since there are few enough posters now. There is also some small hope that the turbo will get unlocked in which case most of what has already been done on the Maxx will be applicable to the Turbo.
krabman said:
There are a few threads on this already. My own thoughts are that separating the development sections would be enough. I suppose I have this opinion partly because I like to believe that people have functional brains and may actually bother to read a little before they flash. I also think that separating these completely would reduce the number of posters for both devices to the benefit of neither since there are few enough posters now. There is also some small hope that the turbo will get unlocked in which case most of what has already been done on the Maxx will be applicable to the Turbo.
Click to expand...
Click to collapse
this is turning into a moto maxx only forum.... needs some cleaning up.
That is because of the locked bootloader on the Turbo, Maxx owners will continue to post more often because they have more to post about. There is no clean up that will fix the locked boot loader and that is what has to change if you want more turbo directed posting. I'm not saying this to give you grief, it is my summation of the situation.
two forum
It would be great to have two forum, one droid turbo, and other moto maxx, excellent :good: :fingers-crossed:
I'd vote for separation. Just as an example search M8 or S4. These have at least half a dozen forums for each phone variant. Why can't this phone have 2?
matheus_sc said:
I think will better have area for maxx, because turbo dont have unlocked bootloader or Lollipop yet.
Click to expand...
Click to collapse
+1
The name of this forum is "Verizon Motorola Droid Turbo". If they aren't going to separate the two, maybe they should rename the forum.
Ally Android said:
The name of this forum is "Verizon Motorola Droid Turbo". If they aren't going to separate the two, maybe they should rename the forum.
Click to expand...
Click to collapse
Right...
Essentially, fans of the Maxx took it upon themselves to post in this Verizon Flagship Device's forum because they decided their device was the same thing. Even though it's not.
Wouldn't be such an issue if XDA allowed ignore filters. I could filter out Maxx posts which keep cluttering up my feed. There has not between a single post on this section regarding the Maxx that I, as a Turbo owner on Verizon, find useful or interesting. Is rather come here and see no new posts rather than have to shan through a bunch of Maxx-related posts.
Sent from my XT1254
distortedloop said:
Right...
Essentially, fans of the Maxx took it upon themselves to post in this Verizon Flagship Device's forum because they decided their device was the same thing. Even though it's not.
Wouldn't be such an issue if XDA allowed ignore filters. I could filter out Maxx posts which keep cluttering up my feed. There has not between a single post on this section regarding the Maxx that I, as a Turbo owner on Verizon, find useful or interesting. Is rather come here and see no new posts rather than have to shan through a bunch of Maxx-related posts.
Sent from my XT1254
Click to expand...
Click to collapse
Only difference is locked bootloader, but if we have our forum will be more great, because locked device dont have much things to do here in xda
I'm going to expand on my previous remarks a little but let me preface this with the fact that back in the beginning I supported the idea of a separate Maxx section. I said so on the threads at the time discussing it as well as asking for it on the official device suggestion thread.
This said my position has changed over time due to the activity level of this forum section. I had thought originally that the Maxx would be introduced in more markets giving it a larger potential group of posters but this has not occurred. The Turbo of course is a Verizon only exclusive for an unknown period. This means it has a very limited market compared to global release devices. As I look at the situation now I don't see much changing in terms of getting new posters to contribute here from either camp and I believe the number of contributors to this forum will go down from here.
The primary benefit of a site like this is learning and sharing experience and this requires having an active community of posters. As is right now the activity level is already comparatively low and you have to ask yourself if this is a beware what you wish for situation. Yes splitting the forum will mean that posters no longer have the other device to contend with when you browse. Yes they did it in the S4 and many other sections as mentioned above but those were global release devices that could be divided while still retaining an active and lively forum within each sub forum of the device. We do not have that luxury, even combined our traffic is a small fraction of any one of the S4 sections.
In my opinion this section should be renamed Droid Turbo and Moto Maxx. They can share nearly all of their development and various mods should the Turbo ever get its bootloader unlocked giving both devices synergy from the other. It will keep more posters contributing to the benefit of both groups of owners. I would however separate the development sections to reduce confusion. This method has been used for other forum sections and it works pretty well. Its not perfect and it doesn't answer to every master but it is a decent compromise.
In the end I'm not trying to tell everyone what to think, I'm saying think about it. Everybody wants their own section and I count myself among them but I think in the end I'm better off sorting through some posts that are directed at a different device in this case than I am getting a section for the Maxx.
I upgraded to BOG5 but found unable to downgrade and root.
Can anyone help me solve this peoblem
I would be very grateful
a133232 said:
I upgraded to BOG5 but found unable to downgrade and root.
Can anyone help me solve this peoblem
I would be very grateful
Click to expand...
Click to collapse
No one can help you solve this problem. BOG5 cannot be downgraded and it cannot be rooted. Period. End of story.
landshark68 said:
No one can help you solve this problem. BOG5 cannot be downgraded and it cannot be rooted. Period. End of story.
Click to expand...
Click to collapse
There's always JTAG...right?
dreamwave said:
There's always JTAG...right?
Click to expand...
Click to collapse
Please stop misinforming new people. I told you why JTAG wouldn't work before you even made your lengthy JTAG "brick" thread (which you referred back to your other nonsensical "petition" thread - the exact thread where I answered you WHY JTAG wouldn't work - in the end because you have absolutely no idea what you're doing).
Just remove this thread already. Or sticky it so there's a chance people will read it and never ask this stupid question again...
Sent from my SM-G900V using Tapatalk
Spartan117H3 said:
Please stop misinforming new people. I told you why JTAG wouldn't work before you even made your lengthy JTAG "brick" thread (which you referred back to your other nonsensical "petition" thread - the exact thread where I answered you WHY JTAG wouldn't work - in the end because you have absolutely no idea what you're doing).
Click to expand...
Click to collapse
Where did you reply in those words? I didn't get any of that out of what you said, unfortunately. Also, on the topic of the "petition" it was mainly to try and inform at least a couple more people and possibly gain a couple more arguments that could be used against Verizon through the FCC. I have a valid legal argument, one that you were being pessimistic about with really no backing, and on the JTAG issue...you didn't offer any reason why that was so, and so I didn't back down at the first sight of doubt. I don't mean to be defensive or aggressive in any way, but I respectfully took your opinion into account (and it was indeed an opinion on many of those matters), factored in the overall theme of posts you had made in the past, and decided that there was (and still is) possibility for solutions in each of these issues. Unless JTAG is specifically disabled at the hardware level (which was actually proven false by what I found and documented in my thread) it is still feasible to use it to modify the Qfuse flags.
dreamwave said:
Where did you reply in those words? I didn't get any of that out of what you said, unfortunately. Also, on the topic of the "petition" it was mainly to try and inform at least a couple more people and possibly gain a couple more arguments that could be used against Verizon through the FCC. I have a valid legal argument, one that you were being pessimistic about with really no backing, and on the JTAG issue...you didn't offer any reason why that was so, and so I didn't back down at the first sight of doubt. I don't mean to be defensive or aggressive in any way, but I respectfully took your opinion into account (and it was indeed an opinion on many of those matters), factored in the overall theme of posts you had made in the past, and decided that there was (and still is) possibility for solutions in each of these issues. Unless JTAG is specifically disabled at the hardware level (which was actually proven false by what I found and documented in my thread) it is still feasible to use it to modify the Qfuse flags.
Click to expand...
Click to collapse
For your petition, you keep saying, you have "valid" arguments. If you do, why do you need to keep continuing the thread? Go take it to court then. Start a class action lawsuit. You are correct, what I stated there is my opinion. Pessimistic about? You wrote so many pages for no reason. What does information do if you don't use it? All you were doing was talking about it. I was telling you why it doesn't work, and why Verizon doesn't have to respond to you, a single person, unless you were to take legal action against them, and even then, you are highly unlikely to win. By all means, take it to court. But know that talking doesn't change anything. If you want to argue that publicity is your motive, the 18k bounty got a thousand times more publicity, and the bootloader is STILL unlocked. There were also actual petition threads that people signed at change.com/etc, that have more "weight" than your thread, yet it is, again, locked still. I bet you the devs care more about a bootloader unlock than you do, because that's what most of their work/fun comes from. What did most of them do? Most (not all) of them jumped ship to Tmobile/international versions.
I took your opinion into account, but your legal backing to my eyes is simply, "Verizon must tell ME why/respond to MY claims as a sole person, not, Verizon has no basis for their argument (as I'm sure they have it somewhere, companies always try to hide their asses)." So like I said, go take it to court, by all means. I'm not being rude, I'm just saying, do something about it if you really believe what you think is right. It's also not pessimistic although you view it that way probably because it opposes your opinion, it's realistic and I've given you logical reasons why, whereas you just keep stating, Verizon has some obligation to respond to you.
As for the JTAG, I stated in one of the reasons why a bootloader unlock is not possible:
Spartan117H3 said:
...If you took the time to look at other threads ranging from the S3, Note 4, etc, you'll learn that the S5 isn't the only one. Also, the reason the Devs don't work on it is because a failed bootloader exploit bricks the phone so that not even a JTAG will revive it....
Click to expand...
Click to collapse
The devs already tried this. All you did was write a multi page post talking back and forth with yourself and new people who have no knowledgeable backing. Look back through your thread. The only support you had was from new people, you probably double posted more than their posts. I think only one senior member responded.
Spartan117H3 said:
For your petition...
Click to expand...
Click to collapse
I do apologize for trying a method that I saw absolutely no documentation on any attempts of, it was a fool of me to try and see if it might just work. You said that JTAG would not work, you gave no links and no reasons why. I understand that there might be a kill flag in there, but if the phone believes itself to be running genuine software I don't see much in the way of proof that it wouldn't accept any firmware rewrite then, especially as at that point Samsung and Verizon would stand to benefit from being able to directly write such firmware. The petition was simply to get even just a couple more eyes on the issue, and with the FCC...IT ACTUALLY IS A LEGAL CASE. I have tried to say that, that they are given ,by forfeit of direct control of the issues by Congress and the courts, a requirement that they use internal systems that are run as courts and have the power of a court, while being only possible to challenge if they act "unconstitutionally" outside their given bounds. The petition was a thing I started basically to try and let people outside of the developer community, who are demographically very likely to be vocal on issues of corporate monopoly (based on the crowd change(dot)org attracts.
I tried doing my research for each, and in basic principle found none that matched either. No, I'm not a longstanding member of the XDA community, and no I'm not an ex-oem firmware dev, but if I have an idea and no one gives me a specific reason why it won't work in a manner that would both completely address all facets of it and in a way that would help others to try and build off of the information contained within, then I will try and implement that idea or publicize it so someone who knows how can do it. Notice, on my thread about the SD Card unlock: I completely summarized the content of my findings in the first post, dead ends I ran into, and what I personally think might work in the future. If someone adds to the thread with info that either adds or nullifies an idea then I will update it and tag the post as I care about knowledge on a whole and getting info to everyone who can use it. My rationale behind this is to allow for anyone who might have an idea, or the capability to form a successful one, to research and take into account the findings of others.
TL;DR: It helps everyone, individually and as a community, to explain why an idea won't work than just to declare that it won't and the person's efforts (all of them) are in vain.
I do not mean to insult you or attack you in any way, and I have no "but" or "however" for this statement. Just for the future, instead of saying "no" and then flaming me when I say "why not," maybe say "why not" because if you know that the answer is "no," not that many issues are so black and white that a small bit of explanation or detail physically can't be given.
BTW, in response to one of your replies in a recent thread where you mentioned how a brick would not be possible to undo even by JTAG then talked about that being universal, what I was discussing was not bricking by means of triggering any lock such as that that you mention. I was attempting to reproduce conditions that would lead to a "failed flash of newer software" wherein no flag is tripped, but the phone could not load any usable kernel, modem, or bootloader image as that would allow for using the method here: http://forum.xda-developers.com/verizon-galaxy-s5/help/g900v-hard-brick-t2914847 that I have really worked on for the s3 to try and boot custom software to flash software to the phone. I am actually still optimistic for one method here because no one has said that it would not boot a very carefully crafted debrick image that would act as an external bootstrap and directly load a completely custom system image quite readily with no qualifiers or signature checks.
And sorry to everyone for the long post, I know it's annoying. Please forgive me :fingers-crossed:
@dreamwave, I mentioned that they were found by researching other phones that have bootloaders locked. There is one phone (I forget which one) where they (I believe two developers) DID get a successful bootloader unlock, but because they bricked so many phones that a JTAG would not fix, they sold bootloader unlocks for $25 a pop to recoup costs for the loss. But it was the phone itself, not a carrier specific version of a bootloader unlock. Meaning that phone worked on all carriers. I know you said you wanted links or whatnot, but it's on 100% XDA, and I'm on my phone right now/don't remember where I read it.
I gave you sound logic of why your solutions do not work, and if you take the time to think about what I say, instead of referring back to your own original statement, you would understand why. That's the thing. I state the reason why, whether or not you follow along with it is entirely up to you. I did not flame you in any way, I always responded with reasons why. It's just like you said, you were promoting awareness for people who are legally sound. But nothing was done, yet you keep continuing/promoting the thread, to what end? You're not going to do anything yourself. So why beat the dead horse?
You're right. I don't have hard documentation of answers. But you act like this is the first phone that has been attempted to be bootloader unlocked. There are threads in other forums for other phones that have been tested. There's also a plethora of sound reasoning against what you're trying to do. Do you need scientific proof and factual documentation that wind exists, or can you tell it exists because you can feel it on your skin?
If I have time later/if you want, I can find the links to what I'm talking about or you can look yourself, but for what it's worth, the developers work together in private to deter people from asking nonsensical questions such as, is it done yet/etc. As I'm not a developer (I just looked up this stuff in my free time), I don't have access to your hard evidence. But it has been stated that what you tried has been done on multiple phones in the past. If me saying that, or me finding the quote of someone saying that isn't enough for you, then by all means, go try it yourself. Developers will not come forward to tell you their progress for the reason I mentioned, so if you're looking for that, you won't find it.
@Spartan117H3
That is certainly reasonably sound logic for the most part, and I understand that many of them do it in private, but if you knew about it, especially other than just "no it doesn't work" for a specific experiment, it would be great if you wrote where any roadblock would lay and maybe a reference to where I could learn more about it. I learned that a major roadblock to parts of that method are the self verification of the bootloader and the external signature check from the SoC itself. What I am hoping to do is see whether or not the signature check and the load file commands are separate or integrated. If they are integrated, then that's probably the end of trying to use the SD Card, but if they are separate then it should be possible to dynamically alter the contents of the card after the initial signature check. Of course it's possible that it doesn't do the same signature check for an external SD card, in which case just modifying it to act as a permanent bootstrap would be entirely feasible.
I know that a lot of people have tried and failed, but if no one has tried this one specifically to its full extent I'd like to go for it. Just someone telling me no doesn't show me that they know what they're talking about. Someone telling me no, and then offering a little bit of a clue why (even just saying they found somewhere where someone tried the method then ran into (blank) as an issue) definitely helps me to try and either find a different method or a way around that issue or roadblock.
Also, I remember you telling me JTAG wouldn't work, but never addressing the SD card method... I can't seem to find any of your posts on my thread, though (a few on the petition one, but mostly didn't recognize the FCC as the deciding body, instead stating justification on the part of Verizon.) The FCC decides what their regulations say and mean, just as the courts do, and require adherence to those interpretations. No standing precedent exists that stands on Verizon's side on this issue from the arguments presented so I'm going for it, and just letting everyone know how it's going and leaving it open to discussion and reply if they have an idea that I might pursue to help my case
@dreamwave, what you are asking is the same as what this guy was "trying" to ask:
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
And the third post by the moderator clarified. As we have already discussed, you don't have enough knowledge (nor do I for that matter) to successfully start and finish a solution. It's like, if we were to build a building with just a hammer and some dirt. Why don't we leave the building process to the engineers? If you actually do have enough knowledge, contact a developer to get into their private work. Otherwise, you'll leave a building unfinished, cluttering up the streets, so to speak.
Basically, you're asking for either A, someone to go along with you in whatever process you try to do (in which case, it would be easier and quicker for a dev to do it his/herself), or B, just to see where progress is, in which case, it is not useful to you nor I, because it's another "are we there yet" question, and we wouldn't be able to continue with it anyway.
You don't know if it has or hasn't been tried, but I'm sure it's been thought of. You are doing it for free of your own accord. You don't think devs would want that 18k bounty way back when? Like I said above, if you have the knowledge, by all means, contact a developer, prove your worth, and I'm sure he/she will let you into their work, with all their notes or whatnot of what they tried that worked/didn't work.
If the bootloader is locked, that means unsigned code is not allowed at the lowest level. Why would an SD card work, when it goes through the OS which goes through the bootloader? Your idea of a JTAG makes a tiny bit more sense than the SD card one, because JTAG is at low hardware level. I didn't bother posting in your thread, because I figured you'd do what you want to regardless of what people say.
I recognized the FCC argument. I don't have an answer against that, but I'm sure/assuming Verizon does. But my justification was, why does Verizon have to answer to you specifically. You don't have a case because you're not going to court with it.
Edit: I can't remember for the life of me where I read about this stuff, all I remember was searching for some very specific bootloader question (a month ago?) that I wanted to know the answer to. The person was describing why root is so easy to achieve compared to a bootloader unlock and said something along the lines of: for root, all you have to do is inject stuff into a rom and see if it sticks. For a bootloader exploit, a failed attempt bricks the phone so that not even a JTAG will salvage it.
The search also led me to a phone which I also don't remember, I believe it was something older, but two devs "charged" $25 per unlock to recover the costs of the phones they bricked.
It is similar to the HTC M9 where people buy expensive Java cards to unlock phones, and unlock them based on donations, but not the same. I'll keep looking to see if I can pull it up.
@dreamwave, Found it, it was actually the HTC M8, so I was close in my edit above. Note, this post also talks about failed bootloaders killing the phone. And note again the reason that counters your petition, but it has no "hard evidence" other than "some person" says it. But it makes logical sense, so it should be left as is (in my opinion, unless you have profound knowledge that says otherwise, because I know I don't). Verizon doesn't need to prove anything to anyone who isn't suing them, or who isn't causing red tape for them. It's a post by a recognized contributor quoting a moderator, the closest you'll get to what you want.
http://forum.xda-developers.com/showpost.php?p=54644576&postcount=10
The Java card that people are using do currently work for both the HTC M8 and M9, but are limited and expensive in comparison to the Sunshine exploit that they charge $25 for (look at the bottom of this post)
http://forum.xda-developers.com/showpost.php?p=54126788&postcount=359
This is all I can provide for you in terms of hard facts. It is the conclusion made on older phones, and applies even more so on newer/current ones. Hope this helps.
Spartan117H3 said:
@dreamwave, Found it, it was actually the HTC M8, so I was close in my edit above. Note, this post also talks about failed bootloaders killing the phone. And note again the reason that counters your petition, but it has no "hard evidence" other than "some person" says it. But it makes logical sense, so it should be left as is (in my opinion, unless you have profound knowledge that says otherwise, because I know I don't). Verizon doesn't need to prove anything to anyone who isn't suing them, or who isn't causing red tape for them. It's a post by a recognized contributor quoting a moderator, the closest you'll get to what you want.
http://forum.xda-developers.com/showpost.php?p=54644576&postcount=10
The Java card that people are using do currently work for both the HTC M8 and M9, but are limited and expensive in comparison to the Sunshine exploit that they charge $25 for (look at the bottom of this post)
http://forum.xda-developers.com/showpost.php?p=54126788&postcount=359
This is all I can provide for you in terms of hard facts. It is the conclusion made on older phones, and applies even more so on newer/current ones. Hope this helps.
Click to expand...
Click to collapse
Thanks, that helps a lot with the SD card thing and my idea there. As to the legal issue though, I disagree a bit with the person there, as though it is in Verizon's interest to keep locking them, well the letter of the law is the letter of the law...and I spoke to someone who isn't a lawyer by practice but did take the BAR exam, what they said was basically that "A lawsuit would be possible if I suffered damages, but wouldn't do much to their practices necessarily. Going through the FCC would involve two steps: a trial in which they will determine if a violation has occurred (my opinion is that one has occurred, and I posted as my last post on the JTAG unlock discussion thread my current arguments), and then a second trial in which remediatory actions/consequences will be decided. This would cover retroactive steps, which would likely include a system whereby a signed patch would be created, and customized (upon request to download) to respond to a specific IMEI/model number. This would allow for a corporation or licensing group to exclude a set of devices while allowing consumer versions to be unlocked. It really doesn't cost me anything to pursue this, and if it annoys Big Red and that's it, then so be it...I'm happy if it does Of course on the same note, Verizon hasn't specifically countered any of my statements/observations, and have really tried to exploit little technicalities such as footnotes 500 and 502 in the FCC auction release, but in each I was able to create responses that very directly opposed those in a way supported by a large amount of text in the release. I'm hoping it will work, even if I wouldn't bet a million bucks on it doing so.
dreamwave said:
Thanks, that helps a lot with the SD card thing and my idea there. As to the legal issue though, I disagree a bit with the person there, as though it is in Verizon's interest to keep locking them, well the letter of the law is the letter of the law...and I spoke to someone who isn't a lawyer by practice but did take the BAR exam, what they said was basically that "A lawsuit would be possible if I suffered damages, but wouldn't do much to their practices necessarily. Going through the FCC would involve two steps: a trial in which they will determine if a violation has occurred (my opinion is that one has occurred, and I posted as my last post on the JTAG unlock discussion thread my current arguments), and then a second trial in which remediatory actions/consequences will be decided. This would cover retroactive steps, which would likely include a system whereby a signed patch would be created, and customized (upon request to download) to respond to a specific IMEI/model number. This would allow for a corporation or licensing group to exclude a set of devices while allowing consumer versions to be unlocked. It really doesn't cost me anything to pursue this, and if it annoys Big Red and that's it, then so be it...I'm happy if it does Of course on the same note, Verizon hasn't specifically countered any of my statements/observations, and have really tried to exploit little technicalities such as footnotes 500 and 502 in the FCC auction release, but in each I was able to create responses that very directly opposed those in a way supported by a large amount of text in the release. I'm hoping it will work, even if I wouldn't bet a million bucks on it doing so.
Click to expand...
Click to collapse
Ok. Except exchange/military is most likely a greater majority of customers than us who want it unlocked. Time is money. Verizon hasn't countered because you're not talking to them, you're talking in a thread. Good luck with your lawsuit.
Spartan117H3 said:
Ok. Except exchange/military is most likely a greater majority of customers than us who want it unlocked. Time is money. Verizon hasn't countered because you're not talking to them, you're talking in a thread. Good luck with your lawsuit.
Click to expand...
Click to collapse
Thanks (P.S.: I have an ongoing case through the FCC that's independent from XDA, a formal complaint directly to the FCC by methods they've provided)
dreamwave said:
Thanks (P.S.: I have an ongoing case through the FCC that's independent from XDA, a formal complaint directly to the FCC by methods they've provided)
Click to expand...
Click to collapse
Is this really what you choose to "Live Free or Die" about? Or do you have too many irons in the fire, and this is just the most annoying? People in New Hampshire have nothing better to do than to sue Verizon for something they have no chance of winning...
ldeveraux said:
Is this really what you choose to "Live Free or Die" about? Or do you have too many irons in the fire, and this is just the most annoying? People in New Hampshire have nothing better to do than to sue Verizon for something they have no chance of winning...
Click to expand...
Click to collapse
Except I'm not suing them, I'm using the methods our gov't has already put in place specifically for occasions such as this. I'm not arguing damages, it's not a lawsuit, it's an FCC complaint...something really different that I think I've explained a couple times
P.S.: I have a lot more that I do, this doesn't take much of my time and as a high school student I basically consider stuff like this a hobby, and have you ever been to New Hampshire? I'm from the southern half of middle NH...not that many "gun wielding hicks" around these parts
I got the phone from a friend who dunked it in a lake and thought it was dead, I figured I'd try and get some use out of it and discovered the larger issue on the part of Verizon. Considering the number of people at my school who ask me to root their phone, being able to tell them "sure" and not ask if they use Verizon (most of them do) first would be really nice.
...this thread got really off topic didn't it
dreamwave said:
Except I'm not suing them, I'm using the methods our gov't has already put in place specifically for occasions such as this. I'm not arguing damages, it's not a lawsuit, it's an FCC complaint...something really different that I think I've explained a couple times
P.S.: I have a lot more that I do, this doesn't take much of my time and as a high school student I basically consider stuff like this a hobby, and have you ever been to New Hampshire? I'm from the southern half of middle NH...not that many "gun wielding hicks" around these parts
I got the phone from a friend who dunked it in a lake and thought it was dead, I figured I'd try and get some use out of it and discovered the larger issue on the part of Verizon. Considering the number of people at my school who ask me to root their phone, being able to tell them "sure" and not ask if they use Verizon (most of them do) first would be really nice.
...this thread got really off topic didn't it
Click to expand...
Click to collapse
High school student... nevermind, kablock...
What do you mean?