yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] ZOMBI3:
Debloated,Deodexed,Rooted 5.7.905

"I am not responsible for anything that happens to your phone flash at your own risk"

Whats included,Droid4 bootanimation/with sound, titanium backup latest free version for those like myself who wanna start restoring apps asap if you guys don't use it sorry for adding it, some minor edits to build prop, dalvik vm heap size = 42 , wifi scan = 90, max events per sec =70,torch intensity =70 camera flash intensity= 100 and i think thats it ,

People I like to Thank "Buckmarble" for helping me with a number of things, and answering all my questions I've ever had :)

Also I like to Thank "droidian1441" for posting the 5.7.905 Leak UPDATE, thank you :)

Here you guys go Flash Via Safestrap,droid3 bootstrap i use safestrap smartest thing to do ;)

EDIT: Just got a email from dropbox suspended for three days :(, gonna upload it else where

Uploading to minus right now/minus link up :)

http://min.us/mOrX922yx#1o <Debloated Version

http://min.us/mqTPcxS5h#1o < Bloated Version

http://min.us/mvLXd0nSU#1o < Additional Flashable razr Keyboard flash after rom :)

.............................................................................................................................

DROPBOX ONLY USE IF YOUR NOT ON A PC please I don't want the links to get suspended again

http://dl.dropbox.com/u/30415631/DROID3DEODEXEDDEBLOATED 5.7.905.zip < DEBLOATED

http://dl.dropbox.com/u/30415631/DROID35.7.905BloatedDeodexed.zip <BLOATED
[Motorola Droid 3] ovelayer:
Woot first to post...awesome thanks 1000x for for this!!
[Motorola Droid 3] ZOMBI3:
Np yw :)

Sent From My Dark Fire DROID3
[Motorola Droid 3] oostah:
haha i just did the update like 20mins ago then see this :rolleyes:
[Motorola Droid 3] somemadcaaant:
Very nice work mate props.

-smc
[Motorola Droid 3] somemadcaaant:
ZOMBI3 what base are you using mate, 5.7.894 or 5.6.890 etc?

-smc
[Motorola Droid 3] ZOMBI3:
Im on 5.7.905 why? Sorta sucks that I did the actual update, before I made the rom, cuz I get 2 bars on hash cm9 I didn't before, but on 905 I get full bars majority of the time, never get lower then 3 bars on it tho

Sent From My Dark Fire DROID3
[Motorola Droid 3] somemadcaaant:
Oh right, i'm guessing the file doesnt have kernel+firmware?

Long wait for the download for me being in oz.

-smc
[Motorola Droid 3] ZOMBI3:
Naw, gotcha,no kernel nothing like that, just like flashing any other rom ;)

What rom are you on now?

Sent From My Dark Fire DROID3
[Motorola Droid 3] somemadcaaant:
Cheers perfect for me, thanks for taking one for the team.

-smc
[Motorola Droid 3] VincentDHam:
Would it be possible for you to make a bloated version of this?
[Motorola Droid 3] ubermetroid:
Installed - running great. thanks!
[Motorola Droid 3] ZOMBI3:
Yw

Sent From My Dark Fire DROID3
[Motorola Droid 3] ZOMBI3:
I could do it for you just waking up, sorry for the long wait

Sent From My Dark Fire DROID3
[Motorola Droid 3] VincentDHam:
That would be great! Thanks.
[Motorola Droid 3] wattnxt:
+1 on a bloated version to look/feel completely stock.

Thanks.
[Motorola Droid 3] ZOMBI3:
uploading right now 75%, gonna add a addition flashable zip for those who like the razr keyboard

EDIT BLOATED VERSION UP,RAZR KEYBOARD ALSO
[Motorola Droid 3] trini.s2k:
i have a question , what is the pro of this rom whats better about it , like can it compare to other roms, just a curious question...
[Motorola Droid 3] droidian1441:
If you havent seen the original thread, he based it off of the 5.7.905 update I posted here last week.

He posted a debloated and deodexed version, a bloated version and a razr keyboard mod.
[Motorola Droid 3] ovelayer:
Hey bro would you mind sharing the DROID 4 bootanimation? Does it have sound?
[Motorola Droid 3] trini.s2k:
oh ok i just read it , sorry!
[Motorola Droid 3] ZOMBI3:
go to themes and apps section i posted it there and yes it does have sound
[Motorola Droid 3] davidhooper:
Has anyone tried this without doing the update first?

Does this ROM work any better than stock without the kernel and radio that was included in the leaked update? In particular if this ROM is installed with Safestrap are the camera and camcorder improved?
[Motorola Droid 3] matthskim:
Would anyone who tried this rom in safestrtap make a comment?
[Motorola Droid 3] somemadcaaant:
Launcher seems smoother over all, it's nice to have a few updated applications and google+ comes with the update like the ICS roms. A few tweaks in the messaging and phone applications.

Camera is also smoother since continuous auto focus has been replaced with touch to focus same as 5.7.894, so it's physically not doing as much work so makes sense.

Over all just seems smoother and reminds me of the 5.7.894 update, only had a few days with it tho and i've heavily customised it with build.prop, Adrenaline, int.d hack, screenshot, reboot and Jewremy notification widgets which helps.

-smc
[Motorola Droid 3] VincentDHam:
the notification widgets didnt work for me??
[Motorola Droid 3] somemadcaaant:
Nah the original mod by Jewremy won't work as it's an old/different framework, needed porting and tweaking to work correctly.

Try this.

-smc
[Motorola Droid 3] VincentDHam:
Thanks!! You know how to make the 1% battery to work?
[Motorola Droid 3] somemadcaaant:
Yeah I like stock, just swap out the icons from the file or upload it to the kitchen and reflash it once it's done cooking.

http://uot.dakra.lt/

-smc
[Motorola Droid 3] VincentDHam:
what files do i swap? its not as simple as adding ro.product.use_charge_counter=1 to build.prop?
[Motorola Droid 3] davidhooper:
I went ahead and installed the bloated version with Safestrap over Hashcodes 894 ROM without wiping data or cache. Phone came up fine with all of my programs/widgets/wallpaper still installed. Ran Psousa's debloat script to remove the bloatware that I did not want to keep. (Once I got used to it I find that I like the Motoblur launcher.)

I have not used the phone much yet, but overall it seems to be more responsive. The response may decline with time and no reboot. I will report back in a week or so if anyone is interested.

I have taken a couple of pictures just to test the camera. The camera opens quicker and takes pictures quicker. The pictures look good on the phone but are still fuzzy when called up on a computer monitor. It took me a while to figure out the touch to focus feature. At first I thought that there was a problem when the zoom bar kept disappearing from the screen. If this OTA is ever released the new camera function needs to be explained to the masses.

I do not see any difference with the camcorder, but I was always petty happy with the camcorder performance on my phone.
[Motorola Droid 3] somemadcaaant:
Sorry mate i've no idea - best to use the kitchen I think, I've never used it but looks painless.

-smc
[Motorola Droid 3] VincentDHam:
lol, oh okay
[Motorola Droid 3] thingonaspring:
DL Links Down

Hey guys, the links to min.us have stopped working, can some kind soul up the debloated version to a mirror for me?

[edit] - scratch that, they're working now
[Motorola Droid 3] lewrydiboys:
Can I flash this on my XT860?
[Motorola Droid 3] ekramsam:
Hi, two questions:

I don't have a custom recovery, can I use the stock recovery to install this ROM? I'm on 57.1.60

Also can I make changes to the build.prop and re-zip the folder and then update or does the zip need to be signed?
[Motorola Droid 3] davwman:
Still not working for me
[Motorola Droid 3] matthskim:
I have been using this rom for one week.

This is the best Rom I have used in terms of the battery life. It is also pretty smooth. With moderate use, the battery lasts more than 70 hours for me.

Great job!
[Motorola Droid 3] raiden:
I just upgraded to the 5.7.905 rom but my baseband still say n_03.13.29P. How can I upgrade my baseband?
[Motorola Droid 3] matthskim:
I understand that the baseband and kernel stay the same. It is just the system files. To do that, you need to use the stock recovery to flash the 5.7.905 update file, not this rom file.
[Motorola Droid 3] ZOMBI3:
=/ hmm, which one do you want debloated or bloated?

Sent From My Dark Fire DROID3
[Motorola Droid 3] ZOMBI3:
If you want the new baseband and kernel look at droidians thread with the leak updates

Sent From My Dark Fire DROID3
[Motorola Droid 3] yus4eel:
MY battery life on this is at least 2x better than on cyanogenmod this is great!

Btw what is the Dark Fire thing you mention in your signature its really bugging me haha.
[Motorola Droid 3] ZOMBI3:
Pm me

Sent From My Dark Fire DROID3
[Motorola Droid 3] dsw361:
Links are down

Edit:Nevermind, can't download on mobile. Works fine on my laptop.
[Motorola Droid 3] ZOMBI3:
I do not know what the problem that causes this is, Im looking for another file server that allows me to upload any size file any suggestions is appreciated thank you

Sent From My Dark Fire DROID3
[Motorola Droid 3] dsw361:
Wow, this rom is super snappy! Still have to test battery life tho.
[Motorola Droid 3] ZOMBI3:
Thank you let me know :)

Sent From My BLAZING FAST DARK FIRE DROID 3
[Motorola Droid 3] dsw361:
With heavy use I got about 14 hours. That's pretty good for the way I use my phone.
[Motorola Droid 3] aross6:
Can someone tell me if the debloated version still has the Mobile Hotspot app incluided in it?
[Motorola Droid 3] ekramsam:
Using debloated version, it has mobile hotspot app
[Motorola Droid 3] ThePeacedog:
Dead Links

All of the links are dead, could someone upload again please? Thanks.
[Motorola Droid 3] Telster:
+1
[Motorola Droid 3] rapboy23:
again upload files links dead
[Samsung Galaxy Nexus] greeced:
This has probably been answered before by one or two people, but I'd rather know from the whole lot of you brave souls who have switched from yakjuux to yakju.

I'm specifically wondering from those of you that have done the COMPLETE switchover to the yakju build... that includes ALL things that come with it, including it's radio.

I know we can flash the KL1 radio on top, but I'm not looking to do that. I want the entire thing to be from Google, and keep it as such. From what I understand, when you have the yakju build, and the KL1 radio, you will not get OTA updates automatically, thus having to flash manually. On the flip side, if its a complete yakju, including the radio that comes with it, you will get the OTA updates automatically.

So here's the questions:

1. Have any of you flashed the yakju build on your phones KEEPING THE RADIO that is a part of that build? If so, what are your experiences with reception/data specifically on the Bell Network? Any difference that you've noticed?

2. Am I wrong in my thinking? If you did flash yakju, then the KL1 radio, will you definitely receive OTA updates automatically? As in no real user intervention other than clicking "update"?

I want to be sure before I do this, because I cannot find a complete image of the yakjuux build that includes everything including the bootloader in case something goes wrong/or doesn't update the way a true Google experience should.

Please let me now.

Thanks
[Samsung Galaxy Nexus] superlj:
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
[Samsung Galaxy Nexus] greeced:
Just want to make sure the radio from the official build works properly with Bell.

Don't really want to create a Frankenstein build so too speak by adding different radios
[Samsung Galaxy Nexus] torradan:
I changed mine to yakju shortly after I got the phone, about two weeks ago.

I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.

Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
[Samsung Galaxy Nexus] greeced:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
[Samsung Galaxy Nexus] greeced:
bump. bump.
[Samsung Galaxy Nexus] neotekz:
why are you so worried about receiving ota automatically? since you are on xda and know how to flash you will always have the latest build. Being in canada we usually are slow to get updates(Galaxy Nexus is still on 4.0.1 here) so whats the point in waiting for ota. if you are planning to flash an update now why not do it again when a new one comes out.

btw to answer your questions about the radio, the stock one,XXKK6, will work fine with bell although UGKL1 seems to work better for me on Fido. UGKL1 is probably the radio that your phone has now. it was on my stock fido GN.
[Samsung Galaxy Nexus] mattymac:
I flashed the entire package, including the xxkk6 radio.. Works perfectly fine on Rogers, no comment for Bell but should be fine. Just try it, flash it back if you don't like it. Takes all of 2 minutes.
[Samsung Galaxy Nexus] mrsifter:
From what I understand (and I'm still new to this as well) you need to use the radio that comes with the official image otherwise you won't get OTA updates associated with that rom.

Newbie account so I can't post links yet but search "galaxy nexus upgrade to official roms yakju build" and its the leemn wordpress blog that says:

"After flashing to yakju build, you can still receive notification of the OTA updates.If you have flashed the radio, system, userdata and boot partitions, and you still have the stock recovery (or have flashed it) from the 4.0.2 image, you will be able to install the updates. However, if you flash a different radio, or different kernel , or a custom recovery, you will need to flash back the stock ones first before being able to install the update."
[Samsung Galaxy Nexus] greeced:
That's the whole thing.

When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.

I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on	JL2. KIES would download KG3 officially back to the phone.

I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.

I know, I'm strange.

So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).

That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
[Samsung Galaxy Nexus] wpghtc:
I flashed it all.

Works great. No issues. I also wanted 100% stock and so far, i am very happy with it.
[Samsung Galaxy Nexus] torradan:
Sorry missed your question, but I'm using the KL1 radio.
[Samsung Galaxy Nexus] superlj:
I am with Fido and have complete 4.0.2 stock rom. I had some strange issues with signals but everything is fine after I changed to a new SIM.
[Samsung Galaxy Nexus] efrant:
I'm not sure what the problem is. When you unlock your bootloader, you just do a nandroid backup, and it backups up your system, data, recovery and boot partitions. The radio is already available. So you can always go back to "stock" yakjuux in case yakju doesn't work (which it obviously does for Canadian users). I've even posted a nandroid backup of my yakjuux build before I flashed yakju. There is a thread in the general section. And to address your concern about "always reverting to stock", yakju IS the stock ROM, it is not a beta or a custom ROM.

The bootloader has nothing to do with yakju or yakjuux or whatever. It will not affect anything related to getting an OTA update or installing an OTA update. Keep your current bootloader if you are worried about not having a backup, and go ahead and flash all of the other images (after backing up your originals of course). That way, you can always return to your yakjuxx if you think there is a problem. Just because you didn't flash the bootloader that came with the latest yakju image does not at all mean you are not using yakju, and I would not call it a "frankenbuild" -- think of the bootloader as the BIOS in a computer. You computer is running Windows regardless if you are using an ASUS P5Q motherboard, or an ABIT IP5 motherboard -- both have different BIOS, but the OS is still Windows. Same with a GN -- you are running yakju regardless of whether you bootloader is 10, 14, 15, etc.

EDIT: To specifically address your question number 2 -- if you flash the system, data and boot images from yakju, you are running yakju, and you will receive the notification for an OTA update when it is available. However, you will not be able to have it install automatically if you don't have the radio image that came with the yakju build and a stock recovery (they are all the same). You can, however, flash those back as soon as you receive the OTA update notification and it will install automatically. Bootloader has no relevance whatsoever.
[Samsung Galaxy Nexus] greeced:
Great explanation. Thank you efrant. You've answered everything I've needed to know
[Samsung Galaxy Nexus] greeced:
Well finally took the plunge and went to yakju from yakjuux. Although my experience wasn't as seemless as everyone elses, so I thought I'd tell everyone just in case someone else runs in to the same problem.

For starters: I followed efrants excellent procedure from this exact post. However it also must be noted that I decided to use the 41F (4.0.1) firmware from Google's images instead of the 53F (4.0.2) image. I did this because I wanted to experience an update. lol

Now, at first I had to try several drivers in order for my Windows 7 laptop to even see the phone with the "fastboot devices" command. I finally found one that works. Coincidentally, one driver will work on one machine, but won't on the next, I have no idea why. After finally getting the right one, I proceeded:

I did all steps to the letter, but skipped steps 4,5 and 12, as the post says they were optional and I didn't really want to lose my bootloader and recovery in case I wanted to revert back to yakjuux.

After completing all steps but those, I did the final "fastboot reboot" and the phone restarted.

Here's where the ride began:

When it restarted, it seemed like everything was fine. It took a while to find Bell's settings, but it was ok. It then said an update to 4.0.2. was available.

Upon the reboot and install, the phone shut off, and rebooted twice, after the second time, I had an android on the ground with its chest open and a RED exclamationed triangle above it. My thoughts were "uh oh". I waited and waited, and nothing was happening. Pressing power and holding it down, wouldn't help.... After approx 5 mins I was about to do a battery pull, and it restarted itself, but remained on the 41F update.

Each restart would say it was upgrading, but never did.. always stayed on 41F.

So I went back and did everything in the procedure, not omitting anything this time (goodbye yakjuux bootloader!) and it went off without a hitch... This time my android figure was standing up, very much alive and getting a heart transplant.

So here I am.. Yakju configured and using the yakju KK6 radio. All seems well. Haven't decided if I'm going to put the KL1 radio on as yet, but thats for another day.

Thanks again efrant for all your help and patience with me.
[Samsung Galaxy Nexus] efrant:
@greeced Welcome to yakju. :) I doubt you will ever go back to yakjuux.
[Samsung Galaxy Nexus] greeced:
Well, I have been on yakju for a few days now and I can say no problems whatsoever.

At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.

As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.

Overall very happy that I'm now Pure Google.

One thing to note:

When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.

I think that should be the case for all firmware updates, including googles.

It's a painful process to redo everything, but well worth it in my opinion.

I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.

We are dealing with computers after all.

At any rate. Just thought I'd update my experience in case anyone else who is on bell felt apprehensive like me.
[Samsung Galaxy Nexus] efrant:
I think the general consensus is that ICL53F is more laggy that ITL41F or ITL41D, so it is not a yakju vs yakjuux issue, it is a 4.0.1 vs 4.0.2 issue.

Radio performance varies with a huge number of factors. If you are happy with how one radio works, use it. If you want to see if another one is better, try it. If you don't like it, flash back. It takes all of 30 secs to flash a radio.

If you believe this, then I suggest that you do not flash older builds and OTA update to a newer ones. This process adds more files to your ROM, and is not as clean as flashing the latest build from Google's factory image site.

When the next version of Android is released, the full version will likely be available on Google's factory image site shortly before OTA's for yakju start rolling out.* If you don't mind redoing your settings, apps, etc., it is better (and faster) to flash the full build, instead of updating your current build.

*My assumption based on release dates for previous versions.
[Samsung Galaxy Nexus] greeced:
Question efrant.

I relocked my bootloader purposely.

If I wanted to test other radios does the bootloader need to be unlocked?

If it does, no big deal, I just won't do it
[Samsung Galaxy Nexus] efrant:
If you rooted and then re-locked your bootloader, yes, you can test other radios. If you did not root, and re-locked your bootloader, you can NOT.

This is why I always recommend that the first thing that people do after purchasing a Nexus device (even before booting it for the first time), is to unlock the bootloader, and leave it unlocked. It has no negative effect whatsoever on anything, including OTA updates. However, it brings significant functionality. And if you ever need to re-lock it (which I can't think of a reason why you would), you can do it at any time.

In your case, you could have tried whichever radio you wanted with no issue if you would have left it unlocked. Now, if you want to try a new radio, you will need to unlock again, which will erase all of your data.
[Samsung Galaxy Nexus] skyblaster:
Ever since I converted to yakju, my Market home screen has not changed. It's the one advertising the official NFL apps. Anyone else have this issue? It's Market 3.4.4 and I've force stopped and cleared cache a few times now with no change.

Cross post: http://xdaforums.com/showpost.php?p=23109032&postcount=83
[Samsung Galaxy Nexus] greeced:
I've looked at a Stock SGS, and a stock SGSII, and all have the same home screen. Google simply hasn't changed it yet, has nothing to do with yakju
[Samsung Galaxy Nexus] AdamUpNorth:
efrant, you da man. Thanks for all the tutorials in your signature. Bootloader unlocked and rocking yakju 4.04.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mbucks911:
anyone know why the voice control that was on the i777 (att) was taken off the skyrocket. its weird that they would do that
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] alude904:
Are you talking about vlingo? Go download it from the market. Or another voice control? I hadnt noticed any difference between the two
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mbucks911:
there is a samsung voice control app that is on the i777 that is not on the i727, on the i727 there is only a voice search feature
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 00mred00:
Yes...that app is also known as vlingo and you can download it from the market

Its the exact same app.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] noberly0203:
I have been using speektoit from the market. I have tryed several others including vlingo and this is best so far still needs some work but good. Closest to siri I could find.