Database Users

Evo 4g rooted before Incredible?

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]

The elusive locked bootloader

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*

I Don't Believe On The Motorola Promise About That Unlockable Bootloader

hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...

Its unlocked for ever
Sent from my MB860 using Tapatalk

Andrew149 said:
Its unlocked for ever
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
you mean locked!? right? lol

Er, dude you really need to read a little bit more on Development forum D:...
Its already unlocked!
Cheers

tan G said:
hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...
Click to expand...
Click to collapse
Moto said they are going to do it. They already dont it on the leaked future builds, not to mention the one Kenn is running which is an ATT GB. Not to mention this is the same way the did it on the Xoom. Theres nothing to worry about, its unlocked 4 ever.

lol - it's already done.

knigitz said:
lol - it's already done.
Click to expand...
Click to collapse
His point is he thinks its going to be removed from the final build. He states he is already unlocked himself.

LOL Someone needs to read through the forums. Bootloader is unlocked already.

Agree with Jay ... some one needs to read the OP ^_^ LOL
I, maybe just optimistically, think they will. The backlash, *****ing, low sales, the fact they said they would, and the fact that we have it already all points, IMO, to them releasing it. Motorola exec. - "Well the kids already have it so lets release it and make us look good." If they are on our side, at least give us what we want, they sell more. DROID - ground breaking - unlockable - sold like hot cakes. ATRIX - ground breaking - locked - not so much
posted via Atrix in lapdock

Does it really matter? For those that actually want an unlocked bootloader, they can get it in the dev forum. For the average user who will still get the OTA update, they probably didn't care about the bootloader to begin with.

Yaotl said:
Does it really matter? For those that actually want an unlocked bootloader, they can get it in the dev forum. For the average user who will still get the OTA update, they probably didn't care about the bootloader to begin with.
Click to expand...
Click to collapse
yup and average users will not probably bother coming to xda.
@OP
you are 2-3 months late regarding the creation of this topic.

madnav said:
yup and average users will not probably bother coming to xda.
Click to expand...
Click to collapse
I'm guess i'm still an 'average user' when it comes to android, but this is where I came to become a superuser (pun intended). I don't think i'm ready to mess with the HK build yet, but I definitely plan to flash a few ROMs when the official unlocked GB update comes through. And if it gets yanked before the final release, hopefully i'll know enough by then to use kenneth's version, or if worst comes to worst, the HK build.

zoso28 said:
I'm guess i'm still an 'average user' when it comes to android, but this is where I came to become a superuser (pun intended). I don't think i'm ready to mess with the HK build yet, but I definitely plan to flash a few ROMs when the official unlocked GB update comes through. And if it gets yanked before the final release, hopefully i'll know enough by then to use kenneth's version, or if worst comes to worst, the HK build.
Click to expand...
Click to collapse
It's not like the HKTW build is as unstable as the build TBH gave us. The only things that don't work is the front facing camera, and fingerprint sensor.
I just didn't restore from a backup, and you can fix the WebTop. So my phone is running fine, and it seems even more stable than FroYo (Besides the obvious bugs)

tan G said:
hi,
guys, I don't want to dishearten you but did you think a minute about the way motorola will unlock your bootloader in the future update??
as they will release an update.zip like in the past, I'm not really sure if they will include the unlockable bootloader inside it and, not sure also if an android update can flash a bootloader. So I am a little anxious for you guys, mine is already unlocked...
Click to expand...
Click to collapse
It really dose not matter if thay include the unlockable bootloader in every update or not. As long as their is a way for it to be done. Thats all the matters. Really only the N1 could be unlocked without much of any hassle. You just needed to know what commands to run,
Once its unlocked. Its unlocked. Cant go back. And just because you flash back to 1.57 or 1.83 and it no longer says "Unlocked" at the top. It is. All you need to do is flash the pudding and it will put those little words back.

pmcnano said:
Er, dude you really need to read a little bit more on Development forum D:...
Its already unlocked!
Cheers
Click to expand...
Click to collapse
this is not the case for other atrix versions than att

JayRolla said:
Moto said they are going to do it. They already dont it on the leaked future builds, not to mention the one Kenn is running which is an ATT GB. Not to mention this is the same way the did it on the Xoom. Theres nothing to worry about, its unlocked 4 ever.
Click to expand...
Click to collapse
that build is a build for developer and developer devices, there is no garantee that it will be the same for user-end releases, anyway I really hope for all people that you're right.
the sbf used to unlock our phone now (att) has been packed by someone in the dev team may by eval or 2dc... or both

JayRolla said:
His point is he thinks its going to be removed from the final build. He states he is already unlocked himself.
Click to expand...
Click to collapse
thumbs up! that's what I said

I will always have an unlocked bootloader

tan G said:
thumbs up! that's what I said
Click to expand...
Click to collapse
tang no matter what update motorola does in the future they wont be able to take away the unlock already created. with that said this post is useless, and a mod should close it, this will give the wrong idea to anyone coming to the forum looking for the unlock. who knows what motorola will bring in the future, fact remains, is unlocked and it aint going back.
"Pandora dosnt go back in the box man - he only comes out!!!!"

Dont feed the troll!!!!!!

Debunking the Atrix Myths!

1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK! Also, updating to v4.5.141 and than unlocking the bootloader will also cause a hard brick!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
3.Xoom ICS release
The release of ICS for the Motorola Xoom does not help in any major way to the development of ICS on the Atrix.
Explanation/Elaboration: Yes, we do need the ICS kernel for Tegra 2. Yes, the Xoom uses Tegra 2. No, they are not the same. The atrix uses the Tegra 250 AP20H while the Xoom uses the Tegra 250 T20. Yes, the one on the Atrix is slower, but more importantly, different! (Thanks live4nyy!)
4.Carrier Unlocking the Atrix (NOT BOOTLOADER UNLOCK)
This is less of a myth, more of a guide. If you CANNOT unlock the Atrix even with the code provided (I can/will not provide), do NOT keep trying. All you are doing is wasting the number of tries you can try before the phone will not accept any more tries. What you should do is flash to an AT&T rom/radio and try again. This is assuming you want to unlock the AT&T version of the Atrix of course. Once unlocked, the Atrix can be flashed to your hearts content and will not be re-locked. (Thanks Abu-7abash!)
Any other widely mistaken facts about the atrix you want corrected?

Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head

matthew5025 said:
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.

UFOs > Bigfoot

matthew5025 said:
1.Bootloader!
When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible.
Click to expand...
Click to collapse
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?

stang5150 said:
I'm curious. So this fuse that blows in the phone when flashed, is the only purpose of this fuse is to identify an unlocked phone? Is this fuse added to the phone by Motorola or are they required by the carriers to install these fuses?
Click to expand...
Click to collapse
eFuse is an IBM invention. I posted a lengthy explanation of this a long long time ago after verifying the Atrix was using eFuse technology. When you read eval's explanation it is very accurate, except that you cannot "burn a bit". You could "set a bit" which sends the signal to overload the hardware circuit.
Carrier can specify they want a locked bootloader or not. I believe the method could be up to the manufacturer, but carrier may also specify type of bootloader lock. Of course, manufacturer may have an internal policy that all phones have a locked bootloader, but include provisions for unlocking it.
eFuse does not blow a fuse per se. This implies there is an actual fuse in the phone. eFuse (electronic fuse) is a circuit built into a chip inside the phone. When you unlock the bootloader a very small electrical charge is sent to that circuit and simply overloads it and burns it out. eFuse technology is not solely used for bootloaders. They are in many more electronic devices than you may think. eFuse is both software and hardware based. Software sends the signal, hardware circuit is blown, software checks this circuit on boot-up, when the circuit cannot be completed the software knows this, and reports, in the case of a phone, that the bootloader is unlocked.
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
---------- Post added at 12:31 PM ---------- Previous post was at 12:25 PM ----------
ifalldownalot said:
UFOs > Bigfoot
Click to expand...
Click to collapse
This ^^^^^^^! LOL

matthew5025 said:
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Well as far as I know UK version is safe to flash back to froyo. I went back from 2.3 to froyo sbf few times myself and few other people confirmed this aswell.
/edit
Never upgraded OTA so my post is useles...nice!

matthew5025 said:
1.Bootloader!
The bootloader of the atrix CANNOT be relocked after it is unlocked! Yes, I know if you flash a stock SBF file the "Unlocked" text will be gone, but it is not relocked!
Explanation/Elaboration: When you flash the pudding file, what you are flashing is a bootloader. When you key in oem unlock ******, you BLOW a fuse. Non-reversible. Hardware based, not software. So, when the 'pudding' bootloader runs, it sees the burnt fuse and knows the phone is unlocked, thus printing the "unlocked" text. When you flash back to stock, the stock bootloader doesn't even care about that fuse, and WILL NOT skip signature check in fastboot aka locked.
This WILL NOT REVERT your phone back to stock, the stock bootloader just doesn't care if you are unlocked or not. Motorola can easily check if your phone is unlocked, but USUALLY will not. DO NOT BLAME ME IF THEY DO FOR YOU! Now, stop going around saying "my phone can be relocked" =)
2. Hard brick
If you OTA to Gingerbread, and downgrade back to FroYo, you WILL get a HARD BRICK!
Explanation/Elaboration: Yes, it the damn fuses again When you update to Gingerbread you will BLOW a fuse in ReservedOdm[1]. If you downgrade to FroYo, you will get an Error "SVF:105:1:2" Mainly what that means is that at the lower part of the Odm[1] called 105, the bootloader expects the fuse to be '1' but found out its actually '2'. It then refuses to boot, sending the phone into NvFlash mode, which we cannot use as we require a SBK from moto.
Reference:Thanks eval-!
Any other widely mistaken facts about the atrix you want corrected?
Click to expand...
Click to collapse
Oem lock ******
Tried?
Sent from my MB860 using XDA App

Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL

Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk

jgc121 said:
Nice, straight forward write-up. Hopefully this helps some of the n00bs get this info through their head
Click to expand...
Click to collapse
Thanks! Its annoying the way they keep repeating the same stuff over and over again isn't it? Drives me up the wall!
live4nyy said:
I got one.
Myth - The Xoom having ICS will help in the development of the Atrix.
Fact - Just because the Xoom is a Tegra 2 device and running ICS does not help (or is very minimal* ) development to the Atrix.
* I don't know the exact details but I'm sure this is the gist of it.
Click to expand...
Click to collapse
Thanks! Will include that point!
CaelanT said:
Now, that said, this thread just serves as another one for idiots to read and ignore. All the info posted here has already been posted in a hundred other threads. Giving "myths" their own thread will just serve to create more inaccuracies as people post "myths" that they really know nothing about. Who is to say that anything posted here is any more accurate from one person to another? Sorry OP, but "myths" may actually become myths in here.
Click to expand...
Click to collapse
The reason I created this thread is so that the next time I want to correct someone, I just link them here, instead of typing out the whole thing again.
On a separate note, I see you are really active on in the Atrix community, helping others. I would like to thank you, a person who is knowledgeable, taking time to answer their questions. Can't say the some about myself.
guidoido004 said:
Oem lock ******
Tried?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
?
ssmr2t said:
Hey Matthew, thanks for the info- I am going to Singapore on Sat for the airshow. Are there cool spots out there to get good deals on accessories for our atrix>? LOL
Click to expand...
Click to collapse
Isn't it next Saturday? And the iPhone is the "hottest" phone here, accessories for iPhones, yes, Atrix, little.
Abu-7abash said:
Not only Atrix related but a general fact, when you sim unlock a phone (atrix included) it won't ever get locked again no matter how/what roms you flash.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
Thanks! Will include that!

Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there

ssmr2t said:
Oh I will be exhibiting there for my company Tues-Friday.. I think Sat is public day.
Booo... I was hoping to get a nice atrix toys while I was out there
Click to expand...
Click to collapse
hey, hey, hey. get a room, you two. keep this thread myth related.

motorola razr M prototype?

hi everyone, so i recently saw motorola razr m. the thing is, it had motorola markings on it like it is some kind of prototype or test device. it was running jellybean. just the markings were a bit curious, if someone can shed some light on what it was. thanks !

mikeverne said:
hi everyone, so i recently bought a second hand motorola razr m. the thing is, it has motorola markings on it like it is some kind of prototype or test device. it works totally fine, gsm unlocked and its running jellybean. everything runs as it should, just the markings are a bit curious. ive attached a pic to see if someone can shed some light on what it is. thanks !
Click to expand...
Click to collapse
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757

Somber73 said:
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Click to expand...
Click to collapse
yea i saw that too. but that doesn't really tell me anything apart from the fact that other phones like mine were also sold(which i already knew).

It would be best to just drop the subject. You have something rare, and if you want to keep it, I would keep it quiet. The guys on the Motorola forum are launching a pretty big investigation into this. I would delete your pic and edit your OP. Don't get me wrong, I DO NOT condone illegal activity, but there is a reason these are out in the open...

Regardless of the circumstances surrounding where or how he got the phone, there ought to be someplace where this guy can get answers as to its origin or what it is exactly without everybody overreacting.
Sent from my XT907 using xda app-developers app

It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!

It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta

cellzealot said:
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
Click to expand...
Click to collapse
thank you! and btw, that wasn't me who posted in the official forums lol. thats the lase place i would think of posting if i had a prototype haha.
sloosecannon said:
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thank you! and yea, i agree.

that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.

jco23 said:
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
Click to expand...
Click to collapse
uh, actually im pretty sure he is telling the truth. its sort of a Pakistani craigslist.

RSD is proprietary software, owned by Motorola. While I know it's very easy to find online, it's not intended for public use. The rules of this site forbid discussion of software installation or use unless that software is distributed by Motorola or one of its partners.
That pretty much sums it up. Had he come to xda, he'd have gotten help. He didn't seem too open to helping the Motorola guys out though, so they didn't help him. Don't see why he would lie about that, he's just a poor guy who wants his confidential Motorola property to work for him... By asking the people that someone stole it from... Yeah...
Sent from my XT907 using Tapatalk 4 Beta

guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?

dasche said:
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
Click to expand...
Click to collapse
Nope. Since it's factory unlocked, you should be able to install TWRP and go about flashing whatever you want. It might be a wiser choice to buy a regular handset, since you want have Motorola property all over the front.