I sought the RUU for HTC European M8 but was not released.
Many RUU have not been released. @LlabTooFeR told me that he doubts that will come out.
I think that if we join in protest against HTC maybe something could change.
What do you think?
I HAVE SENT AN E-MAIL TO HTC, WHERE TO ASK QUESTIONS for RUU release.
If you agree you also send an email to HTC EMAIL CONTACT
I AM SURE THAT THE UNION IS STRENGTH AND THAT A SINGLE MOVE A STONE, A GROUP MOVE A MOUNTAIN.
Do you want to contribute to this?
kalel77 said:
I sought the RUU for HTC European M8 but was not released.
Many RUU have not been released. @LlabTooFeR told me that he doubts that will come out.
I think that if we join in protest against HTC maybe something could change.
What do you think?
I HAVE SENT AN E-MAIL TO HTC, WHERE TO ASK QUESTIONS for RUU release.
If you agree you also send an email to HTC EMAIL CONTACT
I AM SURE THAT THE UNION IS STRENGTH AND THAT A SINGLE MOVE A STONE, A GROUP MOVE A MOUNTAIN.
Do you want to contribute to this?
Click to expand...
Click to collapse
Hmm..... I can't quite read your post. Perhaps you could make the text a little larger.
Not going to work, seen so many of these type of threads before. Save your valuable time and use it for something useful like your family for instance (assuming you have one)
These kind of threads usually (read usually carefully) fade away in time because HTC probably won't respond anyway to your (our) request.
rider5512 said:
Hmm..... I can't quite read your post. Perhaps you could make the text a little larger.
Click to expand...
Click to collapse
It's ok now?:good:
Mr Hofs said:
Not going to work, seen so many of these type of threads before. Save your valuable time and use it for something useful like your family for instance (assuming you have one)
These kind of threads usually (read usually carefully) fade away in time because HTC probably won't respond anyway to your (our) request.
Click to expand...
Click to collapse
I have a family, but i have a passion for modding too.....and a thread does not cost anything
and this, hopefully meet once a user ?
Sad thing is HTC doesn't care we still buy their devices and the only way for a consumer to speak is with their wallet
RUUs were great but what they do can be done manually with a bit of care and research.
exocetdj said:
RUUs were great but what they do can be done manually with a bit of care and research.
Click to expand...
Click to collapse
S-off
Nand backups
Official ota files (with firmwares and stock recoveries)
The world is at your feet, who needs a ruu if you have that ? Basically a ruu.......
But im am not discouraging the OP, just sharing my personal opinion
Mr Hofs said:
S-off
Nand backups
Official ota files (with firmwares and stock recoveries)
The world is at your feet, who needs a ruu if you have that ? Basically a ruu.......
But im am not discouraging the OP, just sharing my personal opinion
Click to expand...
Click to collapse
they are defo helpful for noobs but they also take the fun and experience out of learning lol
exocetdj said:
they are defo helpful for noobs but they also take the fun and experience out of learning lol
Click to expand...
Click to collapse
If you are S-off, they are a great way to quickly (so to speak) reset everything to stock. Yes, you can do all that manually, but sometimes you just want to hit the big red button and make it all go away. That is where an RUU comes in handy.
jshamlet said:
If you are S-off, they are a great way to quickly (so to speak) reset everything to stock. Yes, you can do all that manually, but sometimes you just want to hit the big red button and make it all go away. That is where an RUU comes in handy.
Click to expand...
Click to collapse
Yes, I don't have problems to return completely stock without RUU, I write a guide for this in my Italian forum also....but a RUU can be useful for particular reason or some inexperienced people(or for who can't be S-OFF)
I paid €500,00 for m8, why HTC can't released RUU to me?
Send with my HTC One M8 2014 from TTA
kalel77 said:
Yes, I don't have problems to return completely stock without RUU, I write a guide for this in my Italian forum also....but a RUU can be useful for particular reason or some inexperienced people(or for who can't be S-OFF)
I paid €500,00 for m8, why HTC can't released RUU to me?
Send with my HTC One M8 2014 from TTA
Click to expand...
Click to collapse
It matters not how much you paid for your device. The fact of the matter is when you buy a device you're buying it "as is". If you leave your device "as is" you have little need for an RUU (note I said little need, not no need), as you are free to update officially. It's not HTC's responsibility to provide you a way to return to stock when/if you choose on your own free will to modify your device. You know what you're doing when you do it and you know the consequences of doing it, again not HTC's problem. The fact is you do not require an RUU to have a fully operating, functioning device just the way the manufacturer intended. So what you really want is an extra service, an extra benefit that was never guaranteed or implied by the manufacturer.
It's okay to want this. It's even okay to request it, but what comes off entitled and kind of naive is when you demand that they give you their proprietary update utility that you didn't really pay for. They never told you you were going to get one. Never implied you were going to get one. Yet you demand that they hand one over. That's not a very good attitude to have and it's not the kind of feedback that companies like HTC typically respond to.
This doesn't mean I don't believe that they should provide them. The fact is I do believe they should, but they are not REQUIRED to by any means. As a matter of fact, HTC does provide RUUs at carrier request. They typically do not provide RUUs for is the generic WWE/international software and firmware. For example here in the United States, HTC US has posted official RUUs for AT&T, T Mobile, and Sprint with only one major carrier, Verizon, being left out. Verizon is left out because they request HTC not post RUUs for their software as it contains, again, proprietary software (eg the NFL Mobile app which they pay a hefty sum for every year and other cross licensing/marketing partners, and software). Incidentally, proprietary software protection is also the reason why Verizon does not allow official bootloader unlock. Most of what HTC does are determined by their software and carrier partners not any sinister plot to keep you away from updates.
I have inquired with HTC already a while ago and they told me they'd forward it to their dev department for investigating if it was possible to hand out an official RUU. The fact that they never got back to me means it's a "no" for GSM international. Else we would have a download already now.
They won't change their mind for a handful of XDA users, as I was able to experience myself way back during the OneS time. I had 800+ people backing my case and that is about nothing in their eyes.
In fact, I was told to my face by some HTC manager people that they won't do very much for XDA users except what they offer with htcdev.com - which they consider a lot already. Oh and tolerating but not welcoming unofficial leaks of shipped material.
Never will they tolerate beta material. People leaking such risk a lot of trouble with them.
Moderator information,
Thread has been closed at OP's request.
Many thanks,
Ghost
I ended up bricking my phone trying to get a custom recovery on it and said screw it and got the Moto G 2015.
This is the US AT&T and it's running android lollipop 5.1. Right now it's stuck on bootloop more or less, when I boot it up AT&T says it detects unauthorized software and to take it to the nearest help center or whatever.
I'm wondering if anyone's interested in it for development purposes or whatever? I'm willing to give it away for the cost of shipping or if it's worth anything to you, you can feel free to offer payment for it i guess? It is a decent phone outside of all of AT&T's stupid bull****.
Hope this isn't against the rules to post or anything. I don't really care about trying to make money off this, it just seems like an awful waste of a perfectly good phone if someone with more know-how than me can easily fix it and maybe better the dev community for it.
Feel free to let me know
Tazzypillar said:
I ended up bricking my phone trying to get a custom recovery on it and said screw it and got the Moto G 2015.
This is the US AT&T and it's running android lollipop 5.1. Right now it's stuck on bootloop more or less, when I boot it up AT&T says it detects unauthorized software and to take it to the nearest help center or whatever.
I'm wondering if anyone's interested in it for development purposes or whatever? I'm willing to give it away for the cost of shipping or if it's worth anything to you, you can feel free to offer payment for it i guess? It is a decent phone outside of all of AT&T's stupid bull****.
Hope this isn't against the rules to post or anything. I don't really care about trying to make money off this, it just seems like an awful waste of a perfectly good phone if someone with more know-how than me can easily fix it and maybe better the dev community for it.
Feel free to let me know
Click to expand...
Click to collapse
Hey man, just wondering if this offer is still on the table? I noticed you mentioned it was running 5.1... was that a custom ROM? Any idea if the bootloader is unlocked?
srnoth said:
Hey man, just wondering if this offer is still on the table? I noticed you mentioned it was running 5.1... was that a custom ROM? Any idea if the bootloader is unlocked?
Click to expand...
Click to collapse
It is still on the table, the thing is just lying around. I made a mistake saying it was running 5.1 though, it HAD been running the latest version of cyanogenmod months ago but eventually I needed to return it to stock for something dumb and when I tried to switch back, I bricked it.
The phone was rooted and I'm PRETTY SURE I managed to unlock the bootloader, but it's possible I may have messed that up because I bricked it while trying to flash a custom recovery. The phone still boots into download mode so I figure someone crafty enough with a better ability to figure out what files are required could fix it with ODIN or something.
Good morning
if the offer is still available can you contact me at [email protected]
Thread closed.
7. Do not spam, sell or trade on the forums.
If you wish to advertise a product, simply contact us. We can provide ads but you are not permitted to just post it in the forums. If you do, it will be removed and you're likely to receive a ban.
On the 30th Nov 2012 the Marketplace closed. The buying, selling, trading and / or exchanging of any item is now prohibited on XDA, in any forum or via Private Messages. We now use www.swappa.com
Regards,
The_Merovingian
Forum Moderator
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?
First of all, i don't wanna get flamed because of this, this is just a thought, nothing more, i just wanted to discuss abit more about this, since there's no real discussion thread in any forum about this. So, as we all know, there's no real way to unlock bootloaders wich have bootloader unlock allowed:No status. Yet. I think there is a way, because, let's be honest, it's not a hardware restriction. That means, someone, somewhere, with enough knowledge and experience maybe could unlock it. While Sony's software is really good, i am a long time XDA member, and with a huge history of devices, i really don't like being restricted on Stock ROMs and kernels. This situation has honestly never happened to me, and it's my fault not checking the device i took. Feel wise, this phone is the best i owned. It feels right. It feels premium. The battery is great. The screen is great also, and the camera too. I love it. Just the feel of being locked forever makes me scared actually. Mainly because i plan to stay with this phone for atleast two or maybe more years since it's just too great. And, seeing as Android grows, our device will already be outdated with the next android release. Sure, that's not a problem for users with unlocked bootloaders, since they will be supported with CM/it's kangs and AOSP custom ROMs for the next gen for sure, and maybe even the one after that. But what's with us that have bootloaders locked? Marshmallow and that's it? No more updates? No more security patches? No new features? That just doesn't sound right. Now, i think we, as a community, should really do something about this, yea, maybe it's not a big thing for many of you, and for you with unlocked BL's, but for me it is. What are my thoughts, and our options could be:
1. We could raise a bounty, and buy/give a phone to someone experienced with unlocking and hardcore hacking (the first name wich comes to my mind is @geohot )
2. We could do some research, ask opinions from devs and litteraly everyone we can, do some experiments with this stuff (but that requires someone really brave hahah)
3. I don't know, you can tell me below.
But i really think we should do something about this finally.
NOTE that this includes Xperia Z1/Z2 users also.
Guys i at least want disscus this. Call me stupid and call this all above nonsense, but if there's at least a small shed of light, any hope, we should discover the way.
And sorry for the long post.
Sent using XDA One
There are lots of discussions about this in various Xperia threads.
Here is my $0.02
Geohot will not touch an Xperia device, he has had a C&D from Sony, so will not get involved with them.
No-one will seriously try to find a way to unlock the boot as there is a very simple way already, just buy a device that allows it. Why try and pick a very very difficult lock on the front door when the back door is left wide open. I understand some people have devices that cannot be unlocked but devs will always get ones which can.
Finally, have a look in the cross device development section for a thread about this. Munaji was trying to do just this but AFAIK he made very little progress.
gregbradley said:
There are lots of discussions about this in various Xperia threads.
Here is my $0.02
Geohot will not touch an Xperia device, he has had a C&D from Sony, so will not get involved with them.
No-one will seriously try to find a way to unlock the boot as there is a very simple way already, just buy a device that allows it. Why try and pick a very very difficult lock on the front door when the back door is left wide open. I understand some people have devices that cannot be unlocked but devs will always get ones which can.
Finally, have a look in the cross device development section for a thread about this. Munaji was trying to do just this but AFAIK he made very little progress.
Click to expand...
Click to collapse
Too bad. I'm sure he could do it.
Sent using XDA One
So its clear to anyone who's read of my root attempt or simply heard through word of mouth or whatever the case is. I'm not the most liked user here I get that no this isn't a thread to get hate or admins /mods etc mad closing the thread this is simply an apology to anyone who feels as though I was a troll a lier etc..this is simply this is partly my experience from it what I've seen from the community afterwards and what exactly went wrong with root attempt.. Now first n for most there's been a lot of hate and bs about me saying I did this or that no straight up whatever it is or who said it its false I own up to what I say and or mistakes. Now I get it y'all got a laugh or got disappointed or are simply mad about the way i type stuff out that's fine. Look I've done a lot of learning rooting ROMs etc now what I did wrong was I tried forcing it like I did my Linux box a couple years back..friend of mine he locked me out of it anyway I didn't know that with android it was a completely different thing to get root. I apologize for misleading anyone my goal was to help people but I failed I'll admit it the project went FUBAR an I completely tossed it out. Past couple months or how ever long its been since BL unlock came I've been looking into rooting devices and custom ROMs and kernels sadly i have literally to much hate around me because of a failure..my own fault I let my head get the best of me although I let everyone down here I just wanna say I'm sorry to everyone. I do not wish to be a hated member of this community Android and Linux have been something I've loved for years I'd like to bring ROMs kernels etc to the table.. But who's going to actually use it if people see how hated I am here or a failure etc. So again I apologize and I've learned from my mistakes now I ask of you the XDA community to accept my apology and move forward I'd like to become a real member here like computerfreak, baybutcher and skrilax_CZ etc just to name a few members. Not really shout outs or anything just saying I see the work the positive response from you all and I'd rather be known for good reasons as for hate comments yes I know I'm in for those it's fine. :/ but I'd like to move forward as a real contributor here and unless people can drop the hate I'm unsure if that'll happen but I hope it does to the members of XDA that I let down I'm sorry truly I am. (Also if you really want to hear what happened with root ask and I'll explain the whole story I didn't wanna type it out if no one cares...that is if anyone reads this anyway)
Everyone got too excited and you over promised. Now it's just a joke people refer to but that's due to time and the fact that the bootloader actually did get unlocked shortly after that incident. I don't hold anything against you, but I'd expect occasional jokes from the community. Actually release something (anything) and everyone will forget.
koftheworld said:
Everyone got too excited and you over promised. Now it's just a joke people refer to but that's due to time and the fact that the bootloader actually did get unlocked shortly after that incident. I don't hold anything against you, but I'd expect occasional jokes from the community. Actually release something (anything) and everyone will forget.
Click to expand...
Click to collapse
I hope you are right I've had a lot of hate and that thing with jcase and the TZ exploit that never happened on my end saying I tried getting info on it (mind you I don't steal others work nor would it have helped me due to the fact that goes for bootloaders) and well I'm not willing to screw with bootloaders at all I just want everyone to see I was over my head and was just trying to help is all
i'm tired of people that keep bringing it up, its just a reflection on their character, not yours. as far as i'm concerned its been over since before it was over.
quantum tao said:
i'm tired of people that keep bringing it up, its just a reflection on their character, not yours. as far as i'm concerned its been over since before it was over.
Click to expand...
Click to collapse
Thanks man just trying to get all this damn mess dealt with I figured straight up apology would calm the waters I can completely understand why people where upset hell I beat myself up over the failure for awhile now actually considered saying F it and just leaving XDA that's how much bs happened for awhile
Honestly, I never understood why people create a thread saying "I'm going to work on XXX" instead of just posting the work itself. I've been a member of XDA since 2009 and I've NEVER seen someone post "I'm working on this" and actually come up with something...this includes root attempts, bootloader exploits, ROM ports, etc.
Usually, the people who come out with these kind of things work on it without having to share it with the world.
Nothing productive comes out from one of those threads so I wasn't sure why the thread was even created.
Sent from my DROID Turbo using Tapatalk
The problem is you spoke well beyond your abilities.
Learn something simpler first.
Edit stock for a bare bones pre rooted version, then make it flashable.
Compile some already built ROMs just for an idea how it works.
Then attempt building some ROMs that are based off of cm. You may be able to bring us blisspop or carbonrom with some minor help.
After you get a good grasp, perhaps you could then actually maintain a ROM.
I personally would love to see the nexus experience ROM for our device.
mrkhigh said:
The problem is you spoke well beyond your abilities.
Learn something simpler first.
Edit stock for a bare bones pre rooted version, then make it flashable.
Compile some already built ROMs just for an idea how it works.
Then attempt building some ROMs that are based off of cm. You may be able to bring us blisspop or carbonrom with some minor help.
After you get a good grasp, perhaps you could then actually maintain a ROM.
I personally would love to see the nexus experience ROM for our device.
Click to expand...
Click to collapse
I'm working on porting cm 13 to my Asus transformer tf101 so I can actually contribute to the droid turbo so step in the right direction I guess
mrkhigh said:
I personally would love to see the nexus experience ROM for our device.
Click to expand...
Click to collapse
And the Nexus Experience already has a head start over in the OTHER Quark forum. It was just not updated for the XT1254. So current XT1250/XT1254 -compatible Quark kernel doesn't work with it. But it's already BUILT and ran find on XT1225 until November 2015.
So, that would seem to be very achievable?
Thread cleaned - keep it civil please...
Don't let them get to you. I don't really see how you could have hurt anyone anyhow. Even if you were feeling a little overconfident, at least you tried. I still thank you for giving it an attempt and trying to help others in the spirit of the XDA forums. I was trying at the same time and it was definitely over our heads, but that's how we learn, right? I couldn't have put together a build of CyanogenMod a year ago, but I kept at it. Just don't give up. There will always be someone who pokes fun (appropriate or not).
calsurferpunk said:
Don't let them get to you. I don't really see how you could have hurt anyone anyhow. Even if you were feeling a little overconfident, at least you tried. I still thank you for giving it an attempt and trying to help others in the spirit of the XDA forums. I was trying at the same time and it was definitely over our heads, but that's how we learn, right? I couldn't have put together a build of CyanogenMod a year ago, but I kept at it. Just don't give up. There will always be someone who pokes fun (appropriate or not).
Click to expand...
Click to collapse
True true I'm just happy we got bootloader unlock
Shiftydogit said:
I'm working on porting cm 13 to my Asus transformer tf101 so I can actually contribute to the droid turbo so step in the right direction I guess
Click to expand...
Click to collapse
How would that help the droid turbo community?
Sent from my XT1254 using Tapatalk
PILLMUZIK3600 said:
How would that help the droid turbo community?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Learning to port and build ROMs will strengthen my knowledge of Android then I can use that towards the turbo
Thread closed - point made.