Database Users

[WORKING] ROOT for all Eris'

Big thanks to tereg for the toolkit and the guys who rooted the EVO with a file write/chmod race condition exploit that gave me the idea for this.
jcase noticed that a race isn't actually necessary to exploit the chmod 777 on the file I've been working with, simplifying the script alot.
I used the files from the adb development pack that Tereg put together. Download them here. You don't need them for this root process as long as you have a working adb install.
THE SCRIPTS HAVE BEEN UPDATED MANY TIMES! Please be sure to re-download the new hack-v4.zip before you start if you a returning root seeker.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
Also, if you want to root and can't get your computer to talk to the phone or have some other weird computer related issue you can now try this method, which doesn't require a computer at all!
Unzip hack-v4.zip to somewhere, copy/move the files into your adb-sdk/tools directory/folder.
*updated files to hack-v4.zip @ 7-14-2010 10:43AM Central*
Files to download:
hack-v4.zip
A ROM file, I suggest EvilEris if you want to flash the whole phone OR EngTools.zip If you just want to be root. (Thanks jcase!)
Android SDK (skip if you have a working adb)
Instructions for linux/OSX. - Alternate instructions specifically for MAC
Have adb in your path, or move the files contained in hack-v4.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
sh runinlinuxfromtools.sh
This will take a few minutes, follow the instructions on your screen.
If you get adb: command not found, try
Code:
sh runinlinuxadb.sh
Some people get a permission denied error. Try
Code:
chmod +x ./runinlinuxfromtools.sh
./runinlinuxfromtools.sh
Instructions for windows (thanks tereg!)
Download the hack.zip file and extract it to the desktop. So, you have a folder on the desktop called hack. I would recommend moving or copying those files (EDIT: that are contained in the hack folder) to the C:\android-sdk-windows\tools folder. Why? Because the script runs "adb ____" commands, and unless you've set up adb to be able to run anywhere within the command prompt, the script won't run. So, it will universally work if the files in the hack folder are placed in C:\android-sdk-windows\tools
So, open a command prompt by pressing WindowsKey+R, or going to Start-Run (in WinXP) and typing
Code:
cmd
in the text box there and press OK
If you are in Windows Vista/Windows 7, go to the Start Menu, then type in
Code:
cmd
in the search bar in the lower right-hand corner of the start menu and press enter, and locate Command Prompt in the search results, or go to Start -> All Programs -> Accessories -> Command Prompt
Type
Code:
cd C:\android-sdk-windows\tools
and press enter
Now, I recommend pushing the ROM you want to flash to the SD card now. So, if you download EvilEris3.0 for instance, make sure you download it to the C:\android-sdk-windows\tools folder, and then execute
Code:
adb push EvilEris3.0.zip /sdcard
Replace EvilEris3.0.zip with the name of the .zip file that you choose to download.
Then, type
Code:
runindos.bat
to execute the script.
You might have to run it 2 or 3 times for it to work. If it fails, just reboot the phone normally, then run
Code:
runindos.bat
again once the phone is booted back up and you're ready.
----------(Thanks again tereg!)
If your device reboots into a new screen with options on it, you now have root in recovery mode. At this point you will be flashing your Eris's brains, so YOUR PHONE WILL BE BLANK AFTER LOADING A NEW ROM! All of your apps/numbers will be gone from the phone.
I suggest a nand backup first.
Download and copy one of these ROM's to your sdcard as update.zip and flash it with flash zip from sdcard by selecting "Install zip from sdcard".
The first boot after loading a new ROM takes quite a while to show any activity to the screen. Give it a good 5 minutes before you start wondering if it's ever going to come back.
Eris ROMS
More things you can now do.
Replace that hateful HBOOT 1.49, and get a rooted STOCK phone.
Donate of you luv me!
-----------------
And some love for tereg! Donate a bit to him too, if you're feeling generous.

Dude, seriously. Put up a donate button. I would donate for your effort. This is absolutely amazing.

I will suck yo thang if this works...brb

If this is confirmed I'm returning my eris with the ****ty trackball and rooting a new one >_>

I love you so much for running with our small shot

when doing
cat > data/local/testfile
I get:
System cannot find the path specified

Oh and btw
This should work on ANY HTC Android 2.1 phone.

{
"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"
}

cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile

wag3slav3 said:
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile
Click to expand...
Click to collapse
lol, same thing...
do you want us to do a cd command, because the cat command does not exist i believe. It may not help that i have absolutely no idea what to do in the first place

cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile

wag3slav3 said:
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile
Click to expand...
Click to collapse
nope, that was just how i typed it out in the post, still not working.

How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?

ericFuels999 said:
How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?
Click to expand...
Click to collapse
cat is a unix command
we're on dos
dos doesn't have the same command

xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
I understand that, but that wasn't my question. Refer to my previous post.

xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
THIS EXPLAINS EVERYTHING, sorry for caps, but i got excited :3
any way to do this in DOS or am i gonna have to boot up ubuntu?
scratch that, wag3 got me covered.

xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.

ahem... I get permission error when I tree to reboot **epic sadface**
I"M DUMB I HAVE TO LEAVE SHELL FIRST

Put run 'adb shell' in the instructions before 'then do this'. Not everyone is going to pick up on that.

wag3slav3 said:
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.
Click to expand...
Click to collapse
you should add
"do: adb shell"
to the first post.

[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: here, mirror.
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: here, mirror.
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..

Great app! I am on a Mac and rooted already so I don't need it but this should help about 90% of all new users.
Thank you.

+1 for the program. I rooted it last Sunday, and am too on a Mac, but this should def make the process alot easier for people.

This should go up as a sticky.

man it does not get easier for the new android users lol

Man I wish this app came out sooner...Fkn awesome!
Sent from my SAMSUNG-SGH-I897 using XDA App

One question since this seems to be a major topic as well, any way you could have it load a generic settings.db file or one click exit to the existing one for non-market apps?
That seems to be giving some people a bit of a headache.

decepticon said:
One question since this seems to be a major topic as well, any way you could have it load a generic settings.db file or one click exit to the existing one for non-market apps?
That seems to be giving some people a bit of a headache.
Click to expand...
Click to collapse
I will see what I can do. I don't have a Captivate. I have a Vibrant. But I have sent a request to kirbo20 to send me his file. If I get it I will add it to the app.

TGA_Gunnman said:
I will see what I can do. I don't have a Captivate. I have a Vibrant. But I have sent a request to kirbo20 to send me his file. If I get it I will add it to the app.
Click to expand...
Click to collapse
I will pull mine and post it here in a few

is your file the original?
Sent from my SGH-T959 using XDA App

It's edited to enable non-market apps

This is awesome, I have been waiting for this!
I am having a problem though, I have gotten to the "press the One Root Button" step. The green shell screen says it can't load the update onto my sd card, so when I re-install packages, it can't find the zip file. It does reboot the phone though and it is set on debug, is there a step I missed? I do have another 8g speed6 sd card I put in the empty slot, could that be messing it up?

Well sounds like your drivers maybe not set up right. go to start then run and open up prompt by typing cmd and see if "adb devices" runs and sees your device.
Sent from my SGH-T959 using XDA App

Ah, I just did it manually. Easy. Thanks for the motivation though.

Awesome work. I'll probably wait for the updated version with the "Unroot" option, but very cool nonetheless!

Here is my settings.db file. Some have speculated that it varies some from phone to phone so may need some testing.
It has been edited to enable non-market apps.

reminder to anyone using someone elses settings.db:
Make note of the android_id in your settings.db before swapping. You'll need it!

I think I am going to leave deploying settings.DB alone.
Sent from my SGH-T959 using XDA App

I created a duplicate batch for vibrant when it comes to rooting.
Ill paste the code in a sec.

Side loading
Script I had for SL'ing didn't work cause once adb shell is launched batch imput no longer works.

[How to] The dummies guide to unlocking the bootloader and rooting the R800x

Hope I'm not stepping on any toes, but here goes.
Are you these guys?
{
"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"
}
but you want to be these guys?
Okay, so you've read Mills' instructions and sort of understand them.
1. Download the CWM recovery from multiupload
2. Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
3. Copy this to your memory card and flash it with the booted recovery
4. Reboot and test root
Click to expand...
Click to collapse
Right? Okay, let me translate all that for you.
First things first, you need to unlock your bootloader. To do so
Mills00013 said:
Obtain a bootloader unlock code. Right now the only way to get one is through ashergray or myself. This will change soon but for now its limited in release.
Once you have your code, follow the unlock instructions on either Sony's website directly or by following the instructions here. Please note that you already have your code at this point so if you follow the instructions please disregard anything telling you to obtain a code. These are for GSM models.
Click to expand...
Click to collapse
So kindly ask one of them for your unlock code, and my best suggestion would be to get everything ready so you can unlock the bootloader and flash the booted recovery all in one go.
So download the recoveryPLAY.img and set it aside.
Then download the RootXperia.zip and set it on your SD card in the root directory. So in the main F:\ folder.
Download the drivers and fastboot.exe here http://www.multiupload.com/RS6367SQMT
Okay, we got everything. Follow these instructions http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/ starting at step 6 but please read my notes below also
at step 7, you will hold down the SEARCH button and plug the USB cable into your phone.
When you go to look for the Driver in Step 10 of the guide look for the one on the list that says "Android Bootloader Interface 2.0.10.2 Google, Inc. c:\?????\oem28.inf", that's the one I used.
Once the drivers installed you can locate fastboot and run it, but do this in the command prompt. So you know, go to Start > Run..> type in "cmd" and your command prompt comes up. Type in "cd\" to get to your root directory, then type in "cd c:\documents and settings\.....whateverfolder you have fastboot.exe sitting in"
So Step 13 of the guide, you're in the ...\fastboot\ folder, you can now type in fastboot.exe -i 0x0fce getvar version and that will tell you if you're connected. If you get a <waiting for device> you probably loaded the wrong driver. </life>
If not, then you got the 0.3, so continue with unlocking your bootloader in step 15. Put in your command and the key you got from some really helpful people.
Okay, so you just unlocked the bootloader, awesome. Don't close any windows. Now remember that "recoveryPLAY.img" we set aside? Go get it and move it into the same folder that you have fastboot.exe in.
# Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Click to expand...
Click to collapse
Okay, with your command prompt still open and your recoveryPLAY.img in the same folder as fastboot.exe, type in "fastboot.exe boot recoveryplay.img"
Copy this to your memory card and flash it with the booted recovery
Click to expand...
Click to collapse
In about 10 seconds the screen on your phone will change, you will now see the recovery screen on your PLAY. The volume buttons are UP and DOWN, the power button is ENTER or SELECT. So navigate through the menus to install .zip from SD card, and look for the RootXperia.zip (we put it on your SD card earlier remember?). So you found it, Select it, it will run, the phone will tell you life is great, so scroll up to the top and back out until you see the option to reboot your phone.
Reboot and test root
Click to expand...
Click to collapse
Select Reboot and once you come up, go to the Android market and download something that requires Root, such as Titanium Backup or ROM Manager.
Finally, thank everyone involved for making this happen. Here http://forum.xda-developers.com/showthread.php?t=1098131
I did this on Windows XP, so I'm not sure if everything is exactly the same for any other Windows OS. Mods, feel free to move, delete or what you please with this thread.

Thanks a lot!!
Sent from my R800i using XDA App

Oh, my, gosh! THANK YOU SO MUCH! You don't know how much this means to me!

Thanks 4 dummie guide for noob people like me!!!!!

“S1Boot Fastboot” under the head “Other devices” i dont have that in my device manager
i cant seem to find "Android Bootloader Interface 2.0.10.2 Google, Inc. c:\?????\oem28.inf"
either...
my device manager says:
Android ADB interface under Android Phone
and
PCI input Device under "Other Devices"

To find s1 boot, you need the BLUE LED on
Sent from my Xperia PLAY R800i using XDA App

yea, i know
blue led light is still on

Thank you very very much for this simple and easy to follow guide. I have a very basic knowledge of all of this and many of the guides posted required I fill in gaps I didn't know how to fill.
Thank you!

Android ADB interface under properties says 2.0.10.2 Google
but i tried to update it with the folder and it said it was up to date....

In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned, it means the phone is correctly connected
Sent from my Xperia PLAY R800i using XDA App

dont know wtf i was doing but it finally connected to the phone, bootloader unlocked! just installed rootxperia.zip file bout to see what happens next.

hmm
i hit the power button (select) to reboot system but nothing happens. just momentarily turns screen off and on. i cant select anything now... stuck in clockworkmod recovery app
should i just unplug battery and replug?

KGB920 said:
hmm
i hit the power button (select) to reboot system but nothing happens. just momentarily turns screen off and on. i cant select anything now... stuck in clockworkmod recovery app
should i just unplug battery and replug?
Click to expand...
Click to collapse
to clarifie things - the search button is [select] on the play

FYI, the original method for obtaining unlock codes from Ashergray or Mills has been blocked by Sony. Now, the only way to unlock has to be done through Allejandrissimo, and costs money.
A free solution is being worked on, but we are nearly back to square one as far as unlocking goes.

crono141 said:
FYI, the original method for obtaining unlock codes from Ashergray or Mills has been blocked by Sony. Now, the only way to unlock has to be done through Allejandrissimo, and costs money.
A free solution is being worked on, but we are nearly back to square one as far as unlocking goes.
Click to expand...
Click to collapse
how much money?
because I'm getting so tired of running out of space every time I download an app

Halfway down the page Androhero has a (non-rooted) way to free up space (it works, I have anout 100 apps with 100mbs free)
http://forum.xda-developers.com/showthread.php?t=1194570
Sent from my R800x using XDA App

Bump for helpfullness and newbie R800X'ers.

does this still work?

thirday_95 said:
does this still work?
Click to expand...
Click to collapse
No.

tq mates, such info

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.

*reserved*

Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!

Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again

LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.

Hi mrew42,
Thanks a lot! Much appreciated!

Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81

Letama, can you may be make the same for 3.2.81?

Yes, it will come soon...

3.2.81 is up and instructions on first post updated if you upgrade.

Great
http://www.jbmm.fr/?p=27601
{
"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"
}

cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!

Thanks, will try it out soon.

Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.

ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.

I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?

No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.

Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!

hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!

lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

Root Nexus 4 on Linux

I just rooted my Nexus 4 using Ubuntu 12.04.
The instructions I found weren't quite what I'd liked them to be, none of them were for Linux and I had to do quite a bit of trial and error.
I know that a few years ago I wouldn't have been able to do it with those instructions.
So I thought I'd write down what I did so others can do it easier and faster than me.
To be able to easily understand this guide you need to know the basics about using a terminal, but other than that I'm trying to not to require the reader to know anything.
If you use another Linux distro everything should work pretty much exactly the same, but for the additional packages I had to install, but their name should be easy to guess because they are usually similar across distributions and how you install them should be explained in the documentation of your distro.
Connect your Nexus 4 to your computer using an USB cable.
First I downloaded the ADT Bundle from there developer.android.com/sdk/index.html and unpacked it into a new folder. Doesn't matter where, I'll use ~/androidSDK in those instructions. The tools which you need to root your phone are ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb and ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/fastboot
"x86" means I downloaded the 32bit version and "20130514" is the date of when the version I'm using was published, that will most likely be different for other people.
Now most likely adb and fastboot won't run yet (if you run them it will tell you something like "~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory"). To fix this you need to install the packages "lib32ncurses5" and "lib32stdc++6". You can run the following command to do that:
Code:
sudo apt-get install lib32ncurses5 lib32stdc++6
(got that from there: stackoverflow.com/questions/10005907/eclipse-android-plugin-libncurses-so-5)
For adb to work you also need to activate USB debugging: Go to Settings->About phone and tap "Build Number" until it says you are developer. Then a new entry will appear in "Settings", called "{ } Developer options". Check the box next to "USB debugging", confirm with ok.
Now you need to backup everything on your Nexus 4 because it will be wiped while rooting. You can do this by running:
Code:
cd ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools
(in the future I'll assume you stayed inside that directory)
Code:
./adb backup -apk -shared -all -system
Before this command can finish you need to confirm on your Nexus 4 that it's okay to do that backup (just do what it says on it's screen).
This will put a file named backup.ab in the current directory. You can change the name and location of that file using the -f paramter, if you want.
Run
Code:
./adb reboot bootloader
to boot into the bootloader. After a moment the Nexus 4 should display something like this:
{
"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"
}
(image stolen from reviews.cnet.co.uk/mobile-phones/how-to-root-your-google-nexus-4-50010361/)
Now the actual unlocking happens: Enter
Code:
sudo ./fastboot oem unlock
Maybe try without sudo first (just leave it out), but it only worked with sudo for me; without sudo it displayed "waiting for device" forever and I needed to abort with Ctrl+C.
Download SuperSU from there http://download.chainfire.eu/supersu (at the moment "CWM-SuperSU-v0.98.zip").
Put that file on your Nexus 4 any way you want, one possible way is to do:
Code:
./adb push ~/CWM-SuperSU-v0.98.zip /sdcard/
That assumes you downloaded SuperSU to your home directory. For that to work you need to activate USB debugging again (it was deactivated during unlocking).
Download the Nexus 4 "Touch Recovery" from www.clockworkmod.com/rommanager.
I guess you shouldn't need the touch version, but it's more comfortable for sure. When I downloaded it the file was named "recovery-clockwork-touch-6.0.4.7-mako.img" and that's what I'm going to use when I give you commands to run.
This "Touch Recovery" needs to be installed to the Nexus 4. To do this first boot into the bootloader again:
Code:
./adb reboot bootloader
And then flash the file using the fastboot utility:
Code:
sudo ./fastboot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
(if it needed sudo the last time it will need it again, if not, not)
Now go to the recovery mode (use volume buttons to navigate and power to confirm).
Tap "install zip from sdcard"
Tap "choose zip from sdcard"
Tap "0/"
Find the SuperSU .zip file you put on the phone earlier (tip: scrolling works as usual by swiping or if you want with the volume buttons) and tap on it.
Confirm that you really want to install it.
Boot into Android again and restore the backup you made earlier (if you made one).
Code:
./adb restore backup.ab
You need to confirm that command on the Nexus 4.
As you are now finished you can of course disconnect your Nexus 4 from your computer.
You should be finished now. Unless I remembered something wrongly when writing this because I mostly wrote this from memory, after rooting my Nexus 4. If something doesn't work as I claim then please tell me and I'll fix it (possibly eventually).
I myself followed those instructions http://forum.xda-developers.com/showthread.php?t=2018179 as far as possible and then googled what didn't work or just tried around for a bit.
Edit: As of now (18.8.14), those instructions should still work.