yashsingh1/xdaforums huggingface dataset:
[Motorola Atrix 2] jimbridgman:
The fxz files will not "officially" be release, they will have to be leaked, as Motorola has already said they will not release them. So when they pop up, I can not say.

Did you say that you tried to get a warranty exchange? If so did you tell them that you did something? If you tried and told them you did something, then you are toast. If not then just tell them it won't boot, get them to exchange it. whatever you do, don't ever say you did anything and play dumb, act like you are computer illiterate, they will most likely help you, that is what I did when I broke my bootloader, and they asked me all kinds of things, like if I could get to fastboot (I just played dumb and said huh, what, how do you do that?) they exchanged it for me.

If you have not tried to get an exchange I suggest you call the 800 number, It is posted on this board. Just use what I just said above as a guide.
[Motorola Atrix 2] JRW 28:
LoL, good one!!!

Have to admit I'm having some withdrawals myself :)

I'm just glad we've had someone like Jim on our side who has stuck through all this. I know I have been to the AT&T store several times myself looking at different phones but honestly there just isn't anything out right now that makes me want to give up on this phone!

---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------

I would try a Motorola warranty exchange instead of waiting things out! That's a long time ti be without a good phone.
[Motorola Atrix 2] mtnlion:
There may be some hope for fxz. Motorola has stated that the update prerelease soak test has been pushed to January due to a change request. When that test is issued we may be able to get a useable stock firmware to restore with. I'm keeping my fingers crossed.
[Motorola Atrix 2] halfevildruid:
I know I bailed on the atrix 2 and ATT. I actually ended up on Sprint with the. EVO 3d and living it. Anyway have you all tried booting recovery from fastboot?

Fastboot boot recovery.img

There is a bootloader on the EVO 3d that will not allow kernel flash unless recovery is started from fastboot... Just an idea
[Motorola Atrix 2] jimbridgman:
There is not a recovery.img for us to boot to. We now have the fxz so. The fun with modding has begun, and several of us are hacking away right now on new ROMS for the community, one of the reasons this thread was created, and why things are a little quiet in here right now.
[Motorola Atrix 2] frycook15:
An fxz was released yesterday for our atrixes

Jim u seem to post about 2 seconds before I do lol
[Motorola Atrix 2] jimbridgman:
I just PM'd a few brave souls to alpha test the first stock deodexed ROM, here. So hopefully things go as planned and we can have a New ROM or two for everyone next week.
[Motorola Atrix 2] farshad525hou:
So any news on custom ROM'S. Sorry if I sound a little anxious...
[Motorola Atrix 2] jimbridgman:
Right lfaber06 and I are working two Roms I am workin on CM7 and he is working on CM9.
[Motorola Atrix 2] farshad525hou:
That pretty awesome! So just to be clear we don't need a BL unlock to flash CM7 or CM9 right?
[Motorola Atrix 2] Calundle:
Nope. The locked BL just denies us the ability to flash new kernels and radios.
[Motorola Atrix 2] farshad525hou:
I can safely say I am very excited! :)
[Motorola Atrix 2] digitalferg:
This is some good news! I mean, I want to be unlocked for custom kernel and radio options, but I am stoked if I can at least run the custom ROMs!

-Ferg
[Motorola Atrix 2] farshad525hou:
Again not to sound so anxious.. but any news? :)
[Motorola Atrix 2] jimbridgman:
lfaber06 has already released the first stock based ROM, it is posted in the dev section.

He and I are both working on porting Cyanogen right now. He (lfaber06) is porting CM9, and I am porting CM7. These are not something you will see soon, as they take a ton of work to make happen. lfaber06 has already posted a very beta of CM9 again in the dev section to play with. Sorry there is not better news but with there only being 2 of us, and the amount of work, this is not something you will see very soon.

Jim
[Motorola Atrix 2] matt99017d:
Jim, keep up the great work!
[Motorola Atrix 2] alteredlikeness:
Bumping this thread for attention...:p

Plus, I need to ask for some help in building something... just a simple test rom for starters - but I cannot (for the life of me) get a stable zip-able build. What am I missing? (Trust me, I've searched... I like to figure things out for myself before asking for help... but...)

Here's what I've got, and what I've been up to:

Toshiba Satellite P775-S7215

Windows 7

Java JDK (jdk-7-windows-x64)

Cygwin (cygcheck version 1.123)

dsixda's Android Kitchen 0.192

Tried using the Stock rooted 2.3.6 system.ext3.tar file from a CWM backup to set up the working folder and let the kitchen do it's work and build the rom (with and without deodexing the apps & framework)...

Tried pulling the /system folder with 7zip and dropping it the kitchen's working folder, then build...

Looked closely at other A2 roms' structures to compare...

"Borrowed" the updater-script from Victory (since I want to make a flashable zip, and that rom has the basic symlinks needed)...

Tried using the Kitchen's updater-script...

Tried just re-building someone else's ROM directly...

Even tried doing it without the kitchen, using Sign+ (but that doesn't even give me a full zip package - didn't flash that)...

So, it seems I can manage to get it to build properly, and everything seems to install well through CWM... I've managed to log in to google, and get to the homescreen, with everything seemingly loaded... got SU, got a2bootstrap.. And I'm able to get ROM Manager (as I'm fighting off the auto-updates) from the Market. But, then it starts continuously reloading the homescreen... constantly.. then I'm not able to get into bootstrap, so I'm forced to flash the fxz.. Just tried ROM05 tonight (and there were others before ROM01), just to give you an idea of how many iterations and variations I've tried.

My questions:

Before I go and set up Ubuntu on my machine, can rom building be accomplished with Windows, or does one require Ubuntu/Linux? Do I need the JDK for 32-bit (even though my system is 64-bit)? Do I need to update the Kitchen's tools folder with our device build (if so, how?)? Is it only a permissions issue (though I tried fixing permissions through recovery after one install)? Etc..??

I'm sure it's something simple that I am missing or overlooking, but any help would be appreciated. PM's or posts... Thanks in advance.
[Motorola Atrix 2] cogeary:
Well... you might be able to get by with using Cygwin, but in the long run you will want to move to Linux.

As to your problem... I don't know exactly where you went wrong, but I can think of a better way to do what you're trying to do. AFAIK, the Kitchen can build a working directory from more than just a flashable zip. I am using it to make ROMs directly from .img's inside the fxz's. I am pretty sure it will let you build a working directory from the system.ext3.tar of a CWM backup. The advantage to doing it this way is that the kitchen will detect symlinks and permissions and automatically add that to a generated updater-script.

Once you do this there are two more things you should do :p. First, go to your working directory/META-INF/blah/update-script. Change one of the first lines from "FORMAT ..." to "delete_recursive ...". This might only be for if you are basing your ROM off of a different firmware, but either way it still works. Also, create a new file called "edison" under tools/edify_defs of your kitchen. Copy+paste this into the file and then save it:

# Motorola Atrix 2

change_mnt=yes

param1=ext3
param2=EMMC

param1_sdcard=vfat
param2_sdcard=MTD

use_cache_not_tmp=yes

sys_mnt=\/dev\/block\/mmcblk1p21
cache_mnt=\/dev\/block\/mmcblk1p22
boot_mnt=\/dev\/block\/mmcblk1p15
data_mnt=\/dev\/block\/mmcblk1p25
sdcard_mnt=\/dev\/block\/mmcblk0p1
webtop_mnt=\/dev\/block\/mmcblk1p24

^About 90% of this information is from Jim so give him a big thanks. Hope this helps!
[Motorola Atrix 2] alteredlikeness:
Thanks!

Thank you, and Jim, sooo much!:D I think this info is exactly what I need to make it work (especially that "edison" file, i hope.. at least that's what I thought I was looking for..)

But, to dig into this a little more (for myself, and possibly others)... when I try to do it with a system.ext3.tar the kitchen does not offer me a dummy boot.img. It extracts all of the system files, then it starts making an update-script and removing the symbolic links from the bin and xbin folders, physically removing the files from those folders. So, do I replace those missing files, or..? I've tried to let the kitchen build the rom without replacing the files myself, but then they never return and I'm too freaked out to flash it.. so, I usually replace them. I've tried just using a known working updater-script, also tried letting the kitchen do it for me. I've even tried tricking the kitchen by tossing a fake boot.img in the .tar file :rolleyes:... I've tried so many different ways by now, I lost track.

I got a feeling I'm getting closer though.. Your response, cogeary, is very much appreciated!! Big thanks to those who pm'd me also!
[Motorola Atrix 2] cogeary:
It's OK, the files won't return until you actually flash the cooked ROM - the kitchen deletes the linked files but makes the updater-script recreate them.
[Motorola Atrix 2] JRW 28:
Very good subject as I too have tried building a Rom from a backup and just the system.tar anf aleays been scared to flash the Rom after build because the updater-script looks nothing like what I have for my base Rom that works. It removes a bunch of the sym-links and then when it rebuilds yhe updater script it looks nothing like what I run right now.

But the A2 folder I will def add and I'm still chasing why my inverted apks will not load upon boot. No one seems to know this answer or if they do they won't share :/
[Motorola Atrix 2] alteredlikeness:
That's exactly what I needed to hear! I suspected so, but... Thanks again!

Removing symlinks at the moment...

Plus, after adding the edison file it actually showed me the device name when setting up the working folder - good sign!

...gotta have faith in the kitchen... ;)

-------

Update: Well, I tried again.. This time, in my haste, I forgot to wipe data/factory reset before installing the zip (though i happened to wipe dalvik and cache). Which turned out to be in my favor, as I was able to get past the Accounts Setup (other times I would get stuck there after logging into Google - hit "Done adding.." and boom, FC, and stuck at that screen - though I was able to get online and to the dialer through Voice Search, and receive texts and calls). Another huge bonus was that Recovery on Boot was still there (just finished restoring :)).

But, very soon it started reloading the homescreen again.. the same prob I've had for the last umpteen times. I managed to see my CPU usage on Widgetsoid and it was at like 93%, then I made it into "Running services" and just started stopping everything that was running, thinking that it would help and took another look at my CPU usage - it was at 98%! Got a bad file or two somewhere...

Tomorrow's another day! (but, so is the day after that, and the next, and so on, and so forth... now it's time for bed.....)
[Motorola Atrix 2] hankbizzo5:
Bump this up for the useful info going to need to reference soon.....
[Motorola Atrix 2] Ravikirancg:
access denied

I tried downloading the handset emulator http://developer.motorola.com/tools/android-sdk-addons/addons/Motorola_SDK_Add-on_for_ATRIX2/

but it says access denied.. I have registered and have activated my account.. can any one put up a mirror please?
[Motorola Atrix 2] lkrasner:
you can see the option to install it right from the sdk manager.
[Motorola Atrix 2] jimbridgman:
Bump!!!

For some our more newly acquired wanna be devs...
[Motorola Atrix 2] alteredlikeness:
;)

And, I should note that my former issues with failed zip package builds were mostly caused by edits I made to the AndroidManifest.xml - When I pushed them separately to my phone they worked, but not together with the entire system - I worked around that by not editing it, and going after the other xmls... Maybe JRW could enlighten us (or me) on that subject?? - Did you end up re-signing everything?
[Motorola Atrix 2] JRW 28:
Something I had to find out the hard way and on my own as noone would help me.....

ANYTIME you alter the AndroidManifest you have to sign ALL the system apks. If not the apk with the AndroidManifest you altered WILL NOT run at boot. The signatures all have to match upon boot and anytime you modify AndroidManifest I'm guessing it changes the apks signature.

Another thing to remember also when signing all your system apks is ANY apk that requires updates from the market need NOT to be signed when signing the rest of the system apks as this will cause that apk to not be able to be updated. Simply pull that apk out before signing and then reinstall it in system after signing.

It was a huge pain in my arse in the beginning but once I got it figured out it was a breeze afterwards.

Hope that helps some :good:
[Motorola Atrix 2] alteredlikeness:
Thanks for sharing that! It's like a missing piece in the puzzle...

At one time I had the idea to track down all of the apks that had Android Manifests with the same original dates, and just re-sign all of those apks together - but never went through with it. I think that's kind of along the same lines, though...

Sent from my phone's mind
[Motorola Atrix 2] jimbridgman:
Great info! Thanks guys!!
[Motorola Atrix 2] Fall of Enosis:
First off, thanks for the Bump Jim. +1

Now my question is, I have been using the Android kitchen for a while. And as many of you know I have been trying to get the CRT screen ON effect working for our phones for a while. However, I have NEVER been able to successfully flash a ROM I have made with it.

It keeps giving me a "0" fault in CWM which I have been told is a signing issue?

Anyways, this is my procedure and maybe someone can enlighten me on what I'm doing wrong. FYI: Altered has been a huge help with this, but it's probably just silly me who is doing something wrong. So here goes:

I have been using Lithium as it is de-odexed which makes modifing what I need easier. Once I get it working on a de-odexed ROM i'll move onto a Odexed/stock ROM.

In the kitchen I decompile the ROM, the using Baksmali I decompile the classes.dex for the services.jar file. I then have to make many line edits within classes.dex. I make my edits, and then recompile using smali. Once that it is done I replace the the old services.jar with the new, and compile and sign the new ROM.

Also I have tried just to make a update.zip with the new services.jar file and I get the same CWM fault of "0".

But I have never been able to get any ROM to flash. Even when I took Romulus and just edited the bools to try and get my CRT back the dang thing wouldn't flash.

Anyone have an idea as to what I'm doing wrong?
[Motorola Atrix 2] jimbridgman:
Do you have the edison file for the kitchen? This file forces the kitchen to use an edify style updater-script.

Here is the edison file:

http://db.tt/V7IAmquw

Put it in the tools/edify-defs directory in the kitchen directory.
[Motorola Atrix 2] alteredlikeness:
I would definitely make sure that that one .jar file works by itself, before trying to get it to flash with an entire ROM... You try adb push? Or the taboo Root Explorer method? It might just be an error with your zip package and updater-script...
[Motorola Atrix 2] JRW 28:
Fall of Enosis... not saying you're doing this the wrong way but there is a MUCH more simpler way to edit smali ;)

Lets get one of your problems fixed first though. If your built roms aren't booting lets get this solved first. You def need to add the file that Jim posted into the tools/edify_defs folder to get the kitchen working properly. If after adding that and your rom still doesn't boot, since your using Lithium as a base, simply take the updater.script from Lithium and swap it with the one kitchen built for you ( JUST MAKE SURE ITS V1.3 OR V1.3.1). If your rom now boots you know it's the updater.script and can start looking deeper into what and why.

Now lets get into the smali edits. There is a much easier way of editing these smali files but it will require you setting up smali and baksmali on your desktop. It just simply depends on what you're comfortable with.

By having this set up it saves a lot of time as you simply pull the classes.dex file out using winzip or 7zip and then use baksmali to decompile. Once you have made your edits recomplile using smali and then simply reinsert the classes.dex file back into the file it came from. Winzip or 7zip will make sure it is installed back correctly. With this methos it is simply a pull and reinsert method and you are through in very little time.

I can't walk you through how to set this up but you can google it as that is the way I set mine up and I'm thinking there might have even been a youtube video as well. So much easier and a breeze making these edits now :)
[Motorola Atrix 2] jimbridgman:
Is no one using the APK tool?

It is just an awesome tool to pull apart and re-build the apks, it does all the smali/backsmali for you.

Here is a link to grab it.... There is a version for both linux and windows in the downloads page.

http://code.google.com/p/android-apktool/downloads/list

This thing makes it so much easier to edit all the files, and it will build the manifest for you if I remember right.
[Motorola Atrix 2] JRW 28:
Jim I use APKManager 4.9 for all of my apk editing, I found smali/baksmali when I was getting the reboot option finished for Lfaber06 and just found it to be simpler and quicker as I was spending a lot of my time getting out of soft bricks at the same time :D

It seemed a lot of the themers were using it so I gave it a try and haven't looked back.
[Motorola Atrix 2] cogeary:
This. The only thing I have to add is to make sure that, at the top of your update-script (the one that the kitchen makes before it converts it back to updater-script), change the "FORMAT" to "delete_recursive" (without the quotes). If you try and format it that way it will remove a signature on the /system partition and stop it from booting.

+1 for apktool! However, I recently began doing something similar to what JRW did in order to get around signatures. I think we've got it figured out pretty well, in terms of when to sign what, but sometimes that can be a big hassle. So after I make the xml edits and/or smali edits, I build and then go to the newly created /build directory (not /dist). Then I just drag+drop all the files that I modified back into the original apk. Works like a charm and the signatures always match.

EDIT- Well... kind of. It works fine for classes.dex, resources.asrc, and everything else in res/, but if you change the AndroidManifest you have to resign all system apk's.
[Motorola Atrix 2] alteredlikeness:
I found this smali/baksmali package quite a while ago, and just stuck with it... and I also use the method JRW describes with 7-zip for putting the new classes.dex back (as well as other files) in the jar/apk - that's a great little tool, 7-zip - it makes life a lot easier.. (and i'm sure winzip works just as well).

+1 for APK Manager (i'm on 5.0.2 though)

EDIT: Duh! Yes, I have been and will continue using apktool... plus, it's used in all the APK Manager/editing tools... is there anything else??

P.S. - Development of apktool has been taken over by someone else, and a new version (1.4.9) has been released here: http://xdaforums.com/showthread.php?t=1755243
[Motorola Atrix 2] Fall of Enosis:
Thanks SO much guys. As always. My son is on the PC right now. So I'll give it a whirl later today and update you guys here.

THANKS AGAIN!
[Motorola Atrix 2] alteredlikeness:
Regarding the CRT effect bools mod in framework-res, another method I've come across is to compile, or zip, your apk with zero compression, or in "store" mode.

I've read that it's done to preserve the size of the resources.arsc, which apparently can not shrink in size (possibly related to the signatures?) - but I guess it can be larger(?), because from my experience, usually APK Manager increases it's size if you delete the original when re-compiling. (I'm trying to state this loosely, since that's how my grasp is of it...)

Anyway, it's briefly described here (specifically for the CRT effect): xdaforums.com/showpost.php?p=17139168&postcount=1151 ...

And, I honestly don't recall all of my endeavours, but I did use that method to turn off CRT - but I have made many other bools mods in there and in other apks and just compiled and compressed with APK Manger defaults (which is basically set at max compression - so basically, I don't know how it all works, but it somehow works for me:) (sorry - that doesn't sound too helpful)).
[Motorola Atrix 2] Fall of Enosis:
it's helpful mate. :)

I've learned this whole developer thing is all trial and error. Lol.

And for anyone who's interested, THIS is the guide I have been using to try and get the CRT on effect.
[Motorola Atrix 2] jimbridgman:
Here is a great beginners guide to ROM building using cygwin...

http://xdaforums.com/showthread.php?p=17758451

Hopefully we can encourage more people to give ROM dev work a try. This guide comes from a non programmer.
[Motorola Atrix 2] Drgravy:
I just wanted to share my latest experiment:cyclops:

I've been trying to make a deodexed version of the at&t ICS leak something I could use as a base to mod and tweak to my liking and possibly release a rom someday but I'm nowhere near that yet

I've been using dsixda's Android Kitchen to deodex I had to be very persistant to get it to work

now I want to add that I added the edison file and changed format to delete_recursive in the updater script

it actually fllashed ok but when i booted it all I got was a blank screen (thought I bricked) but thankfully I was able to use Jim's script to get back to 2.3.5 ( I am getting to be a pro at that now I think I've done it a dozen times now.)

Ive tried converting the rom with boot menu manager <----- did not work

tried signing the rom not signing the rom

tried just replacing the app and framework folder in a backup but that did not work either

but I did give up just yet

I thought I would try an updater script like this

show_progress(0.1, 0);

ui_print("mounting system");
mount("ext3", "EMMC", "/dev/block/mmcblk1p21", "/system");
ui_print("deleting app");
delete_recursive("system/app");
ui_print("installing app");
package_extract_dir("system/app", "/system/app");
ui_print("deleting framework");
delete_recursive("system/framework");
ui_print("installing framework");
package_extract_dir("system/framework", "/system/framework");

show_progress(0.1, 10);
show_progress(0.2, 0);
show_progress(0.2, 10);
ui_print("dismount");
unmount("/system");

and guess what it worked!

and now I have a backup of a stock ics leak deodexed

I really wanted a flashable zip but I'll take it

finally

Pretty proud of my self for that

heck 6 months ago I thought a root was in the dirt

now I can start modding to my liking

A big thanks to all the devs here

I've been tearing apart your roms/mods and learning from it

Thanks
[Motorola Atrix 2] farshad525hou:
Just as a piece of advice... when mounting partitions use the busy box command. So mounting system would be run_program("sbin/busybox", "mount", "/system");
[Motorola Atrix 2] Drgravy:
Thanks.

Any advice is always appreciated
[Motorola Atrix 2] farshad525hou:
Sorry typo above. The actual command should be :

run_program("/sbin/busybox", "mount", "/system");
[Motorola Atrix 2] jimbridgman:
Bump... Bump... Bump...
[Motorola Atrix 2] Ravikirancg:
How can I run a .sh shell script in cwm? I mean I extract it to tmp, change perms and then need to use run_program. But that gives me errors.
[Motorola Atrix 2] jimbridgman:
What is your run_program() syntax? You should use busybox and /system/bin/sh in your run_program command in the updater script.

Also what is the error that is thrown?