Database Develop

[SCRIPT/MOD] Deodexed files for Bell (06/05/11)

If you are looking for how to get back to stock Bell, go HERE.​
Disclaimer: I have not tested this on anything but my phone. This is a development section of a hacking website. Make backups. Know what you are doing.​
Credits:
Brut.all for apktool
edgan for 2nd-init
designgears for aroot inspiration.
xda for being a source of info.
​
Requirements:
Windows 7 or Ubuntu 10.10+ (10.10 and 11.04 tested)
Java installed. (For applymods, it uses apktool)
Running Phone, not in recovery mode, etc.
Tips:
Don't factory reset please if something goes wrong, it just erases your personal settings, it doesn't write to the system partition. It also deletes your data partition, making it harder to get back to stock.
Early usb mode, turn your phone on while holding down the lower volume button, when it says fastboot, release and press volume down repeatedly until it says early usb enumeration, then press up volume. It takes 30 seconds or so before adb is ready.
​
Version 9:
Download it here.
What's new:
Added support for 2nd-int (WIP, tested on stock Bell only)
shsu updated to allow a super user to become a super user, acts like sh in that case.
fixed linux install_recovery.sh and uninstall_recovery.sh scripts to use shsu instead of remaining using su. Ditto with ApplyMods.sh
Boot animation now smaller, using jpegs instead of png files, no difference in appearance.
​
Version 8:
Download it here.
What's new:
Added full phone backup and full restore phone options to the menu. It will download a backup if there is none found.
root script more universal, tries psneuter first, then gingerbreak.
Early usb recovery updated, now uses a tmpfs for system, also mounts /sdcard and /sdcard-ext.
Deodexed French 2.1.1 files incorporated.
Misc fixes
​
Version 7:
What's new:
New Menu script for windows and linux in the top folder, double click Menu and enter options.
ApplyMods and other scripts updated to use /data/local/tmp/system, this means I can update system.tar.gz and add folders to be copied into system.
Early USB enumeration recovery option. (experimental but useful as is)
Fixed bugs in windows scripts. Can't get user input from bat file while in a parenthesis block apparently.
Bloat backed up to sdcard now
root and unroot scripts updated with more prompts for rebooting phone.
​
Version 6:
What's new:
Support for Telstra 1.4.2.
ApplyMods can create signed update.zips now, Create_update.bat updated. both using basic ready made scripts in main bin folder instead of creating them on the fly, CR LF issues.
Updated root and unroot scripts, more fool proofing, has to be Bell stock firmware (psneuter doesn't work on telstra).
Includes basic boot animation, and mod for Bell apn on telstra firmware. (Have to reset to default under access point names in settings.)
transparent status bar, yellow tinted white for text color, matches front buttons somewhat.
​
Version 5.1:
Features:
Works under Linux and Windows 7
Includes root and no ads scripts
Patch system for applying modifications.
What's new:
New scripts for doing mods, fixes issues with patch 9 images.
Updated root and unroot scripts, more fool proofing.
New RestoreSystemPartition script
Custom apktool for more [hopefully] bug free installations.
How to use:
Extract archive, keeping folder structure intact.
run a command prompt/terminal (There is a link to one in the windows folder)
run root.bat or root.sh from the linux or windows folders, depending on which one you are using.
Turn the phone off after that is done and turn it back on again.
The rest of the scripts shouldn't be run with psneuter affecting the phone.
run ApplyMods.bat (.sh) [OPTIONAL] This applies webtop hack and translucent status bar, translucent notification drop down, etc. Select update system.tar.gz.
run install_bell_deodex.bat or .sh
System image of stock Bell.
Mirror of above​
Cheers!

Very nice! Looks good!

Will try this when I get home
Sent from my Motorola Olympus

So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Sent from my MB860 using XDA Premium App

cool, i'll try this tomorrow when i don't still have a ****load to do and only 5 hours to sleep
nice to see a Bell dev here!

Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.

Atrices, just so you know
NFHimself said:
Hi,
(What is the plural of Atrix?)
Click to expand...
Click to collapse

Can I run this on my mac? Sorry relatively new to adb
Sent from my Motorola Olympus

you could run it on a mac, just had to edit the script a bit.

Hi,
So what is the benefit of this? Will I be able to theme my device with some of the themes that are available? Or should I play it safe and wait for a bell. Sbf to leak before I try anything and brick my phone again lol thanks in advance
Click to expand...
Click to collapse
I wouldn't try theming with ATT files, I would take what was done to them and apply them myself to the deodexed files here. There may or may not be differences that are not obvious. I am never really sure if there is any benefit to this stuff, it's fun to do, about it.
EDIT: i see that you have included soft_brick.bat is it the same as this one http://forum.xda-developers.com/showthread.php?t=982859 because that one did not work for me thanks again
Click to expand...
Click to collapse
The soft_brick.bat script is specific to the folders I am using for transferring data to /system/app and /system/framework. It tries to get root via psneuter, mounts system read write, deletes dalvik-cache files, and tries to copy the files already on the phone to the right folders. It could be that just one file caused the phone to crash mid copy and copying it again will fix things. This avoids trying to do a usb data transfer of all the files which you don't have time to do otherwise. I was also thinking that install-recovery.sh would be a good place to do this, (and then clobber it later with the init.d hack) but I couldn't find setprop and I wasn't in need enough to select a file to use as a semaphore.
Can I run this on my mac? Sorry relatively new to adb
Click to expand...
Click to collapse
It would be easier to do it all from a sh script really, and that would likely be more compatible with a Mac.
Also I just wanted to say major props for the crazy awesome idea of doing over-the-air download and installation. Really smart and original.
Click to expand...
Click to collapse
Thanks!
Cheers!

maledyris said:
Atrices, just so you know
Click to expand...
Click to collapse
Thanks, a lot, really, 10 chars..

How do I recover from a softbrick from this? Thanks.

Before anything is done, all the files are extracted to /data/local/tmp/app and /data/local/tmp/framework. If you run into problems put the phone into fastboot/early usb enumeration mode (see here) and run soft_brick.bat (.sh for linux)
Quote:
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select​

This is the message I get when i run the batch file.
This is of course when invoking Early USB Enumeration.
Wait for the count down to finish ...
'TIMEOUT' is not recognized as an internal or external command,
operable program or batch file.
clearing Dalvik cache..
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.dex, No such file or director
y
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directory
rm failed for /data/dalvik-cache/[email protected]*.odex, No such file or directo
ry
reinstalling apps
cp: cannot stat '/data/local/tmp/app/*': No such file or directory
reinstalling framework..
cp: cannot stat '/data/local/tmp/framework/*': No such file or directory
done.

The timeout message means you are running a version of windows without timeout, see adeo thread.
The lines for rm just mean there are no files to delete in the Dalvik-cache, which is normal, you should see that the second time around.
The cp lines are saying that there are no files in /data/local/tmp/app (/framework).
So, that's unusual, in order to get soft bricked using my script you would to have copied files from /data/local/tmp to /system, and if you are bricked would be unable to delete the files afterword.
sequence:
cd /system
cp /data/local/tmp/app/* app/
sync
reboot now
**brick**
So, how are the /data/local/tmp/app files being deleted?

No clue. I'm not sure what to do here? Is my phone permanently bricked? Any other way to recover from this? The one thing that could have gone wrong is I tried installing from my behind my works firewall. Maybe I could not download the proper files.

No, you are soft bricked, you only made a change (that I know of) in system files.
Were you rooted before you tried this?
If you copy the soft_brick.bat files and change the last line to be adb.exe shell ls -R /data/local/tmp, what do you get?
Basically, it sounds like to need to get the files copied over to data/local/tmp, how they are missing/inaccessible is odd. So, create a script to copy the files over bit by bit, might take a while but it should be able to be done.
EDIT:
Do this:
from command prompt:
adb.exe shell ./data/local/tmp/psneuter
wait a few seconds
type this:
adb shell ls -l -R /data/local/tmp
if psneuter fails, it isn't in /data/local/tmp, which is also odd.

I was rooted before this. So I should attempt all these commands while Early USB Enumeration right? That doesn't give me much time Lol.

OK, here's the output.
C:\bell_deodex>adb.exe shell ./data/local/tmp/psneuter
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
property service neutered.
killing adbd. (should restart in a second or two)
C:\bell_deodex>adb shell ls -l -R /data/local/tmp
/data/local/tmp:
-rwxr-xr-x root root 585731 2011-01-09 02:02 psneuter
-rw-r--r-- mot_tcmd mot_tcmd 4 2011-03-30 21:00 ap_tcmd.pid
C:\bell_deodex>^A

And sorry to be a pain. How would I create the script? What are the files that need to be copied? Are they included in your script?

[Solved] X8 unable to enter xRecovery / Flashmode

Hello,
I've had my phone rooted for a long time and things were working out quite fine (yes, I have a recent xRecovery backup ) but a couple of days ago I wanted to try out something new, and wanted to prepare my system for the installation of a custom kernel.
Long story short: I used the busybox installer from the market, but it couldn't verify the installation process because of some previously installed busybox version (guess it came with my ROM...) So I used the uninstall option within the app and this is were things started to go down the drain:
Now when I reboot the phone, it's no longer possible to enter xRecovery as it was possible before (pressing back button repeatedly, during SonyEricson Logo) instead the it just reboots straight into Android. And in Android all that works is the log screen - all other applications / services crash. (I really can't do anything, as soon as I try to unlock the screen I'm bombarded with Error Messages, and sometimes the phone reboots because so many services fail)
I still can get into the reboot options menu when I press the power button > 1sec, but selecting "reboot into xRecovery" or "reboot into CWM" doesn't work -> it will just reboot normally again.
It also seems impossible to get the phone into flash mode. (Turn Phone off, Unplug USB, hold Back Button, Turn Phone on, Connect USB - and every possible variation I could find just leads to the phone booting into Android)
What I tried to do:
I still have root access when I connect to the phone with adb, so I reinstalled the busybox binary from the "SuperOneClick" package into the /system/xbin/ folder manually -> no change
I checked the debug log (from adb logcat) for errors indicate a problem, but there's no obvious message
I checked the dmesg output for errors / problems, but here everything seems to be fine
I reinstalled xRecovery manually (files from SuperOneClick) via adb by putting the files (xrecovery.tar+chargemon), into /system/bin -> no change
I tried to get into recovery / bootloader mode by using "adb reboot bootloader" and "adb reboot recovery" -> normal reboot
I checked the permissions of the binary files (su, busybox, chargemon) and they're all set to 06755
I checked if all symlinks of system programs that require busybox / su are pointing to existing binaries, and they all seem to be correct
Before I proceed and start trying some things that are not so easily reversible I've got a couple of questions:
What happens if I delete all files in the "/system/" folder? (the xRecovery files are in that folder and I guess xRecovery itself needs a couple of files to work properly)
Do you have any tips / ideas what I could try? I really don't mind resetting the phone as I have backups, it's just that I can't get into the mode where I can reset the phone
Thank you very much!

In your case, i suggest you never ever, ever fiddle up with busybox again... leave that up to chefs.
Also, i think you should try removing the battery for a couple minutes, then put it back and press back, then (while holding it) insert usb cable. That's a surefire way to get into flash mode (At least for me, sometimes it happens to boot normally even if i press back if i don't remove the battery). Also, just to be sure, before connecting your phone in flash mode, press Windows + R [In your keyboard, obviously] and type "devmgmt.msc" [Without the quotes] and see if you get a new device under USB devices. If it has a yellow triangle, right click it and choose update drivers, then point it to the flashtool folder for drivers, it should be able to find them. Good luck.

Use PCC
PCC Brought my phone to its original state when I had soft bricked my phone. It worked as a charm , and it was back to the state like nothing ever happened. Also my phone got unrooted. Everything stock like I had bought it from the store.
Use PCC , thereafter get your phone rooted again , as you had initially done.

Dude are you kidding me???You are doing it wrong man...
to get into flashmood
1. turn your phone off
2.press and hold the back button
3.without leaving the back button insert ur phones cable ..
you don't. need to turn on your phone after doing this....
use pcc or seus to repair it it's a soft brick......

@all that replied: Thank you for your help, I managed to fix the problem, will explain it in next post in case somebody runs into a similar problem
@Drknzz
about the fiddeling: that's how you learn stuff - in the last 36 hours I was forced to dig deep into android, and it was fun - and now I've got a pretty good picture of the system
Your your tip about removing the battery for a cpl of minutes didn't work for me.
I also tried XperiaRebootOptions, but this app also fails putting the phone into FASTBOOT mode - so I'll have to keep searching for an explanation
@Mayank77
I can't use PCC, because I'm running Linux as my O/S of choice and try to keep my VirtualBox locked (when I was very desperate this morning I tried it in a VirtualMachine, but PCC wouldn't connect properly to my phone)
@noobismyname
thanks, but doesn't work in my case

a little description of how you can solve problems (using Linux) with incompatible versions of su and busybox that can occur when Market Apps like BusyBoxInstaller are used in combination with ROMs that require specific Versions of the above tools.
In special cases this might lead to the problem, that you can no longer enter xRecovery or put your phone into fastboot mode (depending on your ROM) but you still have debug access to your phone.
Requirements
Nandroid / xRecovery Backup on your local machine
Android SDK -> adb
Image extraction tool unyaffs
root access to phone
Steps
Extract the backup image
The backup files created by xRecovery use an uncommon format because of the filesystem used in android. Use the tool unyaffs (code dot google dot com/p/unyaffs) to extract the image to a directory of your choice.
log into you phone with adb
open up a terminal, and use $adb shell to connect to your phone. Change to root user $su root
If required: make the partition writeable
$mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
compare files
open a second terminal window and navigate to the folder where you extracted the backup image. Start comparing the content of the directories with each other. Important files are: /system/build.prop, /system/bin/su ->symlink to system/xbin/su, /system/xbin/busybox, ...... (depending on what you messed up)
the command $busybox ls -l /system/targetdir | grep sought_file [/] comes in handy, because it will output the files alphabetically sorted and not in arbitrary order like the default adb ls proproamm
[*]use adb to push files to your device
if you find a missing / missmatching file use $adb push /file/on/your/pc /data/local/tmp to copy the backup file to your mobile
[*]copy files to target directory
use (as root) $ cp /data/local/tmp/file /system/..... to copy your backup into the correct place
[*]check permissions
check the permission of every file you copied and in case you're unsure: they should belong to root, group root, access permission 755 (or 06755 in case of busybox and su)
$ls -l /target/dir | grep filename to check
$chown root /target/file
$chgrp root /target/file
$chmod 755 /target/file
[*]make sure changes are written to disk
flush all pending filesystem changes $sync
[*]reboot
exit the adb session with ctrl+c
and use adb reboot to restart & enjoy your phone

AIO ZV 8 rooter/CVM NOT WORKING.

I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"

On the "Regain Root after update" post there is talk of using a terminal emulator to make the root stick on V8. The only thing that worked for me is the post at the top of page 7 (or 8?) that has about 8 steps. If you haven't already tried it.
Sent from my BROKEN OUT VS910

antiwesley said:
I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"
Click to expand...
Click to collapse
Try booting into CWM the old-fashioned way (hold down button and power). When I went through all the steps, everything looked liked it failed and all I had was an unrooted ZV8. Even Root Checker said I was unrooted. But then I tried to manually boot into CWM, and it worked! I flashed the new rom, and superuser came with it! Might as well give it a try. There's the possibility that you end up wiping data if you don't actually have CWM, but it sounds like you don't really care at this point...

I went through 2 days of hell to get root. There are so many things to try but I think the one thing that worked for me was that after you root the stock V7 is to run titanium backup. When I ran it it said it had to change su access or something and then I rebooted and did this in a terminal program
su<enter>
echo 'ro.kernel.qemu=1' > /data/local.prop<enter>
but also made sure by then doing this:
cat /data/local.prop
if you don't see exactly the ro.kernel.qemu=1 redo it. I was surprised that I had it wrong but for some reason the terminal app missed characters sometimes.
-Keith

What a maroon.
Sent from my VS910 4G using Tapatalk

$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$

If you are able to have cwm breakout is rooted.
Sent from my Galaxy Nexus using xda premium

Thanks!
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.

stinkyjak said:
$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$
Click to expand...
Click to collapse
koda1789 said:
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.
Click to expand...
Click to collapse
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?

Plumbert said:
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?
Click to expand...
Click to collapse
Are you already on stock ZV7 and rooted? Use Root Explorer and go to /data and create new file, name it local.prop. Open in text editor, enter ro.kernel.qemu=1 then save it. If you can't do that in Root Explorer then you aren't rooted.

Droid 4 Utility ICS Only

This tool is based on the original D4 Utility with additions and rewrites by me. Doing any of this is at your own risk.
08/14 Tool Version now 2.0 !!! THE JUMP TOOL IS DEAD!!! No reason for this now that we have ICS Fastboot files.
08/31 Tool Version now 2.1 Here's what's new
10/25 Tool Version 2.2 corrected minor script error and updated to safestrap 3.05
1. Set of instruction included within the tool. Once you open the tool select menu 1 to display them. This is a .txt file so you must have some reader (I use notepad++).
2. Safestrap 3.05 (Thanks Hashcode)
3. Latest Superuser (3.1.3) and binary (3.1.1)
4. Restore to 6.16.217 ICS or upgrade a GB phone to 6.16.217 ICS with option to save or erase data
5. Unroot script - This will remove superuser, the su binary and busybox. However if you boot into recovery it will still indicate root or at least past root (qe display in recovery). Even a fastboot with data wipe will not reset this.
Where to download: http://d-h.st/users/jsnweitzel
Add the ICS fastboot file to the lite tool to run menu 11 or 12. Get it here: http://sbf.droid-developers.org/cdma_maserati/list.php Then unzip it and add the files to the "files" folder of the tool.
If you have trouble connecting your phone be sure you have the latest drivers installed from moto:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/78460/p/30,6720,8302
Use this tool at your own risk.

Can't wait to try this to go from .213 to .215! Will let you know my results. Right now, there are too many bugs in .213 for me to use it on a daily basis, hope .215 is better!
Edit: nevermind, d-h.st is back up again!
Edit 2: update went very smoothly, thanks!
Edit 3: fixed my issues with a data wipe - almost got bricked, but your tool saved me again! Now I'm back in action with .215 and having the best phone experience ever. If I could hit 'thanks' multiple times, I would!

Works just fine! Thank you very much!

..

Works great!!! Thanks

I just pushed this to my phone and now it is running soo much better (mostly due to the new build of the ICS leak) I was missing a home button and the lock screen, but so far not seeing too many bugs and I have root again. Brilliant! Cheers!

Just giving post a bump, updated tool.

FYI, there is no link to the .217 OTA zip in the OP.

Dave Lister said:
FYI, there is no link to the .217 OTA zip in the OP.
Click to expand...
Click to collapse
Thanks for the heads up. Fixed the link.

So let's see I'm reading this correctly.
I installed the 217 leak file today (got tired of waiting for the ota soak test) and lost root.
To get it back I just need the lite version linked above, is that correct?

bdbraaten said:
So let's see I'm reading this correctly.
I installed the 217 leak file today (got tired of waiting for the ota soak test) and lost root.
To get it back I just need the lite version linked above, is that correct?
Click to expand...
Click to collapse
Yes only menu 9 will not work, everything else should be good.

jsnweitzel said:
Yes only menu 9 will not work, everything else should be good.
Click to expand...
Click to collapse
Any thoughts on what's going on, I tried it and ran option 8 to root but my root apps aren't working. Here's what the screen says:
---------------------------------------------------
[*]
[*] Motorola ICS Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Rebooting device...
[*] Waiting for device to reboot...
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount succeeded
1397 KB/s (0 bytes in 22364.000s)
2321 KB/s (0 bytes in 2005736.000s)
2196 KB/s (0 bytes in 843503.000s)
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
---------------------------------------------------
So it looks like it worked I don't see superuser in my app drawer and when I try an app that can use root like estrongs file explorer it says "feature not available"
Any ideas? I've tried it multiple times and with two different computers (one on vista the other xp pro) and same result.
Thanks.

It look like the install of busybox and superuser were skipped (failed is probably more accurate) for some reason. Did you have the phone set to "MTP" or "PTP" mode. You don't want to run it in mass storage.

jsnweitzel said:
It look like the install of busybox and superuser were skipped (failed is probably more accurate) for some reason. Did you have the phone set to "MTP" or "PTP" mode. You don't want to run it in mass storage.
Click to expand...
Click to collapse
I don't remember which one it was set as. Does it make a difference on mtp or ptp mode for which one works better?

I have only seen an issue with the mass storage mode. Check in the tool files folder and be sure that a copy of Superuser.apk is there. If it still doesn't work I can't see why. As a last resort you could try installing it from the market.

jsnweitzel said:
I have only seen an issue with the mass storage mode. Check in the tool files folder and be sure that a copy of Superuser.apk is there. If it still doesn't work I can't see why. As a last resort you could try installing it from the market.
Click to expand...
Click to collapse
Thanks for the help, the superuser is there in the files folder.
I'm debating if I should try it from the market or just try fastbooting the phone and see what happens.
I only want to root to get rid of the bloat, not sure if I'll install custom roms or not yet on this one.

You can "disable" some apps without root. Looking under settings and apps. Select one and hit disable. For some you will have to uninstall updates first.

jsnweitzel said:
You can "disable" some apps without root. Looking under settings and apps. Select one and hit disable. For some you will have to uninstall updates first.
Click to expand...
Click to collapse
I'll look into that.
I'm going to try downloading the full tool and try that, I was just using the lite version. It shouldn't make a difference but I figure it doesn't hurt to try it. If that fails I'll try to decide what my next step will be.
I tried to install superuser from the market but it wouldn't let me.

just get the one on the market and update the binary and it should work fine.. tib wiil fix the perms when you run it the first time. tried it b4 and it works fine

myfishbear said:
just get the one on the market and update the binary and it should work fine.. tib wiil fix the perms when you run it the first time. tried it b4 and it works fine
Click to expand...
Click to collapse
Are you talking about the superuser app from the market? I tried to get it and it wouldn't let me install it, claims it's already installed but it doesn't show up in my app drawer.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
I GOT IT!!!!!!!!
I had an idea based on the comment about getting from the market so I tried the idea and it worked.
I copied the superuser apk file over to my sd card, I installed it from there and said to go ahead and replace the file that was there. I opened it directly after the install and updated the binarys (said it was current but did it anyway) now my root apps ask for and get super user permission.
So it looks like I'm up and running.
Thanks,
Brent.

A newbie help please...

Hey guys,
Have the C6903 and am looking at upgrading to RomAur v4.1, where at the moment I have C6903 14.1.G.2.257 Generic AU 1277-0078_R3A loaded. I ran some command and it mentioned that Bootloader can be unlock..
So the question is how to do i do the upgrade to RomAur v4.1, while keeping my phone contacts, messages and notes? Dont really care about apps as I can re-download them again..
If there is a post that already mention how this is done please link it for me as I didnt find what I was looking for...
Thanks in advance...
Cheers,
Yots.

yotis118 said:
Hey guys,
Have the C6903 and am looking at upgrading to RomAur v4.1, where at the moment I have C6903 14.1.G.2.257 Generic AU 1277-0078_R3A loaded. I ran some command and it mentioned that Bootloader can be unlock..
So the question is how to do i do the upgrade to RomAur v4.1, while keeping my phone contacts, messages and notes? Dont really care about apps as I can re-download them again..
If there is a post that already mention how this is done please link it for me as I didnt find what I was looking for...
Thanks in advance...
Cheers,
Yots.
Click to expand...
Click to collapse
Why don't you just sync everything with EverNote and Google? I came from an iPhone before getting my Z1 and 2 minutes after switching it ON, it just had my contacts already. Was really amazed. If this works from iOS to stock ROM, no wonder it will work from stock ROM to RomAur.
If you can't get such feature (I doubt a lot that you can't, developers here do such an awesome job) in your custom ROM, just forget it?

Vanarian said:
Why don't you just sync everything with EverNote and Google? I came from an iPhone before getting my Z1 and 2 minutes after switching it ON, it just had my contacts already. Was really amazed. If this works from iOS to stock ROM, no wonder it will work from stock ROM to RomAur.
If you can't get such feature (I doubt a lot that you can't, developers here do such an awesome job) in your custom ROM, just forget it?
Click to expand...
Click to collapse
+1

I suppose is even impossible to update from stock to custom and keep all data. To do that you have make a full wipe to do a fresh install and do not have problems.

Of course its possible...
Backup contacts to google and then restore, backup messages using sms backup and restore afterwards and backup notes using any backup app and restore afterwards...
Or am I missing something here...

Vanarian said:
Why don't you just sync everything with EverNote and Google? I came from an iPhone before getting my Z1 and 2 minutes after switching it ON, it just had my contacts already. Was really amazed. If this works from iOS to stock ROM, no wonder it will work from stock ROM to RomAur.
If you can't get such feature (I doubt a lot that you can't, developers here do such an awesome job) in your custom ROM, just forget it?
Click to expand...
Click to collapse
As strange as it sounds, I really dont want to have my contacts sync to my google account. It was ok when it was in iCloud (I came from iPhone as well) as it was separate from my normal google email and calendar.
eclyptos said:
I suppose is even impossible to update from stock to custom and keep all data. To do that you have make a full wipe to do a fresh install and do not have problems.
Click to expand...
Click to collapse
Yes from what I read a full wipe is required, hence I thought I'd throw it out there to see if anyone have/can do it. All good guess I will do what Vanarian suggest but I will create dummy account to sync my contacts first.
Thanks for the reply guys and have a merry merry xmas!

yotis118 said:
Yes from what I read a full wipe is required, hence I thought I'd throw it out there to see if anyone have/can do it. All good guess I will do what Vanarian suggest but I will create dummy account to sync my contacts first.
Thanks for the reply guys and have a merry merry xmas!
Click to expand...
Click to collapse
Why dummy account anyway? The same account to backup your contact you will use to access to Play Store for apps so no reason to do not do that.
Merry Christmass You Too.

eclyptos said:
Why dummy account anyway? The same account to backup your contact you will use to access to Play Store for apps so no reason to do not do that.
Merry Christmass You Too.
Click to expand...
Click to collapse
The man has his reasons. Is it so hard to understand? Or does knowing his reason help you in any way?
Sent from my C6903 using XDA Premium 4 mobile app

bogdan wst said:
The man has his reasons. Is it so hard to understand? Or does knowing his reason help you in any way?
Click to expand...
Click to collapse
Whatever man. I don't need to understand that, I got 3 accounts but always using 1.

If you are really concerned just use PC Companion Xperia Transfer or backup and restore option, this way you can restore a lot of your settings as well

danw_oz said:
If you are really concerned just use PC Companion Xperia Transfer or backup and restore option, this way you can restore a lot of your settings as well
Click to expand...
Click to collapse
Thanks I have done this.
Guys another newbie question... I did the following:
Downgraded to .534 - successful
Ran vRoot to get root - successful
Ran TA backup and do a backup - successful
Am stuck on "installing cwm recovery for lb" step.. I followed guide from http://forum.xda-developers.com/showthread.php?t=2261606&highlight=cwm+recovery+for+lb+doomlord to install DualRecovery and did both the SuperSU and the SuperUser and I dont think it actually install the cwm recovery "stuff". I get the following:
"CWM and TWRP Dual Recovery for Xperia Z locked bootloader"
"script created by krabappel2548, modified by [NUT]"
"Ported to Z Ultra by Krabappel2548"
[ 1. SuperSU ]
[ 2. SuperUser ]
[ 3. Remove ]
[ 4. Exit ]
Choose your root app to install or another option if wanted [1,2,3,4]?2
=============================================
Step1 : Waiting for Device.
=============================================
Succes
.
=============================================
Step2 : Sending the recovery files.
=============================================
55 KB/s (57 bytes in 0.001s)
4864 KB/s (264012 bytes in 0.053s)
2693 KB/s (8276 bytes in 0.003s)
3682 KB/s (7542 bytes in 0.002s)
4587 KB/s (657704 bytes in 0.140s)
4826 KB/s (2822413 bytes in 0.571s)
4840 KB/s (1581352 bytes in 0.319s)
5021 KB/s (735308 bytes in 0.143s)
1127 KB/s (2310 bytes in 0.002s)
.
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access
Press any key to continue AFTER granting root access.
unknown option -- a
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by RomasterSU
http://www.mgyun.com
Press any key to continue . . .
killing RIC, remount /system rw and temporarily disabling the RIC service...
copy recoveries to system.
rename stock chargemon
copy hacked chargemon to system.
copy dualrecovery.sh to system.
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this install
er
=============================================
Installation finished. Enjoy the recoveries
=============================================
Press any key to continue . . .
Have I missed something?
I should mentioned that I am trying to upgrade to RomAur v4.1 AROMA LB C6903 jb4.3, I was on .257 with no root so had to downgrade to 534 to get root, so I can backup my TA. so did deviate from the install instruction on RomAur's post.

Possibly, you didn't mention turning on usb debugging. Double check that because I also do not see that in your log capture