Related
http://androidforums.com/motorola-cliq/18600-cliq-bootloader-found.html
don't know if this will help any of u devs that are trying to root this thing. hope it helps cuz we need root asap.
condertis said:
What is going on with this forum, Suirebit did you gave up?!
Common people
Click to expand...
Click to collapse
There are various people working on it in different forums outside of xda. There is supposedly leaked source code out in the wild and there is a person working on some kind of non-HTC gold card type of exploit. Google "Root Motorola Cliq" and you'll see the various threads around covering this. Unfortunately there is no dedicated site yet like the Droid has to pool information to form a collective brain trust for this project . Hopefully there will be something for Cliq owners with in the next couple of weeks. Maybe sooner if that source code pans out. (crossing fingers)
factory restore image (dreamimg.nbh) equivilent?
I read a post from a guy (here I think) that stated he had a "factrory image" of some sort, the extension was nothing I had seen before, but it sounds to be the same type of file that HTC has, that when booted to recovery the phone will apply the image automaticly, which is how the dream gets downgraded.
I would think that if source is available and the image is too the only thing I could see stopping root would be a keyset other than the "real" one.
just like the g1 they may have a "dev keyset" that we can use on our fones and to sign updates which also blocks the "normal" updates out.
I have been searching daily for any info on rooting the morrison/cliq/dext, and haven't found much other than a couple forum posts and tweets. There are a few cliq fourms but none seem to have anything but "is root available", "when will it be rooted", "how do I gturn the phone on" type posts.
Let's all buy cyanogen a cliq
Bhang
bhang said:
Let's all buy cyanogen a cliq
Bhang
Click to expand...
Click to collapse
If he said he was taking donations for one, I'd help out . T-Mo has them at 50$ off right now too. But if he had a button in his sig that said "Cliq Donations" i'd log into PayPal right now =). The more advanced dev's that have them, the better.
tep065 said:
If he said he was taking donations for one, I'd help out . T-Mo has them at 50$ off right now too. But if he had a button in his sig that said "Cliq Donations" i'd log into PayPal right now =). The more advanced dev's that have them, the better.
Click to expand...
Click to collapse
same here. someone should let cy know he gots 2 willing. i got 20 on it. i dont even have a cliq and probably wont get one but if he wants one i am willing to help. he is way way to important to my daily use for me to not give what i can.
+1
Id be willing to donate to Cyanogen. The real question however, is whether or not he'd be interested. Correct me if I'm wrong, but I believe parts of blur are not open source.... if that's the case, then cyanogen may not be interested.
In any such case, this phone would be awesome with some optimized firmware on it. Heck, id go for a straight port of CM 4.2.5.
willing to donate
Hi all,
I'm not interested in rooting itself but in to use my mobile as a modem and be able to enjoy a lot of unnofficial updates, the same way I did with my old HTC Polaris...
I'm not a developer, but I'm willing to donate and support testing and getting logs...
I already bookmarked this thread to follow it up.
REgards,
JM
Forgot to clarify... I still have my Polaris, but I'm about to get my Moto Cliq this weekend or early next monday, but I have already played with the one my wife got last week...
I will buy Cyanogen a CLIQ if anyone can reach him and verify that he's interested.
cbrunner said:
I will buy Cyanogen a CLIQ if anyone can reach him and verify that he's interested.
Click to expand...
Click to collapse
http://twitter.com/cyanogen
Hey guys I saw this post strolling around on the internet. Maybe one of our fine devs could help this ambitious guy out..
http://www.droidforums.net/forum/droid-x-hacks/93955-getting-custom-kernels-running-droid-x.html
freaking sweet ! spread this !
Very interesting! Might want to move this thread (or a copy of?) into the Droid X development section.
For a minute there it looked hopeless..but it seems like this guy is really working hard on this. He has found the problem.. apparently the issue is not kenex but drivers. He needs help from someone that has experience with coding drivers...COME ON guys WE CAN DO IT! Lets get all the milestone and droid x devs on this!
This thread was mentioned in one of the threads on development. I hope he's successful, but I'd be surprised if he succeeded.
This guy needs DZO! DZO is a genius with a PhD in computer science. He's the one that pioneered Android on the HTC Vogue (a WinMo phone) and made it possible for all the other winmo htc's to get android. he rewrote all the drivers and such to work with those phones and I'm sure he is smart enough to do this. However, he lives in new zealand i believe and therefore cannot really get an X. Hopefully something can work out.
I think if he said that he said that he would work on the dx then we could get enough donations together to get him a dx. I don't think he would have to have access to the Verizon network to test wether or not the radio is working.
Sent from my DROIDX using XDA App
Hey all,
I'm new to the XDA forums and was wondering if I could some advice regarding ROM development on the DX. I've done some UNIX kernel work and know a fairly good amount of java as well, so I was thinking about looking into developing a ROM of my own as a side project. Can anyone direct me towards some information regarding the porting requirements needed by the DX, or possibly I could help out on another ROM to get up to speed on the process?
From what I've seen around here all ROMs for the DX are made by stripping the stock ROM of MOTO Blur, and adding a few packages that are custom or AOSP. Also, be prepared for people to tell you what to do... it seems to be the popular thing to do.
I would also love to maybe one day get into making a ROM, but I haven't seen any guides or the like for people who want to make a ROM. I would imagine it be a tad difficult.
http://forum.xda-developers.com/showthread.php?t=667298
I haven't done any of this I just was interested and found this awhile ago.
Looking forward to see what you can come up with!
Qwontum said:
Hey all,
I'm new to the XDA forums and was wondering if I could some advice regarding ROM development on the DX. I've done some UNIX kernel work and know a fairly good amount of java as well, so I was thinking about looking into developing a ROM of my own as a side project. Can anyone direct me towards some information regarding the porting requirements needed by the DX, or possibly I could help out on another ROM to get up to speed on the process?
Click to expand...
Click to collapse
My word of advice, since there's a locked bootloader, find every kind of work around you can for performance and battery, otherwise, your rom will be like the rest.
My rom may not come with the best options and all the advanced customizations, but i'll be damned if one outperforms mine in performance at least.. on paper and in theory, anyways. lmao
Qwontum said:
Hey all,
I'm new to the XDA forums and was wondering if I could some advice regarding ROM development on the DX. I've done some UNIX kernel work and know a fairly good amount of java as well, so I was thinking about looking into developing a ROM of my own as a side project. Can anyone direct me towards some information regarding the porting requirements needed by the DX, or possibly I could help out on another ROM to get up to speed on the process?
Click to expand...
Click to collapse
In addition to what drod said... Hit up @Aliasxerog on Twitter! He is currently looking for help with Linux kernel work. He has been working on a new init for the X to bypass the bootloader issue we have all grown to love! If you could give him some help, I'm sure he, along with the entire Droid X community would be forever in your debt
Shoot him a message and see what he has to say...
I can help you out if you have any questions, I am making a couple of roms for the DROID2 right now and the Dx is pretty much the same phone, just send me a pm if you need anything.
Qwontum said:
Hey all,
I'm new to the XDA forums and was wondering if I could some advice regarding ROM development on the DX. I've done some UNIX kernel work and know a fairly good amount of java as well, so I was thinking about looking into developing a ROM of my own as a side project. Can anyone direct me towards some information regarding the porting requirements needed by the DX, or possibly I could help out on another ROM to get up to speed on the process?
Click to expand...
Click to collapse
Sent from my DROID2 using XDA App
DEVS! Would it be possible to use a FroYo Kernel for CM7 like the Droid X Developers did?
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Original Android <3ers! said:
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Click to expand...
Click to collapse
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
daddy_droid said:
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
Click to expand...
Click to collapse
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
And queue take 3... omfg, when will people learn, this is not to debate ETA.
Original Android <3ers! said:
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
Click to expand...
Click to collapse
really not allowed to talk about that? Since when can someone else take away my free speech rights to ask when something is gonna to be released? If you dont want to answer a question for eta then just dont reply to it. After all no one is making you reply to anything.
If you HAVE NOTHING TO SHARE DONT POST IN DEVELOPMENT.
I'm trying to be honest with you and save you from being flamed. Did you even read the first post? The devs don't have the kernel source for the Epic 2.3.3 or beyond, nor do they have it for the Nexus S 4G, so until then, they have to stop developing because they cannot do ANYTHING without it. So an answer to an ETA is never.
lynyrd65 said:
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
Click to expand...
Click to collapse
I think this would be a good idea while we wait for the Kernel source actually...
nullghost mentioned that CM6 would be in the same state as CM 7. Idk why, but yea.
No no, we're saying use the FroYo Kernel for CM7!
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Darkshneider said:
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Click to expand...
Click to collapse
No.
Sent from my SPH-D700 using XDA App
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
The reason being? I dont get how theres source for 2.2 and we cant get CM6, how would 2.3 source help us get CM7 working?
And I got my answer while typing because of Deca. Thnx!
Decad3nce said:
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
Click to expand...
Click to collapse
So you don't like me?
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
I don't mind you, your motives are good, but this environment fosters redundant and pointless poo flingin'. Which usually leads to us responding with the same information, over and over.
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
Great way to lose another Dev.
Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
lynyrd65 said:
Great way to lose another Dev. Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
Click to expand...
Click to collapse
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Decad3nce said:
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Click to expand...
Click to collapse
Developers tend to support developers.
Sent from my SPH-D700 using XDA App
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.