Related
[GUIDE] Turkeys' Ultimate Guide to Root Desire v42.1.1 "Misc Errors are History"
Turkeys' ULTIMATE Guide to Rooting v42.1.1
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 (Adding Now)
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
Root Guide - Pt. 1 - Info
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...
Root Guide - Pt. 2 - UnrEVOked
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...
Root Guide - Pt. 3 - Flashing Your First 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!
Apps2SD
A2SD
First, we need to get S-OFF to flash Amon-RA Recovery. You can use clockworkmod/ROM Manager to do this although it is very error prone so don't!
Now, I'll be honest, I really cba to write and provide support for people S-OFFing, so I'll link to someone elses instead.
But you can still post on this thread with questions, post there if the S-OFF doesn't work.
S Me OFF!
Download the AmonRA recovery image here before continuing. (Make sure you save it in the adb folder inside. the other stuff file below)
1) Make sure USB Debugging is on and make sure you downloaded the 'Other Stuff' file in post 2 and have extracted it to somewhere you can get to easily. (I always reccommend C:\root)
Next we need to flash Amon RA recovery. We will do this via the command line using fastboot. Your phone needs to be in booted Android mode for this next step.
2) Open a command prompt (Start > Run > cmd) and type the following: (you will need to replace some bits if you extracted the other stuff file to a different location.
Code:
cd \
cd root
cd adb
adb-windows reboot bootloader *let your phone reboot into fastboot before continuing*
fastboot-windows flash recovery what-you-called-amonra-recovery.img
fastboot-windows reboot
Next we are going to reboot into your newly flashed recovery image and repartition your SD card. This will format your SD card so please BACKUP your SD Card before continuing.
3) Open the Quick Boot app you downloaded in Pt. 4 and tap Recovery to reboot into recovery mode. Once you are in Recovery scroll down to and select Partition SD Card then select Partition SD. Now use the TRACKBALL to scroll up and down until you get the partition size you want and press trackball to continue. Now select 0 swap unless your ROM supports it and you know what it is. Then set the rest of the SD Card to FAT32 and press the TRACKBALL followed by the HOME BUTTON to confirm and start partitioning!
Note: If you want to use an ext3 or ext4 partition and your ROM supports it, select the SD:ext2 to ext3 option to upgrade to ext3 and the other one to upgrade to ext4. However, I would advise against doing this as you will wear out your SD Card faster.
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 Bravo. Now, you need to recall what version of Android you were on before you rooted. If you were on 2.1, you need to choose one of the RUUs which say 1.21.xxx.x. If you were on FroYo, you need to choose one that says 2.xx.xxx.x. 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 misc errors
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 when I think of some awesome idea I just have to put here. #2
just say WOW! really Great!
Please don't forget radio info.
What a super great guide I really appreciate it, I think we all will
Nice one turkey, I just want to hug you so hard!
{
"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"
}
gascanieto said:
Please don't forget radio info.
Click to expand...
Click to collapse
Whoops forgot that, I'll add it in now
EDIT: Added quickly from an old guide, rewrite soon
Brilliant post
Really Really useful for nooblits
Great, easy guide. wish I had this when I rooted my desire ages ago.
There needs to be more stuff written in plain english - like this guide.
Very easy to read. I'm sure it will find its way into the sticky threads soon enough!
V42 beta....hehe
Anyway, good work! I love it.
Josh.
Can I make a suggestion and ask for a quick guide on updating your recovery image? I have clockwork recovery mod from the first unrevoked tool and thought ROM Manager updated it (it says I am using 2.5.0.7) however whenever I flash a ROM it always says I am on 2.5.0.1. Not sure on how to update it and if I should rather apply the rule if it aint broke dont fix it .
Real nice, one flaw: you use volume keys to navigate in Clockwork (which is default for unrevoked) and trackball in amonra IIRC
Sent from my HDfied HTC Desire
Actually, Clockwork uses the trackball too
Sent from my HTC Desire using XDA App
Hello guys,
Although we now have one-click programs that root our Evos, I am simply the type of person/geek that needs to know the "In's and Out's" and the "why's and how's" of how something works.
I rooted my Evo back in June of 2010 when it was launched, using the then complicated and long process in adb shell. Although I did not stumble in the process at all, I did not know what was really involved and simply followed directions.
With that said:
One of the many Files (flash_image), (mtd-eng.img), (PC36IMG), (recovery.img), needed to root my Evo was the "recovery.img"
Can anyone please explain what this file is and it's purpose.
From what I gather, we have two options to chose from:
1. Amon_RA's recovery
2. Clockworkmod recovery
and these are the programs used to (NAND/Nandroid) create & restore Backups of your system, flash files and wipe information from system.
I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk
yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods
Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.
Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.
Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.
I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.
alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.
I'm on yakju 4.1.2 at the moment with an unlocked bootloader but no root. I would like to go to takju 4.2 so I can get 4.2 right now and hopefully get future updates a little quicker as well. The only thing is I don't want to lose my apps, app data, and sd card contents. I looked through efrant's tutorial here and I could get 4.2 takju that way but I noticed it would result in losing all the app data and sd card contents, which I don't want to do. Is there any other way that will allow me to go to takju 4.2 without losing all that data? I tried looking at mskip's toolkit here but I couldn't figure out if that would accomplish what I want or not. I am a bit of a noob at this stuff which is why I don't want to skip step 10 of efrant's method. Thanks for any help!
J
geckocavemen said:
I'm on yakju 4.1.2 at the moment with an unlocked bootloader but no root. I would like to go to takju 4.2 so I can get 4.2 right now and hopefully get future updates a little quicker as well. The only thing is I don't want to lose my apps, app data, and sd card contents. I looked through efrant's tutorial here and I could get 4.2 takju that way but I noticed it would result in losing all the app data and sd card contents, which I don't want to do. Is there any other way that will allow me to go to takju 4.2 without losing all that data? I tried looking at mskip's toolkit here but I couldn't figure out if that would accomplish what I want or not. I am a bit of a noob at this stuff which is why I don't want to skip step 10 of efrant's method. Thanks for any help!
J
Click to expand...
Click to collapse
To switch from Yakju to Takju, you would need to follow the steps below (considering you know adb & fastboot and have set them up on your computer. Also assuming your Bootloader is unlocked)
1. Download the 4.2 factory images for Takju from http://goo.gl/UMbmS
2. Extract files using 7-zip on Windows (you need to extract twice and will get the files as: bootloader-xxx.img; radio-xxx.img and image-xxx.zip)
3. Copy these files to the location android-sdk/platform-tools/ (if you have the android-sdk installed or to the location where adb & fastboot is)
4. Plug in your Galaxy Nexus (ensure Debug option is enabled under Developer Settings
5. Follow these commands:
a. adb reboot bootloader
b. fastboot flash bootloader bootloader-xxx.img
c. fastboot reboot-bootloader
d. fastboot flash radio radio-xxx.img
e. fastboot reboot-bootloader
f. fastboot update image-xxx.zip
This would update your Galaxy Nexus from Stock 4.1.2 (yakju) to Stock 4.2 (takju) without losing any data/apps
*Disclaimer: I have followed the above to the T and moved from Stock 4.1.2 (yakju) to Stock 4.2 (takju) with Unlocked Bootloader, but you follow these at your own risk.
Cheers!!!
Thanks freezer2000! I used a combination of your recommendations and efrant's tutorial and got my galaxy nexus on takju 4.2 without losing any app data or sd card contents. I'll describe what I did below if it helps anyone else. Just a note...I used a mac so some of the terminal commands are slightly different but efrant describes how to modify his commands to work on a mac. Your bootloader must already be unlocked to do this and keep all your apps and app data.
1. Follow efrant's tutorial verbatim until step 6 of part C. (I didn't do part A or step 4 of part C. because I'm on a mac...I also didn't back up my phone like part B recommends)
2. Once at step 6 of part C. unzip the .tgz file, but do NOT unzip the image-takju-jop40c.zip file that is within the unzipped .tgz file. You should have 6 files total after unzipping the .tgz of which I used three in the updating process -- a bootloader-xxx-xxx.img file; a radio-xxx-xxx.img file; and the previously mentioned image-takju-jop40c.zip file that I did NOT unzip. Make sure these files are in the same directory as the attachment that is downloaded from efrant's tutorial.
3. Continue with efrant's tutorial at part C. step 7 and follow the instructions verbatim until you reach part D. step 2; my bootloader was already unlocked so I skipped ahead to part D. step 4.
4. Follow efrant's tutorial verbatim from step 4 - step 8 and stop after completing step 8. This is pretty much exactly the same as what freezer2000 recommended except for freezer2000's step a, which I couldn't get to work (I'm on a gsm nexus so I did NOT do step 8a or 8b)
5. This is where I picked up with freezer2000's steps. Type in the command line: ./fastboot-mac update image-takju-jop40c.zip
At this point everything seemed to stop for about 30 seconds or so and then 4.2 began to flash to the phone. 5 minutes later or so and I had 4.2 up and running.
I'm pretty much a noob at this and I'm sure my description of what I did isn't that great. Anyone who would like to clean it up or explain what I did in better terms/more detail please feel free. I'm still not sure exactly how what I did is different from efrant's method or if there are any problems with doing it the way I did (and pretty much the way freezer2000 explained except for his step a).
Based on my understanding I first updated the bootloader to a takju compatible version, then updated the radio to a takju compatible version, then flashed the takju 4.2 zip file which basically condensed the rest of efrant's tutorial into one step and avoided deleting my apps and data.
I'm sure there is a very good reason why efrant unzipped the image-takju-jop40c.zip, I just don't understand why. If someone could explain it I'd appreciate it.
As always, no guarantees what I did will work on your phone but it worked for me.
That sounds complicated. Couldn't you simply do the following?
backup with TB
copy the TB folder to your computer
switch over
copy TB back and restore
Sent from my Galaxy Nexus using Tapatalk 2
untruestory said:
That sounds complicated. Couldn't you simply do the following?
backup with TB
copy the TB folder to your computer
switch over
copy TB back and restore
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I think you have to have root to use Titanium Backup and I don't have root. Also, I tried TB once before on a nexus one that I rooted and it didn't really backup everything as well as I'd hoped. Maybe it's gotten better since then.
geckocavemen said:
Thanks freezer2000! I used a combination of your recommendations and efrant's tutorial and got my galaxy nexus on takju 4.2 without losing any app data or sd card contents. I'll describe what I did below if it helps anyone else. Just a note...I used a mac so some of the terminal commands are slightly different but efrant describes how to modify his commands to work on a mac. Your bootloader must already be unlocked to do this and keep all your apps and app data.
1. Follow efrant's tutorial verbatim until step 6 of part C. (I didn't do part A or step 4 of part C. because I'm on a mac...I also didn't back up my phone like part B recommends)
2. Once at step 6 of part C. unzip the .tgz file, but do NOT unzip the image-takju-jop40c.zip file that is within the unzipped .tgz file. You should have 6 files total after unzipping the .tgz of which I used three in the updating process -- a bootloader-xxx-xxx.img file; a radio-xxx-xxx.img file; and the previously mentioned image-takju-jop40c.zip file that I did NOT unzip. Make sure these files are in the same directory as the attachment that is downloaded from efrant's tutorial.
3. Continue with efrant's tutorial at part C. step 7 and follow the instructions verbatim until you reach part D. step 2; my bootloader was already unlocked so I skipped ahead to part D. step 4.
4. Follow efrant's tutorial verbatim from step 4 - step 8 and stop after completing step 8. This is pretty much exactly the same as what freezer2000 recommended except for freezer2000's step a, which I couldn't get to work (I'm on a gsm nexus so I did NOT do step 8a or 8b)
5. This is where I picked up with freezer2000's steps. Type in the command line: ./fastboot-mac update image-takju-jop40c.zip
At this point everything seemed to stop for about 30 seconds or so and then 4.2 began to flash to the phone. 5 minutes later or so and I had 4.2 up and running.
I'm pretty much a noob at this and I'm sure my description of what I did isn't that great. Anyone who would like to clean it up or explain what I did in better terms/more detail please feel free. I'm still not sure exactly how what I did is different from efrant's method or if there are any problems with doing it the way I did (and pretty much the way freezer2000 explained except for his step a).
Based on my understanding I first updated the bootloader to a takju compatible version, then updated the radio to a takju compatible version, then flashed the takju 4.2 zip file which basically condensed the rest of efrant's tutorial into one step and avoided deleting my apps and data.
I'm sure there is a very good reason why efrant unzipped the image-takju-jop40c.zip, I just don't understand why. If someone could explain it I'd appreciate it.
As always, no guarantees what I did will work on your phone but it worked for me.
Click to expand...
Click to collapse
Being a silent viewer on XDA for the last 2 years, I took some steps for granted (as mentioned in efrant's tuts). Glad the info was helpful to you to some extent.
Hit Thanks, if it helped you.
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
untruestory said:
That sounds complicated. Couldn't you simply do the following?
backup with TB
copy the TB folder to your computer
switch over
copy TB back and restore
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Kindly correct me if I am wrong, but using TB would ensure the apps and related data is backed up, how about images, music and other files in the sd will be backed up?
Also how can one switch from Yakju to Takju without flashing the factory images (i know there are custom roms based on each variant, but is there any way to got stock without loosing your data/apps)?
I've been using TB since the release of the evo4g and it's always worked great for backing up all apps and app data. Restoring system settings from one ROM to another tends to break stuff though.
I don't know what to tell you to do without root. You could root, switch, then unroot I suppose.
Titanium won't backup all your saved and downloaded files. If you wanted to save absolutely everything just copy and restore the whole contents of the phone's storage.
Do what you like I guess but if you're gonna tinker around as far as changing your ROM might as well be rooted. Just my opinion.
Sent from my Galaxy Nexus using Tapatalk 2
a. adb reboot bootloader
b. fastboot flash bootloader bootloader-xxx.img
c. fastboot reboot-bootloader
d. fastboot flash radio radio-xxx.img
e. fastboot reboot-bootoader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
At this point you still have your recovery, in order to robot your phone, if you want
not working!help!
freezer2000 said:
Being a silent viewer on XDA for the last 2 years, I took some steps for granted (as mentioned in efrant's tuts). Glad the info was helpful to you to some extent.
Hit Thanks, if it helped you.
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Kindly correct me if I am wrong, but using TB would ensure the apps and related data is backed up, how about images, music and other files in the sd will be backed up?
Also how can one switch from Yakju to Takju without flashing the factory images (i know there are custom roms based on each variant, but is there any way to got stock without loosing your data/apps)?
Click to expand...
Click to collapse
thanks freezer2000 for the steps,but it doesn't work on mine!everything was running smoothly until the last step fastboot blablabla.zip
it has been running for over 2 hours and still not upgraded.how to solve this.please help.
I've been searching around for a stock RUU, but Goo.im seems to no longer have it in it's archives and all the digging about has lead to dead links or Rooted versions of the Stock. I'm trying to restore it to trade in for repairs to street.
Would anyone have a copy of any Stock RUU's available? Non-rooted of course. <:
Madatsubomi said:
I've been searching around for a stock RUU, but Goo.im seems to no longer have it in it's archives and all the digging about has lead to dead links or Rooted versions of the Stock. I'm trying to restore it to trade in for repairs to street.
Would anyone have a copy of any Stock RUU's available? Non-rooted of course. <:
Click to expand...
Click to collapse
Try here:
http://androidfiles.org/ruu/?developer=Supersonic
Sent from my EVO using xda premium
If you are on Hboot 2.18 and it's S-ON, then the biggest problem that you may run into is that it will not except any RUUs if your misc partition has been updated. You would have to first downgrade the misc partition before attempting to run any RUUs.
If that's the case, you can download my old sdk.zip file found here
https://dl.dropboxusercontent.com/u/38127313/sdk.zip
Unzip the file to a folder on your computer, then copy the mtd-eng.img and flash_image to the root of your sdcard.
Then you can follow part of this guide (forget about the title), but you only need to follow steps 30-39 (the previous steps replaces step 29 and substitutes the PC36IMG file found in step 33) in order to downgrade the misc partition, assuming that your phone is still rooted also. You could also use the PC36IMG file in step 33. Mine is just part of that sdk.zip file.
http://forum.xda-developers.com/showthread.php?t=1473373&highlight=s-off
If you are not on Hboot 2.18, but S-ON, then the PC36IMG file inside my sdk.zip file should work fine. Just be careful to rename it PC36IMG.zip and not PC36IMG.zip.zip.