Database Develop

[PROGRAM] Updated:One Click Root/UnRoot (Mac and PC)

Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.​
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.​
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)​
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su​
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.​
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.​
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..

the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..

junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.

I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?

s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App

TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props

please do it for Mac OS.
best wishes...

Awesome application thanks!
Sent from my SGH-T959 using XDA App

Great, easy app. Works!

Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.

alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?

TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?

Relase src code. I may be able to port to unix/macosx and/or java.

I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks

kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.

Yeah release the source... Ports will follow if necessary

jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.

Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.

Lets see the java port. or even an APK to do so

jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.

☢Upgrade to Froyo (Droid 2.2) RIGHT NOW on Droid X ☢ Froyo 2.3.13 Deodexed is HERE☢

☢Upgrade to Froyo (Droid 2.2) RIGHT NOW on Droid X ☢ Froyo 2.3.13 Deodexed is HERE☢
☢Important Notes☢
Watch a Video Tutorial on How to Upgrade to Froyo
Links for Downloads
Get update.zip form HERE or HERE
Root your device with the 1-Click Root Method found HERE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Only use this method if stuck in bootloop or have errors installing froyo
☢Important Notes☢
* Applying SBF will perform a factory reset and wipe all data off your device
* I have tested this method and had no problems
To Apply SBF
1a. Download RSD Lite
SBF INSTRUCTIONS: Install the RSDLite 4.7 program by double clicking on the program.
Move the pst_flash.ini file into the following folder --> Program Files/Motorola/RSDLite
1b. Download .604 update HERE rename to update.zip and place in root of SDcard
1c. Download SBF from HERE
2. Install the drivers that apply to your Operating System. (attached are Win 64 bit drivers)
3. Unzip the SBF into a folder.
4. Open RSD Lite and find the UNZIPPED SBF
5. Put your Motorola Droid X in bootloader mode (With Device off, Press Volume Down and camera buttons then press power). Now connect the Droid X via usb.
6. Click start and sit back.
7. Device will reboot automatically and you will need to remove battery to power down
To Apply .604
1. Press home button then power button to boot in recovery.
2. Press search key to show recover options
3. Use volume rocker to move down to "run update.zip"
4. Press okay
5. After completed scroll down to format device and click ok
6. After formats complete scroll up to reboot device
Use 1 Click Root
1. Download File droidxroot.zip from HERE
2. Plug in droid x and set to pc mode
3. Made sure USB debugging is enabled (settings...applications...development)
4. Run 1 Click Root
5. You have to toggle bluetooth and press continue at same time (when it ask you to) Can try again if it doesn't work the first time
6. You can now Apply Froyo 2.2 Update

Official Froyo Changes
Applications
�� The Froyo version of the Android OS is designed to provide improved application performance.
�� Froyo gives you the option to Allow automatic updating for Android Market apps you download.
�� Froyo brings the ability to rotate your phone up to 270° and your apps will display properly.
�� Froyo offers tips, shortcuts, and assistance from the home-screen widget.
�� You will see improved video playback and applications will open faster and tasks will complete quicker.
�� Froyo gives you the option to select where applications are installed. You can select the phone memory or storage card memory depending on your needs.
�� You can choose to automatically update Android Market you download. This way you will always have the latest application installed.
�� Your applications will work when the phone is in portrait mode or turned to the left or right in landscape mode.
�� The home-screen widget makes it easy to get to know your new phone, read tips and get assistance.
Screen Brightness and Power
�� Froyo allows applications to override the OS power settings.
�� Froyo Car Dock applications will offer brightness controls making nighttime use of Car Dock applications more comfortable on your eyes.
�� Froyo allows applications to manage power settings to maximize battery life.
Gmail Application
�� Froyo allows you to quickly move through your Gmail messages using the new forward and back buttons.
Flash Support
�� Froyo allows you to download and install Adobe Flash so you can view your favorite Flash powered websites and access Flash based games.
Exchange ActiveSync Integration Improvements
Corporate Exchange email admins will appreciate the greater control provided by these Froyo powered improvements
�� Wipe after a certain number of password attempts and enforcement of auto lockout time.
Froyo corporate email security improvements give Exchange admins the ability to:
�� Remote wipe or remote lock the Android Smartphone1
�� Apply and enforce password length and complexity rules.
�� Apply rules to automatically wipe the Smartphone after the maximum number of invalid password attempts.
�� Apply inactivity timeout rules to automatically lock the phone.
Camera and Camcorder
�� Froyo enables the LED flash during video capture.
�� The LED flash improves your videos captured in low light situations.
�� Easy-to-use video formatting tools let you quickly format video for sharing via upload to video sharing services or video messaging.
�� The camera functions are easier to use with the on-screen buttons to control zoom, white-balance, focus and geo-tagging.
Bluetooth
Froyo Bluetooth voice dialing enhancements will confirm your voice commands both on-screen and by repeating your commands.

Custom recovery been out for this thing a whole half hour and no replies?? How is this thread not exploding! =P

Thanks guys for all your hard work.

Yessss!!!
It has finally happened! Now all we need are ROMs. I understand we may not have kernel support *YET* but a stock 2.1 rooted ROM still makes me happier than nonblur motoblur Droid X UI. Blah.
So once the OTA for 2.2 comes out and we have the new kernel do we think that the custom recovery will be able to work the same way? Then we can have stock froyo yes?

elkniwcire said:
It has finally happened! Now all we need are ROMs. I understand we may not have kernel support *YET* but a stock 2.1 rooted ROM still makes me happier than nonblur motoblur Droid X UI. Blah.
So once the OTA for 2.2 comes out and we have the new kernel do we think that the custom recovery will be able to work the same way? Then we can have stock froyo yes?
Click to expand...
Click to collapse
I sure hope so, now we gotta wait for official froyo so we can grab the kernel off it and just install a stock barebones froyo without all this blur garbage
Sent from my DROIDX using Tapatalk

Thank you, thank you, thank you!
I used the market app, which worked perfectly

Great job just purchased it off market place. Now let the roms begin

Congratulations...
I would like to congratulate and applaud the team of CM and bow to Koush for his work..
I don't have a X, as I did, but own a Evo, but, there is NO discrimination where I come from in Droid Town...

bignadad said:
http://www.koushikdutta.com/2010/08/...-recovery.html
Well, this was a *****.
Caveats:
This is not a *real* recovery. The way this recovery works is by hijacking portions of your boot process during system initialization and starting into recovery instead. So, if you hose your system *COMPLETELY* you will need to SBF. Specifically, if your logwrapper, logwrapper.bin, or hijack binary are missing from /system/bin, you will be screwed.
Do I have to be rooted to run this?
Yes.
So can we now install custom ROMs?
Yes, but you can't replace the kernel or boot image. But really, once you have access to /system, anything is possible. It will just take a little hackery.
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
How do I boot into recovery?
You can manually create the /data/.recovery_mode via a terminal file and simply reboot, and you will be in recovery. Or you can use the handy Droid X Recovery Bootstrap application to reboot into recovery.
What if my phone won't boot? How do I get into recovery without the app?
When the hijacker runs, it will automatically create the "/data/.recovery_mode" file after it finishes. This tells the system that the next time it boots, it should boot into recovery. But, when the system starts, the Droid X Recovery Bootstrap will then delete that file when Android is fully started, to prevent you from booting into recovery. So what does this mean? If you fail to boot, simply pull your battery, and your next boot will be into recovery (unless your /system is *really* hosed, in which case you need to SBF).
How do I fix my phone if I really mess it up?
Use an SBF. Google it. http://twitter.com/b16a2smith/status/21544626803
Why does the Droid X Recovery Bootstrap start on boot?
As mentioned above, it needs to log that your phone booted successfully and recovery mode is not necessary. It also replaces your "adb daemon" with one that has root permissions, allowing for easier usage of the adb command.
Will this work with ROM Manager?
Yes, but not yet. I need to make some minor updates to ROM Manager first to support this recovery. Future recovery updates will come through ROM Manager.
Is this open source?
Yep.
Recovery: http://github.com/koush/android_bootable_recovery
Droid X Bootstrap: http://github.com/koush/DroidXBootstrap
Droid X Hijack: http://github.com/koush/android_vendor_motorola_droidx
OK STOP TALKING, WHERE DO I GET IT?
You can donate and grab it for $2 off the Android Market (search for Droid X Recovery Bootstrap), or you can download it for free here: http://koush.tandtgaming.com//motoro...XBootstrap.apk
Click to expand...
Click to collapse
this op is an exact copy paste of koush's post. give him credit in the post. you didnt take the time to write this. CREDIT FOR THIS GOES TO KOUSH. you mentioned him once, last line of your post in the smallest font possible

CM and Koush pull through once again!

nandroid backup complete! Thanks koush!
Really hoping to see bird/rain's Froyo release soon too. There is a thread in alldroid that they got custom kernels working with the dev phone, lots of stuff happening at once!
http://alldroid.org/default.aspx?g=posts&t=646&p=4

Now we wait for a stock 2.1 rom or a 2.2 rom without kernel. Ill b happy just to be rid of blur tbh
Sent from my DROIDX using Tapatalk

This is fraking awesome, can't wait to get home and mess around wit it
Sent from my DROIDX using XDA App

I've been wondering, since you can't use roms with different kernels. Would it be possible to find a Rom, lets say a 2.1 SENSE UI Rom for a Hero or something with the same kernal. Does that mean that you could flash your rom to that or is the kernal on the droid x different than a kernal of the same number and such on a different device?

This is awesome, looking forward for some roms

mattyboy1013 said:
this op is an exact copy paste of koush's post. give him credit in the post. you didnt take the time to write this. CREDIT FOR THIS GOES TO KOUSH. you mentioned him once, last line of your post in the smallest font possible
Click to expand...
Click to collapse
well duh! I'm no rookie to making post here... perhaps that is why i put the DIRECT LINK above the actual post from kousch.... so when the user clicks that they see the actual page by kousch himself.... NEVER did i state that i had anything to do with this... I'm just passin the news along.... is the link not mentioning him????? i think everyone got that but you..... thanks for stating the obvious

oXeNo said:
I've been wondering, since you can't use roms with different kernels. Would it be possible to find a Rom, lets say a 2.1 SENSE UI Rom for a Hero or something with the same kernal. Does that mean that you could flash your rom to that or is the kernal on the droid x different than a kernal of the same number and such on a different device?
Click to expand...
Click to collapse
oXeNo - While I would love to see the same thing, unfortunately that won't work. The kernel is what talks to the hardware and the hardware, as you know, is very different on the X from HTC devices (especially the fact that the processor has a separate GPU). So, this would require a port of the software and I've come to learn that sense is so deeply in bed with each specific setup that a port would be a huge task.
Sent from my DROIDX using XDA App

Has anyone tried to remove this yet by using the SBF or some other method? Before I put this on here, I wan to make sure I can get rid of it too.

[GUIDE] – Flash SBF/Root/Recovery/DeOdex -> A to Z - SBF 2.1.1 + 1080p + P.ROMS!

After various requests, official and unofficial I have taken the time to consolidate all the needed information to make the flashing process as simple and as noob friendly as possible! Please follow the guide below!
This is the A to Z guide on how to Flash custom SBF, Root, Install Recovery and enable such things as GreyBlur and 1080p recording on the Atrix!
After the release of 2.1.1 from France’s MotoAtrix I was anxious to see what could be done on this SBF.
As we know this is the latest SBF released on the 29th of April, 2011. It is, based on the version numbers, the next step forward from 0.37 on the Stock BELL phone.
After a lot of benchmarking (now 2800-2900 hundered on Smartbench 2011) and testing as well as feedback from the Intl/Bell community, it seems this is the most responsive and battery efficient SBF. I’m amazed at how speedy the phone is, including boot up (which is at least a third faster than 1.4.2)… HSUPA is unlocked as well on this SBF, so this is good news for us as there is no need to flash custom, sketchy mods to enable this on our phones. As for the fingerprint reader, the driver appears to have been updated so it is incredibly responsive so this is an improvement although 1.4.2 was great in this regard.
*To find out more about HSUPA, read the FAQ at the end of the post.
At the moment though, as it stands I can only recommend you install GreyBlur as it is currently the one with the least amount of bugs, and the BEST battery performance.
DISCLAIMER: All of the procedures below require some basic computer knowledge and could potentially brick your phone. Please proceed with caution and make sure you read everything CAREFULLY.
Everything has been tested but requires that this guide is followed TO THE LETTER. AT&T ATRIX NOT SUPPORTED
>> Be aware that sections of this guide apply ONLY to 2.1.1 and now 2.2.3 and are NOT for AT&T Atrix at all! <<
Please check out this AWESOME VIDEO GUIDE HERE! (Thanks to J-Roc!)
Part 1
Part 2
Part 3
Part 4
Make sure your device is in the list below:
Supported devices:
South Korean Atrix (Information pending)
Brazillian Atrix (Base OLYLA U4 0.50.0)
Argentinian Atrix (OLYLA U4 0.50.0 Variant)
Canadian Atrix (OLYLA 0.37.4)
Mexican Atrix (Information pending)
Australian Atrix (OLYEM 1.4.2)
UK Atrix (Orange. Information pending) <----- DO NOT INSTALL GINGERBLUR/GREYBLUR... just 2.1.1
French Orange Atrix (OLYEM_U4_1.3.3)
Required files: (Download all of these as needed)
RSD Lite 5.0 -> Here
Win 7 Drivers x32 (if applicable) -> Here
Win 7 Drivers x64 (if applicable) -> Here
Download 2.1.1 SBF if you are going to Flash this.
OLYEM 2.1.1 SBF -> Here
Mirror -> Here
The Preparation script includes the needed APKs to obtain root and install Clockwork Recovery.
Seven’s Prep Script - > Here
GreyBlur 2.1 -> Here <-- 100% working, great performance.
GingerBlur 4.0 -> Here <-- Nasty startup bug, work around soon.
Seven’s BlurFix -> Here
Seven's DeOdex Tool 2.0 -> Here
GUIDE INDEX:
STEP 1: How to Flash the latest SBFs (Guide for EVERYONE)
STEP 2: ROOT and RECOVERY (and now: DEODEXING!)
STEP 3: Flashing GreyBlur/GingerBlur
STEP 4: Apply BlurFix Patches: Fix issues with BLUR Roms and enable 1080p recording + tweaks!
STEP 5: APN Information and FAQ!
ENJOY!!
GingerBlur/GreyBlur was created by XDA's very own Kenpenneth! Support his work!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

STEP 1: How to Flash the latest SBF (Guide for EVERYONE)
This is a quick guide on how to flash the latest SBF.
This applies to all SBFs as well so use as needed but operate with caution as doing something wrong here could seriously damage your phone. Make sure the SBF file you are attempting to flash is compatible with your phone. (RESEARCH, do no ask in these threads as Google will easily yield the correct results)
-Make sure your phone is unplugged
-Install the required Drivers for your phone (x32 bit or x64 as needed)
-Extract the SBF zip file to your desktop. It will create a folder with a file with an .SBF extension and should be about 1.4gb in size.
-Install RSD Lite using the installer linked above. This will create an Icon on your Desktop
-Execute RSDLite. This process will take a long while the first time, about 3-4 minutes max.
-Once the program is open, plug in your phone in to the computer. Wait for Windows to notify you that the drivers have been configured correctly (takes 2-3 minutes max)
-Unplug your phone from your PC and then reboot your phone.
-As the the phone powers up (Right as the Red M appears) HOLD the VOLUME UP key…
-The phone will display this message: “Starting RSD protocol support”
-Wait about 20 seconds (on the safe side)
-Having the RSD Lite window open, plug in your phone.
-RSD Lite will display your phone information in the bottom and should list it under slot 1.
Status: Connected…
-Click the button the left of START, a button labeled as: “…”.
-Navigate to the SBF file you extracted above.
-Once you have selected this SBF file, the information readout will display in the “File Properties” Window.
Now you are ready to flash:
-Select START
This process will take about 5-10 minutes depending on your computer. You will know this process is finished once your phone has fully booted and about 2 minutes have passed. WAIT the 2 minutes as sometimes people unplug the phone before RSDLite clears and this has caused issues previously. At this point, after having flashed:
REBOOT your phone. DO NOT SETUP until after the first reboot.
-Unplug your phone from your computer, close RSDLite
-After Reboot, complete the MotoBlur setup. (you can skip it but it’s better not to as it is known to cause some issues on some SBFs and phones).
Wait a few minutes and now the phone is ready for the next step.
You have now successfully flashed!

STEP 2: ROOT and RECOVERY
REQUIREMENTS:
External SD card. Make sure your phone has it inside. <– THERE IS NO WAY TO ROOT WITHOUT THIS.
Noob HELP – Skip this section if you are experienced with ADB and debugging mode.
In order to prepare for this download the “Preparation Script” from the Required Files section above.
-Making sure your phone is unplugged go to:
“Settings -> Applications -> Development”
-Enable USB Debugging – Tick the box.
-Plug in the USB cable to the phone
-Wait for the phone to acknowledge the connection.
-Pull down the Notification bar up top and select “USB Connection”
-In this prompt select “None” and press OK
-The phone will reconnect to the computer with USB.
-Unplug the phone and reboot
-After the phone boots up, plug the phone to the computer.
Now let’s move on to ROOT and RECOVERY
-Make sure USB Debugging is enabled. Plug in your phone (if not already plugged)
-Extract SevenPrepare.zip to your C:\ drive, Example: C:\SevenPrep
-Double click SevenPrep.bat
-Follow the prompt. This will basically install GingerBreak and System Recovery
-After the prompt closes, execute GingerBreak from your appdrawer and hit "Root".
-The phone will reboot. After the phone reboots, execute "System Recovery" from your appdrawer and hit "Install Recovery"
-You will get a SuperUser prompt, asking you to either Allow or Deny this application access to your phone. Hit “Allow”
-After a few seconds it will say “Install complete”
Your phone is now Rooted and Recovery has been installed - Stop here if you are interested in keeping your phone on STOCK and are not interested in flashing the Ginger/Grey ROMS. If you wish to de-odex stock 2.1.1 read below, if you do not know what this is, skip it.
DE-ODEXING (OPTIONAL)
If you are interested in theming stock 2.1.1 or installing language packs such as arabic, you will need a De-Odexed ROM. In order to do so I've created a little tool that will get you going.
REQUIREMENTS:
Make sure you have downloaded Seven's Deodex Tool 2.0.
>>Please be aware this tool is ONLY for 2.1.1. Using it otherwise WILL brick your phone.<<
-Make sure USB Debugging is enabled. Plug in your phone (if not already plugged)
-Extract SevenDeodex2.zip to your C:\ drive, Example: C:\SevenDeodex2
-Double click SevensDeodex.v2.0
-Follow the prompt. This will basically install the deodexed system files and give you instructions on what to do next.
-DO NOT CLOSE THE CMD PROMPT.
-After all the files have been copied, simply follow the instructions listed in the BAT file.
If you read the prompt carefully you will see it instructs you do the following the following:
-Open up ADB Shell and type the following commands in this order, one by one:
su
cd /data/local/tmp
chmod 755 install_script.sh
./install_script.sh
Simple! It will take a minute to finish. Once it is done your phone will reboot and you will be de-odexed!

Step 3: Preparing and Flashing GreyBlur/GingerBlur
>> IF YOU HAVE A LAPDOCK READ HERE!! << - >> If not skip this portion and move to: How to Flash GreyBlur!
It just so happens that if you simply flash over 2.1.1 the default keyboard layout for the Lapdock will be stored as AZERTY and your special characters will not function properly. This is mainly because by default the hardware keyboard layout is set to France.
BEFORE flashing GingerBlur/GreyBlur you MUST follow these steps to ensure that the selected Keyboard layout matches your current Lapdock SKU.
You must do the following:
-Dock your Phone with Stock 2.1.1 on your Lapdock.
-Wait for Webtop Environment to properly initialize.
-Once the Webtop has booted, go to the upper right hand corner and click the COG. This will open up a menu.
-Select Keyboard
-Click on the "Test settings box" and type freely using your Lapdock keyboard. As you will notice it will not type what you keyboard layout is unless you have the French lapdock.
-Click the Keyboard Language... button
-This will boot you into Settings->Language & Keyboard Settings
-Scroll to the bottom and you will see two boxes that will allow you select which Keyboard layout you wish to choose.
-Set BOTH of them to English US (if this is your keyboard layout, this applies to Canada, US). If you have a different layout, choose it from here!
-You will notice it will NOT let you set the bottom one untill you unplug your phone and replug it. Follow the instructions!
-Once you have successfully changed these settings go back to the "Test settings box" and type freely using your Lapdock keyboard.
Now it will properly reflect your current layout and these settings will be saved! Move on to the next section below.
How to Flash GreyBlur!
REQUIREMENTS: AC Power Adapter – keep this plugged in until you finally boot GreyBLur.
-Having downloaded either GreyBlur or GingerBlur, copy one of these files the root of your INTERNAL SD card.
-Make sure Recovery has been installed (if you followed the guide above you are ready to go!)
-Once Recovery has been installed, open the program and plug your phone to the AC power.
-Select “Recovery Mode” -> You will receive another SuperUser Prompt. Select ALLOW.
-The phone will now reboot and enter Clockwork Recovery.
NOTE: If at this point you could not enter recovery, it is because you are NOT plugged into AC power. It will NOT work on USB power as this is a security measure so that we can access Clockwork Recovery when our phone is not booting into Android OS.
-Once in Recovery, use the VOLUME UP and DOWN keys to navigate.
-Navigate down to the option “Install zip from SDCARD”, Press the power button to enter that submenu.
-Once in this new menu select: “Choose zip from internal SD Card”
-Select the zip file you copied in the steps above. Example: GreyBlur-2-1.zip
-Once you have selected this zip file, scroll down and select YES.
-The installer will run and once it is finished it will say “Install from sdcard complete”
-Select “+++++Go Back+++++”
-Once at this menu select: “Wipe DATA/Factory Reset”
-Select “Yes”
-It will take a few seconds until this is complete and you will see a message that says “Data Wipe Complete”
You are now ready to start your phone!
-Unplug your phone from the AC power
-Select “Reboot System Now”
You will now see how the GingerBlur/GreyBlur logo as your phone boots up shortly after the Red M “Dual Core” Logo.
-After the boot finished, ALWAYS ALWAYS ALWAYS select “Set-Up”
NOTE: >>SKIPPING THIS MAY CAUSE ISSUES SO DO NOT SKIP IT. SWYPE WILL CRASH. <- This is normal until we apply a fix! <<
-Complete the MotoBlur setup. (In this case, NEVER SKIP THIS….!!!!!!!!)
-Register or log into motoblur blah blah blah you’re done!
-As you are finishing it will prompt you to update your phone. DO NOT UPDATE!!! Just select later….
-Add any needed APNs to enable DATA on your phone. If you don’t know how to do this read the FAQ at the end of this post.
-You will also see a POWER icon on your upper left hand corner. Open the notification bar, click the notification and select the correct profile for you. I use PERFORMANCE MODE.
You now have successfully Flashed GreyBLUR on your phone but this is NOT all that is needed.
Read below.

Step 4: Apply BlurFix Patches to fix compatibility issues with GreyBlur/GingerBlur and enable performance tweaks!
This patch will fix update notification NAGS, remove Swype and also will enable 1080p Video recording as well as enable performance tweaks!
READ FAQ for more information.
Noob HELP – Skip this section if you are experienced with ADB and debugging mode.
-Pull down the Notification bar up top and select “USB Connection”
-In this prompt select “None” and press OK
-The phone will reconnect to the computer with USB.
-Debugging mode will now be enabled.
If it does not:
-Unplug the phone and reboot
-After the phone boots up, plug the phone to the computer.
Patching:
-Having downloaded Seven’s Blurfix Patch from the Required Downloads above, extract this file to your C:\ drive. Example: C:\SevenBlurpatch
-Open SevenBlurpatch folder
-Run “Seven's Blurfix”
-Follow the steps prompted in the CMD window.
-After the script files have been copied over it will ask you to press any key to continue.
-It will leave you with an open ADB Shell, displaying the “$” symbol.
Type in the following commands in this order:
su
At this point, MAKE SURE YOUR PHONE’s SCREEN IS ON. PAY ATTENTION as it will prompt you to ALLOW or DENY. Select ALLOW on your phone or this will FAIL. If it fails run Seven’s Blurfix again.
The $ sign will change to a # sign.
This means you have Root access through the terminal window. Now we will manually execute the script.
Type the following command at the # prompt:
./data/local/tmp/blurfix_script.sh
After this the phone will reboot and then you are READY TO GO! Read Step 5 for APN information and FAQ!
No more ATT update nags, no more issues and 1080p recording enabled! Performance tweaks enabled, tethering re-enabled. Read the FAQ Section on how to record in 1080p!

STEP 5 - APN Information and FAQ
Here is the correct APN information for all pertinent carriers. I was unable to find the Korean APN information so if someone will PM me this, I will gladly add it!
It can be found -> Here
This is how you add APN settings:
-Press the Menu key
-Go to Settings
-Go to Wireless controls
-Go to Mobile networks
-Go to Access Point Names
-Press the Menu key
-Select New APN
-Add pertinent information
Depending on what carrier you use, these are the settings:
You might need to add 2 APNs for your specific carrier.
Whatever is does not have settings, leave blank.
After you have added your APN information make sure you ENABLE the little RADIO icon.. its the circular icon, that is usually empty after adding APN information.
Frequently Asked Questions!
Q) What's so special about 2.1.1 vs Stock or 1.4.2
A) A lot of things! Some of the most noticeable improvements are the boot time when using stock 2.1.1. It is FAST and the display is much more responsive than stock Bell Motoblur. Also MotoBlur is much more responsive in loading and switching between screens, even the stock keyboard is an improvement in terms of feedback and usability. Stock 2.1.1 no longer lags when typing. The fingerprint reader has improved significantly as well in comparison to previous SBF. Quadrant scores also went up for me in comparison to 1.4.2 GreyBlur. There is a lot of feedback regarding this but all of it has been GOOD.
Q) Should I stay on 2.1.1 STOCK or should I flash GreyBlur/GingerBlur?
A) Stock is actually quite decent, for Canadian Fido users there is a HUGE improvement as the carrier name is actually correct now and does not take 50% of the notification bar. None the less, GreyBlur runs beautifully and even faster on this SBF! Its quite impressive in boot time, smoothness and the loss of all the bloatware is quite good. It also provides theming support for us International users, so that we may use 1.5.7/1.8.3 framework themes!
Q) 1080p recording?!
A) Yes.. By running Seven's Blurfix Patch, LGCamera Free is installed. This as well as an internal mod allows 1080p recording on the phone! There are however special settings to get it to work.
Instructions:
-Start LGCamera
-Press the Back key to get rid of the purchase nag or buy the full version!
-Select the Video option to switch Video recording
-Press the menu key to open the options menu
-In the options menu scroll down to Video settings and set the following settings. (This is the only way 1080p will work!)
Video Resolution: 1920 x 1080 (1080p)
Encoder: Default
File Format: MPEG4
Video Bitrate 13 Mbit
Hit the red button and you're good to go!
Q) What is HSUPA?
A) High-Speed Uplink Packet Access (HSUPA) is a 3G mobile telephony protocol in the HSPA family with up-link speeds up to 5.76 Mbit/s. By default both the ATT and Bell ROMS have this disabled and therefore features like Voice over IP, skype, videochat are almost unusable. By enabling HSUPA this allows you to use these and also benefit from faster uplink access therefore speeding up you're mobile internet.
Q) Why is GingerBlur 3.1 not recommended.
A) It has been shown in various threads and people's reports (in my original thread) that 3.1 has various glitches and issues. Non functional Home button (when skipping motoblur setup), wifi issues (although most of them resolved now) as well as terrible battery life. GreyBlur on the other hand has proven to work PERFECTLY and is a better platform to have custom framework modded ontop of it. Use all both of these at your own risk!
Q) Why is Swype removed by applying BlurFix Patch?
A) Because there are issues with it. I'm also not allowed to post information or files related to swype on how to fix it. The alternative is to install the updated beta which can be found here in the DEV section. Much better fix/alternative.
Q) I want my Launcher to be smoother! How?
A) Use LauncherPro. It is by far the smoothest. A good alternative is GoLaucher Ex which is also great.
Q) I did not get the Power Icon that you mentioned in your guide.. what did I do wrong?
A) This is a feature of the Atrix called Power Management. It can be accessed at: Settings->Battery Manager -> Battery Mode. There you can select whatever profile you want!
Q) I want to flash other themes! What do I do?!
A) Feel free to flash any theme that is for ATT framework ONLY.. As long as you have GreyBlur installed this will work. Try to flash themes for 1.5.2 and 1.8.x ATT. Previous ones are unknown and unsupported.
Q) I flashed a theme and now, my phone wont boot!!! what do I do? Do I have start over again?
A) No you dont! First if this happened, you have to Factory Reset. (That sucks.. But its the price we have to pay to get this functioning)
Follow this short guide below: How to access Android Recovery
-On your first reboot after flashing a new theme, hold VOL down as the phone powers on.
-Then use power down again to select Android Recovery
-Once selected, press Power button ONCE, then VOL UP
-Tap lower right hand corner of screen if you have no buttons
-Select Wipe data/factory reset using volume buttons
-Triple tap (or more) on the lower left hand corner of the screen to select OK
-Using the same method, reboot the phone using that option in the menu!
-The phone should boot.
Should the phone not boot, it means you flashed something unsupported so back to square one!
Q) My Lapdock Keyboard is all messed up!! What do I do?
A) Unfortunately you did not read the section above (STEP 3) which specifically states what should be done in preparation to flash so that your Lapdock Keyboard functions properly. I am attempting to create a hotfix patch for this to avoid people having to reflash but at the moment there is no other way.
Q) I wish to DeOdex Stock 2.1.1 so that I may theme my phone without using GingerBlur/GreyBlur or to install Arabic Language pack. What do I do?
A) Read STEP 2, after ROOT and RECOVER there is a section now, which contains instructions on how to use the 2.1.1 DeOdex tool I've created.
Q) I'm having connectivty issues with DATA and VOICE.. what do I do?
A) Flash this radio -> HERE. This generally solves issues with connectivity.
If you have any more questions please let me know!

thanks, but why do you say gingerblur 3.1 is not recommended?
running it on 1.4.2 and don't have any issues... just wondering before I update to 2.1.1

scorneil said:
thanks, but why do you say gingerblur 3.1 is not recommended?
running it on 1.4.2 and don't have any issues... just wondering before I update to 2.1.1
Click to expand...
Click to collapse
This info will be added to the FAQ section but just be aware 3.1 drains battery like hell. Don't mind people saying that resetting stats will fix it but a lot of people have reported issues with that. (I suspect it has something to do with Gallery3D version which is a known drain)
2.1 on the other hand has much snappier performance and the battery life is just a lot better.
Also people using phones from other regions, international regions have reported issues with it if you read the thread.

Well done guides!
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!

seven2099 said:
This info will be added to the FAQ section but just be aware 3.1 drains battery like hell. Don't mind people saying that resetting stats will fix it but a lot of people have reported issues with that. (I suspect it has something to do with Gallery3D version which is a known drain)
2.1 on the other hand has much snappier performance and the battery life is just a lot better.
Also people using phones from other regions, international regions have reported issues with it if you read the thread.
Click to expand...
Click to collapse
ya, i did have the battery issue but it's much improved (in my case anyway) with a battery calibration.
Battery drain or not that Gallery3D is horrible.
thanks for the info

scorneil said:
ya, i did have the battery issue but it's much improved (in my case anyway) with a battery calibration.
Battery drain or not that Gallery3D is horrible.
thanks for the info
Click to expand...
Click to collapse
No problem! Thanks for the feedback. Make sure you read the section on the BlurFix Patch I've created. This will disable the OTA nags and add a few goodies!
Enjoy SIR!

Question about the 1080p recording - is this sufficient for a daily driver? I don't use my camera a ton but when I do, it's normally extremely critical. And because we have another camera app included (which has the options to allow 1080p after we've applied the appropriate mod) is it safe to assume that the native camera app is the same?
I guess what I'm asking is if the normal camera app stays as is, where as the LGFree camera app is able to use the mod?
Thanks for all your hard work, man. And thanks so much for giving us Bell Atrix users MUCH more than just a glimmer of hope. I'm floored at how well the new SBF file is. Holy ****!!! Now I can't even begin to imagine how much opportunity there is once we start looking at Gingerbread and future framework. Never knew how much of an improvement we'd see without even unlocking the full capabilities and dual core processor.

Ok so what exactly is fixed in this sbf? Telstra fixed the hsupa... what does this fix?
edit: nevermind...
Sent from my Motorola Olympus

bongd said:
I guess what I'm asking is if the normal camera app stays as is, where as the LGFree camera app is able to use the mod?
Click to expand...
Click to collapse
The regular app does not support 1080p yet. This is simply because there was probably no budget left when developing this to enable it (although simple enough, would probably require a lot tweaking on their part to get the best out of the camera)
As for LGCamera, the Free version or paid version can both produce MUCH better image quality than the Stock camera. I will add some more information to the FAQ as to how to improve image quality using LGCamera.
Cheers! and Glad you like it! I do agree, it is AMAZING.

ChongoDroid said:
Ok so what exactly is fixed in this sbf? Telstra fixed the hsupa... what does this fix?
Sent from my Motorola Olympus
Click to expand...
Click to collapse
Read the guide and user feedback.

Hi seven,
First of all, thanks for the hard working!!!
Everything is fine, except that I didn't get the power icon after flashing greyblur. What program is that?
Also, how can I get gingerbread theme on greyblur?
Cheer!
Thiago

Beat me to the edit haha... All right well I guess I'll have to flash this at my friends windows machine.
Sent from my Motorola Olympus

seven2099 said:
The regular app does not support 1080p yet. This is simply because there was probably no budget left when developing this to enable it (although simple enough, would probably require a lot tweaking on their part to get the best out of the camera)
As for LGCamera, the Free version or paid version can both produce MUCH better image quality than the Stock camera. I will add some more information to the FAQ as to how to improve image quality using LGCamera.
Cheers! and Glad you like it! I do agree, it is AMAZING.
Click to expand...
Click to collapse
You are a machine, brother!
Thanks for helping us increase the user experience with this phone 10-fold! Only ****ty thing is that a few people at my work place are getting Atrix's and now they want me to put these amazing mods on their phones too.. sheesh. Look what you've done!

bongd said:
You are a machine, brother!
Thanks for helping us increase the user experience with this phone 10-fold! Only ****ty thing is that a few people at my work place are getting Atrix's and now they want me to put these amazing mods on their phones too.. sheesh. Look what you've done!
Click to expand...
Click to collapse
LOL hahahahaha
No worries dude! I do what I can because I LOVE this phone.

tsouza said:
Everything is fine, except that I didn't get the power icon after flashing greyblur. What program is that?
Click to expand...
Click to collapse
Glad you enjoy the effort! The power icon can be accessed under:
Settings-> Battery Manager -> Battery Mode.
There you can select what you want!
tsouza said:
Also, how can I get gingerbread theme on greyblur?
Click to expand...
Click to collapse
Yes you can get Gingerbread theme. Check the Themes and Apps section! you can find plenty that work on ATT framework! After you flash though and if your phone does not boot, make sure you simply do Factory Reset (I know this sucks terribly.. but its the price we pay to get this functional!)

[MOD] Atrix Mods application V1.06 (7/15/11)

Disclaimer: I have only tested this on my own phone. Everything should work fine, but I am not responsible for anything lost on your phone..​
Here is an application based on my Bell Deodex scripts. Still a work in progress, but I am running out of things to do with it so it may be ready for public consumption. I just ran through a test of all the features, so far, so good.
Features:
Full Phone Backup and Restore (partitions 1-14, 17)
Root / Unroot
Early usb enumeration recovery mode
2nd-Init support
Odex/Deodex system files. (Bell stock, Telstra and French supported, ATT firmware support would just be a matter of creating the right system_$version.tar.gz archive and putting it in my Dropbox account.)
There are some changes compared to my scripts:
I am not using /data/local/tmp anymore, instead I am using /cache.
Instead of suspending android vis setprop tcmd.suspend 2, which obviously wouldn't be good from something running within android, I am using my early usb enumeration wedge to do it on the next boot before android loads via a script run from /cache.
Slight mods to that have been made to support this functionality, it requires shsu to be installed from my root install. So, if you have rooted using something else, you need my shsu in /system/bin.
ApplyMods is not being used, I could possibly port apktools over, but for now, the mods are baked into the deodexed system files.
I have compiled my own version of Gingerbreak, based on the source for GingerBreak_v1.2.apk. It detects our Froyo better by seeing if there is a 2.2 in the version anywhere. Also, it now takes a path argument so it's not limited to running from /data/local/tmp, and not hard baked with an android application path. Also, the app installs SuperUser.apk as a regular application, not a system one, and prompts you to unmount your internal memory and sdcard, so preserve their contents while GingerBreak is active.
Still more testing needs to be done, I have been working with stock Bell for most of development.
Bugs and feature requests welcome.
Cheers!
Credits:
ChainDD for the Gingerbreak apk, and the The Android Exploid Crew.
edgan for the 2nd-int stuff, see his thread here.
Tested:
OLYLA_U4_0.37.4: 100%
OLYEM_U4_2.1.1: 100%
Fixes:
1.0.1: debloat script fixed when deodexing, it was working but the files were getting replaced by the archive.
1.0.2: check added for shsu
1.0.2: Fixed stupid backup bug, creating directory "backup" and copying to "backup_$version"
1.0.3: Added reboot dialog popup
1.0.3: Fixed force close when no sdcard mounted. (postexecute in asynctask was assuming initialized data, not done when aborted)
1.0.3: Backup/Restore now archives data partition.
1.0.3: Multiple Backups now put up a selection dialog.
1.0.4: Added settings menu option
1.0.4: Updated early usb recovery mode, osh mount moved and replaced, using flag to avoid rerunning the same code.
1.0.4: Reboot option moved to menu. Requires root, when rooting just turn phone on and off, Superuser.apk gets installed after you reboot.
1.0.4: ATT sideloading support added. Reason for the move for Superuser.apk to next boot.
1.0.4: Recompiled 2nd-int, it's now 5KB instead of over 400KB. Have to find some working source for taskset to do that same there.
1.0.5: Added long click to backup button to force a restore operation
1.0.5: finished off settings dialog to implement internal vs external storage.
1.0.5: Misc layout updates, smaller font description text.
1.0.6: Fixed root.sh script, missing / resulting in 0 byte files. Doh!

Some attempt at docs.
Root/Unroot
I am using Gingerbreak to gain a temp root, which then runs a root.sh script with elevated privileges to remount /system and copy su and sush to /system/bin, link in /system/xbin to su, and copy su over to /osh/sbin/frozenfish. Prior to running GingerBreak, the app brings up the system settings for memory cards, so you can unmount them. This will keep you from losing the contents of your internal memory and external sdcard, the app will wait until you have unmounted both. You still have to reboot however. Be sure to click install or replace for Superuser.apk when your phone reboots, around 10 seconds after you see the home screen again.
Unroot just uninstalls Superuser.apk and and deletes the files copied above.
Early USB enumeration:
How to enter:
Hold down volume down when you first turn the phone on, it will say fast boot.
Click volume down until it says early usb enumeration mode.
Press up volume to select.
What it is:
All this boot mode does is enable the usb port so it is available for adb access.
App_Process:
What this is:
It's what starts all the androidish things happening, otherwise you have just linux running on your phone. It is located in /system/bin and is called by init in init.rc. It invokes pre-zygote, zygote, and post-zygote classes (sets of functionality related to getting all the phone services running).
Early usb mode recovery:
What this is:
This is a script in /system/bin replacing app_process. This gets activated when there is an update.sh in /cache OR if you are in early usb enumeration mode and the usb cord is plugged in. In either case, the system partition is moved to /old_system and a copy of it is running from ram, system and root are in read write mode, both sdcards are manually mounted.
So long as you are booted into early usb enumeration mode and the usb cord is plugged into your PC, the phone will wait for the plug to come out, halting the boot process. You can fix your framework-res.apk files, do whatever, and the phone won't crash. When you are done you can pull the plug and the phone will continue where it left off. The system partition is remounted read only and put back as /system, the sdcards are synced and unmounted for vold to find later on.
(Your pc will beep saying usb is disconnected, that is the script turning off usb while it is copying the system partition, it will beep again when it reconnects usb. This is to avoid being in an adb shell and things are still in the works.)
If you have an update.sh script in /cache, regardless of whether you are in early usb enumeration mode, it will go through the same process above, the script will do it's thing while the real system partition is out of the loop, and continue on automatically.
2nd-Init:
This is implemented by adding (not replacing) mount_ext3.sh in /system/bin.
This script changes the affinity of init to be single core, and hacks into it to restart init. Everything already done up to the point in init.rc where mount_ext3.sh is located is not undone, there is a replacement init.rc stored in /system/etc/rootfs that leaves out the bits that were already done and disables some reboot detection. In my implementation of this, I make the phone insecure by replacing the root default.prop file, it gives root access to adb, and causes eclipse to freak out in it's console tab.
Deodex/Odex:
This app attempts to download a file to internal mem from my dropbox account named system_$version.tar.gz, where $version is the contents of your ro.build.id. This file contains the deodexed app and framework files, as well as some tweaks for build.prop in /system. It may also contain a bootanimation and apns list if you are running on Bell and have a foreign firmware loaded. A backup of the odexed files is also created in internal mem, as well as contents of any modified folders. The downloading is done right away, the deodexing is done via update.sh script on the next boot. Same process applies for reversing things.
Full Phone Backup/Restore:
This has nothing to do with nandroid or backing up personal settings.
The contents of /dev/block/mmcblk0p1 though mmcblk0p14, and mmcblk0p17 are dumped to internal mem in a folder called backup_$version, where $version is your ro.build.id. The data partition (mmcblk0p16) is 2GB, I create a tarball of that instead of a straight dump, you can do a factory reset to get that back to stock if anything goes wrong. The cache partition (mmcblk0p15) is just temp space, I leave that out.
To restore the process is reversed, it is implemented as update.sh in /cache for next boot. In this case the script reboots the phone and deletes itself. You can't replace the contents of system by essentially flashing it, and keep it's mount going.

Looks very cool! Will check it out.
BTW your Early USB Enum hack has saved me so many times, I cannot thank you enough! I wrap all my hackery in if [ $(getprop ro.usb_mode) != "debug ] ; then
Now! Keep up the good work =)

Nfhimself,
This looks really great! Three quick questions though. What do you need for this to work with an att atrix? Will this tool root a fresh sbf install? How should sideloading be enabled first to install?
Thanks

eval-, glad to be of service.
airbillion, I know little about the side loading issues with att, bit of a chicken and egg, nothing in an apk will enable it to be loaded. I thought I read side loading was possible now with ATT. Other than that, there is nothing intentionally Bell specific other than the deodex stuff I mentioned.
Cheers!

Will the rest of the features (other than odex/deodex) work on an AT&T Atrix? I was a bit confused about this and wanted to clarify.

Yes, it should, no reason why not.
Cheers!

This is awesome thank you!
Sent from my MB860 using XDA Premium App

NFHimself said:
eval-, glad to be of service.
airbillion, I know little about the side loading issues with att, bit of a chicken and egg, nothing in an apk will enable it to be loaded. I thought I read side loading was possible now with ATT. Other than that, there is nothing intentionally Bell specific other than the deodex stuff I mentioned.
Cheers!
Click to expand...
Click to collapse
Nfhimself,
Thanks for the reply. Att still needs to enable sideloading for atrix, but that can be done manually. Im still unsure what you need so we can deodex with your program though.

eval- said:
Looks very cool! Will check it out.
BTW your Early USB Enum hack has saved me so many times, I cannot thank you enough! I wrap all my hackery in if [ $(getprop ro.usb_mode) != "debug ] ; then
Now! Keep up the good work =)
Click to expand...
Click to collapse
NFHimself, what exactly does Early USB Enumeration do?

airbillion said:
Nfhimself,
Thanks for the reply. Att still needs to enable sideloading for atrix, but that can be done manually. Im still unsure what you need so we can deodex with your program though.
Click to expand...
Click to collapse
Don't need anything, just haven't made a deodexed archive available,yet.
Cheers!
Sent from my MB860 using XDA Premium App

n1ckr0th said:
NFHimself, what exactly does Early USB Enumeration do?
Click to expand...
Click to collapse
It's for using adb in early usb enumeration mode and for running scripts prior to android booting. Without it, android continues to boot and if there are any issues it auto reboots. That's the gist of it.
Cheers!
Sent from my MB860 using XDA Premium App

NFHimself said:
Don't need anything, just haven't made a deodexed archive available,yet.
Cheers!
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thanks nfhimself! Any plans on making one?

Really annoyed that it won't download from my phone.... anyone able to?
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: nevermind it worked Haha

marko! said:
Really annoyed that it won't download from my phone.... anyone able to?
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: nevermind it worked Haha
Click to expand...
Click to collapse
Cool, also downloads fine from xda app.
Cheers!
Sent from my MB860 using XDA Premium App

airbillion said:
Thanks nfhimself! Any plans on making one?
Click to expand...
Click to collapse
Sure, is the latest 1.83 these days? Or rather, is that what everyone is using on att?
Basically, I just be deodexing the files, applying some tweaks and uploading to dropbox. I would have to look up what is going on with webtop on att, to match the ones already done up.
Sent from my MB860 using XDA Premium App

NFHimself said:
Sure, is the latest 1.83 these days? Or rather, is that what everyone is using on att?
Basically, I just be deodexing the files, applying some tweaks and uploading to dropbox. I would have to look up what is going on with webtop on att, to match the ones already done up.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thats great if you can do this for the att users! Yes 1.83 is the most recent and most used on att. Im not too sure about any differences on the att webtop compared to bell or the others, but if you need anything just ask.
Thanks
Sent from my Dell Streak using XDA Premium App

many many many thanks!!! ))))))
Btw how do we enter early usb enum?
About sideloadind and att, it will be on gingerbread enabled..
Until then if u can try install this app using adb, and then threw this app install modified gingerbreak.. Don't know for sure if it works..
Sent from my MB860 using XDA App

Can't get the deodex to work on stock bell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: what size is the deodex file?
Edit#2 : now it says everything works but after reboot still showing odex files I. System/app

i've the same probleme
can donwload deodex files for at&t 1.8.3

[SOLVED] CM 12.1 stuck in bootloop after installing certain apps

So recently I ran into a problem where installing certain apps causes bootloop for me, such as:
SimSocial ( https://play.google.com/store/apps/details?id=it.rignanese.leo.slimfacebook )
Camera Roll - Gallery ( https://play.google.com/store/apps/details?id=us.koller.cameraroll )
Twidere for Twitter ( https://play.google.com/store/apps/details?id=org.mariotaku.twidere )
After installing the above apps, the launcher crashes, then the phone reboots itself. After restarting, the same thing happens again. The only way to end it is to remove the app using the recovery.
The problem seems to be very similar to the one described here
After some research, the problem seems to be caused by this
Someone made a fix here, but apparently it's made for the Moto G, and it doesn't work on Xperia SP (I've tried, the phone can't even boot afterwards)
I have no idea how to implement the fix myself because I'm a noob to all of this.
Does anyone have an idea on how to fix this without upgrading to a newer version of android?
The rom I'm using is Candy5 ( https://forum.xda-developers.com/xperia-sp/development/rom-candy5-t3196185 ), if that does any help.

Try "Low-RAM Property Patcher" by AdrianDC. Maybe it will work in "Candy".

ze7zez said:
Try "Low-RAM Property Patcher" by AdrianDC. Maybe it will work in "Candy".
Click to expand...
Click to collapse
Just tried and it didn't work. The amount of ram doesn't seem to be related to my issue too :/

Each time, on a clean ROM, install each application separately and save the logcat after running it.
When you do this, try different installation order of subsequent applications.
In this way, you have the chance to find out which application is causing problems.

ze7zez said:
Each time, on a clean ROM, install each application separately and save the logcat after running it.
When you do this, try different installation order of subsequent applications.
In this way, you have the chance to find out which application is causing problems.
Click to expand...
Click to collapse
I have tried a number of apps and found the apps I mentioned above cause the exact same problem. They cannot run at all. In fact the phone starts crashing right after finishing the installation. I have tried it on a completely clean rom installation too, and the same thing happens. I will try to get a logcat tommorow though.

You are correct about the bootloop. It affects old rom, pre-CM 13. I have applied the patch you have mentioned a few weeks ago and it did work on my phone, Samsung Galaxy S3 AT&T. I have shared the solution at the proper threads: https://forum.xda-developers.com/showpost.php?p=76721233&postcount=1215.
I think if you want to patch yourself, you might want to look at this. It's for KitKat but I think it should work on Lollipop.
https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184

nehc_rm said:
You are correct about the bootloop. It affects old rom, pre-CM 13. I have applied the patch you have mentioned a few weeks ago and it did work on my phone, Samsung Galaxy S3 AT&T. I have shared the solution at the proper threads: https://forum.xda-developers.com/showpost.php?p=76721233&postcount=1215.
I think if you want to patch yourself, you might want to look at this. It's for KitKat but I think it should work on Lollipop.
https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184
Click to expand...
Click to collapse
Yes I have tried the first solution in your post before making this thread. Unfortunately it caused bootloop (or stuck at the sony logo screen, I can't remember which). I'll try and see if I can get the second solution in your post to work though. Thanks for your reply.

Are there really no other solutions? I've been searching for months and everyone just link the same zip that doesn't work on Xperia SP.

steveglowplunk said:
Are there really no other solutions? I've been searching for months and everyone just link the same zip that doesn't work on Xperia SP.
Click to expand...
Click to collapse
The only options you do have is to do a edit with hex editor. The patch is specific to rom and os version. The person who made this patch did a good job on documenting the steps. https://forum.xda-developers.com/showpost.php?p=77174238&postcount=188
I think I have seen 3 different patches: KitKat, Lollipop, Marshmallow. Patch needs to be applied to proper OS.

I have finally fixed it by following the guide here ( https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184 )
The guide only tells you how to disassemble the libandroidfw.so, but it didn't say how you can "reassemble" it. So I used another software called Binary Ninjia ( https://binary.ninja/demo/ ) to edit it, and it worked! (and yes the demo is enough already)
Tell me if you want the detailed steps on how I did it (I don't think many people still use CM 12.1 on their Xperia SP anyway so I'm not going write it now unless someone asks so)

steveglowplunk said:
I have finally fixed it by following the guide here ( https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184 )
The guide only tells you how to disassemble the libandroidfw.so, but it didn't say how you can "reassemble" it. So I used another software called Binary Ninjia ( https://binary.ninja/demo/ ) to edit it, and it worked! (and yes the demo is enough already)
Tell me if you want the detailed steps on how I did it (I don't think many people still use CM 12.1 on their Xperia SP anyway so I'm not going write it now unless someone asks so)
Click to expand...
Click to collapse
I am glad you've fixed your phone. I was lucky enough that the patch worked on my phone. It's not an easy bug to fix. I am wondering how many people do know about this bug.
If you want to post the guide is up to you. But I think it's worth documenting everything. You never know who might need it.

Looking for this some help
I wouldn't mind a walkthrough on it (if you still remember/have it around)?
I'm trying to patch this for an older phone I have that only supports CM12.1 and it's a pain.

MattEffinTurner said:
I wouldn't mind a walkthrough on it (if you still remember/have it around)?
I'm trying to patch this for an older phone I have that only supports CM12.1 and it's a pain.
Click to expand...
Click to collapse
So obviously you'll need root access (which you should have already if you're using a custom rom anyway), and a pc
ALWAYS MAKE A NANDROID BACKUP FIRST, you never know if things will go wrong
Now install the Binary Ninjia demo ( https://binary.ninja/demo/ ) (There are other disassemblers but this one is what I used in my case, and the demo is free)
Afterwards, everything is basically just following the guide here ( https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184 )
1. Get the libandroidfw.so from "/system/lib" somehow. The guide suggested using adb pull but you can also use whatever root browser of your preference to copy it out and send it to your pc with bluetooth or something
2. Open your libandroidfw.so in Binary Ninjia
3. Open "android::AssetManager::getPkgName(char const*)" on the left by double clicking on it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it's set to "Disassembly Graph" at the bottom left
4. Right click on the highlighted line (the code "movs r3,#0") - Patch - Edit Current Line
5. Change the 0 to 1 instead and press enter
6. In the top toolbar, go to to File - Save and save it...somewhere
7. Send the edited libandroidfw.so back to your phone with adb push or bluetooth or whatever method you prefer
8. On the phone, with a root browser or a terminal emulator, copy the edited libandroidfw.so to "/system/lib" and replace the original one
You'll need to remount /system as rw first to be able to successfully replace it
I prefer using the terminal emulator so I'll use this method for demonstration. In the terminal emulator, enter these commands
Code:
su
mount -o remount,rw /system
cp /path/to/<your edited libandroidfw.so> /system/lib
9. Set its permission to -rw-r--r--
If you use a terminal emulator, use the following command to set its permission (in case if you don't know how)
Code:
chmod 644 "/system/lib/libandroidfw.so"
10. Reboot and pray you haven't broken your phone
11. If it boots up, you should be able to live happily ever after with the bootloop crash problem gone
I can't send my edited libandroidfw.so as the fix seems to be rom and device specific. But I hope my guide is clear enough for you to fix the problem on your own. :fingers-crossed:

Excellent!
Thank you so much for this!
After several hours of fighting with it yesterday (and lots of Google-fu) I finally managed to patch the file (and all for the sake of changing a 0 to a 1 in a library file).
Once I get enough posts in, I'll be able to post the patched file for my ROM in it's thread (though I doubt anyone's still using it at this point, lol)

MattEffinTurner said:
Thank you so much for this!
After several hours of fighting with it yesterday (and lots of Google-fu) I finally managed to patch the file (and all for the sake of changing a 0 to a 1 in a library file).
Once I get enough posts in, I'll be able to post the patched file for my ROM in it's thread (though I doubt anyone's still using it at this point, lol)
Click to expand...
Click to collapse
I'm glad to hear you have fixed this annoying problem too.
Just out of interest, was your method similar to mine?

steveglowplunk said:
I'm glad to hear you have fixed this annoying problem too.
Just out of interest, was your method similar to mine?
Click to expand...
Click to collapse
Yes, it was pretty well identical to your method (I used adb push/pull to move the file off and back on).
I knew what I was looking for in the file but it took some time to figure out how to use Binary Ninja.