Before modding my I9000 to cyanogenmod 7, I wanted to ensure the 3 button combo works.
Unfortunately on my Galaxy S (Swisscom branded) it didn't.
And unfortunately for me all howtos were for people with Windows and Odin and I have Ubuntu.
Disclaimer
This how to worked for me (Samsung Galaxy S, Darkys Rom with Android 2.2.1), I have no idea if this works for every kernel, lagfix, whatsoever. I was ready for the risk (i.e. saying goodbye to my phone as it was modded already and I wouldn't get a replacement for it).
If you're not sure here some background infos:
- Richthofens how to (that's the fix you'll install, his how to is for Windows/Odin)
- more infos on the last heimdall step
Check if the 3 button combo really doesn't work
1. Turn off phone
2. press Power, Volume-Down and Home for about 4 seconds
3. If you see the normal Galaxy S logo then the 3 button combo doesn't work
Precondition 1: adb
1. download tar into /usr/local/bin/: http://developer.android.com/sdk/index.html
2. Fetch adb:
Code:
/usr/local/bin/android-sdk-linux_x86/tools/android update sdk
leave all the defaults and install
3. put adb into your path:
add this to ~/.bashrc:
Code:
export PATH="$PATH:/usr/local/bin/android-sdk-linux_x86/platform-tools/"
reload:
Code:
source ~/.bashrc
4. go sure adb server runs as root, otherwise do:
Code:
pkill -f adb
sudo /usr/local/bin/android-sdk-linux_x86/platform-tools/adb start-server
This should now show your phone:
Code:
adb devices
Precondition 2: Heimdall
Install commandline binaries from http://www.glassechidna.com.au/products/heimdall/
Precondition 3: 7-zip
Code:
sudo apt-get install p7zip-full
And now the real stuff
1. download the fix: http://www.multiupload.com/1M96Y946ZW
2. unzip:
Code:
7z x GT-I9000_P-SBL_RCVDL_FIX_ODIN.7z
tar -xvf Aries_P-SBL.tar.md5
this now produced boot.bin and Sbl.bin
3. turn your phone into download mode:
connect you phone
ensure usb debugging is on
run
Code:
adb reboot download
your phone should now show the download screen
4. install fix with heimdall:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
If this is a duplicate feel free to delete Admin. I see the one click via windows but I can't seem to find the Linux method. This works after the 6.2 update so I assume it would work with any firmware.
http://androidadvices.com/root-amazon-kindle-fire-mac-os-linux/3/
First up download and unzip the Kindle Fire Rooting Package for Linux in your Linux based computer and then you need to proceed to open the terminal window.
Go to the folder where you have unzipped the contents of downloaded file and then open the terminal window in your computer to enter the below mentioned commands.
cd Downloads/KindleFireRootLinux
sudo mkdir ~/.android
sudo cp adb_usb.ini ~/.android/.
./adb-linux kill-server
So, once you have finished entering the commands which are mentioned above, you now need to execute two more command which are,
./adb-linux devices
sh runmelinux.sh
Device will reboot. I then use Voodoo OTA RootKeeper for Amazon content that is broken when device has root.
Does this work for Mac also?
Hey. While trying to port a TouchWiz ROM, I came across tar.md5 files. For some reason, every guide to open this format assumes you're using Windows. I use Linux Mint, so it was a bit of a problem. I found the solution, and thought I should post it here.
Materials required:
Android Kitchen
Linux distro with p7zip
Basic Terminal knowledge
Procedure:
1. Download Android Kitchen here: http://forum.xda-developers.com/showthread.php?t=633246
2. Download and install p7zip (for Ubuntu-based distros):
Code:
sudo apt-get install p7zip p7zip-full p7zip-rar
3. Open a Terminal in the directory where you have your tar.md5. Do:
Code:
7z e SomeReallyLongNameHowDoesSamsungRememberThis.tar.md5
And wait for the shell prompt to appear again. When it does, go to Android Kitchen's original_update folder and paste the boot.img and system.img that were extracted there.
4. Open a Terminal in Android Kitchen's directory. Do:
Code:
./menu
1
(just press enter, type nothing before it)
(type number corresponding to "system.img and boot.img" and press enter)
When it asks you for your password, give it the password. It needs that for mounting the IMG file.
Now your /system folder is in WORKING_whatever, and you can make a ZIP from Android Kitchen. Done.
Dear all,
This took me forever to figure out, so I'd thought I'd share how I rooted my Xperia Z1 Compact (Mini) using Ubuntu 14.10. (You could do this using Windows by skipping Step 2).
First, these were the problems I encountered using other methods:
- Using kingroot worked, but it was very suspicious (there's a nice thread that listed all the mysterious behaviours of kingroot - I can't find it so please just search for it).
- I never tried PRF Creator, since it was yet another Windows app.
- Flashing any boot.img into boot would cause an eternal boot loop.
- Thus I had to use Sony's Emma to enable flashing a recovery.img into recovery; but for this, I needed VirtualBox, and for VirtualBox, I needed USB 2.0 (3.0 didn't work).
- Old versions of SuperSu would never work. The only version that worked is the BETA 2.49.
So here are the steps that worked for me. (I don't guarantee that it will work for you). Make sure you back everything up and unlock your bootloader (you can relock it again using FlashTool).
Here are the steps in brief (details below):
0. Get Ubuntu to recognise your device.
1. Make sure you have stock firmware (either officially by Sony Update, or by flashing a .ftf using FlashTool).
2. Use VirtualBox and a copy of Windows straight from Microsoft (yes, it's free and legal).
3. Use Sony's Emma on Windows to do a "TA update".
4. Back on Ubuntu use fastboot to flash a recovery (fastboot flash recovery recovery.img).
5. Boot your phone into recovery and flash the SuperSu.
The Details:
0. Get Ubuntu to recognise your device
On Ubuntu, open a terminal and type:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
type:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", GROUP="plugdev"
Save, then exit.
Then type this command:
Code:
sudo service udev restart
Next, test that it's working:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
On your phone, enable USB debugging:
Settings -> About Phone -> Build Number (tap Build Number 7 times until developer options enabled)
Settings -> Developer options -> USB debugging
Connect your phone to your Ubuntu and type:
Code:
adb devices
This command may cause your phone to alert you that your computer is trying to modify your phone. Allow it. Then type the above command again in your ubuntu and you should get something like this:
Code:
List of devices attached
XXXXXXXXXX device
where XXXXXXXXXX is your serial number.
1. Get stock Lollipop (14.5.A.0.270) on your phone
You can either get the update straight from Sony or download it and flash it using FlashTool.
From Sony:
If your bootloader is unlocked, relock it using FlashTool (click on the BLU button)
Use the update tool on your phone: Settings -> About Phone -> Software Update.
Using FlashTool:
Download FlashTool and unzip it.
In a terminal cd into the FlashTool folder and type:
Code:
./FlashTool
(you may have to give it permissions first: chmod +x FlashTool)
Click on the "BLU" button to unlock your bootloader (this is necessary for any fastboot command, see below).
Click on the XperiFirm button (the last one on the right that says "XF"). Select a firmware of your choice. Then click on the line under the PayPal symbol that says "14.5.A.0.270..." (for some reason, there's no button, just a line of text). Then click Download. If you didn't change the default "User home", the files will be downloaded to your home directory in .flashTool/firmwares/Downloads
Once it finishes downloading, close the XperiFirm windows in order to return to FlashTool. FlashTool will then take some time converting the stock firmware into a flashable .ftf file (placing it in .flashTool/firmwares).
Once it's done, click on the button with the lightning symbol, select Flashmode and then your firmware and click Flash. It will wait for you to connect your phone in Flashmode (turn phone off, hold the volume down button and then connect the USB cable). Once it detects your phone, FlashTool will flash your firmware, again taking some time.
2. Install VirtualBox with a Windows 7 Guest
Install VirtualBox and the Extension Pack from the virtualbox website (make sure the version of the extension pack is the same as the version of virtualbox. I used 5.0.
Download the image of Windows 7 (what I used) available free from the Microsoft Dev download page (dev.modern.ie/tools/vms/linux/). Unzip it and then double click it to open it in VirtualBox. Follow the VirtualBox prompts to install it (Microsoft recommends assigning between 1 and 2 GB of RAM).
Before running the guest machine, select the Windows 7 machine in Virtualbox and click on "Storage" then "USB". Make sure that USB controller is enabled, and select USB 2.0. (It never worked with USB 3.0 for me. Also, my laptop has one USB 2.0 port and one USB 3.0 port, and I had to make sure I used the correct port.)
3. Install and run Sony's Emma
The following will only work with an unlocked bootloader. Use FlashTool to unlock it (BLU button - see step 1 under FlashTool).
Run the guest Windows and install Emma (developer.sonymobile.com/services/flash-tool/). In the downloaded zip file for Emma, copy the customization.ini file to C:\Program Files\Sony Mobile\Emma\
Run Emma.
Turn off your phone and put it in flash mode (hold volume down and then connect usb). At the top of the VirtualBox window that shows your Windows running, click on the Devices menu, then USB, then "Sony D5503...". Your guest Windows should now detect your phone, and so will Emma.
In Emma, in the list of "Services" on the right, select the one that ends with "TA Update" and flash. When it's done, close Emma and VirtualBox.
4. Flash a recovery
On Ubuntu, download a recovery image. I used this one: Z1_DooMLoRD_AdvStkKernel_FW-757_v04.zip from this page:
http://doomlord.xperia-files.com/ (scroll down a bit to find it). Unzip this file and rename it to recovery.img
Then in a terminal type:
Code:
fastboot flash recovery recovery.img
This command flashes to "true" recovery as opposed to the command "fastboot flash boot boot.img" which installs into boot. I'm no expert, and I'm not sure what the difference is between boot and recovery, but you need Emma to enable recovery. (I tried doing things the boot way, ie, without Emma, but it resulted in a bootloop.)
Note also that this recovery is based in CWM. I read somewhere that TWRP won't work using this method, but I never tried it.
5. Use recovery to flash SuperSu
Download BETA-SuperSu-v2.49.zip from here (this is the only version of SuperSu that worked for me; earlier versions failed).
Copy this file into your SD card (using a card reader, or boot up your phone normally and connect it to your computer).
Boot into recovery: Turn off your phone. Press the power button and volume down button together. When the phone vibrates the first time, release the power button (but keep holding the volume down button). When the phone vibrates again, release the volume down button.
On the recovery menu, select "Install zip" and then choose your the BETA-SuperSu-v2.49.zip from your sdcard. When it's done flashing, go back and select "reboot system now". It might complain that "Root access possibly lost. Fix". Ignore it and select "No".
Your phone should now start up and SuperSu should appear in your app drawer. If you open it, it should start up with no complaints. (Or install the app Root Checker just to be sure).
AFAIK Virtualbox doesn't add your user automatically to vboxusers group which is required to share USB devices between the host and guest machine.
You can do that by running
Code:
sudo usermod -aG vboxusers <your username>
Makenai said:
Code:
sudo usermod -aG vboxusers <your username>
Click to expand...
Click to collapse
thanks for the tip, I would like to note that there's a missing blank space and ' - ' symbol in the sentence, it should be like this:
Code:
sudo usermod -a -G vboxusers <your username>
Regards
Hi,
i did everything until step 3 where i loaded 14.5.A.0.270. I didn't do "TA update"
My question is: because after that i used a lot the phone and configured many things, is it possible con continue with step 4 and later, without loosing any data?
cheers
While every documentation is useful - post's subject does not exactly corresponds to action.
Using Windows under Ubuntu is still using Windows.
As far as I am aware there is flashtool working directly on Linux platform.
This allows to get rid of virtual devices, host-to-guest device delegations, problems with direct hardware access from guest, something what always may be potential source of problems.
Hi there, now 5 years later i got hold on this device and i want to root this very same model.
Unfortunately important links are dead. I can't find a trustworthy recovery image for this device since doomlord.xperia-files is gone. (4. Flash a recovery)
Can anybody help?
Basically, this is a copy-paste thread from this thread.
THIS GUIDE IS FOR LINUX (AND OS X ?) ONLY! Windows version here
Download file here: https://mega.nz/#!wooAGJYA!Hr7VUkPRt1Xx9QxaRSIX-r7u9R8OtBhcpb8W5FdwHS8
Open a terminal (Ctrl + Alt + T) and go to your "~/Downloads" directory (or basically where you download your files):
Code:
cd ~/Downloads
Now, unzip the archive you just download:
Code:
unzip FixOOS3-TWRP.zip
You should now have a folder called "FixOOS3-TWRP". Go into this folder with "cd" command :
Code:
cd FixOOS3-TWRP.zip
Get sudo access (script won't run if not in root):
Code:
sudo -s
and then:
Code:
./fixoos.sh
.
The script will flash all necessary files to your device, and after 3 seconds. it will automatically reboot onto new TWRP.
From this TWRP you'll be able to flash newest CM 13 ROMs and OOS 3.x.x.
If there is no ROMs present on your phone, you can still push it with (be sure to stay in the current directory to use "./adb") :
Code:
./adb push <name_of_the_ROM>.zip /location/on/the/device/
of you can sideload it:
Code:
./adb sideload <name_of_the_ROM>.zip
(Be sure to be in "sideload mode" in TWRP).
For more pictures, check out original thread by @djsubterrain : fastboot outputs are pretty much the same, beside the fact that you are on Windows and Linux.