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

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 !!

Related

It is simply ridiculous that HALF of the Nexus One RAM is unusable in stock...

...so I am compelled to root. ALL I care about is unlocking that other 256 (himem, I think it's called) for use and apps2sd would be nice but not necessary. Any other practical enhancements would be welcome. I'm using build ERE27. So which ROM fits that description best and where are the easiest instructions with links to download? I have been all over this and other sites and there are so many tutorials and none seem identical. Try Youtube and you know what you get? The most popular root tutorial (by far) flat out tells you from the start "This is not for beginners". Well, where the **** is the one for the beginners? I've jailbroken Iphones and flashed ROM's on to WM devices but I've never seen a more convoluted method to implementing a ROM replacement for a phone. Step by step (with backup reminders at critical times during process) would be great.
For example (from CyanogenMod):
Before continuing, you should first copy all the necessary files to your SD Card. Doing so will make the entire process much easier and faster.
Files you will need:
Download the latest release of CyanogenMod for the Nexus One and the Google Addon from http://forum.xda-developers.com/showthread.php?t=623496
Download the latest release of Amon_Ra's Nexus One Recovery Image from http://forum.xda-developers.com/showthread.php?t=611829
Rename Amon_Ra's recovery file "Recovery.img", and copy all three files to the root of your SD Card
Click to expand...
Click to collapse
I'm sorry, did you not just provide me with 2 files to download? Where does the third come from? And why does every "Link" lead to a full page with 3700 more links rather than just a freaking file to download??
Even Droiddog uses a Mac during the process because a PC would have been far too convenient for the masses (Plus I don't want the Desire ROM-too borky).
Preparing myself beforehand (going through the motions of the root without rooting) led to me opening 7 windows instead of direct file downloads. 7 Windows. 7. Does it really have to be this arduous?
I'm sorry for the frustration but deciding to root was suppose to be the hard part. Now I'm just overwhelmed with the unnecessary difficulty of it all. In truth, I'll probably be posting "thanks" from a rooted N1 by tomorrow and wondering what was so hard about all of that.......or I'll be crying over a $530 brick in my hands.
I believe Cyanogen mod (latest version in the link) includes the himem by default, just install that and you'll get the more available RAM (unless there is more steps to the process), I do not use Cyanogen.
Please note this is not the iphone OS we are dealing with here, things will not be as simple as a button press.. I honestly do not know what a "noob guide" is when it comes to Android, it all seems so straightforward to me... If I rooted my G1 and I'm only 13, not even being a nerd at that (wouldn't care if I was though..), I would imagine it not being hard for anyone..
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
DMaverick50 said:
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
Click to expand...
Click to collapse
Choppy scrolling is just that launcher2, and has nothing to do with the actual phone hardware which is a good thing. I went back to an older 2.0 launcher that is MUCH MUCH faster with continuous scroll.
I will switch if continuous scroll is added to launcher2, but yeah that choppiness stinks
It's a bug the iPhone had its bugs too. One of the great things about rooting your phone is not having to wait for Google to fix bugs the devs here do it nice and quick. I waited a month then rooted my phone and I am happy I did.
Prod1702 said:
I waited a month then rooted my phone and I am happy I did.
Click to expand...
Click to collapse
Does the extra 256 of ram make a noticeable difference in the overall speed and experience of the device (you should know having gone a month with stock on it)?
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
jz9833 said:
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
Click to expand...
Click to collapse
Is this true?
CM mode unlocks a good upgrade portion of the ram, for example with 10 apps Open I used to have 60 or less MBS left of ram, after CM upgrade with Kspec theme, i have 10 similar apps open and have 200+mbs of ram left, dont believe me? I actually made a video while still pretty shocked, check it, might as well rate and sub. I think I had 230+mbs while 10-12 apps running
www.youtube.com/user/exclusivegslick = my only video.
Ok to answer a few of your questions:
Does CyanMod include more ram? YES. This bump up in ram is included in the Kernel, and all of the newest roms have this including the undervolted/overclocked kernel's as well.
You get about 400mbs after the free up.
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Ok here is a quick summary that will hopefully help the other guides make more sense. USE THE OTHER GUIDES STILL this is a conceptual map.
1) Install Android SDK to your COMPUTER which gives you ADB and the windows drivers. The drivers can also be downloaded via another thread. Search drivers/sdk drivers/adb drivers etc..
2) Download/install Fastboot to your COMPUTER
3) Download Amon Ra Recovery 1.6.3 to your Fastboot FOLDER on computer
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
*This gives you all of the proper stuff. Make sure you get ADB SDK drivers loaded I stumbled here and wasted a couple of hours*
6) Unlock bootloader via fastboot. This is a command given from your Computer in DOS prompt in the folder you created with fastboot stuff. Your phone is connected and you are in the BOOTLoader. READ the guides for exact directions or the androidandme video, or countless other things.
7) Install Amon Ra's Recovery while still in FASTBOOT from a command via your computer. Follow guides or even first post on Amon Ra's Thread.
8) Now that you are unlocked. Go into RECOVERY which is done via the bootloader. Guide will give exact direction.
9) **** MAKE A NANDROID BACKUP **** just get in the habit. It is your FAIL SAFE. This in theory makes a nandroid backup of your "stock but unlocked" setup. I always "RE" nandroid backup before making changes or when I "Like" my setup. Command is in recovery.
10) WIPE data via recovery command.
11) FLASH from ZIP - pick Cyanogenmod5.0.4.1 (file you dl'ed to your sd card)
12) Flash from ZIP - GAPPS(googleapps) (file you dl'ed to your sd card)
REBOOT the phone. VOILA. Your done.
Important notes. If you decide, IFFFF, to update the radio. NEVER EVER EVER EVER pull the battery. MD5CheckSUM the radio download. and Repeat NEVER EVER EVER EVER pull the battery until the radio is entirely installed. It can take awhile. This is how you BRICK your phone.
Anyways. that is a real high lvl overview but maybe puts things in perspective easier.
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
britoso said:
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
Click to expand...
Click to collapse
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
I know what you mean with the "this is not for beginners", it was annoying because, even cyanogen had to unlock his first android phone some time. I followed that guide anyway, after doing as much research as possible. It didnt work though, i could not go straight from unlocking the bootloader to installing amon_ra's recovery, i had to install superboot first. I was hoping for a 30 minute root job, but it ended up taking about 4 hours all up.
I think the stock android kernel is .29 Which only recognises 256mb ram, cyanogen's mod is on the .32 then the .33 kernel which is a highmem kernel, by flashing cyanogenmod you are automatically unlocking the extra ram, no other work is required.
Also, i would suggest sticking with the ERE27 radio, i personally have no problems with reception with it, also if you don't flash the radio, your chances of bricking your phone are very very very low. If you want to do the radio, you can flash it later, when you are more experienced.
seanowns said:
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Click to expand...
Click to collapse
I downloaded the Android SDK
2) Download/install Fastboot to your COMPUTER
Click to expand...
Click to collapse
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
Click to expand...
Click to collapse
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
Click to expand...
Click to collapse
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
whodatfever said:
I downloaded the Android SDK
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
Click to expand...
Click to collapse
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Gr8gorilla said:
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Click to expand...
Click to collapse
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
addon - vs mod
whodatfever said:
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
Click to expand...
Click to collapse
The add-on was what Cyanogen made before google released the source code for android 2.1. It is not a full custom rom.
The ROM's ie. 5.0.4.1 is all the Cyanogen tweaks, highmem etc. 360 degree rotation (left right and upside down if you enable it) and all sorts of stuff.
You really should try both radios and see which one works better for you. Some people have better results with one and some the other. I have the best continuous 3G/HSPDA signal with the ERE36B radio.
On Cyanogen mod forum, go to nexus one and there is a link to get the latest stable ROM 5.0.4.1 that is what you want. You have to also download the Google add-on.
Cyan used to include them but got a nice letter from google telling him he was not allowed to "optimize" their stuff. So he puts it in a separate package as is, and you have to flash it after you flash his rom to get the google apps.
Google apps will be called: gapps-passionERE36B(2) or something very similar.
I am willing to answer any questions you have just send me a pm.
andythefan said:
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
Click to expand...
Click to collapse
there is a thread here about your warranty and as long as you have a problem that is a legit hardware defect HTC has been replacing them, dust under screen bad battery, and a few other things.
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
whodatfever said:
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
Click to expand...
Click to collapse
Remember if and when you flash the radio, plug in phone, and whatever you do, do not pull the battery while it is doing the radio. That is the biggest NO NO. It can make a nice nexus One paperweight. As long as you dont pull the battery you will be fine. I have flashed mine about 4 or 5 times....and I have flashed roms about 1000 times.
The phone is going to reboot a couple of times during a radio flash, be patient.

[GUIDE] Complete and Thorough Guide to Rooting the Nexus S [+ No wipe] [GRH78C]

May NOT work for 2.3.3, if attempting on 2.3.3 use old part 1! - Will wipe all data though
Windows ONLY!
Hey guys, rooted my Nexus S today, and decided to write a thorough, detailed guide on how I did it, as none of the guides I had found had everything detailed. I came across a few problems, and all of this is in the guide. I successfully completed it on my Nexus S running 2.3.2, so any version below that will also work.
The original guide was made by AllGamer, and can be found here. I followed this guide, and added things when I found it was needed
The full guide with everything (including links, pictures) can be found on my site, Complete Android.
New info: Upon finding another thread over at XDA (http://forum.xda-developers.com/showthread.php?t=931865) it has been realized that you can root your Nexus S without unlocking the bootloader, and therefore not loosing your data on the SD card. Part 1 for the new method is still the same, but choose the new Part 2!
WARNING: Rooting your device will wipe all data off it, so you will loose EVERYTHING! Make sure you backup all important data first. Only applies to old Part 2 (fastboot oem unlock method), but it is still a good idea to backup important information!
Click to expand...
Click to collapse
What you will need:
Nexus S (obviously)
Android 2.3 SDK
USB Cable
PDAnet (for drivers)
Clockwork Recovery Image
Superuser
Part 1
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Once it has finished downloading, unzip it, and run the SDK manager.
Select whatever components you wish to install, but you MUST make sure you install Google USB Driver (Available packages > Third party Add-ons > Google Inc. Add-ons > Google Usb Driver package, revision 4) otherwise this guide will not work!
We must now install the Google USB Driver, or the phone will not be recognised as a device other than a mass storage device.
Connect your Nexus S to your computer, and put it in USB storage mode.
Put it in USB Debugging Mode (Settings > Applications > Development > USB Debugging)
Windows should now recognise your Nexus S when you plug it in, and ask to install drivers. It probably won’t find anything, so we need to help it manually.
(Installing drivers manually varies between Windows versions, so please refer to http://developer.android.com/sdk/win-usb.html if you are having trouble). Launch Device Manager (you can find it in Control Panel), find Other Devices, and listed under that heading, you should find Nexus S. Right click, and select Update Driver Software. Click Browse my computer for driver software, find your SDK folder, then the google-usb_driver folder inside it, click OK, then Next. This should install the USB driver successfully. Reboot your computer.
Power off your Nexus S, connect it to your computer via USB cable, and boot it into the Bootloader Interface (you can do so by holding down the Power and Volume Up buttons at the same time).
It should say LOCK STATE – LOCKED, in white just above the green Android. You are now ready to move on!
Part 2 - Fastboot oem unlock method - WIPES ALL DATA!
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use ‘fastboot oem unlock’ (the rooting command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn’t).
Now in the command prompt, type in (without the quotes) ‘fastboot oem unlock’.
Now turn your attention to the phone, and read through the new information displayed on the screen. Using the Volume keys select Yes, then press the Power button. This will WIPE EVERYTHING! I bear no responsibility for any lost data on your phone!
If everything is successful, on your phone, the LOCK STATE should now read UNLOCKED, and on your computer, the command prompt window should say something like this:
Download the Clockwork Recovery image (here if you don’t already have it) to your Android SDK tools folder (*Android SDK*\tools).
Rename the newly downloaded Clockwork Recovery image to ‘recovery.img’ (no quotes).
Now we need to flash it to our Nexus S, so enter this command into the Command Prompt (make sure it is in the Androis SDK tools folder!) ‘fastboot flash recovery recovery.img’ (without the quotes).
If all is successful, the Command Prompt window should look something like this now:
Download the superuser app to the Android SDK tools folder.
Power on your Nexus S, leaving it connected to USB.
Mount the USB storage, and drag and drop the superuser .zip file you just downloaded into the root of the internal SD card (so Computer > *Device Name*, not in any other folders!). It should look something like this:
Power off the Nexus S, and return to the Bootloader Interface (step 9, part 1).
Select Recovery using the Volume buttons, then the Power button.
The phone should reboot into Clockwork Recovery, but if not don’t panic, just repeat steps 9-12, including downloading a new copy of the file (mine only worked the second time around, don’t worry!)
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot. (You will now also have an unlocked padlock when you boot up)
Done! You now have to set up your phone again like when you first got it, but it will be rooted now.
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
Make sure Part 1 is completed.
Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot.
Done! You should still have all your data present on your phone, and have root access!
Notes
As AllGamer said in his tutorial:
It’s normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you’ll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you’ll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Keep this in mind! It's not because you did something wrong
Also, some root apps require BusyBox to be installed, as I found out with Titanium Backup, so once you set up your Nexus S again, head on into the Market, and download BusyBox. It installed fine on my Nexus S this way, and now TB works fine.
I hope this is the best, most thorough guide you will find on rooting the Nexus S. Enjoy! Feedback is appreciated, and I will help out if you need any extra help.
Your guide has been wonderful however I'm stuck on part 2, step 4. I tried writing in the path to my directory and they keep giving me whatever I wrote in the command prompt "is not recognized as an internal or external command, operable program or batch file"
"Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’."
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
STARSCR33M said:
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Click to expand...
Click to collapse
Ok so if you want to change directories in the command prompt, you need to use the command
Code:
cd
So in your case I would type in
Code:
cd c:\Users\Du\Downloads\android-sdk_r09-windows\android-sdk-windows\tools
That way is fool proof, however you could take a shortcut, because you are already in the Users/Du folder (because of how it looks when you first open it), you could just type in
Code:
cd Downloads\android-sdk_r09-windows\android-sdk-windows\tools
Hope that helps
ravidavi said:
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Click to expand...
Click to collapse
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
EDIT: New approach added, now there is choice and easyness for all
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
Click to expand...
Click to collapse
Thanks
Jonathon Grigg said:
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
Thanks
Click to expand...
Click to collapse
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step. Once you're in clockwork you pretty much own the phone. I'll be interested to see if someone can use clockwork to flash a new boot image once rooted without the unlock; if so I can't see any reason to unlock the bootloader. That said, mine is unlocked, and I like it that way, but many won't root for fear of losing data on the phone.
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it. I guess that's there own fault for not doing enough searching on their own...
Anyways, nice and thorough effort. I'm sure many will benefit from your additions to AllGamer's tutorial.
distortedloop said:
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step.
Click to expand...
Click to collapse
I have been wondering that myself. My guess is that for the average user you don't need to, but maybe it's for real power users who build their own ROM which has been fully modded or something, I'm not sure.
but many won't root for fear of losing data on the phone.
Click to expand...
Click to collapse
I definitely agree with that, and your guide is probably the best way for those people!
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
Click to expand...
Click to collapse
Exactly, this is one of the better uses for both methods. I already had to wipe my phone twice due to Samsung CS so I'm used to it Although it does give you a chance to clear out the apps you don't need. Doing that I noticed better battery life on my phone.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it.
Click to expand...
Click to collapse
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Thanks distortedloop
This is awesome cause i relocked my bootloader i really just needed root. Thanks!
Edit oops lost track of tabs open.
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Jonathon Grigg said:
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Click to expand...
Click to collapse
Nicely done. Thanks.
sam4free said:
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Click to expand...
Click to collapse
That's what I suggesting a couple of posts above (root without unlock to at least make a backup of user data).
Restoring a titanium backup would not re-lock the phone. A nandroid restore might, depends on what all it imaged and restores, but it's so easy to re-root, that doesn't seem like a big deal.
Jonathon Grigg said:
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Click to expand...
Click to collapse
Looks like you forgot to add the link in your copy pasta.
AtomicPC said:
Looks like you forgot to add the link in your copy pasta.
Click to expand...
Click to collapse
I've been working on it I just wanted to get it up here as soon as I could That's why I mentioned that the full guide is available on my website. I'm going back to school today, so I don't really have too much time for changing links now. Besides, most people on XDA should know how to look at the 'What's needed' part
Sent from my Nexus S using XDA App
Jonathon,
Thank you for posting this detailed guide to rooting without losing your data! I do have a question. As you've probably heard, there are a few updates coming soon and if they are like they were on the N1, they always broke root. So getting root back was tricky unless I "unrooted" before applying the update. Using your method, is it easy to "unroot"? Thanks!
No problems
As for your problem, I never actually had a N1 so I don't exactly know why that would happen. So far from the 2 updates available to NS owners it seems like the OTA update does break root but it appears to be the same to get it back again. Can someone confirm this? I haven't been through an update with my root yet.
As for unrooting, if you haven't unlocked the bootloader (so you have followed the new part 2) I think it is just a case of finding a stock image (I think there's a GRH78 one around here somewhere) and booting into Clockwork Recovery and flashing it. That should remove root and then also give you a notice to install the GRH78C OTA update so you get the latest version.
I think that is what you meant? If you did unlock the bootloader (using the original part 2) then I think you just have to follow the same steps as I mentioned just then but afterwards go back into the bootloader interface and run 'fastboot oem lock' and it should be right.
Sent from my Nexus S using XDA App
Question on Part 2- step 1.
Code:
# We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
hmanxx said:
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
Click to expand...
Click to collapse
When I tried to use the fastboot command with my Nexus S connected, it would hang and not do anything, despite leaving it for about 5 minutes. I searched online, and found the PDAnet solution, so I don't know what the difference is exactly. All I found the Google SDK USB drivers to do is enable you to see your device in Device Manager, however you could try it without the PDAnet drivers, and let me know what happens!
Thanks
Thanks for the prompt reply.. I tried out the google driver..it doesnt work under fastboot. I eventually get the fastboot enabled driver..that could explain why the pdanet driver required.
After i installed the fastboot enabled driver, i could test the connectivity under fastboot with "fastboot devices"
thanks going to try out rooting..i just want simple root access..without wiping data is a ++ ..
I managed to run fastboot boot recovery.img...going into clockwork menu..apply the superuser.zip.(for froyo version)..till completion..no word of failure..
However after rebooting, su and SuperUser.apk are not installed.( I used adb to check the system/app and system/bin folder.
Edit- manage to root properly after system mounting .
Just a note..to properly complete the rooting, one need to apply mounting then mount system before applying the Superuser.zip install from sdcard.
Prior to step 11, you may want to add the following steps for folks having problem to get the superuser.zip to install properly.
Originally Posted by droidmage
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
Thanks for the extra bit of info, I will attempt to add that in when I get a bit more time on my hands. when I did it it seemed to work fine so thanks for discovering that!
Enjoy your rooted phone
Sent from my Nexus S using XDA App

SUCCESS !! :) FM Radio app by HTC: Reverse Engineer: Please help

I'm working to enable FM radio functionality, RX and TX on HTC Legend and other devices with TI FM chip.
I need help to get this done ASAP. I'm an experienced embedded Linux dev, but I'm pretty new to smartphones and Android.
A few weeks back I managed to muddle my way through on phone gold card creation, downgrading, rooting, CWMod (2.5 ?) installation, CMMod7 nightly install, S-Off and new Radio flash. Since then I haven't flashed anything and probably forgot half of what I learned.
So now I want to flash the best ROM for the purpose of figuring out the audio routing "secrets" of the HTC FM app. Any suggestions for the best ROM for that purpose ?
Next, I could use some pointers to the best posts or web pages to refer to for flashing the HTC Rom, and then later flashing back to CM7. As easy as possible. Can I do something Nandroid like and save the entire state of the phone to easily get me back to where I started with CM7 ?
Yes, I AM a dev, but very much appreciate easy to follow step by steps that don't leave me scratching my head wondering if I'll brick my device or create some other catastrophy . Eg: Should I ignore those error messages or not worry ? Do I have to reboot 5 times while clicking my heels ? Etc.
Once I get the above figured out, perhaps this thread can be used for discussion of the observations and any reverse engineering results.
Thanks !
Well, the best ROM would probably be BlaY0's, as it has the FM functionality. Take a nandroid of that and then install CM (as that's what your developing for, ye?). Then nandroid the CM and you can easily switch between the 2 without the need to set it up again.
BlaY0's ROM is based of the official HTC one, so it would probably do for the reverse engineering stuff. Thus I don't think you'd need to go back to a stock HTC ROM. If you do you can just flash a pre-rooted one (found here) and that would do it.
TheGrammarFreak said:
Well, the best ROM would probably be BlaY0's, as it has the FM functionality. Take a nandroid of that and then install CM (as that's what your developing for, ye?). Then nandroid the CM and you can easily switch between the 2 without the need to set it up again.
BlaY0's ROM is based of the official HTC one, so it would probably do for the reverse engineering stuff. Thus I don't think you'd need to go back to a stock HTC ROM. If you do you can just flash a pre-rooted one (found here) and that would do it.
Click to expand...
Click to collapse
OK, thanks GrammarFreak. BlaY0's ROM 0.7 it is.
Hate to be/seem so newb-ish....
So I'm running CM7 now. So:
(1) Run ROM Manager Backup.
(2) Watch phone go into recovery mode with red triangle and exclamation mark.
(3) Don't freak as the backup will take maybe 10-20 minutes or so.
(4) Phone reboots back to CM7 I presume.
(5) Pull any important data from sdcard including ROM backup files.
(6) Download http://blay0.r3volutionary.net/b-0.7.zip
(7) Run ROM Manager to flash Blayo.
(8) Reboot and mess around with Blayo ROM.
(9) When done messing, optionally save Blayo ROM and mods with ROM Manager Backup.
(10) Use ROM Manager restore to return to CM7 ROM.
Sound good ? I don't even have to remember which key when booting brings up CWMod recovery mode ?
I couldn't find a canonical web page documenting CWMod/ROM Manager and it's usage.
Gee my phone has been stuck in red mode for a while now...
EDIT: So I'm reading threads and getting the impression the red triangle is not what I want. So I run "adb reboot" and will check and see if the backup looks good.
I can understand that the "community" has to somehow pull together to pool info, but my experience seems typical of what so many face.
In order to figure out some sort of semi-foolproof method of doing XYZ it seems I have to search threads all over to collect the full info. 50-100+ page threads are a challenge. Do I start with the first few posts or pages of posts, or should I skip to somewhere near the end for latest info ? Yes I can read to see if first posts are updated etc.
Before I started the rooting process on my phone, I read QUITE a few big threads from begin to end. And I made LOTS of notes to try and figure it all out and avoid problems. And my head got so full it almost exploded, and I almost sorta gave up, dived in, did a few more google searches on the way and thankfully finally ended up with a nicely open device.
But it all seems so ridiculously difficult, UNLESS you happen to come across some very succinct, accurate and informative HOWTO somewhere that works well for you.
/rant off
Ok, I want you to do a couple of things:
Forget about ROM manager, it's a piece or crap and it creates more problems than it solves.
So, you said you performed S-OFF, correct? Did you let the S-OFF procedure install ClockworkMOD recovery? Given the red triangle of doom I doubt it. No worries. Here's what you do:
Download this (it's the ADB tools) to a known location. Then extract the zip to a known location. Open a command window in that location (for the sake of this guide: C:\ADB) So open CMD (start, run, type CMD, hit enter) In CMD type "cd C:\ADB". Plug your phone into the computer (make sure you're using CM). Debugging mode should be on (you'll get a notification in the status bar of your phone). Now, I want you to download this (CWM 2.5) and save it to C:\ADB. In CMD type "adb push recovery.img /sdcard" Wait for it to complete. It will output a file-size, time taken and resultant transfer rate. When it's completed type "adb shell". You'll end up with a "#" and nothing else (if you get a "$" just type "su" and hit enter, and on the phone's screen accept the Superuser request). Now, type "flash_image recovery /sdcard/recovery.img", let it do it's thang. When you see the "#" type "reboot recovery", and your phone will reboot to CWM. This is what I refer to as a win
Now, from clockworkMOD you can use the trackball (move and click) to select "backup/restore" then "backup". Let it do its stuff. Once backed up you can flash B-0.7 and then back that up. Note down the name of each backup so you know which is which
TheGrammarFreak said:
Ok, I want you to do a couple of things:
Forget about ROM manager, it's a piece or crap and it creates more problems than it solves.
So, you said you performed S-OFF, correct? Did you let the S-OFF procedure install ClockworkMOD recovery? Given the red triangle of doom I doubt it. No worries. Here's what you do:
Download this (it's the ADB tools) to a known location. Then extract the zip to a known location. Open a command window in that location (for the sake of this guide: C:\ADB) So open CMD (start, run, type CMD, hit enter) In CMD type "cd C:\ADB". Plug your phone into the computer (make sure you're using CM). Debugging mode should be on (you'll get a notification in the status bar of your phone). Now, I want you to download this (CWM 2.5) and save it to C:\ADB. In CMD type "adb push recovery.img /sdcard" Wait for it to complete. It will output a file-size, time taken and resultant transfer rate. When it's completed type "adb shell". You'll end up with a "#" and nothing else (if you get a "$" just type "su" and hit enter, and on the phone's screen accept the Superuser request). Now, type "flash_image recovery /sdcard/recovery.img", let it do it's thang. When you see the "#" type "reboot recovery", and your phone will reboot to CWM. This is what I refer to as a win
Now, from clockworkMOD you can use the trackball (move and click) to select "backup/restore" then "backup". Let it do its stuff. Once backed up you can flash B-0.7 and then back that up. Note down the name of each backup so you know which is which
Click to expand...
Click to collapse
Thanks for the newb-friendly instructions. Much of I don't need, but may help others.
I'm running Linux, I've had adb etc installed for 2 weeks. I've got the SDK installed w/ Eclipse but never tried it, but have done App Inventor. And I've been poking around in the innards of the various source codes, binaries, firmwares and other files for the last 2 weeks too.
OK, I'll "Forget about ROM manager" and just use CWM after manually rebooting into it with Volume Down or whatever.
I'm pretty positive I'm S-OFF and have CWM 2.5.0.0.7 or so installed. ROM Manager says so. I have CWM on before I S-Offed using the Bell/Virgin modified alpharev boot disk.
I'll do the backup manually with CWM later tonight when I get back to this. I checked the SD and the backup isn't there, although there are still 3 backups I took when I installed CM7 2 weeks ago.
So I guess I do a complete flush or wipe or whatever when installing the new (or a backed up) ROM ? And since the backup is a nandroid type it will absolutely restore to exactly the same state as when the backup was taken ? But the SD card is not touched...
EDIT:
"adb reboot recovery" gives me red triangle of doom.
"adb reboot bootloader" gives me AlphaRev and I see S-Off and HBOOT 1.000000000
Did AlphaRev remove CWM ?
Given that you get the red triangle we can assume you don't have CWM installed to /recovery, you have it in fakeflash. Nothing inherently wrong with that, just FYI
As for your rant in post numero uno, I've often considered trying to put together a comprehensive "document" on the matter, but it'd take an age and would probably raise more questions than it'd answer.
"adb reboot recovery" gives me red triangle of doom.
"adb reboot bootloader" gives me AlphaRev and I see S-Off and HBOOT 1.000000000
Did AlphaRev remove CWM ?
Click to expand...
Click to collapse
See above about fakeflash. You could well use the image I linked above and use flash_image on the phone or fastboot to flash it
Fakeflash is pretty easy, I either do that or do my business in rom manager as I find that easy.
Rom manager method for installing a new rom:
If rom manager isn't installed, do so from the market
start up rom manager
tap "backup current ROM" (I suggest naming your backup, I just use the rom name)
Let it reboot and do it's thing
When it's booted back into CM7, open up rom manager again
tap "install ROM from SD card"
browse your sd for your rom and tap it.
You are presented with 2 check box options
Since we already backed up make sure "backup existing rom" is unchecked
If you are flashing a new rom, make sure "Wipe Data and Cache" is checked
If you are flashing a newer version of the same rom, you can leave this area unchecked as it will not erase the stuff stored on the phones built in memory
Press ok, let it do it's thing and thats it.
Place the fakeflash update.zip from http://forum.xda-developers.com/showthread.php?t=698404 on the root of your sd card
turn off your phone
Hold the volume down button as you press the power button
using the volume buttons, navigate to "recovery"
press power
your phone will reboot to th red triangle (of DOOOM)
Don't panic, hold volume up and press power (if it gives you an error just wait few seconds)
Using the volume buttons to scroll and power for enter choose "apply sdcard:update.zip"
Use the trackball and go to "Nandroid" if you are using ClockWorkMod 2.5.xxx fake flash or "backup and recovery" if you are using ClockWorkMod 3.xxx
hit "backup"
Let it do it's thing
If you're installing a new rom, scroll to "wipe data/factory reset", wait, then choose "wipe cache partition". If your installing a newer version of the same rom, don't bother.
Scroll to "install zip from sdcard"
scroll to "choose zip from sdcard"
choose your zip, let it do it's thing, and thats that.
You're SD is not touched at all during flashing, no need to backup those files.
Wow, can't believe I typed all that out...
TheGrammarFreak said:
As for your rant in post numero uno, I've often considered trying to put together a comprehensive "document" on the matter, but it'd take an age and would probably raise more questions than it'd answer.
See above about fakeflash. You could well use the image I linked above and use flash_image on the phone or fastboot to flash it
Click to expand...
Click to collapse
Re: rant, don't want to come off as complaining, I KNOW documenting semi-foolproof procedures is tons of work, to do properly. I understand a big problem is consideration of the large set of combinations of ROMs, recoveries, apps, S-On/S-Off states, Radios, etc.
OK, cool, I want "realflash" type recovery then. I guess that's one reason to have S-Off ?
I had to slightly alter your first command by appending a '/'.
EDIT: WOOHOO ! Success I think ! Feel free to skip the rest of this post unless you want to hear the details of my adventure...
Thank you ! Editing this post the last hour I wrote "Success ! " here anticipating such, but alas, I have some issue.
I don't know if I have to be extra patient as deodexing happens, Or if I'm stuck in some boot loop... I see "HTC quietly brilliant" and screen flashing on and off and re-writing the HTC spam.
Re: HTC FM app. OK, cool, I see :
ls -l /system/app/HtcFMRadio.apk
-rw-r--r-- root root 826176 2008-08-01 07:00 HtcFMRadio.apk
And bluetooth. Is there any way to switch normal media output, like from TuneIn radio etc, to my cheap new bluetooth headset ? I pushed the button in CM7 and I see I could start a voice dial, but I figured BT would take over all audio I desired routed through it.
-----------------
I did:
adb push recovery.img /sdcard/
adb shell flash_image recovery /sdcard/recovery.img
adb reboot recovery
In the CWM menu I had to select "Nandroid", and then "Backup".
That completed.
I didn't want to bother rebooting, so manually grabbed the backup files:
adb shell ls -l /sdcard/clockworkmod/backup/
adb shell ls -l /sdcard/clockworkmod/backup/2011-02-27.03.19.57/
mkdir cm7backup-2011-02-27.03.19.57
cd cm7backup-2011-02-27.03.19.57
adb pull /sdcard/clockworkmod/backup/2011-02-27.03.19.57/boot.img
adb pull /sdcard/clockworkmod/backup/2011-02-27.03.19.57/cache.img
adb pull /sdcard/clockworkmod/backup/2011-02-27.03.19.57/data.img
adb pull /sdcard/clockworkmod/backup/2011-02-27.03.19.57/nandroid.md5
adb pull /sdcard/clockworkmod/backup/2011-02-27.03.19.57/recovery.img
adb pull /sdcard/clockworkmod/backup/2011-02-27.03.19.57/system.img
Then to be sure:
cat nandroid.md5
md5sum *.img
Yes, looks good ! Now for Blayo:
cd ..
adb push b-0.7.zip /sdcard/
Goto CWM. Version 2.5.0.1, I had a 7 at the end before. Fine I'm sure.
Use volume up/down to select install from a ZIP. Press power to select. Oh, oh, shoulda used the trackball switch as it powered off.
Whoops, press power again and screen comes back, LOL. Choose zip from sdcard and use trackball switch this time. Move and select Blayo b-0.7.zip
Wonderfully wacky confirmation. Error message saying it can't find the zip file. Hmmm....
Reboot a few times and finally do "adb reboot recovery" and retry install from ZIP.
No go, get:
-- Installing: SDCARD:b-0.7.zip
Finding update package...
Opening update package...
E:Can't open sdcard/b-0.7.zip
(bad)
Installation aborted.
Try to open 98 MB zip file. No go. AHA ! corrupted file.
Try download from mirror 2: http://www.dkmdesign.dk/custom_roms/blay0/b-0.7.zip File is supposed to be 126 MB.
Gee I'm glad there's an unzip process that checks the integrity of ROM flashes.
So again:
adb push b-0.7.zip /sdcard/
And install, running..... Done !
Try to use power button to reboot. Use back key and "reboot system now". Cross fingers and offer the gods sacrifices...
See androids on skateboards again. Recall I may have to be patient as deodexing happens... See "HTC quietly brilliant" spam,,, in this context,good. Waiting....
Waiting.... screen flashing on and off and writing the HTC mind control spam.
Try reboot when tired of waiting and same thing. AFAICT, from "adb shell ls * etc" on the filesystem, Blayo ROM is installed but just won't stop flashing the HTC logo.
speedyink said:
If you are flashing a new rom, make sure "Wipe Data and Cache" is checked
Click to expand...
Click to collapse
Thanks. Maybe that's my boot loop or whatever problem now. I didn't recall seeing that option, but should be there with CWMod, so I'll try installing Blayo again after that.
There was some Wipe in main menu, and another w/ factory reset. Also in advanced menu I selected Wipe Dalvik cache. I left the Battery Stats alone. Hmmm. Naah !
Did all 3 wipe twice for good luck. Rebooted in between. Installed. Now waiting... Oh here's the HTC screen again. Time to read the Blayo thread to see how long to wait. etc.
Man what a pain ! Yet likely a world easier than the new paths I attempted to forge on my previous LG Optimus Chic resulting in a hard brick, LOL.
WOOHOO ! Success I think !
Welcome to the BlaY0 universe.. Just remember that many of us went through this journey as well to have our phone in same state Glad you got to fully download the BlaY0 rom from my mirror.. now happy reverse engineering..
Sent from my Legend using XDA App
whitetigerdk said:
Welcome to the BlaY0 universe.. Just remember that many of us went through this journey as well to have our phone in same state Glad you got to fully download the BlaY0 rom from my mirror.. now happy reverse engineering..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
Thanks. Figured I was finished messing with such nasties once I had CM.
(In case you aren't aware, I have scripts that make the FM radio "work" on CM7. I can scan and see RSSI as expected etc. Only "problem" is I haven't figured out the audio routing part yet so no sound, which is why I'm exploring the HTC app for it's special tricks.)
What I want to do now is try running my hcitool scripts and see if they work on Blayo ROM.
If yes, then the Blayo ROM has something the CM7 ROM needs.
If no, then there's likely some magic step required on either stock ROM or CM7 ROM and likely the HTC FM app is doing that step, directly or indirectly.
But the needed hcitool is not on Blayo ROM. I find 3 of the hci utils and install them. Now I can't get hciattach running, which I think is needed for hcitool.
I'm guessing I can edit /init.legend.rc and change service hciattach to enabled. Reboot and no dice. Try running from command line also with no luck. At one point it hung, but now:
# hciattach -n -s 115200 /dev/ttyHS0 texasalt 4000000 flow
Unknown device type or id
# hciattach -n -s 115200 /dev/ttyHS0 any 4000000 flow
Can't set device: Device or resource busy
Can't initialize device: Device or resource busy
# hciattach -n -s 115200 /dev/ttyHS0 any
Can't set device: Device or resource busy
Can't initialize device: Device or resource busy
Waiting with baited breath
Sent from my Legend using XDA App
pjgodd said:
Waiting with baited breath
Sent from my Legend using XDA App
Click to expand...
Click to collapse
Bated ? Baited=fish
Well AFAICT, the world of Bluez bluetooth and hciattach, hcitool, hciconfig and hcidump doesn't get along with the TI BT stack world of btipsd and btipds_cli.
I'll have to bust out the NDK and start trying APIs.
But FIRST, I'm happy to report that btipds_cli is a pretty interesting and cool tool. Once I rebooted, turned BT on and learned the quirky UI, it wasn't too long before I had FM audio coming out of the speakers or the headphone.
I even tried a BT over FM option in another menu, but no go. Next I'll try the FM Tx, cause I'd REALLY like to see if that works.
btipds_cli doesn't seem to want to start FM a second time though, so a few reboots might be needed for testing.
I think it's possible that the "14.start_audiO" option in the "4.fm_Rx/" is the missing link for FM in non HTC ROMs. I don't know yet if it initiates a digital PCM / SCO connection or just switches analog. I don't see any new processes for that but btipsd might be doing the good stuff.
Following this thread with great interest..
Sent from my Legend using XDA App
I still can't get the transmitter to work, despite all the commands seeming successful. Both with hcitool on CM7 and btipsd_ci on Blayo0.7.
So I think one, or both, of the following are the TX issues:
(A) - It is somehow disabled by the hardware. The Tx antenna pin could be tied to ground, perhaps even through a capacitor or something. It may even just be unconnected and unable to transmit a few inches because it's inside an RF shield.
(B) - The firmware file for the FM portion disables TX, yet the registers still respond as if it works.
(A) would be difficult to infeasible to fix.
(B) should be fixable by loading a firmware file from a TI FM chip device that is known to support transmission.
For a TI based device that is known to transmit, I presume firmware files for a TI or TI partner evaluation board may work.
So far I can't get hciattach and hcitool etc working on BlaY0 ROM.
I HAVE, however, gotten btipsd and btipsd_cli to work on CM7. I had to create the /data/btips directory and am running btipsd manually in foreground.
What I find is exactly the same as with my hcitool scripts: everything seems to work but actual sound doesn't exit the device. Even after doing everything else the same as with BlaY0 ROM.
The /etc/firmware files on both ROMs are identical.
So I'm thinking there is some other thing separating the two ROMs. Could be some HTC customized library, or a config file or who knows.
Hi Mike, your work is appreciated, i hope you wil get it to work. We have great legend dev's. Please BlaYo and. Ali Ba, help this guy!
mikereidis said:
I HAVE, however, gotten btipsd and btipsd_cli to work on CM7. I had to create the /data/btips directory and am running btipsd manually in foreground.
Click to expand...
Click to collapse
Then you got as far as I did a few months ago. The btipsd stuff can be found in the original init.legend.rc, if you are interested.
mikereidis said:
So I'm thinking there is some other thing separating the two ROMs. Could be some HTC customized library, or a config file or who knows.
Click to expand...
Click to collapse
"Customized library" applies here, but that's in fact a euphemism for "all kinds of proprietary code in the framework".
I gave up reverse engineering after looking at the disassembled HTC radio application. As I already told you there are loads of pointers to closed source TI code that can be found in the framework (= /system/lib/whatever.so). You will have to reverse engineer all those rpcs, libandroid_servers and god knows whatnot.
ali ba said:
I gave up reverse engineering after looking at the disassembled HTC radio application. As I already told you there are loads of pointers to closed source TI code that can be found in the framework (= /system/lib/whatever.so). You will have to reverse engineer all those rpcs, libandroid_servers and god knows whatnot.
Click to expand...
Click to collapse
Oh, there must be SOME shortcut...
Since I have the FM radio and audio working with the btipsd_cli. I'm not sure the answer would lie in the HTC FM app. Or at least the answer is in btipsd_cli also.
I'd love to find the source to btipsd_cli. I DO have source for TI's fmapp and fmstack-0.12 and I can see they share some, but not all code.
In a log I can see an HCI command is sent when audio starts; I just don't know which one or with which parameters.
btipsd_cli has some rather weird bugs that prevent me from experimenting well with audio routing. When I disable analog, audio keeps playing. At first I thought it was using digital, but now I think it's part of the buginess. When I select various digital options, various weird things happen, including a crash in btipsd for most of them.
If I can run some HCI queries, I might get better clues or the actual answer. I managed to get hciattach to sort of work with "texas" as the type, but I think I need "texasalt" and the binary I have that runs on Blayo doesn't support it. The CM7 binaries wont run on Blayo.
So unless there are some other tools I can use, I'm wondering if it's time to write an NDK app.
Unless I can increase the verbosity of the btipsd logging to tell me everything it's doing. Will check.
These AudioRouting strings aren't in the CM7 libandroid_runtime so I tried pushing the Blayo lib to CM7. GUI never boots fully, but no audio still using the btipsd_cli.
Same when I also replace libandroid_servers.so, bluez-plugin/audio.so and bluez-plugin/input.so
strings blayo/system/lib/libandroid_runtime.so |grep -i audiorouting
FM_RX_DisableAudioRouting
FM_RX_EnableAudioRouting
nativeJFmRx_SetAudioRouting(): Entered
nativeJFmRx_SetAudioRouting: fmapp_set_audio_routing() returned %d
nativeJFmRx_SetAudioRouting(): Exit
nativeJFmRx_disableAudioRouting(): Entered
nativeJFmRx_disableAudioRouting: FM_RX_DisableAudioRouting() returned %d
nativeJFmRx_disableAudioRouting(): Exit
nativeJFmRx_enableAudioRouting(): Entered
nativeJFmRx_enableAudioRouting: FM_RX_EnableAudioRouting() returned %d
nativeJFmRx_enableAudioRouting(): Exit
nativeJFmRx_EnableAudioRouting
nativeJFmRx_DisableAudioRouting
nativeJFmRx_SetAudioRouting
FM_RX_DisableAudioRouting
FM_RX_EnableAudioRouting
DisableAudioRouting
EnableAudioRouting

[HOW-TO/INFO] Bell FAQ [9-25-2011]

This is my attempt at a Bell FAQ, it is a work in progress.
Q. Why don't the instructions I found on how to do X not work?A. This is a development forum, sometimes things are written in shorthand assuming you know things you don't. At lot of things are specific to one carrier's phone or another. Sometimes things change and are now obsolete, something new was found, a better way of doing things, if you were not following it all along you are likely to be lost. Read between the lines, you are a human being with reasoning abilities, figure it out. ​Q. What should I do first?
A. Backup your phone. That means everything, especially your pds partition. Nandroid won't cut it and you have already modified your phone beyond the ability to get back if you can run it.
Ex. dd if=/dev/block/mmcblk0p3 of=/sdcard/backup/mmcblk0p3
Save your backup on your computer, create a zip of all the files, burn it off on cd/dvd, put it in a safety deposit box at your bank. Be prepared for bricking your phone. A lot of things mentioned in threads here are developed and tested for ATT phones, they may not work 100% on your phone.​Q. What is ADB?A. It stands for Android Debug Bridge or something like that. It is a program that runs on your computer that lets you talk to your phone using special commands. Your phone has to have adb enabled, it's a setting under application/development.
Ex. adb shell
This opens a linux shell connected to your phone. Linux is an operating system for computers, it is also used as the base for android phones.
Ex. adb install file.apk
Ex. adb push file /tmp
Ex. adb pull /tmp/file .​
Q. What is CWM recovery?A. Android phones come with a special boot configuration that allows for changes to the android system from a place outside the system. It is very corporate and does the job for official signed updates, but only Motorola and it's oems can sign the updates. Not much fun for us. CWM recovery is a replacement for the official recovery system that doesn't require signed updates.
You install CWM recovery using fastboot or moto-fastboot.​Q. What is unlocking the bootloader all about?A. It is the means of putting CWM recovery on your phone so you can install roms and other packages. It allows you to flash a partition with mods and have the phone not soft brick when you reboot. When the unlocked versions of the atrix bootloader were found it started a new round of mods. A lot of the threads prior to that are now obsolete.​Q. How do I unlock the bootloader?A. There is a huge thread already about this, see here.
WARNING: this is a permanent change to your phone.
Summary:
1. Download the archive
2. Extract the sbf inside, whatever it's called, that is the one to use.
3. Use linux sbf_flash or rsdlite from windows to install it.
3. fastboot oem unlock
4. Copy code fastboot spits out.
5. fastboot oem unlock code
6. fastboot reboot
You will see unlocked while booting and when you get into android you will have ~300MB of ram. This will need to be fixed. Also, you will lose all your data during the process, do a backup first.​Q. What is fastboot/moto-fastboot?A. It's a program to access the phone and do stuff, write phone partition images mostly. The stock one can only handle tiny system images, pretty useless for the Atrix, xda member eval- compiled the motorola version for us that can handle larger system images, do a search for moto-fastboot.
Ex. moto-fastboot flash recovery recovery.img.​Q. How do I fix the ram problem?A. I did up a CWM recovery zip to update the boot and recovery partitions to contain a kernel command line with the missing bit "[email protected]" added. See here.
There are other means of doing this, some boot images come prepackaged with the command line already embedded. There are ATT compiled kernels with a patch inside the kernel itself to do the same thing. You can search for those when you are ready to try things like custom ATT kernels on your phone.​Q. How do I root the phone?A. If you are unlocked and you have fastboot flashed a version of CWM recovery, it is trivial. By that I mean almost impossible for newbies to figure out.
It would go something like this:
1. Boot into CWM recovery.
2. use adb shell
3. adb push a su binary to the phone.
4. mount system as read write as /system
5. copy su binary to /system/bin
6. make sure it has the right permissions, 06755 mode , user root, group root.
7. unmount -l /system
8. when in android look on the market for Superuser.apk, install.
Every rooting method out there is all about putting su into /system/bin with 06755 permissions, most don't work anymore since Gingerbread. If you are looking for a simple, no brain involved solution, you are likely to get something working and also something else you didn't want like a replaced preinstall partition or an installed busybox with different functionality for some important system commands. (Busybox may be more up to date even, but if it doesn't do what is expected of the older version, it's still not good.)
Another way would be to create a CWM zip that simply puts the linux su binary in system with the correct permissions. Some info about creating your own can be found here. Doing this is more involved that just doing it manually, but it would be a good practice for getting into creating CWM updates.
Here is a link to a exploit someone did up to root the phone when running GB. Haven't tested it, and with an unlocked phone it is totally redundant, but it's nice that some found yet another security hole in the OS, seems similar in result to psneuter, so be sure to reboot the phone to fix the exploited system.
Seriously, if you are going to be reading or posting in the development section of xda for an android phone, take the 5 minutes to become familiar with adb and a few linux shell commands, it will save you hours of confusion and aggravation. If you fly blind trying things on your phone without understanding what you are doing you are eventually going to get into a place you can't get out of and need a new phone or REALLY have to struggle to understand things. You were warned. ​Q. How do I get back to stock?
A. You can't unless you have a backup of all your phone partitions and can update your radio and bootloader to be stock. Once you unlock your phone, it is recorded that you did so by blowing a physical fuse on the phone. This cannot be restored, you will need a new phone.
What does stock mean to you? When I bought my phone it had a certain radio, the bootloader couldn't be unlocked, the android system files had certain versions, etc. Beyond the android system there are 18 partitions that I know of on the phone, most phones do with 5-6. Every ota update or sbf files take the normal files and change them to something else, non android partitions get modified or replaced.
I have some solutions for getting close to stock, do a search for Gobstopper. There is one for Bell 2.2.2 and Bell 2.3.4, use one or the other. These attempt a full back to stock operation, that means the radio and bootloader will be stock, recovery will be stock as well. (All the partitions that are on the phone are written over with the ones that were on my phone when I bought it, with the exception of partitions 3 (pds), 15 (cache), 16 (data), and 18 (userdata or internal memory), factory reset clears cache and data, you don't want pds touched or internal memory.) Unlocked will no longer be displayed when you boot and you will no longer have CWM recovery installed. You will need to install the unlocked bootloader again and fastboot flash recovery again if stock is not what you wanted. (Your pds partition is not involved in this operation, so if you made changes to it, either directly or indirectly via a sbf this will not restore it, your pds partition contains individual phone information.)
More about sbf format here.​Q. What does the pds partition taste like?A. It's not really fit to eat. Now you know.
It is mmcblk0p3, a partition on your phone, it is mounted as /pds when android boots and contains a bunch of folders and files that nobody really understands fully but Motorola. Having a look at some of the files you will see things like your network physical address, bluetooth physical address. You will find threads where the display is all arsed up, cpu running at half speed, touch screen not working right, etc, all due to something going wrong with /pds. It is best to back it up and not mess with it. Restore it in an emergency. Maybe one day everything in there will be figured out, take a stab at it yourself.
See this thread by edgan for how to back up your pds partition.
See this thread by KeRmiT80 about attempting to fix your pds partition. Good motivation to see previous link.
​Q. I lost network data access after flashing X.
A. Check your APN list, if it's not a Bell firmware you are using, it probably doesn't have Bell's APN list. Scratch that, you don't know what that is or how to check it.
It stands for Access Point Name and a big list of them is stored on your phone in one big file (/system/etc/apns-conf.xml), each firmware has it's own version of it. Your phone will get two numbers from your carrier's phone network to do a look up in this list to figure out what configuration to use. So say it gets mcc 302, mcn 610, it will check the phone and look up 302, 610 in the file and read what it says there and use that config to try to connect. Now, another thing is that the phone knows what the home network is by these two numbers, embedded somewhere in the system. A foreign, non Bell carrier won't have Bell's numbers in there so your phone will think it's roaming. If you have roaming disabled, guess what, no data connection. Your carrier should be smart enough not to charge you for roaming, never had a problem with that, but you never know.
Here are the apn settings you can enter manually for your phone, see Bell's support link.
​Q. How do I get webtop over HDMI to work?
A. There are several threads on getting this to work on ATT phones and others, they are specific to the firmware being run on the phone. They involve copying two deodexed files to your system/app folder and replacing the ones already there. You will also need to clear your dalvik cache to get the new code recognized. They are DockService.apk and PortalApp.apk. If you are not deodexed then you also have to remove the .odex files for both.
Here is one thread for Gingerbread, in the zip there is one for ORFR that will get you to viewing the webtop on Bell GB, but applications don't load.
Here is another thread for Froyo that works, see the Bell specific bit in the OP. This does not work from Bell Gingerbread.​ To be continued...
Hoping the Mods sticky this
A link should be attached to the wiki as well. I will try to when I get home if it isn't done already.
shouldn't this be in general? or q&a?
Magnetox said:
shouldn't this be in general? or q&a?
Click to expand...
Click to collapse
Probably both. Most things referenced are in development.
Cheers!
Sent from my MB860 using xda premium
y2whisper said:
Hoping the Mods sticky this
A link should be attached to the wiki as well. I will try to when I get home if it isn't done already.
Click to expand...
Click to collapse
+1 this should be a sticky on either or both general or development...
cheers for this...this thread is going to help me with my youtube viewers BIG TIME!!
Very nice!
Keep it up NFHimself!
NFHimself said:
This is my attempt at a Bell FAQ, it is a work in progress.
Q. How do I root the phone?A. If you are unlocked and you have fastboot flashed a version of CWM recovery, it is trivial. By that I mean almost impossible for newbies to figure out.
It would go something like this:
1. Boot into CWM recovery.
2. use adb shell
3. adb push a su binary to the phone.
4. mount system as read write as /system
5. copy su binary to /system/bin
6. make sure it has the right permissions, 06755 mode , user root, group root.
7. unmount -l /system
8. when in android look on the market for Superuser.apk, install.
Every rooting method out there is all about putting su into /system/bin with 06755 permissions, most don't work anymore since Gingerbread. If you are looking for a simple, no brain involved solution, you are likely to get something working and also something else you didn't want like a replaced preinstall partition or an installed busybox with different functionality for some important system commands. (Busybox may be more up to date even, but if it doesn't do what is expected of the older version, it's still not good.)​ To be continued...
Click to expand...
Click to collapse
I used this method to root the stock Bell Gingerbread ROM. Works on an Atrix too. It's a quick download and easy for those people who may not be comfortable with the adb command line.
http://www.psouza4.com/Bionic/
thx
useful for newbies
but can you put some more details about returning to stock and explain the pds partition in details plz?
papakilo10 said:
I used this method to root the stock Bell Gingerbread ROM. Works on an Atrix too. It's a quick download and easy for those people who may not be comfortable with the adb command line.
http://www.psouza4.com/Bionic/
Click to expand...
Click to collapse
Had a look at the script in that one, should be fine, doesn't install a busybox or anything like that. I don't care for Superuser.apk in /system/app myself, but it won't harm anything having it there.
Cheers!
ytwytw said:
thx
useful for newbies
but can you put some more details about returning to stock and explain the pds partition in details plz?
Click to expand...
Click to collapse
I added a few things, anything in particular you wanted?
I am trying to avoid step by step tutorials or spoon feeding everything, so people who are lazy/careless will have to attempt to think for themselves. It just leads to more questions, more laziness, and bricked phones, and I don't have the time these days.
Cheers!

[How To][For Newbs] Unlock/Root/Recovery/Nameless ROM v7 (and SIM Unlock!) Desire C

It looks like CM10 is the way to go for ROM on this phone... if there's enough demand (or if someone hasn't already written one) I may re-write this for CM10 if I have the spare time.
Unlocking, Rooting, and installing Custom ROMs can brick your phone! If you're going to follow these instructions, then make sure you FOLLOW THEM! Don't skip steps, or assume you have all the software if you don't. Best case it just won't work but worst case you'll need to completely restore your phone and that can be difficult and sometimes impossible! Proceed with caution, especially for new users. I used Windows 7 Ultimate 64-bit for these steps -- however they will also work fine (if you're a semi-experienced linux user) on Ubuntu 13.04 and Fedora 18. Check my profile for my email if you have questions and nobody is answering here, as I don't come on XDA much anymore. Catch me over at eevblog.com/forum if you need, my username there is MrAureliusR.
Now I have a bunch of thanks Thanks everyone who gave me thanks! :good::good:
You'll Need:
HTC Desire C (obv)
Working internet connection to go to HTCDev Boot Unlocker
An archiving software, eg WinZip, WinRAR, 7zip, etc (in Windows)
A copy of Superboot for the Desire C, which you can download here . You can follow their instructions if you want, I'll be basing this part off of theirs anyway with additional info for newbs
A copy of a recovery module, namely CWM for Desire C -- found here (written by munjeni -- all credit goes to him!!)
A copy of Nameless ROM (I use v7, all versions can be found here (written by einstein.frat -- all credit goes to him!!)
Here's the direct download for Nameless v7.2 build 7
http://d-h.st/Ta5
A copy of WinRAR is helpful -- go here if you need one and pick the English .exe near the top.
Also, when going to the HTCDev website, pay close attention to the box that says Required Software. You need all three of the things they ask for, namely:
Android SDK Tools
HTC Sync Manager (it contains the USB drivers for your phone)
Java Runtime Environment
I won't give links for these as they provide them there. As I mention below, these are super important! Don't forget!
IMPORTANT NOTES:​
ALL the files you need (with the exception of software that is downloaded and installed (ie Android SDK Tools and HTC Sync Manager, WinRAR) should be put into C:\Android ... this makes things SO much easier when you go into command prompt as all you need to type is cd C:\Android before typing the other commands I give.
Another point to keep in mind -- any time you need to put the Desire C into "bootloader" mode, you need to disconnect the phone from the USB cable, and take the battery out, put it back in, and power on by holding Power + Volume Down at the SAME TIME. Easiest way for a newb to do this is push Volume down FIRST and hold it, then hold the power button too till the screen lights up. If it just boots normally, you didn't take the battery out. Hold them till the screen lights up with a bunch of text. You'll use the volume buttons to move through the menu, and the power button works like the Enter button - it selects whatever option you have highlighted. Before you finish step 1, it will say ***LOCKED*** at the top. Afterward, it will say ***UNLOCKED*** ... also, you always need fastboot mode. You have to select this from the list. Sometimes, you might need to select Bootloader and THEN fastboot. Either way, for any of these steps to work, it needs to say FASTBOOT USB at the top above the menu options. This means you've selected fastboot mode AND the USB cable is plugged in, plus the drivers have been installed and your computer can communicate with the phone (FYI this is why HTC Sync Manager must be installed).
This method, like all ROM installs, requires a factory wipe. This means that EVERYTHING on the internal memory (texts, contacts, apps that aren't on the SD card, calendar info, basically all your personal info) will be wiped. YOU SHOULD DEFINITELY DO SOME BACKUP FIRST! I will stress there are TWO TIMES at LEAST you should back everything up -- first, right now, before you've done anything, and second, when in recovery mode right before we wipe again and overwrite the original ROM. That way you have fail safes and an easy way to restore in case of error. If you follow the instructions closely, you shouldn't have any problems... also, if you later want to relock and unroot, having your stock ROM is invaluable! It's quite likely you'll never get it out of your wireless provider!
Whenever I mention CMD or command prompt I'm telling you to go to Start --> Run and then type in "cmd" (no quotation marks) and hit enter
Step 1: Unlock your Bootloader
​ So, the first step is to unlock your bootloader. As I mentioned before, there are instructions on the HTCDev website. But I'll give you quick pointers on that process:
Go to the HTCDev website
When you select your phone model from the list, the Desire C is NOT listed. Instead, scroll to the bottom of the list and click "All Other Supported Models"
HTCDev will require you to register. It's a good idea because that website can be very useful
The website will also ask you if you are sure you want to do this -- remember, doing any of these things can and probably will void your warranty -- make sure you're willing to part with it before proceeding.
MAKE SURE you have all the software I mentioned above installed. I cannot stress this enough as many, many questions on other threads were resolved by simply ensuring the latest versions of all three are installed. Just follow the links before you do anything else on the Step 1 page. Some of the files are big (>100MB) so it might take a while depending on your connection speed. Be patient -- these are vital to everything working!!!
Follow the steps CLOSELY. It's pretty easy, even for someone who doesn't have much experience. However if you can open My Computer and you know where the Run... dialog is in Windows you'll be fine. A key pointer that I almost missed is you HAVE to remove your battery, you can't just choose the Power Off option after hitting your Power button. This is because you need the phone to coldboot (boot from scratch)
At the end of three pages, they will email you a file that you'll need to finish the process. This is why you had to register, and why it's important to use a real email address. Before you follow that last step, make sure you select, copy and paste EXACTLY what they ask for, or else it probably won't work.
You'll get the binary unlock file via email. Download this, and copy it to the same directory you used for the previous steps (I used C:\Android because it's the easiest to get to when using Command Prompt ... FYI if they don't mention it, you have to use the command cd C:\Android (or whatever directory you put the files you gathered in the second page into) before it will recognize fastboot as a command, because you need to be in the directory that executable is in. Super important for newbs who haven't used cmd before!!!
Follow the last few steps, and voila! You have a bootloader unlocked HTC Desire C :laugh:
Was that so hard??? Not really. Now for the second step, installing Superboot. This step is pretty easy too.
Step 2: Load Superboot​
So next step. This one is quite a bit easier.
Go to this link and download Superboot r1 for Desire C
Extract the .zip to a directory (I used, again, C:\Android\r1-golf-superboot or something like that)
Reboot your phone into bootloader mode, just like you did at the beginning of the HTCDev steps in the last step. It should now say ***UNLOCKED*** at the top. If it doesn't, you did something wrong in the first step. Go back and re-read everything and make sure you did it right. Remember, every time you want to get into bootloader mode, you have to remove the battery first, then power on while holding Volume Down
Once your phone is rebooted into Bootloader, and it's connected via USB cable, select Fastboot (again, just like last time) in the menu. It should say FASTBOOT USB at the top
Now go into the folder you created with r1-golf-superboot in it, and just double-click install-superboot-windows.bat
If it was successful, it'll say so. Nothing will have changed on the phone's screen. Reboot the phone. It should automatically load and reboot the phone. While booting up it may take a bit longer because superboot is setting up your superuser privileges.
For advanced users:
Another easier way (at least for me) is once you've extracted r1-golf-superboot.rar, copy the boot.superboot.img into your working directory (C:\Android)
Boot the phone into fastboot USB mode
Type the command: fastboot boot boot.superboot.img and bang! It'll load and reboot automatically. I like this method because I like to do every command line step by hand, call it a Linux user habit.
Now you're unlocked, and Rooted!! How easy was that? Superboot is great for newbs because it automatically installs superuser (su) and the superuser APK, no messing around with anything else required.
Step 3: Install CWM Touch Recovery for HTC Desire C​
This step is super, super important because it allows you to back up your current config and also to wipe everything. Backing up is almost completely necessary! If something DOES go wrong you can just restore the backup you're going to make. Plus you also use CWM Recovery mode to later install the Nameless ROM (or any ROM) from a .zip file.
Again, there's instructions on the download page thread, but I'll help with some pointers for newbs here.
Go to this link and download the file. It's an attachment called CWM_Touch_Desire_C.rar on the first post. If you have trouble opening this .rar then just search WinRAR in Google and download that, it's free and works great. Don't worry, even though it's a beta in my experience it's completely stable. Not to mention a great piece of software by munjeni
You're going to use fastboot to install this. It's a quick, pain-free process like the last step. Just remember to do everything exactly as follows:
Extract the one file in the .rar (recovery.img) to C:\Android
Open up cmd again and go to C:\Android (cd C:\Android)
type in fastboot flash recovery recovery.img and hit enter. Boom! Done. just remember to reboot your phone before cotinuing with the next step.
EDIT: Also, before installing the ROM, it's a VERY good idea to make a backup using CWM Recovery. Boot into bootloader mode, select recovery, choose Backup and Restore, and pick Backup. If it defaults to your internal memory, then pick backup to external SD.
NOTE: It's up to you which recovery to use. Once you've downloaded a compatible .img file, the easiest thing to do is rename it to recovery.img and type the above command.
Here's a link to TWRP recovery for the Desire C: http://forum.xda-developers.com/showthread.php?t=2148015
Step 4: Install Nameless ROM v7 for HTC Desire C​
This is the final step, and the most difficult one. There's a couple different steps that need to be done properly for everything to work.
UPDATED FOR VERSION 7 OF NAMELESS
Go here and download version 7 to your desktop. (NaMeLeSsR0m_v7.o.0_HtCDeSiReC.zip) The boot.img is inside the archive now (as of v7, if you have an earlier version you need to get the boot.img that goes with it, ask in this thread or in the Nameless thread)
Once the .zip for the ROM is downloaded, remove the boot.img and put it in your android folder (C:\Android). Copy the rest of the archive onto the SD card. You can either do this using a cardreader (if your computer has one built-in or you have one for your camera or something) or because you have the HTC Sync Manager installed you can just boot into your regular version of android and when you connect the USB cable, pick "Disk drive" as the connection type. Then just drag and drop the file into the SD card. MAKE SURE that you're a) copying it to the SD card, NOT the internal memory b) copying it directly into the top level folder of the SD card. For example, if it shows up as drive J:, then you copy it to J:\ and not into any folder
Now, reboot your phone back into bootloader mode. Again, select fastboot, and make sure it says FASTBOOT USB. Remember, you need to unplug the USB cable, remove the battery, power up into bootloader (Power + Volume Down) and then reconnect the USB cable after it boots (see Important Notes at the top if you've forgotten).
Open cmd and go to C:\Android
Type in fastboot flash boot boot.img and bang! It's done. This step is crucial or your Wi-Fi won't work -- also with v6, this is necessary for other features to work, like customization. If you've come here and you've already installed the ROM and your Wi-Fi just says error, you need to flash the boot.img onto the phone.
Now that you've flashed the boot.img, select Reboot in Bootloader on the phone. You can disconnect the USB cable now. However, make sure your phone is mostly (minimum %80) charged
When the bootloader comes up again, this time select Recovery. This is the software you installed in the last step. This is a REALLY great little recovery program that has a lot of neat options and awesome features. It's very easy to use and it even uses touch! However I have huge hands and I just continue to use the volume up/down and power buttons to move through the menus.
Once you're in recovery mode, the FIRST THING you should do is select backup/restore and backup everything, to the SD card. I had a problem with this step: even though I picked SD for the backup it told me there was only 93MB of room and it probably wasn't enough. This makes me think that it was trying to backup to internal memory. (EDIT: You have to just choose backup, not backup to SD card, because it's switched -- backup to SD card will try to backup to the phone's internal memory... the reason I didn't realize this earlier was because I had very little room left on my 2gb sd card and thought that 93mb seemed right ^_^) Anyway, IF THAT HAPPENS TO YOU, and you are unable to back up, DO NOT PROCEED ANY FURTHER. If people are having this problem I will find a way to fix it. Personally, I was VERY VERY stupid and decided to install the ROM anyway, without a backup -- however, if my phone had died or any of a thousand other things had gone wrong I would have had MAJOR problems... DON'T do this without a backup!!!!! I cannot stress this enough. If something goes wrong and you have a backup to restore you will feel like such a pro. If something goes wrong and you don't you'll feel like a fool and spend hours trying to restore your original ROM.
After you've backed up, go back to the main menu (using the touch buttons at the bottom of the screen) and select wipe data/factory reset. Scroll down to the one 'Yes' option and select it.
Then go back to the main menu, select wipe cache partition, and again say Yes.
Go back to the main menu again, go to Advanced, then select Wipe Dalvik Cache, and select yes. NONE OF THESE STEPS CAN BE UNDONE -- make sure you've backed up first!!!
Now, go back to the main menu, and select "install ZIP from sdcard" ... scroll down and pick the Nameless ROM ZIP file that you copied earlier (NaMeLeSsR0m_v7.o.0_HtCDeSiReC.zip)
NOTE: einstein.frat has changed the installer as of v7 build 5 and up. Simply pick "wipe + install" if you want to do a fresh install, and then pick "Standard" for installation type. If you are upgrading from a previous version of Nameless, then simply go to mounts and storage in the CWM main menu, format /system & /cache, then go back to the main menu; pick advanced, and then Wipe Dalvik Cache. THEN proceed with the installation, and pick don't wipe.
You're basically done!!! Once the phone reboots, DON'T freak out if it takes upwards of 5 minutes on the boot screen... which is now an animation of the world turning!
Enjoy.
You did it!! Hopefully you didn't have too many problems. I really hope this thread helps someone, I remember when I had little experience and I was SO thankful when people put all the info in one place like this. If you did, click on THANKS, I'd appreciate it.
To other users -- if I made any huge, glaring errors please let me know ASAP. I re-read this a couple times but I'm pretty exhausted, I typed this all at one sitting. I did this to help show that I really am serious about this forum and I want to help & learn as much as possible. Plus I'd like to majorly thank all the people who wrote all the amazing software that went into this -- you know who you are!!!
Best of luck
-AC
PS I'll do my best to answer any questions users have in this thread. In my opinion NO QUESTION IS STUPID!!! So don't be afraid. HOWEVER at least do a cursory search, it might already be in here or somewhere else.
CUSTOMIZING THE LOOK OF YOUR DESIRE C (MOVED UP HERE)​
Wow! I've been off XDA for a bit, and I just came back around now (was away visiting family...) can't believe Nameless is at 5.0! I'm installing it now and then I have to re-push my custom battery, lockring and boot animation... I'm going to add those three things in this post here, just so all the info is in one place. Remember that to make your phone look really sick a good wallpaper makes ALL the difference. You can find some sweet ones on deviantART and also in the original Nameless ROM thread, einstein.frat lists some cool ones in a post there... I actually use one of the ones that he listed!!! All together I think my phone looks pretty sick, have a look here and here !!! Remember that if this post helped you please click THANKS, these walkthroughs look short but this one took me over an hour to put together. The one above took way longer!!!
REMEMBER THAT YOU HAVE TO DO THE COMMAND adb shell sysrw BEFORE YOU CAN PUSH ANY FILES!!!
LOCKRINGS & BATTERY ICON MODS:​
So in the original Nameless thread, somewhere... einstein links to a page full of custom lockrings. I won't go into too much detail in making custom lockrings, but I will explain how to push them onto the phone. Don't follow instructions elsewhere -- if you have all the proper software from my original post that's all you need with the Desire C. Lockrings need to be .jpg, and they need to be 171 x 171 pixels. They also need to be named lockscreen_ring.jpg. You can make pretty much any image a lockring but it's cooler to choose something that's circular. I'm a HUGE Gears of War fan so my lockring looks like this: (red one in the upper left) ... if you want to use any of these go to this post but DO NOT look at his steps!! I'll explain it much simpler here. Just use that page to harvest yourself a lockring.
{
"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"
}
REMEMBER THIS IMPORTANT TIP: you have to use a program like Photoshop to resize the image to 171 x 171 ... YOU CANNOT USE MS PAINT as it just crops and does not actually resample the image... and 'resizing' it in paint by dragging the little handles creates a gross, blocky, choppy, crap image that nobody wants on their nice HTC Smartphone I downloaded a program called Paint.NET which is actually a great image editor. It's free and does a great job making lockrings and/or battery mods.
Battery mods are more difficult to make... because most battery mods that you'll find are not prepared properly for the Desire C, unless you are comfortable with the stock one you actually have to harvest a preview image of a battery mod, chop it into 100 equal pieces, and the save each one as a different 'frame'. This is a very complicated (and frustrating to do by hand!!) process... IF YOU WANT to try the battery mod that I made (warning: it's not perfect... I mean, it looks fine but if you watch the battery icon while it's charging you'll see what I mean ) I will include it in this post along with my Gears of War lockring...
LOCKRING STEPS:​ Once you've got your lockring ready, follow these steps:
Download this file - HtcLockscreenLite.apk (new link, I'm hosting it now)
Open HtcLockscreenLite.apk with WinRAR
Drag and drop your lockscreen_ring.jpg to the folder /res/drawable-mdpi/ INSIDE the HtcLockringLite.apk archive. If anyone is confused by what I mean by this, don't hesitate to ask and I'll clarify with screenshots.
Put your now customized HtcLockringLite.apk in your ADB folder (C:\Android in my walkthrough above)
Open up cmd and dir to the ADB folder
Remember to type adb shell sysrw first
Type command adb push HtcLockscreenLite.apk /system/app/
Reboot and voila! There's your lockring
EDIT: Answered my own question. You have to re-push the lockring even after pushing SystemUI.apk So the one I included will ONLY do my battery mod.
BATTERY MOD STEPS:
​ Ugh, I'm getting tired as it's 1:30 AM here in Canada (I wrote the boot animations part about 20 minutes ago, if you were wondering LOL). So I'll try and make this sweet and to the point.
If you're a newb, and you're already nervous just being on the xda-developers website, then making your own battery icon might not be that easy for you. You can do it, but it's not in the scope of this walkthrough. I hope you already have all the .png's needed for the battery modification (If you don't and you want to use the custom battery that I converted for use on this phone, then just skip ahead to the steps below. As far as I can tell this SystemUI.apk that I included below will not change your lockring as well...)
I'm going to assume you already have the 200 or so files that make up the battery icon, as follows: (or that you're using the linked file below)
stat_sys_battery_0.png
stat_sys_battery_1.png
...
stat_sys_battery_100.png
stat_sys_battery_full.png (an exact copy of battery_100.png, for some reason...)
stat_sys_battery_charge_anim0.png
stat_sys_battery_charge_anim1.png
...
stat_sys_battery_charge_anim100.png
stat_sys_battery_charge_animfull.png (for some reason there's this one too)
If you have all these files, in the size 21 x 21, .PNG format, then you just need to open SystemUI.apk with WinRAR and drag and drop all of them into the /res/drawable-mdpi/ folder. That's MDPI not HDPI ... It'll probably ask you to overwrite if you did it properly. Let it import, and then follow these steps:
Copy your new SystemUI.apk to your ADB folder .. my custom SystemUI.apk is here (if DropBox cuts it off for bandwidth reasons just PM/email me and I'll get it to you).
Open command (cmd) and dir to your ADB folder (outlined above)
Remember to type adb shell sysrw
Type the command adb push SystemUI.apk /system/app/
Voila!! All done. Type adb reboot and check out your sick new mods!!!
BOOT ANIMATIONS:
So you need to find a boot animation that's compatible with this phone, and this version of android (4.0.3). They usually come in .rar format so of course you need WinRAR. Extract this to your folder that you used above, (C:\Android).
The bootanimation that I use can be downloaded here. That bootanimation was made by user kevinrocksman ... once downloaded you extract both files to C:\Android, open up cmd and dir C:\Android (or again, wherever your files and adb are) and then type: (if your file names are different, then PM me and I'll help figure it out. I'm guessing that all the files need to be in a .zip called hTC_bootup.zip no matter what the frames are... I can help )
adb push hTC_bootup.zip /system/customize/resource
adb push htc_boot.mp3 /system/customize/resource
And presto!! Do a reboot from adb by typing in reboot and watch the magic happen Technically that mp3 could be anything, as long as you adhere to the format (ie, MP3, 320kbps, filename: htc_boot.mp3, length 3 seconds). Actually, I have a feeling that mine glitched, because that sound seems like it should be longer than 3 seconds, but hey, its still cool so I haven't screwed with it yet.
EDIT: I have a new .mp3 that's way cooler, it sounds like an old-school modem booting up! You can replace the one above by downloading it here
S-on ?
reserved
paslanmaz said:
my brother has this phone we wannt to play around but ı have question about s lock phone says S-ON so should ı unlock it first at start or ı can do root ,custom recovery and flash rom or ı have to s-off first ı could not find satisfying way to s-off for our phone inside tons of pages ı have read for
long to short ı can simply follow this steps with s-on phone or ı should s-off first and how
Click to expand...
Click to collapse
No, there's no need to S-OFF the phone for the steps above. I did all of this with my S-ON Desire C.
-AC
AirCombat said:
No, there's no need to S-OFF the phone for the steps above. I did all of this with my S-ON Desire C.
-AC
Click to expand...
Click to collapse
thnaks for respond ı am going to try asap hope everything goes well by the way my brother claim him phone copmrass has frozen after spftware update but according net search phonw has not got comprass comprass some nfc and back light issue this phone full of suprises
Yeah I just got this phone four or five days ago and I was surprised to find those things out too. No compass, no backlit keys, and it still needs a lot of developer work. But despite this it runs great, very smooth especially with Nameless.
Hope all goes well feel free to ask any more questions in this thread. I'll be happy to help.
PS I hope you and your brother realize the risks involved. Make sure you are very careful and follow the steps exactly.
Sent from my HTC Desire C using xda app-developers app
what about addons?
guide to installing addons? havent been able to find one?
pokegeek said:
guide to installing addons? havent been able to find one?
Click to expand...
Click to collapse
What add-ons do you want to install?
If you want to install custom bootscreens or lockrings, just go to the nameless thread and einstein.frat outlines how to do it... he even shows you how you can make any lockring you want, technically.
thanks
thanks i couldnt find the post
but what i ment was like when he first released his rom he had a long list of add ons to install but now he puts them all into one easy rom! yay!
oh yeah does anybody know where i can find the 1024 mhz overclock for this device like the guy is useing thats at the top off the antutu list?
phone: htc desire c
rom: nameless V3.0.0 (going to be 4 very soon)
kernal: 756 overclock
latest antutu score: 2565
Already rooted my phone, but did not install recovery
Deary me, I have a problem. I rooted my phone easily using the instructions on a different website. Unfortunately I cannot post links until I hit 10 osts, which is the first time I ever seen that on a forum! Now I want to install some sort of recovery so I can flash some ROMS and apply tweaks and so on. The guide on that forum only helped me root the phone. Do I need to take some precautions when I install the touch CWM?
MrToastedAndroid said:
Deary me, I have a problem. I rooted my phone easily using the instructions on a different website. Unfortunately I cannot post links until I hit 10 osts, which is the first time I ever seen that on a forum! Now I want to install some sort of recovery so I can flash some ROMS and apply tweaks and so on. The guide on that forum only helped me root the phone. Do I need to take some precautions when I install the touch CWM?
Click to expand...
Click to collapse
How do you mean? If you just follow the directions above it'll go nice and smooth ... lemme know if you have problems...
thank for the rooting guide......
Will flashing different kernals when installing the rom help with battery life?
How do you unlock the sim? Supposedly I have a locked Desire C, but I don't think so.
Also, I've followed the walkthrough reaching the Nameless ROM. It all worked fine, but I didn't like theme of the phone, and when changing I noticed some graphical errors in the clock, etc... so I wanted to go back to my backup (note: you don't make it in the internal sd, that's the internal memory, but just the standard backup). And when I got back to it, my wifi doesn't work. I think it's the Nameless boot.img I backed up, since that is flashed before backups are mentioned... I also tried the stock rom from here but Wifi has an error there too. Where can I get a stock boot.img?
AirCombat said:
How do you mean? If you just follow the directions above it'll go nice and smooth ... lemme know if you have problems...
Click to expand...
Click to collapse
Thanks alot for the reply! I will try this out, but I have already rooted my phone so I will try from step 3. We need more development for this phone! Also, does Nameless have a working Wi-Fi?
Tried backing up to SD card, only 93 mb of space!
---------- Post added at 05:48 PM ---------- Previous post was at 05:28 PM ----------
Haha, awesome. Instead of using backup to SD card, I just chose backup. That default for Backup is SD card while backup to SD card is the opposite, backing up to the phone. I downloaded Nameless v5.0 and the bootscreen is a earth spinning with HTC DESIRE C NAMELESS on the top in Landscape. Hopefully this goes fine... Was really easy installing Touch CWM Recovery. You should update your guide at where the part says "backup to SDcard" to just say choose backup. Phone booted up now, didn't take 5 minutes for the 5.00 THANKS A BUNCH!
I already stated that in the post above you, but it's good you found out by yourself.
BTW the CWM backup gave me a bad md5 checksum, noticed a few people also have the problem, could be due to the CWM itself.
Anyway, I was able to solve it with this guide: http://forum.xda-developers.com/showthread.php?t=1835914
And we have our own proper sub-forum for DesireC!
Check it out: http://forum.xda-developers.com/forumdisplay.php?f=1989
Mods should sticky this thread in the Desire C sub forum.
Installed Nameless v5.0 and it is running very stable, my daily driver, no problems except for the occasional slowdowns but I guess that's a problem with Android. Unfortunately, a moderator locked the Nameless development thread
Moved to Desire C General as per OP request.
Sent from my Micromax A57 using xda app-developers app
I cant root my phone can u teach me ?
sarthak bhave said:
Sent from my Micromax A57 using xda app-developers app
I cant root my phone can u teach me ?
Click to expand...
Click to collapse
Do you have a desire C? If you want to root your micromax a57 you should search the forums here. If you can't find any info try googling it. If that doesn't work I might be able to help but my area of expertise is currently HTC and LG phones.

Categories

Resources