Related
I wanted to ask a simple question do we know if the NBH updates are signed or not?
I am working on a hybrid to get root back on RC30s phones.
Please if anybody knows the answer to this.
(I have something done already but dont have any stock rc30s to test with.
The file changes are good and the nbh works as modified however it works on an engeniring bootloader because it doesn't check signatures. humbug
http://rapidshare.com/files/176990405/DreamIMGTest.html
From what it sounds like they are signed, by htc themselves. But I have a stock rc30 and I'll try it.
Freaking rapidshare is slow uploading now.
afbcamaro said:
I wanted to ask a simple question do we know if the NBH updates are signed or not?
I am working on a hybrid to get root back on RC30s phones.
Please if anybody knows the answer to this.
(I have something done already but dont have any stock rc30s to test with.
Click to expand...
Click to collapse
I would be happy to test. I have a couple of stock rc30s that can be used.
afbcamaro said:
I wanted to ask a simple question do we know if the NBH updates are signed or not?
I am working on a hybrid to get root back on RC30s phones.
Please if anybody knows the answer to this.
(I have something done already but dont have any stock rc30s to test with.
Click to expand...
Click to collapse
The first 256 bytes of the nbh is the signature.
JesusFreke said:
The first 256 bytes of the nbh is the signature.
Click to expand...
Click to collapse
so question to you....if we know where the signature is, would there be a way to apply the signature to an NBH that we create? if creating one is possible.
Sure, you can change the signature, but how are you going to generate it? Do you have the keys from HTC? If not, might as well give up now
korndub said:
so question to you....if we know where the signature is, would there be a way to apply the signature to an NBH that we create? if creating one is possible.
Click to expand...
Click to collapse
Don't think you quite understand how signatures are created. You can't just toss a signature off one Android version on to another.
Damn I see the signature!!
A mute point then here is the file anyways.
http://rapidshare.com/files/176990405/DreamIMGTest.html
The file changes are good and the nbh works as modified however it works on an engeniring bootloader because it doesn't check signatures humbug
momentarylapseofreason said:
Don't think you quite understand how signatures are created. You can't just toss a signature off one Android version on to another.
Click to expand...
Click to collapse
i do understand that, just some tiny bit of hope...i know that signatures are based on filesize and name and content and all that.....
What about swapping sd cards when the signature is read?
Just an idea.
It seems the bloody bootloader dumps the files straight into RAM before it flashes them making the sd swap impossible or at least difficult. It seems the next step is jtag, but this will not be within the realm of the average user or even advanced user.
Freaking T-mobile and HTC, I really hate their signing crap. They should have at least made the bootloader not read freaking signature hashes.
Im still looking at the file itself to see if their can be any exploits. The bootloader is closed source so there is no way to know easily when the check is actually done, or the update process itself handled
afbcamaro said:
Freaking T-mobile and HTC, I really hate their signing crap. They should have at least made the bootloader not read freaking signature hashes.
Click to expand...
Click to collapse
Let's try to keep the heated opinions to a minimum. Google has already clearly stated that locked root is working as intended for the G1 as per HTC and T-Mo's specifications. This forum is for discussing active development issues, not debating the merits of Android implementation on Dream.
My friend trust me I AM actively working towards development on this device. I don't however need a father lecture on it (especially on a silly comment). I understand T-mobiles and Googles position and respect it. I understand how you feel and it would be well warranted if you were talking with a newbie that does nothing towards xda-developers goals, i however Im not.
If I decide to vent lightly then that is my prerogative, i am not debating anything here simply a frustrated rant since ive been working all day of and on, on this.
----
Anyways..
Has anybody started to trace for jtags yet?
afbcamaro said:
Anyways..
Has anybody started to trace for jtags yet?
Click to expand...
Click to collapse
That's a little early don't you think? I don't want to solder my precious phone. It's all big corporations' fault.
Stupid T-Mobile.
LOL @ coolbho3000
Damn corporations
Thank you for taking things lightly and having fun!
I believe jashsu posted a diagram or pic showing the disassembled view of the device and possible points of attack. I don't think either of you meant any harm in your posts but text doesn't quite relay emotion properly. Great work by you both and please keep posting in these forums as I look forward to both of your contributions and appreciate what you've already done.
ashslay
Thank you for your understanding
Im looking at my phone right now disasembled. lets see what we can get
Thanks again
afbcamaro said:
It seems the bloody bootloader dumps the files straight into RAM before it flashes them making the sd swap impossible or at least difficult. It seems the next step is jtag, but this will not be within the realm of the average user or even advanced user.
Freaking T-mobile and HTC, I really hate their signing crap. They should have at least made the bootloader not read freaking signature hashes.
Im still looking at the file itself to see if their can be any exploits. The bootloader is closed source so there is no way to know easily when the check is actually done, or the update process itself handled
Click to expand...
Click to collapse
are you good at ARM assembly (or any other cpu assembly is fine, once you know one, you know all ) and do you have a good understanding of how overflow etc exploits works - if yes, PM me it would be nice to work together.
I want to do everything I can to develop for this phone. What I need from the people here is a stock flash able rom. I have made great progress on this phone but but idk how to build stock roms and at this point I'm not sure I have the mental capacity to learn it.
Sent from my MB865 using Tapatalk
So...you have made great progress doing what?
There is a Chinese ROM floating around, maybe you can use that.
I want to do everything I can to develop for this phone. What I need from the people here is a stock flash able rom. I have made great progress on this phone but but idk how to build stock roms and at this point I'm not sure I have the mental capacity to learn it.
Click to expand...
Click to collapse
LOL...
Without a stock ROM, we have been unable to develop much...
What have you developed, here?
Mostly the community is hacking the stock installed rom, and fixing what Motorola has purposefully broken, but with out a few more pieces and a working sbf, you are not going to get a "Stock" ROM.
If you really want to help out go jump into the bootloader unlock forum:
http://forum.xda-developers.com/showthread.php?t=1328714
jimbridgman said:
LOL...
Without a stock ROM, we have been unable to develop much...
What have you developed, here?
Mostly the community is hacking the stock installed rom, and fixing what Motorola has purposefully broken, but with out a few more pieces and a working sbf, you are not going to get a "Stock" ROM.
If you really want to help out go jump into the bootloader unlock forum:
http://forum.xda-developers.com/showthread.php?t=1328714
Click to expand...
Click to collapse
I use cheesecake 4 times a day every day. If I find something I compare it to what others have found.. What have I developed? Nothing more then a headache. Using the bionic safestrap I have been able to recover from 3 soft bricks. 2 of them using adb to push to the phone and 1 using the restore tool. But i had to remount /emmc to /sd-ext. But I think at this point I am done trying anything with this phone.
One more thing.. what can't we use all the stock files I've pulled from the phone to make a flash able zip?
lfaber06 said:
I use cheesecake 4 times a day every day. If I find something I compare it to what others have found.. What have I developed? Nothing more then a headache. Using the bionic safestrap I have been able to recover from 3 soft bricks. 2 of them using adb to push to the phone and 1 using the restore tool. But i had to remount /emmc to /sd-ext. But I think at this point I am done trying anything with this phone.
One more thing.. what can't we use all the stock files I've pulled from the phone to make a flash able zip?
Click to expand...
Click to collapse
Seems like you know a lot more than all of us who have been working diligently for the last 60 or so days with this phone.... Why don't you give it a try and see if you can create a flash-able zip.
You can't build a flash-able zip, because you can not zip or tar files on the filesystem that are in use, and the kernel has a ton of files open and locked. the backup software gets around this in a couple ways that we really can't do, and backups are useless to make flash-able zip from. That is why we need the sbf or fxz or source code to make a flash-able, zip or ROM.
That is why we have warned everyone over and over and over, about trying things we post, right now. The information is not to try out, it is sharing of the developers, and for those of us working on actually developing solutions for this phone. There have been so many bricks, because people are not listening.... I am actually thinking of trading my phone with a buddy to get out of this, because I am tired of hearing about all the bricking people are doing, and having to help save someone who did something to their phone that they did after we told them not to.
Unless You Know What You Are Doing Don't Try This At Home. Until we get the fxz or sbf files. I am getting tired of saying this...
P.S. doing work on the cheesecake thing does not make you a Developer. Hell I am not an Android Developer, I am a UNIX and Linux Hardware architect and UNIX and LINUX Kernel Developer, so I am am able to use all that, 20 years of experience on the Android kernel, and I have been hacking and working on phones a long time.
Now I know it is great to try things and learn, but while learning, it is best to try things we say are safe first, then once you are more comfortable with certain things, then try something daring, that you know how to do.
I am in no way trying to insult you, just realize that right now, with the little help we have on the experienced development side of things, it is real painful to get things moving forward when people don't listen, or do things they are not ready for and then keep asking for help when they killed their phone in the process.
jimbridgman said:
I am actually thinking of trading my phone with a buddy to get out of this, because I am tired of hearing about all the bricking people are doing, and having to help save someone who did something to their phone that they did after we told them not to.
Click to expand...
Click to collapse
Please don't leave us Jim. You are an incredible resource. I'm new to Android and have learned many valuable things from you.
Remember, you don't have to help every person that bricks their phone.
Jim if you try to leave we will find you! ;p
Sent from my MB865
mtnlion said:
Jim if you try to leave we will find you! ;p
Sent from my MB865
Click to expand...
Click to collapse
LOL... I am not going anywhere, I am just trying to make a point, that things like this killed the Atrix board, and I hope we don't repeat that.
We are here to help, and I wish that it would be realized that we are in "Research" mode right now, and are not to point of actually hacking, or have very many how to post yet for that reason.
You can't buy common sense but stupidity is free.
Sent from my MB865
jimbridgman said:
LOL... I am not going anywhere, I am just trying to make a point, that things like this killed the Atrix board, and I hope we don't repeat that.
We are here to help, and I wish that it would be realized that we are in "Research" mode right now, and are not to point of actually hacking, or have very many how to post yet for that reason.
Click to expand...
Click to collapse
WHEW.....You had me fixing to start looking at phone options!!! Honestly I'm to the point where I just read them and ignore them otherwise I say things I shouldn't LoL. But I will be the first to say this, IF THIS BOARD GETS AS BAD AS THE OG ATRIX DID, I WON'T HAVE A PROBLEM WALKING AWAY!
---------- Post added at 01:27 AM ---------- Previous post was at 01:01 AM ----------
mtnlion said:
You can't buy common sense but stupidity is free.
Sent from my MB865
Click to expand...
Click to collapse
You can't fix stupid either......
JRW 28 said:
WHEW.....You had me fixing to start looking at phone options!!! Honestly I'm to the point where I just read them and ignore them otherwise I say things I shouldn't LoL. But I will be the first to say this, IF THIS BOARD GETS AS BAD AS THE OG ATRIX DID, I WON'T HAVE A PROBLEM WALKING AWAY!
Click to expand...
Click to collapse
Part of the issue I think is that everyone, who is doing these things, is of the I need this now, no matter what, camp... I just came a phone that had this, so this phone should too... LOL.
Yeah if it comes to anywhere close to the OG Atrix board I am out so fast it is not funny.
The thing is that I am most of the time ignoring these posts, but when you 6 people all did something similar, or like the OP did 4 or five things that messed his phone up, because he/they were impatient, you kind of have to tell them, look if you don't like it, get another phone. Heck the OP tried to say he was helping the cause by doing these things, when it was said so many times don't try this....
jimbridgman said:
Part of the issue I think is that everyone, who is doing these things, is of the I need this now, no matter what, camp... I just came a phone that had this, so this phone should too... LOL.
Yeah if it comes to anywhere close to the OG Atrix board I am out so fast it is not funny.
The thing is that I am most of the time ignoring these posts, but when you 6 people all did something similar, or like the OP did 4 or five things that messed his phone up, because he/they were impatient, you kind of have to tell them, look if you don't like it, get another phone. Heck the OP tried to say he was helping the cause by doing these things, when it was said so many times don't try this....
Click to expand...
Click to collapse
The funny thing is the "OP" didn't do anything he was told not to due.. Instead he/I tried new approaches and have actually been able to recover from a few soft bricks at this point. We get places from trying new things not by talking down to those that try them. I'm trying to help as I own the phone too. I am not in any way "under-educated". I am a .Net developer and I am doing my best in my free time to help the community by opening up this phone to its full potential. Now, Am I impatient.... Hell Yes.. I want CM7 and ICS now. Will I get it now?.. No, but i'm trying to get the rest of you on your way. I cant believe you would try to push someone so willing away..
A better way to go about it would be to post your discoveries and share them to help others out instead of demanding things you need.
lfaber06 said:
What I need from the people here is a stock flash able rom.
Click to expand...
Click to collapse
We aren't pushing anyone away that is willing to help and we welcome everyone that is willing to hel. But when you experiment know that we might not be able to help you and we have no way back to stock. By experimenting we found root,the bionic's bootstrap and we will have to continue to experiment. Part of progress is by finding out what works and what doesn't.
We need to all work together and not against each other. But with that said if you look at the amount of recent posts with people experiencing problems and calling for help is because they didn't do any research before hand and now they are asking for help for something they could have very well prevented by patiently doing a little homework.
With the progress you have said to have made, start a new thread about it explaining the procedures you went about to recover from the soft bricks so others can benefit from them as well. I can promise you we are all very interested.
JRW 28 said:
A better way to go about it would be to post your discoveries and share them to help others out instead of demanding things you need.
We aren't pushing anyone away that is willing to help and we welcome everyone that is willing to hel. But when you experiment know that we might not be able to help you and we have no way back to stock. By experimenting we found root,the bionic's bootstrap and we will have to continue to experiment. Part of progress is by finding out what works and what doesn't.
We need to all work together and not against each other. But with that said if you look at the amount of recent posts with people experiencing problems and calling for help is because they didn't do any research before hand and now they are asking for help for something they could have very well prevented by patiently doing a little homework.
With the progress you have said to have made, start a new thread about it explaining the procedures you went about to recover from the soft bricks so others can benefit from them as well. I can promise you we are all very interested.
Click to expand...
Click to collapse
Thanks, and Very well said, I agree 100%
Mod Edit:
Thread close as it poses a high risk for our members plus if you are sure this will not work..then do not release publicly. Instead ask for volunteers and PM them the info.
Also, calling us this "OK THANKS GAY xda" won't help you neither.
Cheers,
M_T_M
Senior Moderator
PS: If you reopen...follow my suggestions, please.
OK WAIT
EVERYONE READY TO DOWNLOAD WAIT A SEC.
I don't know if this build will or won't work. It may brick your device and it may work. If you are a developer please check the .zip folder and possibly correct any errors. It should work, considering how closely similar jellybean and ICS are. The same problems existing in ICS should still exist here so brace yourself. There are probably even more problems as well. DEVELOPERS NEEDED FOR HELP. please be cautious and aware of the negative possibilities.
Wow I am definitely not going to be the first to test this. If this is JB working with everything that is working in CM9, I will gladly throw it on my device. Who's going to bite the bullet first?
With 3 posts I'm also hesitant.
Yeah i just switched forums though so im new to xda
allenk09 said:
Wow I am definitely not going to be the first to test this. If this is JB working with everything that is working in CM9, I will gladly throw it on my device. Who's going to bite the bullet first?
With 3 posts I'm also hesitant.
Click to expand...
Click to collapse
Trust me i would be hesitant too, this is not my first time building something but it is still sketchy.
I'll test it if someone can at least ensure that it doesn't cause the phone to explode LOL.
Has anyone been brave enough to try this yet?
ken314stl said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
This is what I'm waiting for. If everything in ICS works from this and doesn't just brick my phone from the start, I'd gladly throw it on my phone.
I would hope a DEV would look at this and see if they think it's safe.Without a known DEV confirming the files will write correctly on the phone I wouldn't touch this......no offence.
Yeah UMMM...
Ok so i tried my own build on my triumph after backing up and turns out it didn't boot the rom so back to drawing boards... I didn't brick by the way so it's a pretty harmless fail at that.
It's umm well
Rola Addict said:
I would hope a DEV would look at this and see if they think it's safe.Without a known DEV confirming the files will write correctly on the phone I wouldn't touch this......no offence.
Click to expand...
Click to collapse
Yeah i hear ya... it is useless but safe as long as you have a backup... but don't bother trying at the time because it is again useless if it don't boot.
I haven't found the answer, and I was actually just curious as to what the hurdles are switching the bootloader in the rom is?
Being that I am on the JB BL, I am stuck with mainly two roms, Clean and Hydro. Both great roms, but was just curious from a dev standpoint, since we have both the ICS and JB bootloaders floating around out there, what hurdles are in place keeping a JB BL version of AOSP being made.
Thanks!
Mario
+1 I would like to know also. I keep seeing don't do it you will brick but can't find any information about what happened or when. Yes I have searched! I may not be able to recover from a problem that you just breeze through as we are all different. The subject deserves further study.
I can place Asus ICS update on my sdcard and get an offer to downgrade just as I got offers to upgrade.
Maybe someone can provide links or definite info about this situation.
there are some devs trying to get this working, but it seems to be very hard to get it running
mikaole said:
there are some devs trying to get this working, but it seems to be very hard to get it running
Click to expand...
Click to collapse
Maybe someone will start a thread to collect and share info about this problem.
tobdaryl said:
Maybe someone will start a thread to collect and share info about this problem.
Click to expand...
Click to collapse
No, the devs should work on this problem and trying to fix it not discuss why its not running.
As far as I know it has something to do with the new Kernel.
mikaole said:
No, the devs should work on this problem and trying to fix it not discuss why its not running.
As far as I know it has something to do with the new Kernel.
Click to expand...
Click to collapse
I was speaking of the devs starting and maintaining the thread.
I have seen one post here (FT300) asking for testers NVFlash but it is common in other threads.
The more heads involved the better the chances of conquering the problem.
Take the nook tablet!
Bauwks broke open the locked bootloader problem, you never see him post but he is there and knows his stuff.
AdamOutler seldom posts but he broke booting from the sdcard.
Numerous threads were provided a key piece of the puzzle by people who seldom post and are not listed here as developers.
These things have a better chance of coming to pass with more people involved and that is the reason for a sharing thread.
Obviously the thread has to be highly regulated as to what can and can't be posted for it to be effective.
There are good devs in this forum also and I'm sure they are working on the problem and I take nothing away from them or their contributions, but maybe there are people in the wings who could also help (not me).
I will be a tester as needed but don't have current knowledge base to work with. Like others here I am trying to learn by studying and following examples of others.:good:
mikaole said:
No, the devs should work on this problem and trying to fix it not discuss why its not running.
As far as I know it has something to do with the new Kernel.
Click to expand...
Click to collapse
I can see both +'s and -'s to this. Myself, I have both Engineering and Computer Science degrees and quite an extensive amount of programming experience, but I have never worked on the Android platform. Any and all information pertaining to the reasons or methodologies behind why something isn't working is all food for thought for someone like me and might be a trigger to motivate a breakthrough. Being in the dark in most cases doesn't move anything forward, and I think there is an old saying that really applies here... "Why recreate the wheel."
I know a lot of programmers think "Do it yourself and learn", but at the same time, we are all trying to work to the same goal, getting the best user experience we can. With that said, if every single person had to start off at point 0, it would take an infinitely longer amount of time to get to where we could be. If we all shared ideas, and in some simple form or another, had a collection of proofs that have worked, then it would allow anyone with minimal android programming experience a way to start somewhere beyond point 0, and get up and helping as quickly as possible.
For those who simply want to sit back and complain about something not working but have no interest nor will to contribute, this may be the issue we are experiencing with programmers who just have no interest in hearing people whine and fill up their threads.
Just my 2c.
Mario
Anyone have any links to people who actually bricked trying to go back to JB from ICS? I have searched and searched without any positive results. I only get don't do it, it will brick your device.
Hey all, I came from Samsung Skyrocket- just switched to HTC One X ... and I immediately looked for the JB 4.1.1. I downloaded and installed it. I'm not new to rooting, but did not take the time to read up on the version. The same day I upgraded I quickly found out that it was a big mistake. I was just wondering is there anyone out there working on a root for AT&T 3.18. I read a lot of posts and some speculate there are people somewhere but does anyone know for certain. I love all you Devs on XDA and your dedication. Thanks for reading
I'm sure someone is working on it. There just isn't a thinkthank thread. You should go make one!
ggsnyder0318 said:
Hey all, I came from Samsung Skyrocket- just switched to HTC One X ... and I immediately looked for the JB 4.1.1. I downloaded and installed it. I'm not new to rooting, but did not take the time to read up on the version. The same day I upgraded I quickly found out that it was a big mistake. I was just wondering is there anyone out there working on a root for AT&T 3.18. I read a lot of posts and some speculate there are people somewhere but does anyone know for certain. I love all you Devs on XDA and your dedication. Thanks for reading
Click to expand...
Click to collapse
Well, being that the official JB was released just a few days ago, I doubt it. Just like when a brand new iOS comes to an apple device, it takes time to find the exploits and stuff. If you came from the skyrocket, I would imagine, you would have checked XDA first, before looking into any official sites. That's what I do. Just in case I don't lose my root. When it comes to rooting, you HAVE to take the time to read. Especially with the HTC, it's a multi-step process. With the bootloader unlocking, geting SuperCID, rooting, getting your adb/fastboot working. Just have to be patient. But it is all worth it. I am sure many of the other HTC users in this forum would agree.
Herc08 said:
Well, being that the official JB was released just a few days ago, I doubt it. Just like when a brand new iOS comes to an apple device, it takes time to find the exploits and stuff.
Click to expand...
Click to collapse
3.18 started rolling out nearly a month ago (approx. March 7). And the OP is asking whether anyone is working on it, not whether an exploit has already been found. So the only way this would be answered conclusively, is if a dev (or devs) responded positively, that they are indeed actively working on it.
redpoint73 said:
3.18 started rolling out nearly a month ago (approx. March 7). And the OP is asking whether anyone is working on it, not whether an exploit has already been found. So the only way this would be answered conclusively, is if a dev (or devs) responded positively, that they are indeed actively working on it.
Click to expand...
Click to collapse
Thanks for the correction. Mis-read it using the app. And it has been that long? It felt like only a few days about the JB update. I would imagine, some devs may be working on it, but as you said, no one knows for sure until a dev responds.
Herc08 said:
Thanks for the correction. Mis-read it using the app. And it has been that long? It felt like only a few days about the JB update.
Click to expand...
Click to collapse
Yup, its been at least that long. This thread was posted on March 7, but the first reports of it rolling out starting getting posted on March 6, if I remember correctly.
The RUU was posted later on, maybe 2 weeks ago, or a little less.
redpoint73 said:
Yup, its been at least that long. This thread was posted on March 7, but the first reports of it rolling out starting getting posted on March 6, if I remember correctly.
The RUU was posted later on, maybe 2 weeks ago, or a little less.
Click to expand...
Click to collapse
Ah, then that is probably what I am referring to. Anywho, I would imagine a dev would post here first (the forum, not this thread), as these forums are pretty darn popular. But, it never hurts to Google.
Thank for the information fellas... I should have been a little more patient and a little less gung-ho. I was really shooting for someone to say..."I'm working on that right now" but that's ok. I'll just have to wait like the rest of the hundreds if not thousands that were like me. This update is a little jumpy... meaning it freezes up from time to time and reboots every now and then. Not all that smooth because of the bloatware I imagine...Thanks again for the reply's
ggsnyder0318 said:
I was really shooting for someone to say..."I'm working on that right now" but that's ok.
Click to expand...
Click to collapse
You generally almost never see those kinds of posts unless the dev has at least an alpha working or needs testers. The reason being, obviously, is because the moment anyone gets identified as working on the exploit, they get bombarded with nonstop "Are we there yet" posts and PMs.
iElvis said:
You generally almost never see those kinds of posts unless the dev has at least an alpha working or needs testers. The reason being, obviously, is because the moment anyone gets identified as working on the exploit, they get bombarded with nonstop "Are we there yet" posts and PMs.
Click to expand...
Click to collapse
Very true. And I'm guessing they probably don't want to get hopes up about something that might not even happen.
Devs often don't say anything unless they think they have it. Some of the exploits for our device have come practically out of nowhere. I remember the original bootloader unlock method (CID spoof), the dev just came on here and posted the method, and was like "sh1t, I didn't even know there was a bounty, thanks for the money!" lol
iElvis said:
You generally almost never see those kinds of posts unless the dev has at least an alpha working or needs testers. The reason being, obviously, is because the moment anyone gets identified as working on the exploit, they get bombarded with nonstop "Are we there yet" posts and PMs.
Click to expand...
Click to collapse
Yeah that's understandable, you are correct. I remember when I rooted my skyrocket people were always after the devs...time? How far along messages would popup everywhere. As you can see I've been a member since I got my skyrocket and have never posted once. I always found everything by reading everything. I got use to the speed of my Skyrocket, now I have this HOX as it is referred to here. With the stock it's pretty close to the speed of the skyrocket. But, I know it can be a lot faster with the root and less bloatware. Thanks again guys for the reply's
redpoint73 said:
Very true. And I'm guessing they probably don't want to get hopes up about something that might not even happen.
Devs often don't say anything unless they think they have it. Some of the exploits for our device have come practically out of nowhere. I remember the original bootloader unlock method (CID spoof), the dev just came on here and posted the method, and was like "sh1t, I didn't even know there was a bounty, thanks for the money!" lol
Click to expand...
Click to collapse
But it will happen.....sometime in the next few months I hope. AT&T is always making things difficult 50% their fault,50% mine I guess. Thanks