Database Develop

[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Easy & Safe!)

Turkeys' ULTIMATE Guide to Rooting v42.1.2
Note: It does not work on 2.2.1 Wildfire's (i.e. - Any bought after Feb - March 2011)
Like this guide? Hit the thanks button at the bottom left of this post
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me, you can do so below.
GBP
EUR
USD

So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...

So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...

Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF

Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!

A2SD
Note: It has come to my attention that doing this with ROM Manager doesn't work most of the time. If you have problems please partition your card another way. (I recommend GParted - There is a Live CD if you don't have Linux)
First, we need to partition your SD card with ROM Manager. This will wipe all the data on your SD card so please backup before continuing.
1) Open ROM Manager (Download it from the Market if you don't have it - Although you will need the Market Mod to show all apps) and press Menu > Manually Override Recovery **Not sure exactly what it says, pls could someone help me out here** Then scroll down to Partition SD Card. Choose the ext size you want for your apps to be installed on, then tap 0 for swap size, then tap OK to reboot into recovery and start partitioning!
Note: While it's partitioning it will show a picture of an Android. You can press (Power?) to see what it's actually doing and if there's any errors.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.

Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Buzz. Now, you need to recall what version of Android you were on before you rooted. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.

Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse

Reserved for good measure.

I'm sure this will help many people. Should be sticky'd

HCDR.Jacob said:
I'm sure this will help many people. Should be sticky'd
Click to expand...
Click to collapse
Good Idea!!!
For the rru you need to click on the windows mobile section and select buzz NOT bravo

Added A2SD guides, misc fix & unroot guide. Bump to v42.1.2

Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin

PanGalactic said:
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
Click to expand...
Click to collapse
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now

42turkeys said:
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
Click to expand...
Click to collapse
And buzz is under windows mobile for some reason

The guide really great....but the shipped rom website don't have RUU for Buzz

coltrain said:
The guide really great....but the shipped rom website don't have RUU for Buzz
Click to expand...
Click to collapse
Look under windows mobile - who put it there? Those files do work.

This thread still not stickied?

Piece of art already. Should be stickied for sure.

I thought a bit about 'reporting' the thread to make a mod notice it but it said specifically what report was to be used for , so i didn't do it , i guess we'll have to bump it up so it gets stickied. Great post !!

[MOD][DEPRECATED] eRecovery

Content deprecated and removed to avoid confusion.

updated: 31/7/2011 to remove 'lastresort' method
updated: 10/08/2011 to remove 'saveme' method
II. Instructions on how to use (applies to Nova)
If you're not a developer or cooker and you just want to know how this works, you're in the right place. Like I've said before, this MOD is already patched in Nova. Assuming the others will also follow these instructions, this is how to use it:
Method for booting directly into recovery:
Repeatedly press a physical key *
* For the key press method, it needs to be a physical key, not one of the capacitive buttons. It also needs to be pressed or released for the script to work, so do not hold it. Example: volume down, G, ... You need to press it before the boot animation and you have a 3 seconds time frame to do this so it's best if you just repeatedly press it every second or so.
This is it.
Now you can play around with less fear of having to flash firmware all the time.

Noejn said:
Repeatedly press a physical key *
Have a file on your microSD card called "saveme" **
Have a file on your microSD card called "lastresort" **
Click to expand...
Click to collapse
So, we can use either one of these three methods to boot into recovery?

evilenter said:
So, we can use either one of these three methods to boot into recovery?
Click to expand...
Click to collapse
Yes, but read the *s.

Is this only for the NOVA ROM? and can you post a link to your PayPal donation page, if you have on that is...

This is just amazing. Thank you so much, again, Noejn.

"saveme" or "lastresort" mus be empty files without any extension?

rgabi88 said:
"saveme" or "lastresort" mus be empty files without any extension?
Click to expand...
Click to collapse
Unless you change the detection scripts yes.

thx you for show us every detail!

i already bricked my fone during restore through cwm recovry...will button method or file method working in my bricked fone without nova rom ? i cant check as i handover my ob to lg custmr care

sankhauaa said:
i already bricked my fone during restore through cwm recovry...will button method or file method working in my bricked fone without nova rom ? i cant check as i handover my ob to lg custmr care
Click to expand...
Click to collapse
Can you share how have succeed to break it just to know and to avoid doing the same mistake.
Regards,
Me

sankhauaa said:
i already bricked my fone during restore through cwm recovry...will button method or file method working in my bricked fone without nova rom ? i cant check as i handover my ob to lg custmr care
Click to expand...
Click to collapse
Uhh, AFAIK you can't.

nice ...
thx man

Noejn said:
So, following the progress on this thread: [BRAINSTORM] Booting directly into recovery, I have devised a way that will surely help us in this department.
I will now split this into 2 sections:
1# post - MOD outline and guidelines for developers / cookers
2# post - Instructions on how to use (applies to Nova ROM)
I. MOD outline
Alright, so, first of all, you need to know this method is actually 2:
a) daemon hijack
b) postboot script hijack
Since redundancy is important I figured out it was best if we had a safeguard at least in two places. Also keep in mind that even though it partially uses the daemon hijack method, this is not a xRecovery like for SE XPERIA devices. This mod will get you in the true recovery in its own partition, it won't mount one on /system which for instance has quite some caveats (tricky to format /system...).
a) daemon hijack
While XPERIA devices hijack the usbcharge daemon, we don't have that binary on our OB. So I went looking for one who could be of use and I decided for the compass one.
So, first step: go to init.rc on the ramdisk, look for akmd2 daemon (compass) and change the entry to this:
Code:
service akmd2 /system/bin/akmd2
user root
group root
oneshot
Next step: rename your /system/bin/akmd2 to whatever, for example 'compass'.
Now, create an empty bash file and first, put there our microSD card file detection script (1st safeguard):
Code:
mount -t vfat /dev/block/vold/179:17 /mnt/sdcard
if [ -e "/sdcard/saveme" ];
then
rm /sdcard/saveme
reboot recovery
fi
As you can see, it will reboot to the real recovery, it won't mount one like xRecovery.
After that script, comes the second one for key detection (2nd safeguard):
Code:
cat /dev/input/event0 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck ];
then
reboot recovery
fi
Now, event0 is physical key. If you want this to work with capacitive buttons, switch to event1. And remember, it's not holding down the key while it boots, this implies either pressing or releasing, that's the only way to trigger event0.
And finally, we have to redirect to our compass daemon, so assuming you renamed it to 'compass':
Code:
/system/bin/compass
Voilá! Pretty easy isn't it?
Now let's go to the 2nd method.
b) postboot script hijack
While this is executed later at boot (already in the boot animation) it's also less dependent on /system.
It's fairly simple, just open this file: init.hub.post_boot.sh, and add to the ending:
Code:
mount -t vfat /dev/block/vold/179:17 /mnt/sdcard
if [ -e "/sdcard/lastresort" ];
then
rm /sdcard/lastresort
reboot recovery
fi
This will check for another file. There you go.
Now keep reading.
Important stuff
Q. Are there any pre-requisites for this to work?
A. Yes, you'll need busybox on the ROM at question.
Q. Can it be broken?
A. Yes it can. While for 90% of developers' actions it will work, sometimes it won't and you'll end up flashing firmware sorry. For example, if these conditions are assembled, it will break: a) no busybox; b) broken kernel / c) crucial service /system files missing.
Q. Do I need to do anything to get working this on Nova?
A. No, it's already been patched with this mod. Just read post #2.
Click to expand...
Click to collapse
Can one of this methods work on stock rooted firmware? How to do this? Can you guide me to do this? I'd like to have one of the two ways (maybe both, why not??) to boot into recovery...

i've tried to mod init.rc but at reboot the file returned original and don't work
why

Just tested it pressing G button, works fine. Thanks man this is great.

Please tell me where wrong, init.rc at root edit akm2 to root root and save, reboot and go back as before.
why whats wrong.
Thanks

[one click] **Linux version** of LG Revo All in One Pkg

NOTE: THIS WILL NOT WORK ON ZV8!
Greetings.
Here is a Linux Version of the "LG Revo All in One Pkg for Root, CWM 5.0.2.7, and Unroot" by mtmichaelson. Most of the credit belongs to him, I just took his script and re-wrote it in Perl to run on Linux! Enjoy!
With this you can root or un-root your LG Revolution, install ClockWorkMod Recovery, or reinstall Stock Recovery!
DISCLAIMER: Neither myself, nor the original author are responsible for ANYTHING that may or may not happen to your phone!!! Rooting your phone etc. voids your warranty! For this reason this software should be considered EXPERIMENTAL and used with caution as such. By using this program in any way you accept your own fate!!!
As always, BACKUP before using! You may also want to read up and make sure you know how to flash the stock firmware before doing this in case anything bad happens. It should be safe, but you can never be too careful!!
READ THE DIRECTIONS!
Tested on my Gentoo Linux amd64 (multilib) system with Perl v5.12.4 and included adb binary, and my guiniea pig phone -- LG Revolution running VS910V7 (Gingerbread). It should also work fine on Froyo but I haven't tested it.
Instructions:
Step 1: Download and unzip the "LG Revo All in One Pkg for Root, CWM 5.0.2.7, and Unroot" by mtmichaelson. Found here: http://forum.xda-developers.com/showthread.php?t=1348557
Step 2: Install adb (from the android sdk) on your linux machine and make sure it can be found in your PATH.
Alternative: You can download the x86 adb binary attached to this post.
Also available here: http://www.box.com/s/juac85czze1zv43bloc0 Make sure to put it in your PATH!
Step 3: Download the linux version (linux_aio.pl)(gzipped, and attached to this post!). It's also available here: http://www.box.com/s/0tk5zv3nf6731605u0k2 Place it in the folder where you extracted the original LG Revo All in One Pkg for Root by mtmichaelson. It should be placed in the same folder where the .bat file for windows is located.
(Optional) Step 4:Install the perl Term::ANSIColor module if you don't have it already for better looking, and more easily readable output! (This will work fine without it though so feel free to skip)
Step 5: Make the script executable and run it!
a. Change to the directory where the linux_aio.pl script is located.
b. Make executable by typing:
Code:
chmod 755 linux_aio.pl
c. Run it!
Code:
./linux_aio.pl
Step 6: Follow the on-screen instructions and enjoy!
Troubleshooting:
USB Connection problems:
* Make sure phone has usb debugging enabled. Found in settings->Applications->Development
* Make sure usb connection mode is set to "Internet Connection"
* Make sure the user you run the script as on your computer has permission to access the usb devices. (You can run it as root, but you're a good linux user that doesn't run unknown scripts from the internet as root right? right? )
* Use the factory cable that came with the phone, no extension cables or hubs or anything weird. (Although it did work fine for me using a 10ft usb cable)
* If it can't find adb you need to add it to your PATH!
Code:
$ export PATH=$PATH:/path/to/your/adb/binary
* If it can't find one or more of the required files, make sure you placed the linux_aio.pl script in the correct location! (See Step 3)
* If you are trying to un-root etc. while running Gingervolt and get errors about /dev/log/main not being found, you might need to go back to a stock gingerbread or froyo before using this (you did make backups RIGHT???! ).
Thanks to:
* mtmichaelson for making this possible by making the original AIO in the first place, and allowing me to copy it and make a linux version!
* Revolutionary and the Android Exploit Crew for making zergrush possible!
* Anyone else directly or indirectly involved!
Screenshot: http://www.box.com/s/unvxy7exxtynaoubhhom

Nice Job. Nice to see tools in Linux being made. OpenSource all the way!!!
-Cybie

Thanks!
I was originally making it just so I didn't have to fire up a barely working windows box from the closet, but I figured why not put in a little extra time and share it!

Awesome job man! I have dual boot between Ubuntu and Windows and usually I'm on Windows but I'm sure this will help out a lot more people.

[HowTo] making a System Dump of Stock Firmware for 'Dummies'

Hi folks,
we have some lucky users among us with a generic (Dev) IMEI - some of these are able to get OTA updates, thought for testusers and/or developers from Samsung, after they install latest Test firmware XXLSA from sammobile....some got updates up to XXLSC and already provided a dump. Others got updates up to XXLSD (and maybe higher in future - who knows, where the journey ends...), but don't know what to do to share this firmware with us 'Flashaholics' here on xda and other forums...
Now, as more and more people asking me (why ever me...) how to make a system dump from Stock Firmware, I decided to write a short 'HowTo for Dummies'. So if you know about someone, who has a unknown Test Firmware installed, or YOU are the chosen one, just follow this tutorial and make us happy
This is just one way of several to do this - but as I think, it is the easiest way for newbies (without having to use Android SDK and adb shell on PC --> that's what experienced would do )
Prerequisites:
- at least 1,4 GB free space on internal SDcard
- a brain (and above 80 IQ-points...)!!!!!
Step 1) Rooting your Stock Firmware (thx to Phil for the steps, I just copy/pasted them) --> if you already have Root + busybox installed, go to Step 2) directly
download this Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip and this cwm-non-touch-6.0.1.4-i9100.zip
Put the previously downloaded cwm-non-touch-6.0.x.x-i9100.zip file on your external sd card
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-non-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
(You can easily unroot your device afterwards...it is also described in Phils thread, where I took all these from: [20 Sep 2012][ICS]Universal Rooting for most ICS phones, Any ROM, now with CWM6 )
Step 2) Making a complete System Dump of Stock Firmware:
Install 'Terminal Emulator' from Playstore
Open Terminal Emulator
type 'su' with your internal keyboard and press return button
grant Superuser access on upcoming popup window
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin
==> this will generate 'modem.bin' (= Modem) on your internal SDcard (will be finished after a few seconds)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage
==> this will generate 'zImage' (= Kernel) on your internal SDcard (will be finished after a few seconds)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hidden.img
==> this will generate 'hidden.img' (= preload partition) on your internal SDcard (will be finished after a few minutes, as it is more then 300 mb!)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img
==> this will generate 'factoryfs.img' (= system partition) on your internal SDcard (will be finished after a few minutes, as it is more then 800 mb!)
Now you have the following output / files on your internal SDcard:
modem.bin
zImage
hidden.img
factoryfs.img
==> zip these 4 together and upload them to a hoster ==> post the link here and devs can start building a new ROM (Stock + CustomROMs) and kernel devs (now we luckily have Phil for that) can preroot the kernel + put in CWM recovery.
That's all and really very very easy....
Disclaimer:
I am not responsible for any damages - it is your risk (though it is not a dangerous thing to do!)

hope this will be a very good guide in getting the new leaked rom from sammy

Nicely done my friend this should ease up on some of the users (the ones who get updates for us XD)
Congratulations on this, now you see why community loves you soooo. liebe endet nie !!
es ein vergnugen es zu lesen. gute arbeit eybee :good:

Thank very much boss
Hope you will be one of the prof when xda university will open.
Thank you very much
Hope now when we will see LS(any letter) it will be with the links of the dump
Envoyé depuis mon GT-N7000 avec Tapatalk

Funny
Envoyé depuis mon GT-N7000 avec Tapatalk

Cool bro thanks but you can use the supersu.zip and the busybox.zip from stock recovery
Tapatalking on my n7000

msedek said:
Cool bro thanks but you can use the supersu.zip and the busybox.zip from stock recovery
Tapatalking on my n7000
Click to expand...
Click to collapse
It was easy copy paste for me in the rooting part....you can root and install busybox in 567 different ways...in the end the result counts

Clicked for Newsworthy article. :thumbup:
Sounds really simple for someone who doesn't have the second prerequisite.
Back uped the info.
Sent from my GT-N7000 using Tapatalk 2

Sharing your valuable knowledge and experience is priceless for those who are interested. Well, me, I simply follow pros like you.
Sent from my GT-N7000 using xda premium

In addition to Step 2:
I made the dumps from my PC with a connected device with "adb", so I could copy them to the harddisk directly.
"adb devices" for checking if connection is established, "adb shell" switching to the device, "su" for root access, and then the commands eybee1970 explained in detail.
After that I fetched the files in my file manager from the connected device.
I prefer to work with terminal windows on the PC and not on the device.
With this you do not need Step 1 - because I didn't

another great one from eyebee
great guide for learners like me
thanks

ThaiDai said:
In addition to Step 2:
I made the dumps from my PC with a connected device with "adb", so I could copy them to the harddisk directly.
"adb devices" for checking if connection is established, "adb shell" switching to the device, "su" for root access, and then the commands eybee1970 explained in detail.
After that I fetched the files in my file manager from the connected device.
I prefer to work with terminal windows on the PC and not on the device.
With this you do not need Step 1 - because I didn't
Click to expand...
Click to collapse
That's why I said 'for Dummies'....no PC, no Android SDK, no adb shell...just the device

This is a superb guide! cheers eybee

Deleted
Sent from my GT-N7000 using xda app-developers app

Now the history rolls back...
as people raced to create their own custom roms.
The chosen ones with their great knowledge was kind enough to uncover about the custom rom things and shared it with some tutorials here in xda-dev for people who needed it.
Just like the old time...when WinMo has a bright future here.
Thanks a million for devs and chefs at xda-dev who always spread the lights.

ZacDerbyshire said:
Great guide. A little off topic but I don't know where else to ask and you are an expert in ROM making. How do I put things like all multiwindow apps and 4 way reboot in the ROM build before it goes on the phone? Sorry again for it being in here, can't find anywhere else to ask.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
4Way reboot mod is at the system/framwork/ directory "android.policy.jar" file is responsible for this stuff....
as for all multi apps after an investigation it appeared it looked for a certain statement to know whether its a sammy app patching that code to the launcher and editting the policy for this feature too gets you all apps access (almost all) as some just dont work....
there are plenty of guides and tutorials over the internet and forums... on different phones mostly but with a little time you can manage everything as you want to so READ some enjoy!
i'am guessing we need to start writing more tutorials in the N7000 section in here we have no knowledge sharing mostly developing and some new guys are ready to try their own so we have to share everything it started with eybee (thanks to him) and hopefully will continue with all other guys who do mods.... no matter how small it can be usefull.
believe it or not but even devs assist each other with mods its not like each one was born with all that OP-Code in his head

Ah...good guide eybee.Let me see if i can make a shell script to dump the partitions and make odin roms out of it.I already have scripts to dump and make odin rom for /system,/data partitions.will add preload,kernel and modem to the script.Let me see how my time permits today.Hope the script will help people.But the only drawback is it will work only on linux.Users may use cygwin too for it
Sent from my GT-N7000 using xda app-developers app

eybee1970 said:
That's why I said 'for Dummies'....no PC, no Android SDK, no adb shell...just the device
Click to expand...
Click to collapse
For my case adb shell was not succeed. Device reboots unexpectedly while dumping factoryfs. Maybe file size is too big. Thus I had to use terminal emulator though pc keyboard is much more convenience

Great tutorial!
Sent from my GT-N7000 using xda app-developers app

Two remarks:
Typing something like "dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img" is never something I would call easy. If you do not have Linux shell commands knowledge, than these are about "50 characters without meaning" that you have to type (on the keyboard of your device - which is even more error-prone).
PC or Note: it is never dummy-simple.
Making a batch wich automatically generates an ROM installable with ODIN (so the result are tars) is dangerous.
The difference between "dump" and "dumb" isn't so big - as I just proved myself.
When you make a batch with a complete process from dumping, copying, building to a "blob" installable with Odin there will be no step in the process for quality control.
Example (hurts to write this): If there's something in the original Rom you are dumping that couldn't be shared then it makes its way through the process in to the final Rom. And the dummy user of these scripts will never know or can protect himself from it.
Only pro from this: after learning this the hard way you don't feel like a dummy user anymore.

[Q] HTC One, Linux, mtpfs and the like

On GNU/Linux, I get mixed results with a HTC One and mtpfs and the like. I followed that wiki page: URL wiki.gentoo.org/wiki/MTP , and updated it at the same time... The whole thing is eplained here: URL forums.gentoo.org/viewtopic-t-988160-highlight-.html
It is my first Android phone, so I am sure of nothing at that time. To summarize, when mounting it with plain mtpfs, I get 2 main directories in the mount point, "/media/HTC/Internal memory" and /media/HTC/Playlists", and some directories which have files in them look empty. After more try and retry, it look like when it is a directory along with files, I can see both the directory(ies) and the files, but as soon it is only files, I cannot see them.
But other implementation "seam" to work fine. As example, with simple-mtpfs, I get the whole phone hierarchy directly at the mount point, and all the files are here. So I use them.
I succeded to unlook it. But before to try to put new stuffs in it like ROMs and Kernels, I want to try to make a backup. I read tons of threads, but more I read more I am lost for now. So, a simple question. I get my phone mounted in ~/HTC. I coppied all the files from ~/HTC to ~/BacktupHTC. If my phone let me to copy them back into the phone, will it be a reliable way to restore the complete phone?
I didn't try at that time, I prefer to be careful and ask before. It look like the file hierarchy I get is some kind of emulation of the real file hierarchy of the phone.

I also get adb to work:
Code:
#
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT36WW906579 device
Code:
#
adb backup -apk -shared -all -system -f backup20140417.ab
Now unlock your device and confirm the backup operation.
This solution will not back up and restore contact, SMS or calendar information, according to what is on https android.stackexchange.com/questions/28296/full-backup-of-non-rooted-devices
Is it some Linux application I can use to browse the content of the ab file I get with this?
But I have one more question. As it is possible to mount the phone via simple-mtpfs, it must be possible in theory to use classical backup tools like rsync. Is it possible or not?
If I try and that fail, what is the risk?

Well, I get rsync to work, but it look like, without to install a Recovery, it is not possible to make a full backup. I get the same files with rsync than with adb or simple-mtpfs. So next step for me will be to install a new Recovery.

I am done with the installation of the Recovery. I made 2 backups and installed my first ROM, the MaximusHD.
It work great. :good:
Now, I could begin to write an Android on GUN/Linux guide for complete Android dummies.