Well, i just found out about two things. People including our own designgears have the stock SBF file http://forum.xda-developers.com/showthread.php?p=11952597#post11952597 but seems like they won't give it to us because they think someone will lose their job.
While we don't want anyone to lose their jobs, i don't think they can trace it back so i really don't understand dg's reasoning in this.
The second thing is that since dg is asking how to flash this thing, i'm guessing he has his atrix (or another atrix) back, since his first motivation in returning it was the lack of the sbf in order to unbrick his device.
DG how about you ask your source for his opinion? Does he really think he can get traced to you? If not, i would guess it would be ok with him to leak this to us.
It's only right to HONOR the source's request. You don't like it? Go find a Motorola contact.
If you think that companies like Moto cant digitally sign software. Oh wait whats that boot loader issue again?
franciscojavierleon said:
Well, i just found out about two things. People including our own designgears have the stock SBF file http://forum.xda-developers.com/showthread.php?p=11952597#post11952597 but seems like they won't give it to us because they think someone will lose their job.
While we don't want anyone to lose their jobs, i don't think they can trace it back so i really don't understand dg's reasoning in this.
The second thing is that since dg is asking how to flash this thing, i'm guessing he has his atrix (or another atrix) back, since his first motivation in returning it was the lack of the sbf in order to unbrick his device.
DG how about you ask your source for his opinion? Does he really think he can get traced to you? If not, i would guess it would be ok with him to leak this to us.
Click to expand...
Click to collapse
Its clearly stated in the thread, the source does not want the file given out. Mods can we please close this thread before it starts a war over a file thats not being released.
I understand the source wants it kept on the DL... But why even bother giving it out at that point?
That's like someone saying here's a free lambo, but the catch is you can't take it out of the garage so I don't get in trouble.
Sent from my MB860 using Tapatalk
Clienterror said:
I understand the source wants it kept on the DL... But why even bother giving it out at that point?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because the Atrix isn't accepting the file through RSD, xoom uses a similar chipset. So hes asking the Xoom devs for help making RSD work. Hes not flaunting hey I got the sbf and you don't.
YellowGTO said:
Because the Atrix isn't accepting the file through RSD, xoom uses a similar chipset. So hes asking the Xoom devs for help making RSD work. Hes not flaunting hey I got the smf and you don't.
Click to expand...
Click to collapse
Oh no I understand DG isn't being an ass or anything, I was just curious.
Sent from my MB860 using Tapatalk
Clienterror said:
Oh no I understand DG isn't being an ass or anything, I was just curious.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I can promise you, if anything comes out of this. DG will give out all the info he can.
well of course i don't mean to start a war but yes i am curious i thought any sbf file would work with rsd lite and when i started the thread i didn't see an indication that the file didn't work right now. Rather, i was happy because it looks like dg got an atrix back (he even said in another topic that he tested debian on the atrix)
I would understand if the file hasn't been leaked because it didn't work, although dg isn't the only dev and maybe the other guys can make something about it, but the file can't get traced back to the original insider.
Probably just need the right version of RSD lite
sorry i am not a dev i am just curious on dev, what is the significance of a SBF file? is that equalivent of an OS of a pc? where we can wipe the pc clean and load os at will?
it lets you reload your stock os if the phone gets bricked so hard and adb cannot be used. it's basically the #1 reason of why dg returned his phone, because he had the risk to brick his phone and couldn't go back to stock. it seems that he has his phone back which is very nice for us.
franciscojavierleon said:
it lets you reload your stock os if the phone gets bricked so hard and adb cannot be used. it's basically the #1 reason of why dg returned his phone, because he had the risk to brick his phone and couldn't go back to stock. it seems that he has his phone back which is very nice for us.
Click to expand...
Click to collapse
If you have the SBF and software to flash it, motorola phones become stupidly hard to actually brick. It saved me a couple times on my old backflip
The sbf will, from what I understand, give devs a better idea on how the bootloader works. Hopefully this takes them.one step closer to unlocking it.
Sent from my MB860 using XDA App
If it's true that DG has his Atrix back, then woot! At least he'll be able to dev much more safely, and won't go through 9999 devices.
Clienterror said:
I understand the source wants it kept on the DL... But why even bother giving it out at that point?
Click to expand...
Click to collapse
As DG is valued member of the developer community I imagine that someone more or less attempted to bribe him with it to keep his atrix and continue developing. This in no way is meant as a slight against his source or DG.
Man_of_Leisure said:
As DG is valued member of the developer community I imagine that someone more or less attempted to bribe him with it to keep his atrix and continue developing. This in no way is meant as a slight against his source or DG.
Click to expand...
Click to collapse
Yea, I could see someone giving him a bribe especially if they had a captivate before this (been running perception for a llllooonnggg time now). Although I respect the leeks wishes, I do think he/ she is maybe a tad paranoid. I'm sure enough people have access to this at moto that they couldn't trace it back with any amount of certainty.
Sent from my MB860 using Tapatalk
franciscojavierleon said:
well of course i don't mean to start a war but yes i am curious i thought any sbf file would work with rsd lite and when i started the thread i didn't see an indication that the file didn't work right now. Rather, i was happy because it looks like dg got an atrix back (he even said in another topic that he tested debian on the atrix)
I would understand if the file hasn't been leaked because it didn't work, although dg isn't the only dev and maybe the other guys can make something about it, but the file can't get traced back to the original insider.
Click to expand...
Click to collapse
franciscojavierleon said:
Well, i just found out about two things. People including our own designgears have the stock SBF file http://forum.xda-developers.com/showthread.php?p=11952597#post11952597 but seems like they won't give it to us because they think someone will lose their job.
While we don't want anyone to lose their jobs, i don't think they can trace it back so i really don't understand dg's reasoning in this.
The second thing is that since dg is asking how to flash this thing, i'm guessing he has his atrix (or another atrix) back, since his first motivation in returning it was the lack of the sbf in order to unbrick his device.
DG how about you ask your source for his opinion? Does he really think he can get traced to you? If not, i would guess it would be ok with him to leak this to us.
Click to expand...
Click to collapse
Clienterror said:
Yea, I could see someone giving him a bribe especially if they had a captivate before this (been running perception for a llllooonnggg time now). Although I respect the leeks wishes, I do think he/ she is maybe a tad paranoid. I'm sure enough people have access to this at moto that they couldn't trace it back with any amount of certainty.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Wow, you guys seem to be pretty certain about something you know not much about then again it is not your job that is on the line here. I find it even more interesting that you think because many people have access to it that is difficult to trace. I can tell you from experience depending on the deployment method, you can trace this stuff to a particular machine and user. I personally do not know what motorola is doing but I am glad he is respecting the source wishes.
Back in WM days Microsoft was known for doing this stuff. Many time when you got an internal leaked build, you had to go through it to ensure there were no finger prints. You literaly had to scrub it to ensure traces were gone.
Thread Closed, any sub-sequential threads regarding this will also be closed in respect for DG and his source. Do not press this issue.
Related
This is the word on the 4G forum here on XDA! Hope this soon leads to the incredible root but for now ill just be jealous.
Link: http://www.engadget.com/2010/05/24/htc-evo-4g-rooted-in-record-time-video/
P.S. Thanks to anyone working on incredible root.
i was equally as upset hope this helps us out
nevermind if you go to the source: http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/
they state "At this time, we believe that this specific exploit cannot be applied to Incredible."
Darn that really sucks
mejdam said:
i was equally as upset hope this helps us out
nevermind if you go to the source: http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/
they state "At this time, we believe that this specific exploit cannot be applied to Incredible."
Click to expand...
Click to collapse
Boo!
When I read the news on engadget, I had the warm and fuzzies. Same android build. Same sense. CDMA radio. Rooted! What a downer!
How can we get an INC into these guys hands? I'd be willing to donate some cash if it helps.
Dont post this crap in the DEV thread, there are 3 other sectiosn for this on XDA
1wayjonny said:
Dont post this crap in the DEV thread, there are 3 other sectiosn for this on XDA
Click to expand...
Click to collapse
Lol not like it would hurt, that **** already full of spam and beggers haha
it was somthing in the bootloader that found that the incredible does not have. But rest assured that its bieng worked on and im sure we will have root.
nah, it wasn't the bootloader
looks to me like he flashed a leaked image based on where he starts the video and seeing how he doesnt show us the bootloader or anything involving recovery/fastboot. My guess is that since this was an evo prerelease is that someone at htc with the shipping rom weasled a su apk in there while also having the test keys to sign. I never see anyone talking on irc and i assume we are months away from root.
edit: after looking on the website it seems as if they have done deeper work than i assumed. I believe there may be similarities in what they did and what we need. He mentions that he used his linux background and knowldge of hacking bootloaders. maybe something is in store for us unlucky incredible users
nope it has been stated that it will not work for us. And it looks like my bootloader theroy is wrong..... mmmmm i wonder what it could be.
are you judging by this little footnote? "At this time, we believe that this specific exploit cannot be applied to Incredible." - taken from grack.com . If they did anything to the bootloader i would assume an exploit can be derrived from this method. we dont need to use their entire method. From what i hear their bootloader is a higher version than ours which should make it more difficult to crack. If they ever release how they did it Im sure we can find some hope to help us.
1wayjonny said:
Dont post this crap in the DEV thread, there are 3 other sectiosn for this on XDA
Click to expand...
Click to collapse
Knowledge is power and not sure what was up your rear when posting but any bit of information on semi similar phones never hurt anyone. Seeing how this isn't a post about an accessory app theme maybe could go into general but this is more of developmental news then general.
Well, I at least feel better knowing others are going through the same "pain" I am faced with. I'll donate my time and resources (I still don't have the Incredible thx to it being sold out everywhere... maybe I will try the Best Buy closest to me... although they kind of stink, they don't even carry any Apple computers while most ever other BB does) to get this fix0rz for the peeple!
Hero_Over said:
looks to me like he flashed a leaked image based on where he starts the video and seeing how he doesnt show us the bootloader or anything involving recovery/fastboot. My guess is that since this was an evo prerelease is that someone at htc with the shipping rom weasled a su apk in there while also having the test keys to sign. I never see anyone talking on irc and i assume we are months away from root.
users
Click to expand...
Click to collapse
Nothing to do with test keys, no leaked images. There is no way to modify it to the incredible.
lol, I knew it was going to be rooted before, but I had some hopes it could have been used to help with the root for the Incredible. Oh well, such is life. I'm sure there are some Verizon Android developers that are still working on this....All the give me root and where's the root and other I want root spamming is not going to help with anything other than the continuous spamming of this section.
I really hate this waiting for the Unlockers/Root for any phone as it's nothing but spamming.
Just be patient and it will come. Then it's time for you to show your gratification to the developers for their hardwork that I'm sure most do in their spare time and not as their source of income...
[Insert some more I want root spam after this message]
he is lying about the whole thing. i did not give it to people i liked...
i only gave it to people that developed for the epic and people that they trust weather i liked it or not.
I gave firon the leak of dj29 then whodaman & firon decided to leak it without my approval a week later... they have the power to leak froyo without me approving that .. it take time to test froyo.. i assure you that guy that leaked it is not a developer or a tester..
thanks the mods for closing the thread of the dk05 leak because flashing the leak is NOT SAFE!
i just don't want people bricking their phone and yes it has a signature. don't take word for it my source confirmed it..
the closed leak lasted for a week before it became out of control..
Good to know that bro!
Sent from my SPH-D700 using XDA App
noobnl said:
he is lying about the whole thing. i did not give it to people i liked...
i only gave it to people that developed for the epic and people that they trust weather i liked it or not.
I gave firon the leak of dj29 then whodaman & firon decided to leak it without my approval a week later... they have the power to leak froyo without me approving that .. it take time to test froyo.. i assure you that guy that leaked it is not a developer or a tester..
thanks the mods for closing the thread of the dk05 leak because flashing the leak is NOT SAFE!
i just don't want people bricking their phone and yes it has a signature. don't take word for it my source confirmed it..
the closed leak lasted for a week before it became out of control..
Click to expand...
Click to collapse
I agree it wasnt posted by many people who had it for a REASON as to prevent problems and people getting BRICKED or not flashing properly.
Sit back and think about how long the leak has been out do you all really think that if it was WORTHY of being let out to the masses it would have taken so long? No it would have been posted as a rom for mass consumption REALLY Fast....
BUYERS BEWARE
noobnl said:
the closed leak lasted for a week before it became out of control..
Click to expand...
Click to collapse
I think the epic forums are out of control. As someone stated, we should all be helping eachother.
I just see noob has done a lot of amazing work for the epic, people should be grateful & all they do talk garbage & complain. I should just get my evo back & leave all this behind.
rjmjr69 said:
I agree it wasnt posted by many people who had it for a REASON as to prevent problems and people getting BRICKED or not flashing properly.
Click to expand...
Click to collapse
That explains why the modem was not released. Now why wasn't the rom released?
I think the epic forums are out of control. As someone stated, we should all be helping eachother.
Click to expand...
Click to collapse
They absolutely are.
I tested DJ29 for about a week and found it was good enough for a release. DK05 bricked my modem, so I didn't consider it safe.
The ROM was -probably- okay to release, but the modem is not.
It was not held back for fame or any bull**** like that.
There are too many trolls on these forums who obviously don't understand the time and patience it takes to make things like this possible.
I appreciate all the hard work you've done noob, and firon.
I really wish I had the knowledge to participate, but my time will come
halfcourtshoes said:
I think the epic forums are out of control.
I should just get my evo back & leave all this behind.
Click to expand...
Click to collapse
You are dead right on this one. The Epic side of the house is unbelievably bad. Not only are things slow, at no fault to anyone here, but there is WAY too much bickering in these threads. I go to the threads concerning my EVO and love it. I come here and am continually caught off guard by the way folks are. Either way, I want my Epic to stay my main phone, so I keep coming back.
Any one know what the "phone,orange triangle and little computer" mean. I fear I bricked my phone. I can't even get into download mode now. WHen I press 1 and power up the charging battery comes on the screen. Thanks for trying to keep this from happening. This the first time I have bricked a phone in many years. Guess ut was bound to happen at some point.
Why not just release the rom + modem with a disclaimer that it may brick your phone and require an Odin flash? Also, the safety net Odin represents in itself, I think, nullifies any danger from bricking.
And another thing; don't send things to people over the internet and expect them to stay secret.
done12many2 said:
Either way, I want my Epic to stay my main phone, so I keep coming back.
Click to expand...
Click to collapse
Lol, that's my problem. I love my Epic, so I just skim through the bickering & hang around. No offense but a lot of it does seem about egos & fame, but I understand what goes into being a dev & it is nice to have recognition for your work. But at the same time it's not safe to release stuff not ready for the primetime because everyday average users looking for a better phone experience will just end up bricking their phones. & like I said, everything noob has put out has been quality work & I've never had a problem with any of it. just my two cents.
ptfdmedic said:
Any one know what the "phone,orange triangle and little computer" mean. I fear I bricked my phone. I can't even get into download mode now. WHen I press 1 and power up the charging battery comes on the screen. Thanks for trying to keep this from happening. This the first time I have bricked a phone in many years. Guess ut was bound to happen at some point.
Click to expand...
Click to collapse
Pull the battery and try again.
ptfdmedic said:
Any one know what the "phone,orange triangle and little computer" mean. I fear I bricked my phone. I can't even get into download mode now. WHen I press 1 and power up the charging battery comes on the screen. Thanks for trying to keep this from happening. This the first time I have bricked a phone in many years. Guess ut was bound to happen at some point.
Click to expand...
Click to collapse
Hm. What you're describing sounds like you have the phone plugged in while you're trying to enter Download mode, which isn't very effective. Try plugging it out first.
Anyway we can have you guys upload DK17 at least for us to flash or odin? I can wait for the final modem...jjst want an up to date rom.
vgambit said:
Why not just release the rom + modem with a disclaimer that it may brick your phone and require an Odin flash? Also, the safety net Odin represents in itself, I think, nullifies any danger from bricking.
And another thing; don't send things to people over the internet and expect them to stay secret.
Click to expand...
Click to collapse
Because despite all the warnings in the world people who should not touch things of this nature WILL and then a storm of accusations and mad people will hit the forums... What ever happened to being a MAN OF YOUR WORD? thats the beef
DONT SEND THINGS ON THE NET??? Guess you certainly would not be trust worthy
vgambit said:
Hm. What you're describing sounds like you have the phone plugged in while you're trying to enter Download mode, which isn't very effective. Try plugging it out first.
Click to expand...
Click to collapse
mattallica76 said:
Pull the battery and try again.
Click to expand...
Click to collapse
Thanks guys. I'm not sure what was happening but I finally got it to work. Back up and running. I pulled the battery walked away and tried again and it worked.
Defiantly waiting for the ok from the people in the "know" before trying this again. Thanks for trying to protect us from ourselves. LOL
rjmjr69 said:
Because despite all the warnings in the world people who should not touch things of this nature WILL and then a storm of accusations and mad people will hit the forums... What ever happened to being a MAN OF YOUR WORD? thats the beef
DONT SEND THINGS ON THE NET??? Guess you certainly would not be trust worthy
Click to expand...
Click to collapse
Very well put. I am ok waiting. I don't think it's some big conspiracy. I feel better knowing that the newer radios seem to fix the gps. Now we just need to make it safer to use. Until then I'll just pull up a chair, crack open a beer and roast some marshmallows courtesy of all the flames. Anyone care to join? lol
I'm not getting dragged into another fight on here, the **** with Hero was bad enough, but I will say a few things on this issue.
1. Odin gives a safety net, and it works well.
2. The modem is safe, so long as you're competent enough to flash it right. Thats not a shot at anyone who got a brick from it, but it works fine for me and many people who flashed it successfully.
3. This ROM is essentially **** anyway. I had one of the early leaks of it, and I went back to DJ29. The music player has issues, there are UI bugs in the launcher, the camera & flashlight APIs are broken for everything but the stock camera app, and there's still the lag issue on unlock. This is all straight off a wipe as well, so it isn't that.
4. Sometimes it isn't good to give everything to the public. I don't agree with keeping it in a secret little circle for devs, but sometimes things NEED to be tested and cleaned up before they can be given to the public.
5. As for the whole thing that it was a lie that there are tags from the source in the ROM, I'm not aware of everything, but I have found a few myself. All pointing to one Korean name, who built the ROM originally, and it's the same name as on the DJ29 leaks. I'm sure you're smart enough to find it. Does that mean he leaked it? No, but it is still a liability for him and his career because it was built on his machine & probably by him as well. Some people on here are just selfish and don't realize that their craving for the latest and greatest could cost someone their job.
There. I'm done.
This is exactly why the Epic community is not progessing as fast as the Evo community, the leaks don't get put into the right hands. And progress haults, I understand your concern about bricks but maybe you should post a thread with a request for people to Close beta test and perhaps create an application that can be filled out and submitted via PM to the person in control of the leak, this could help the rom fall into the correct hands that can test and verify a rom.
Thank you.
Well when you released dj29 he lost his job then
It sounds really complicated and risky, and some of the posts I've read seem to indicate that wifi tether might not work after installing froyo. I can live without flash on my phone, but wifi tether is my only at home source of internt and there's no way I'm paying Sprint's greedy asses thirty bucks a month for something android's capable of doing for free.
Sent from my SPH-D700 using XDA App
Yorebuttrules said:
It sounds really complicated and risky, and some of the posts I've read seem to indicate that wifi tether might not work after installing froyo. I can live without flash on my phone, but wifi tether is my only at home source of internt and there's no way I'm paying Sprint's greedy asses thirty bucks a month for something android's capable of doing for free.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Its really not that difficult. Just backup your phone (boot into clockwork>backup+restore>backup), flash the new PIT+modem through Odin, and install quantumROM (or any other rom) from zip on SD through clockwork. No issues for me here. ^,^
Plus, you can always restore if something goes wrong or flash to stock and restore the data from your backup.
I'm pretty new to android and I was kinda worried at first as well, but seriously its not hard at all. I cringed when I first rooted my evo and now on to my epic and I'm not scared at all now. Rooting my phone was the best thing I've done to it and I don't regret trying. I know there are "risks" involved but as long as you read and follow the instructions posted in literally every post then you'll be fine. And flashing to froyo was way easier than I thought. I was gonna stay on 2.1 till the official 2.2 release came out but I can't leave stuff alone. And it was super easy! Odin worked exactly as described and flashing roms is a simple process. You just have to read and read again. So have fun and happy modding.
Sent from my SPH-D700 using XDA App
Yorebuttrules said:
It sounds really complicated and risky, and some of the posts I've read seem to indicate that wifi tether might not work after installing froyo. I can live without flash on my phone, but wifi tether is my only at home source of internt and there's no way I'm paying Sprint's greedy asses thirty bucks a month for something android's capable of doing for free.
Click to expand...
Click to collapse
Nothing risky about it just need the capability of following simple step by step directions (seeming to become a rarity today). Most the people on here should have crapped their pants in the early days of android flashing SPLs to load roms that would have a high probability of bricking the phone requiring a JTAG repair to get working again.
konaman said:
I'm pretty new to android and I was kinda worried at first as well, but seriously its not hard at all. I cringed when I first rooted my evo and now on to my epic and I'm not scared at all now. Rooting my phone was the best thing I've done to it and I don't regret trying. I know there are "risks" involved but as long as you read and follow the instructions posted in literally every post then you'll be fine. And flashing to froyo was way easier than I thought. I was gonna stay on 2.1 till the official 2.2 release came out but I can't leave stuff alone. And it was super easy! Odin worked exactly as described and flashing roms is a simple process. You just have to read and read again. So have fun and happy modding.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm begging you to please not encourage him. I promise this will be a much happier place without him :~)
To the OP, you are correct in saying this is risky business. Enjoy your Epic in its stock form as it is already an excellent phone. Wait till your official upgrade comes out very soon and just enjoy!
Sent from my SPH-D700 using XDA App
drago009 said:
You are a ***** and we dont care!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Though the OP is not ready for the world we have indulged in, there is no reason to use that language and offend others. I'm sure we all have doubted in the past to do something.
At his pace and time he will join us and step up to the challenge. PLEASE refrain your language!
- SFC Megabite
"Perfection is my life goal, excellence will be tolerated, WHOA!"
Thread moved to General.
Also, I cleaned up the thread. If you have nothing useful to add to the OP's message, don't reply.
egzthunder1 said:
Thread moved to General.
Also, I cleaned up the thread. If you have nothing useful to add to the OP's request, don't reply.
Click to expand...
Click to collapse
request? I don't see a request from the OP, just him stating that he thinks it is risky to flash 2.2.1 and we were telling him why we didn't think it was risky. Is the forum getting so controlling that an opinion related directly to an OP's post is labeled invalid??? My post didn't call him any names or make fun of him, just stated that its a developers forum, not for people who can't live without problems.
This place gets crazier every day.
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
From what I've heard, the "key" so to speak, in burned into the CPU itself. Its my understanding the only true way to unlock the BL is with Moto's keys, which we wont be getting any time soon. Whatever your plan is, I wish you the best. But we've had roughly 20+ of these threads come and go on here with everyone thinking they can crack it, and nothing ever pans out. Its a matter of the right people with knowledge and the right equipment to do the job, but those things have just not come together yet.
Once again, I wish you the best!
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
MrKazman said:
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
Click to expand...
Click to collapse
MrKaz,
+1 to your idea. Hey, who knows what will work.. with all that is going on, I wouldn't be surprised if the one idea that works..is some off the wall idea such as a chip flaw... Go for it man... I say take the idea and run with it.
best of luck
Your idea is one that I have been working on. All that needs to happened is find a way to dump the info to a computer and resign or make a dummy key to patch and inject back in.. unfortunately I have yet been able to inject anything because once dumped and cleared it doesn't regonize still active.. blah DX
MrKazman said:
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
Click to expand...
Click to collapse
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
gpaulu said:
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Click to expand...
Click to collapse
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
http://www.and-developers.com/boot:boot_chain
You may want to take a look at this. I think it's about the milestone, but it is similar to if not the same as the droid x
tekahuna said:
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
Click to expand...
Click to collapse
I love your honesty!
Sent from my DROIDX using Tapatalk
Syco54645 said:
I love your honesty!
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Beesley doesn't... LOL
http://twitter.com/TheRealBeesley/status/30036655129763840#
@LexusBrian400
build.prop edits vs. Droid X Froyo Overclocking & AP Mode Tethering
Maybe I should put up a donation link, huh? LOL
P.S. I can't help but think your username is a reference to B-Legit's verse on Sideways... Little known fact: The Ambassador himself gave me the handle FreeWELL.
http://www.youtube.com/watch?v=3YXGvsbSjLw
Didn't notice that you mentioned jared. I rather like him. Let's just leave it at that...
Sent from my DROIDX using Tapatalk
Update
I'm getting more and more familiar with this situation every day. I'm also starting to realize what a big problem this is. I've spent a good deal of time pouring over the work they're doing with the Milestone which is kind of the same thing but isn't. Nonetheless I applaud the work they do and donate my CPU to Androinc. After that I've been reading and collecting every Block Diagram, Datasheet, Whitepaper, and post about mbmloader, m-shield, omap, and the like. Yeah, its complicated alright. The fact is though that its just a lock. A lock is a system based on deterrent not prevention. Systems built for mass production have accepted flaws to keep costs down. Chips aren't perfect, code is not perfect. Use the weakness against the system and the lock is picked. The more complex the system the more chances to get in....
Eh, I digress...
Anyone wanting to learn more about this let me know.
The search continues....
Kaz
Motorola, I paid for the Hardware. I can handle my own software and security...
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Ubermicro13 said:
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Click to expand...
Click to collapse
Well ill drive to help out...as long as someone has some snaps on the petro!
Sent from my DROIDX using XDA App
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
As much as I want to believe that this can be done, its close to impossible and honestly not worth the persons time to try it, they did a good, well great, job of locking this thing down but ill say that liberty actually makes this feel like a new phone.
Sent from my DROIDX using XDA App
IWHBYD said:
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
Click to expand...
Click to collapse
Just take one for the team there buddy.... lol
Sent from my DROIDX using XDA App
what does the CEO of motorola look like?
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
openbox9 said:
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
Click to expand...
Click to collapse
not it *noses*
to fix problem with modem(radio) issue relating to CDMA RADIO, signal bars, gps, voice audio, multimedia, 2g and 3g firmware and some power management issues with s5pc110( hummingbird) and modem (radio hardware)
if you have a odin flashable tar, PM me..
noobnl ( cyanogenmod epic team)
Newer than dk28?
Sent from my SPH-D700 using XDA App
Is there a modem newer than dk28 that anyone has? I thougt the source for the leaks didn't want to risk it again.
Sent from my SPH-D700 using XDA App
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
riceknight said:
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
Click to expand...
Click to collapse
10-char!!!
n00b,
I love your work. You're an amazing developer, you're a nice guy, and you contribute a lot to these forums. Everyone likes you and you're somewhat of a legend around here.
However, to have someone to leak you unpublished work from a huge corporation is incredibly risky. The NDA's that people sign are pretty iron clad that if they leak information, they won't be able to have a job anymore. Their trust is completely lost if they get caught and they'll have trouble finding work elsewhere. They might even face jail time and fees. That's how serious this stuff is.
I'm as anxious as the next guy in order to get the new modem, froyo, and other mods. However, if you're REALLY interested in developing... why not join the machine? AKA try to get a job with Sprint, Samsung, Motorola, HTC, etc.? You can use all of us for references! Seriously, why not turn your hobby into real money with a career with them? To program for Android in the Bay Area would net you atleast over $100K a year!
DangerZone1223 said:
I'm as anxious as the next guy in order to get the new modem, froyo, and other mods. However, if you're REALLY interested in developing... why not join the machine? AKA try to get a job with Sprint, Samsung, Motorola, HTC, etc.? You can use all of us for references! Seriously, why not turn your hobby into real money with a career with them? To program for Android in the Bay Area would net you atleast over $100K a year!
Click to expand...
Click to collapse
As someone who works for a large corporation, I can tell you that the companies in question probably have people just as good as n00b employed with them (not to take anything away from n00b since his work around here has been awesome). The problem in these large companies isn't talent (IMO) as much as it is the RED TAPE. Some of the red tape is needed, but probably like 5% of it.
riceknight said:
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
Click to expand...
Click to collapse
Last time noobnl tried to keep a lid on things, it kinda blew up in his face. There was a whole lot of drama about it. I do hope someone can help him out on this, though. It would be nice to see some more progress from our community. We've kind of stalled out while waiting on Samsung and Sprint.
riceknight said:
Thats why a source should PM a trustworthy Dev like Noobnl instead of just releasing it outright and getting backlash. I'm certain that Noob will insure anonymity and find a way to best put it to use.
Click to expand...
Click to collapse
I would think that any reliable source that cared would have given it to him a long time ago. If they are willing to leak a new modem then why not just leak the kernel sources while they're at it..
Sent from my SPH-D700 using XDA App
DK28 was not leaked to devs. Our devs got their hands on it because someone with hardware version .4 got an OTA and worked with them to dump it to a useful format. The update.zip was also temporarily available on Google's servers.
leatherneck6017 said:
DK28 was not leaked to devs. Our devs got their hands on it because someone with hardware version .4 got an OTA and worked with them to dump it to a useful format. The update.zip was also temporarily available on Google's servers.
Click to expand...
Click to collapse
it was a tar leak.. and a ota leak too
Noob talk talk to me! I know you are a sly dog what's going on? You always have the inside track so I take it this is a hint. I hope ll is well.
Sent from my SPH-D700 using Tapatalk
You know, you could probably just edit the CDMA parameters and be done with it... I know that my radio problem is that it picks up towers that are too weak into the "active set" and that it is a recent common Samsung problem on several models. They tweak it so that it will utilize too low a signal level in order to decrease the number of "out of service" states as well as decreasing its apparent time to ready.
I just don't know how to do this on the Epic, and am waiting to see if the official 2.2 update fixes this. I know it started with the DI18 update, and persists with DK28, and disappears when flashed back to DI07. My brother's Epic which for some reason has never updated from DG17 (and he doesn't care to do it manually) and does not display this behavior.
On the A900 years ago it was easy with QPST. Actually, come to think of it, my Sanyo 8500 did it too, and I fixed that one as well.
... bump....
Do u know if the newest modem was leaked and know who would get it? Sorry i cant help i was just asking if it was leaked somewhere?
davidrules7778 said:
Do u know if the newest modem was leaked and know who would get it? Sorry i cant help i was just asking if it was leaked somewhere?
Click to expand...
Click to collapse
Obviously not or this this thread wouldn't be here.
Poryhack said:
Obviously not or this this thread wouldn't be here.
Click to expand...
Click to collapse
well he must kno something we dont know, maybe somepne got a leak and thats y hes asking?
Sources would be 10000x harder to leak than a phones zimage, modem, and /data/. Soure is held in a source control mechanism (git) internally usually, and unless the leaker is a dev, they probably don't know what to get. And if the leaker is a dev, they probably only have access to their piece of the project. Places I've worked in the past have been so anal bout what parts of source I see/have access to that I couldn't even tell what other features other devs were working on.
Sent from my SPH-D700 using XDA App
There's a January leak in somebody's hands, he knows it. I do too.
He wasn't asking for a source. He asked for the new modem which is out
Sent from my SPH-D700 using Tapatalk