yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] perdurabo2:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
[Atrix 4G Android Development] designgears:
already did ;)
[Atrix 4G Android Development] t0dbld:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!

lol so excited cant spell or type
[Atrix 4G Android Development] jimmydafish:
Slow Down Everyone...

this is P3Droid again,

I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.

This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.

either way good luck, but do not return the device to ATT if you break it.
[Atrix 4G Android Development] humancyborg:
Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
[Atrix 4G Android Development] jimmydafish:
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.
[Atrix 4G Android Development] Smith7018:
smiths-MacBook-Pro:~ smith$ shasum /Users/smith/Downloads/motoboot.bin

fda1fdbfd70628cbf1c79361525168847a00830b

smiths-MacBook-Pro:~ smith$ md5 /Users/smith/Downloads/motoboot.bin

MD5 (/Users/smith/Downloads/motoboot.bin) = f3cb372a7498f175b53dc7881e4bd3c2

​

P3Droid, you have past experience with Dev phones and retail phones, what does this mean to the hacking efforts? Does an unsigned bootloader move us past any of the previous obstacles or is this just something to study?
[Atrix 4G Android Development] jimmydafish:
If you would like to brick your device I can teach you how to get it on, but it will require you to be rooted and running a custom recovery, the other method requires a fully released sbf file.
[Atrix 4G Android Development] t0dbld:
i am listening and i am not flashing anything yet .. .i heard ya before and i hear ya now :)
[Atrix 4G Android Development] switchgott:
Could this bootloader work on Defy also?
[Atrix 4G Android Development] t0dbld:
I do have to say though with this Xoom news... gives us hope that maybe with GB release for atrix that was promised soon and to include 1080p it might also come with unlock/lock
[Atrix 4G Android Development] t0dbld:
omg ... no please step away from the thread before you hurt your self and others
[Atrix 4G Android Development] jimmydafish:
I'm worried about all of you, no one wants to hack Motorola phones more than TBH, we want to share what we know, and find new avenues of attack. But what i'm afraid of is zealousness will win out over reason. We have killed 4 phones so far, 3 dev phones and 1 consumer phone, which has cost us more than 1500 dollars. So we would like to help you avoid our costly growing pains.
[Atrix 4G Android Development] DarkSi08:
I'm sure we all understand and appreciate your experience and your concern. I would hope that anyone willing to dump this dev bootloader on their device would fully expect that the phone will never work again. Anyone who doesn't expect that probably shouldn't be working on development.

Otherwise, we're not comparing apples to apples with your work, as I'm sure you know. :)
[Atrix 4G Android Development] t0dbld:
i understand.... just like i understood that this file he got from god knows where still only represented the exact same thing i was trying to do that you stopped me from before ... i do understand chain of trust etc..
[Atrix 4G Android Development] designgears:
Thanks, I removed the link to the flashing program... and added a note.
[Atrix 4G Android Development] perdurabo2:
P3,

But at the same time, you previously mentioned TBH has no Atrix devices in-hand, so we haven't been expecting much, except advice.
[Atrix 4G Android Development] s44:
No chance. The Xoom is unlocked because it's Google's Honeycomb flagship, as Droid 1 was for Eclair. The latter's open release didn't make for unlocks on the Milestone, Droid X, Droid 2, or Atrix, and neither will the Xoom's.
[Atrix 4G Android Development] humancyborg:
Actually it's been confirmed that the Droid 1 bootloader being unlocked was actually an error and not intentional in any way.
[Atrix 4G Android Development] iammorris:
Source?

.
[Atrix 4G Android Development] thunderpack:
I was thinking that the rumor was 2.3 would be reserved for the Nexus S and everyone else would get gingerbread as 2.4?
[Atrix 4G Android Development] cellzealot:
That's just the nature of rumors I suppose.

All we know is what the files tell us, we get little else in the way of accompanying documentation most time. We did not anticipate getting these files at all and they were part of another set of files for a different model.

And to echo my partner p3droid again, no, they will not help "unlock" the bootloader if it is hardware locked like the TI OMAP/Qualcomm AP/BP chipset devices.
[Atrix 4G Android Development] perdurabo2:
The 2.3/2.4 version numbers are pretty arbitrary. Developers go by build numbers and version control tags. In other words, I wouldn't read too much into this.
[Atrix 4G Android Development] jimmydafish:
you are quite incorrect, the 2.3 or 2.4 is a very important designation just like 2.1, 2.2, 2.2.1. Motorola denotes their builds by the the Google release the the build version of blur ex. (2.2.1 Blur 3.4.2)
[Atrix 4G Android Development] jimmydafish:
I am not speaking out of turn here, what we are holding is extremely valuable. We may not have the phones but we do have the firmware that is on the Atrix, we even have the Gingerbread build for the Atrix. So while I may not have the phone, I can definitely look at what is going on, to some degree.
[Atrix 4G Android Development] labsONE:
But how do WE get our hands on this firmware? I'm still looking for a complete image WITH the Webtop partition for research.
[Atrix 4G Android Development] Smith7018:
We don't. Sigh..

P3Droid, so you have all of those files and now (or you probably had it already) you have the devkit bootloader, is there anyway that those files could help us? You seem very knowledgable on this situation, so has getting this BL made us any closer to the end goal of Custom ROMs or is this more or less a red herring?
[Atrix 4G Android Development] Chad_Petree:
why is no one talking about the zoom having a semi unlocked bootloader? :confused: this could mean something for the atrix
[Atrix 4G Android Development] jimmydafish:
It is a red herring, only useful if you have a dev phone.
[Atrix 4G Android Development] upNsmokeAllDay:
The Xoom was announced with a fully unlockable bootloader and I will definetly buy that with that news.
[Atrix 4G Android Development] Smith7018:
No, it probably doesn't. The Xoom is a flagship Android device, Google would rather die than have it be restricted. The reason nobody is talking about it here is because this is the developer section for the Atrix 4G.

Well, then any ideas/progress from TBH? I get my device in about two weeks (I shipped it home, stupid college...) and I thought I'd look into it then, but if there's little to no guarantee of any progress, I might return it and wait for the S2 :\.

So if we have to hack the checks out of the NVRAM and mbr (IIRC), then couldn't we flash this bootloader? Well, then I guess it wouldn't matter anyways because if there was nothing to check signatures, then having a signed BL wouldn't make a difference, right? :\

Sorry about the stream of conscious writing hahah
[Atrix 4G Android Development] perdurabo2:
No, I'm quite correct. Hi, I'm an Android committer! You are misunderstanding what I said.

The "2.x" style version numbers are essentially tags on a build #. So while there may be Olympus betas floating around with 2.3, that doesn't mean it will or has to be 2.3 when pushed to the public. Google could tag tomorrow's build as 2.4.

What's with people with no idea what they're talking about rudely "correcting" us?
[Atrix 4G Android Development] jimmydafish:
You are correct, but I was speaking about the Atrix build #'s because this is the atrix dev section. But of course Google can designate any build # to the git/source as they please.
[Atrix 4G Android Development] Smith7018:
While you're correct, you're arguing over semantics here. I'm sure P3Droid understands that just because a build number says "5.0" doesn't mean that Android Peanut Butter Cup exists. Isn't it possible to have a thread without arguing about who's "more right" here? :o
[Atrix 4G Android Development] perdurabo2:
I think you replied to the wrong person. I was merely answering the other fellow's question regarding the beta build 2.3 versioning, despite Google folks saying otherwise. Then jimmy jumped in :rolleyes:
[Atrix 4G Android Development] cellzealot:
You know that it's worth noting that some of the best minds in the Android community have taken a long hard look at the Motorola locked/encrypted bootloader and have simply chosen to walk away and not deal with the problem. Koush wrote the bootstrap recovery very quickly and then stated flatly that he would not port CyanogenMod to the DX and that was that. CVPCS tried for many months to get custom kernels to boot on stock hardware using kexec and many other methods while he was developing his ROMs for D1 and then finally dropped it all to go work for CyanogenMod. We ourselves spent many months exploring the posibilities and looking for the "golden egg" in the NVM in the early stages when folks like Nenolod were claiming the existence of a hidden Engineering mode string that could be enabled that ignored the Efuse on the OMAP chip. Our work proved that to be nonsense but we never found a solution or workaround. I would add that we never made any claoms whatsoever about our ability to do so either. What we had was and is unique access to internal files and documentation that we thought would give us a leg up or at least a fighting chance of finding a flaw or magic bullet.

There is no such thing and we have long since come to terms with that.

You folks have all the fire and inspiration right now to tackle it again with a somewhat different set of puzzle peices and tools but the same fundamental problem.

Despite all this neither p3droid nor myself is cynical about it and would love to help the community here in any way we can and will do so.

Edit: It is also worth noting that I do not consider myself anywhere near in the same class as Koush and CVPCS and others and not one of the best or even better minds in Android. :D

I am not a programmer or dev of Android or any other OS...I am an old school Motorola hacker enthusiast...that's about it.

Just wanted to make that clear thanks!
[Atrix 4G Android Development] Smith7018:
Color me stupid, but isn't this situation similar but not nearly as bad? We're not fighting the chip's defense system here (eFuse), we're fighting multiple signature checks, right? Now, mentioning this might get people angry at me, but would the work on the iPhone's bootloader mirror any of this? I know it's nowhere near the same in terms of code, but didn't they have to find an exploit that got past bootloader signature checks, too? I know that there are ways to access "bootloader mode," does that allow for commands like the iPhone's?

http://theiphonewiki.com/wiki/index.php?title=IBoot_Environment_Variable_Overflow

This exploit uses an exploit in the iPhone's iBoot's ability to parse commands, could we do something similarly? Sorry if this has been brought up before.
[Atrix 4G Android Development] zambezy:
Correct me if I'm wrong but you need engineering H-Boot (SPL)... not bootloader... The SPL verifies the signatures...
[Atrix 4G Android Development] mburris:
Ding Ding Ding.
[Atrix 4G Android Development] designgears:
I will get that for us :)
[Atrix 4G Android Development] Main Target:
DG You're taking too long
[Atrix 4G Android Development] jimmydafish:
H-boot is an HTC thing and no past motorola Droid devices have used an H-boot. I may be wrong as I too am new to the Atrix but that has only been an HTC phone thing, no other manufacturers. This is why unrevoked has only worked on HTC phones.
[Atrix 4G Android Development] youareme7:
I'm pretty sure you're right on that as well. I'm not sure but I believe the equivalent stage 2 loader for Motorola is known as mbmloader.
[Atrix 4G Android Development] Ririal:
A good suggestion, but as far as I understand it, they didn't circumvent the need for a signed file. Apple signs the firmware when you flash it through iTunes, and it contacts Apple's server for the signature. What the community did was mirror that server and store the SHSH keys Apple was sending out, so you could sign the firmware to the device, even after Apple stopped signing it. If you stored the signed key for a firmware version for your device (either locally or through Saurik's Cydia app), you could always flash that version to your device. If you didn't store the key and Apple stopped signing it, you cannot put it on your phone. Ever.

http://www.saurik.com/id/12 Saurik does a much better job of explaining than I do, if you're interested.
[Atrix 4G Android Development] sdlopez83:
Originally Posted by Festaman

I got this from an someone inside Motorola. Who I know and don't want to get into trouble. SO i am trying to keep this as generic as I can.

You can bypass the bootloader. However he could not me how. But, he did tell me that you should look at how the LG was bypassed. That might help. Also, later this year Motorola will tell people how to do that safely."

I think he may mean the LG Alley? But i am not sure i am waiting for a return email
[Atrix 4G Android Development] robxcore:
thats a pretty interesting statement....;)
[Atrix 4G Android Development] daveop:
This would be great news. Hopefully you can get some evidence that this is at all true. Thanks for the heads up.
[Atrix 4G Android Development] zeyoner:
So maybe you should take a crack at it..
[Atrix 4G Android Development] TheDude:
Sad :(

Not to be lame... but if geohot can hack the ps3... this is just as doable ... I understand that is totally out of context.
[Atrix 4G Android Development] Ririal:
If we want to get geohot on cracking this, all we need to do is get him a phone and a dock, then remove a core advertised feature and piss him off so he hacks it to get it back. That's why he went at the PS3 with such fury. ;)
[Atrix 4G Android Development] ydgmms:
like 4G? :D
[Atrix 4G Android Development] perdurabo2:
Then why don't you have it done yet? What are you doing posting here? Get busy, don't be lame.
[Atrix 4G Android Development] zambezy:
So has anyone attempted to flash this bootloader...?

If this is truly an engineering bootloader.

Has anyone confirmed to the NON existence of e-fuse of any kind that would flip out if the bootloader didnt match..?

Cant be a pioneer without catching some arrows... =)
[Atrix 4G Android Development] zambezy:
DELETED....
[Epic 4G General] nebrando:
I noticed that the Google Maps Live wallpaper is no longer part of the options on Froyo.

Does anyone know how to get it on there or any news about it?

This happened on an update.zip upgrade from DI18 to EB13 on multiple phones.
[Epic 4G General] amitbk:
Also looking for it

I'm also looking for it. Please update if you find it.

In the meantime, you can use this alternative:

http://xdaforums.com/showthread.php?t=700786

Also, in this thread people are also looking for this wallpaper.
[Epic 4G General] nebrando:
Thanks for the links. I tried the one you suggested and it just force closes everyone I try to load it. Oh well, the quest continues.

Thanks again for the help.
[Epic 4G General] drumtrucker:
crap, they just got Google Maps Live Wallpaper working right. Was finally tracking live.
[Epic 4G General] swear0730:
Who is "they" and how do I activate this on my phone? I have never been able to find out how even though once in a while I come across a reference to "Google Maps Live Wallpaper" on the interwebz. Can't find it on the market. Can't find it as an option in Google Maps. Can't find in in my wallpaper picker.

Any further explanation would be appreciated.
[Epic 4G General] drumtrucker:
'They' would be GOOGLE (thought that was obvious, but maybe not). Your phone and Android version must support 'live wallpapers'. I think it started at 2.2. If it does, when you go to WALLPAPERS from home screen there will be a LIVE WALLPAPERS choice.

Until a recent GOOGLE MAPS update, if you have GOOGLE MAPS installed, MAPS would appear on the WALLPAPER/LIVE WALLPAPERS list. It started appearing there many iterations of G Maps ago.

I got all excited today when another update for G Maps popped up, thinking maybe they had accidentally left it off the last one and were updating to fix... no such luck.

I am back to using Advanced Map, which does a FORCE CLOSE everytime you boot phone, but after that works fine.
[Epic 4G General] austin420:
Can you not roll back the update in the application manager?
[Epic 4G General] drumtrucker:
I am trying to get older version now. Will check the 'roll back' angle, but found website with them.

http://www.freewarelovers.com/android/app/google-maps#old_versions

6.0.1 didn't do it, trying 5.8.0 next
[Epic 4G General] austin420:
I just tried the "uninstall updates" method. It only went back 1 version, and did not restore the wallpaper function.

They mustve removed it a few versions back.
[Epic 4G General] drumtrucker:
OK, now I am wondering WTF. 5.8.0 no go either and it was working on my phone just a few days ago.

I just got a 'certified like new' warranty replacement and am running GB where my old phone was still on FROYO. I am starting to suspect that may have something to do with this.
[Epic 4G General] drumtrucker:
I did manage to restore my fascinate to state it was before warranty exchange, Blackhole 4.4, a Froyo rom. Goolge maps was 6.xxx and the wallpaper was woring. Am now back on GB rom and it is not on available list of love wallpapers...

i just don't get it.
[Nook Color Android Development] jasoraso:
I definitely prefer hard keys, even with the modifications in CM7. I'll give your zip a try next time I flash a rom (I've already changed my qwerty.kl on this rom).

One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
[Nook Color Android Development] EpicFail236:
An excellent point. Editing my zip and attaching v2. thanks to you!
[Nook Color Android Development] chemical1der:
success! just flashed this along with nightly#4 and it works like a charm.
[Nook Color Android Development] digitalslacker:
I love this. always get stuck in pics in Facebook and can't get back.

Question though, what do you all use for a good alternative to adjust the volume on the fly?

Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
[Nook Color Android Development] EpicFail236:
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
[Nook Color Android Development] digitalslacker:
thanks, i'll check it out.
[Nook Color Android Development] xyexz:
What would be really cool and I'm not sure it's possible and I know it's not in the scope of this thread; but a way to change functionality of the buttons per app. So for example when in Pandora (or music app of choice) buttons behave as volume buttons, but under other various apps like gallery it could be home+back button set.

Seems like you'd have to have an app running as a service and monitor the currently running focused app (not in sleep mode) and depending on what has focus do a live update to the qwerty.kl file to change buttons to expected functionality, not sure if a reboot is required after an update to the kl file though?
[Nook Color Android Development] spikey911:
How can you revert back to stock?

Also is there a way to swap the keys? It seems more natural to have the back key as the +

Thanks for your work, installed without a hitch..
[Nook Color Android Development] WhiskeySlx:
change mapping in step 4 from here:

http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
[Nook Color Android Development] fattymcdirty:
not working with

[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}

buttons still remain in their normal functionality...
[Nook Color Android Development] EpicFail236:
Thanks for the heads up, will review and post v5 sometime today.
[Nook Color Android Development] bigted41:
my status bar always shows with HoneyComb, so I always have the back menu buttons. are there apps where this is not the case?
[Nook Color Android Development] knucklesmckay:
Anyone try this on froyo yet?
[Nook Color Android Development] EpicFail236:
Yeah, I totally deleted an extra file, added to v5 and it should now work with this eMMC build. oops.

I will have to put together a stock zip and put it up sometime in the near future. Your swap keys is not easily done directly, but I have posted a new flashable zip that will swap the keys, flash INV-v5 to have the volup function as back and voldown to work as menu. This one I haven't tested, as I don't actually have my nook with me here now, but in theory it should be OK, as all I did was swap the mappings in the kl files.
[Nook Color Android Development] rickpref:
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.

Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.

I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.

I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.

Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
[Nook Color Android Development] EpicFail236:
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.

That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
[Nook Color Android Development] rickpref:
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
[Nook Color Android Development] EpicFail236:
My ADB machine was down and out at the time, so I had to do it via ES file manager and the terminal on the nook itself, but yeah, manual replacement was the way to go. sometimes a bit of command-fu is just easier than the alternative.