Related
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
hi, this is how i managed to get root working on my tab, everything went fine for me till it came to booting into recovery then nothing use to happen so i combined two separate guides to get it working. thanks (bcmobile and 411tecknology)
the command in "(getting root 5) )" worked for me as i was getting stuck with "fastboot flash recovery skitzandroid-recovery.img"
i unlocked the bootloader by firmware upgrade the the following
for all those people like me with no experience in dos commands or linux, hope this works for you
PREPARE:
1) With your Tab in fastboot mode (step 1 of “GETTING ROOT” below), make sure you have a working fastboot implementation:
working dir\\fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won’t get any response.
2) Downlad the two files attached to this thread
3) create a folder in drive c naming it "root"
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!) c: root
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder( c: root) should now have 1 IMG file and one ZIP file.
6) copy fastboot files to the the folder that you are going to use as working dir ( c:root)
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
working dir or c:\root>adb push skitzandroid-10-1v-root.zip /sdcard
GETTING ROOT:
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
keep doing cd.. until you get to "c:>" then
cd/root
5) Run the following command:
c:\root> fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options)
to select “Install zip from SDCARD” (or something like that)
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
Once complete, use the Volume rocker to select “REBOOT” from the menu and press (tap!!!) the POWER button to confirm selection.
9) YOUR’RE DONE. Press the thanks button on this thread to continue
TESTING:
Check your apps menu to confirm the existence of SuperUser app.
whats wrong with this?
http://forum.xda-developers.com/showthread.php?t=1079781
Nothing!
I used it on UNLOCKED 10.1v (not from Vodafone) and had no data loss!
Great, Thanks
Frank
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
TNTCOSMOS said:
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
Click to expand...
Click to collapse
once you start your device in fastboot mode and connect it with the computer to make sure your device is recognized by the computer you open command prompt take it to your working dir.. (ie. c:>root) in our case type fastboot devices and hit enter, if your computer recognized your device you will the serial number under it.
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
assuming you have installed sdk if not please do so, then staying in sdk go to
(C:\android\android-sdk-windows\platform-tools ) by clicking your mouse in desktop
(not cmd prompt). above eg.. is how i installed sdk on my desktop yours may be different, now in platform-tools you will see two files called fastboot copy them both to to your folder called ..root.. and you are set to go.
bottom line is if you want to start fastboot from any folder in cmd you have to have these two files in the folder.
also if you know that your device is detected by your computer dont worry about step 3. all it does is tell you that your device is connected.
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
TNTCOSMOS said:
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
Click to expand...
Click to collapse
Glad to hear that you finally got the root.
same problem
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
i've tried with pdanet too but it's not working....like the computer can't see the device...any ideea ???
and when i write "fastboot boot ......etc......" it says <waiting for the device>
please help
You need the drivers installed for fastboot, have you installed them? Please have a look at the [Guide] Unlock your bootloader thread. it contains all the details to get fastboot working.
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
zbuggy said:
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
Click to expand...
Click to collapse
The easiest way if you are rooted is to install rom manager from the market. It has an option to reboot to recovery if you have CWM installed. It also allows you to update to the latest CWM recovery if there is one.
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Download latest rom and instructions from samfirmware.com using odin Get ur tab into fastboot mode with 3 button recovery and start from scratch.
It should work out
Sent from my GT-P7500 using Tapatalk
zbuggy said:
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Click to expand...
Click to collapse
Do the following. If you have not yet odin.
Download the full rom.
Follow instructions in how to get into fasboot in sticky thread.
Once in fastboot you can load recovery via it, to do that download the recovery from droidbasement.com/blog, search on pershoot's website for recovery 4.0.4 if i remember correctly then type
fastboot boot recovery.img
where recovery.img is the name of the file you downloaded from droidbasement.com
Recovery will then load give it a minute or so.
Once loaded you can push the downloaded full rom via adb. That is part of the android sdk.
Like this: adb push romfile.zip /data/media/ (this will take a few minutes)
Then in cwm instal rom.
I hope it helps. Btw, remember you need to flash the wipe script of the rom before you install the rom if you are comming from stock.
Send from my GT-P7100
10x everybody it worked!!!!!!!!
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
DannyBiker said:
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
Click to expand...
Click to collapse
Hello,
I have been successful with rooting on win7. With win xp - after a few day struggling - fastboot did not give a go. Hope this helps
I just can't get the "Adb Original" signature from Pdanet. I always get standard Adb. I add the galaxy tab lines in the .inf file but still...
Do you guys edit the inf file with Wordpad or another tool ?
HELLO TO ALL…..
By 3xeno-
This procedure works only on devices that are S-OFF'ed with Revolutionary or have their bootloaders unlocked with HTCDev. Also, its perfectly usable on Linux as well.
I OPEN THIS THREAD SO THAT ANY NOOB WHO WANTS TO FLASH RADIO OR CLOCKWORKMOD RECOVERY VIA HIS LAPTOP.
MANY NOOB FACE PROBLEM WHEN THEIR GPS DOSEN’T WORK AFTER FLASHING MAINLY CM7.THIS CAN BE RECTIFIED BY REFLASHING LATEST RADIO.
I ALSO FACED AND EVEN WHEN I WAS FIRST TRYING TO INSTALL CUSTOM ROM MY PHONE HANGED ON WHILE INSTALLING BECAUSE OF CWM.I RE-INSTALL/RE-FLASHED VIA LAPTOP AND VOILA!!!I WAS USING CM7.THIS METHOD IS A HARD PUSH ONE METHOD,SO
I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE TO YOUR MOBILE,BRICKING OR YOUR MOBILE REFLECTING YOUR RED ANGRY FACE IMAGE IN IT’S SUPER BLACK SCREEN AFTER PRESSING POWER ON BUTTON.THIS WILL 99% DOSEN’T BRICK BUT I DON’T GUARANTEE OF 1% BECAUSE OF YOUR BAD LUCK.ENJOY!!!!
THIS IS NOT MY INVENTION FIRST OF ALL.
A SIMPLE STEP USED FOR FLASHING RADIO AND CWM(PRIMARILY),many more things can be flashed, via laptop/desktop(only windows)
WHAT YOU NEED:
1. HTC SUITE
2.ADB FILES(Including Fastboot)
3.ANDROID USB DRIVERS
4.USB CABLE
5.FULLY CHARGED MOBILE
7.windows 7
PROCEDURE FOR INSTALLING ANDROID USB DRIVER:-
1.turn off your mobile,press vol.down+power button.
2.now from hboot(the screen that comes with 3 android) select fastboot using vol. down button and press power button.
3.after step 2 connect your mobile to your laptop having WINDOWS 7
4.now in your laptop open device manager and from there u will see android mobile(something starting with android) with a ! in yellow triangle.
5.right click on that and select update driver.
6.a dialogue box will appear and from there select the folder where u had saved android usb driver.
VOILA!Your device is ready to be used in fastboot mode.
PROCEDURE TO INSTALL RADIO:-
1.save ADB files,radio,cwm and fastbbot files in one folder where u will remember. For e.g- I save on c drive folder naming android.(android is a folder name where my radio.img,cwm.img and ADB files are copy pasted)
2.[IMP.]open command using option RUN AS ADMINISTRATOR.
3.now write cd/
C:\cd android\
C:\android\fastboot flash radio radio.img
U will be done
4. for cwm:
C:\android\fastboot flash recovery recovery.img
(remember to rename CWM file to recovery.img)
Any version of cwm and radio can be flashed via this method.
IF I HELPED PRESS THANKS BUTTON.
DOWNLOAD:-
latest radio-http://www.mediafire.com/?70kd4654129q6um
android usb driver-http://www.mediafire.com/?3tt3zfadg64usi1
latest CWM-http://www.mediafire.com/?4pn88xkpawg8b8b
Download fastboot files from njec21 post(4 post,thanks man for uploading file)
Really Ankurcul was this really necessary? There are many existing guides already for this,all you have done is add laptop in. Hope this does indeed help someone but like I said many existing guides already.
Regards Slymobi.
MANCHESTER together UNITED forever
Mother of all caps lock.
Also, ADB=/= fastboot.
If you instruct them to just download the ADB files, they wont get faatboot along with it.
@slymobi if u search general q&a section half of the noobs generally question about gps issue nad then over and over again we have to tell them what procedure to adopt.
it's just simple to open a single thread so that in future as per you so many threads of just one question can be reduced....
@njec21-bro just calm down....i don't wanna rude with u.....so mind ur words otherwise pm me any comments u want to give....don't make this thread bad for noobs that they won't try this and keep questioning about simple things
I'm didn't mean to be rude, I just think you abused caps lock a bit.
My second point still stand though.
How you're saying it right now is that they just need to download ADB, which doesn't include fastboot.exe, which is needed for your guide.
Link to fastboot:
http://android-roms.googlecode.com/files/fastboot-win32.zip
k...that's was a mistake that i didn't included fastboot and thanks for that njec....
+1 respect man...
You might want to add to the guide that this procedure works only on devices that are S-OFF'ed with Revolutionary or have their bootloaders unlocked with HTCDev. Also, its perfectly usable on Linux as well.
Will try this
I will try and i will press the thanks button, if it works....
---------- Post added at 12:53 PM ---------- Previous post was at 12:16 PM ----------
It will be nice if u add the flashing of KERNAL...
You might want to reduce your caps usage, it seems as though you're shouting, and this should go in the general section.
Sent from my Wildfire using Tapatalk 2 Beta-5
thanks 3xeno....
@usaff22-it's not shouting bt just want things clear that person reading it will read carefully.anything wont work will disguise this guide in which there is no point.what problem i faced and what i see in general sections about same gps issues i wrote.
i don't see any point in posting it in q&a section.
@balaedge- i'll look forward to it....same lame excuse college work....
hey,i tried this method but when i try to install recovery.img it is written status malformed 1 bytes...maybe i am noob but i didn;t find an answer in google) can you help me?)
dreamkill3r said:
hey,i tried this method but when i try to install recovery.img it is written status malformed 1 bytes...maybe i am noob but i didn;t find an answer in google) can you help me?)
Click to expand...
Click to collapse
Did you try re-downloading the recovery?
yes,i redownloaded it,i even tryed another image and the same problem :/ i observed in the last time that i cannot change my cwm even with the app(droid explorer) which i used always for changing it....i something wrong with my phone?
see,from my side recovery is clean as the same recovery iam using....
what exact procedure did u adopted....
did u run command as an admin??
Ankurcul said:
see,from my side recovery is clean as the same recovery iam using....
what exact procedure did u adopted....
did u run command as an admin??
Click to expand...
Click to collapse
yes,and it runs as system32 :/
@dreamkill3r-open cmd from system32 folder and run as admin.
connect ur mobile in debugging mode... and write command as
c:\android\adb devices
see what it says
Ankurcul said:
@dreamkill3r-open cmd from system32 folder and run as admin.
connect ur mobile in debugging mode... and write command as
c:\android\adb devices
see what it says
Click to expand...
Click to collapse
i tried some methods to write this comand,but every time it s written that it is a wrong command
Before you do adb devices do this:
in cmd type in "cd [adb.exe location]" Replace [adb.exe location] with the place you have adb.exe.
i got this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Lista of devices attached
SH159PY02094 device
and i have one more problem(in this case i only ask for help if someone can help me) in the last time,my phone can just stop working and i need to take off the battery for reboot it,the combination Power Button+Volume Down+Trackball doesn;t work :/ what can be the problem of my issues?
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.
Sony rolled out Android Pie 9 50.2.A.0.352 for Xperia XA2 Ultra 2 days ago. I was wondering if I proceed with the update from my rooted Oreo, will I have any working Root for Android 9 for my phone?:silly:
Only a few regions has gotten Pie so far. Makes it hard to work on getting root when most of us are still waiting.
Edit: XA2 Ultra H3223 USA just got Pie today.
Looking for this one too hoping on of this days root method will come out ..
anyone tried using magisk ? the root method last time in Oreo ? want to try it out but i'm afraid my phone will get bricked
danger
qhuinzy_09 said:
Looking for this one too hoping on of this days root method will come out ..
anyone tried using magisk ? the root method last time in Oreo ? want to try it out but i'm afraid my phone will get bricked
Click to expand...
Click to collapse
You're rightly afraid. Steer clerar of magisk. Wait for a proper rooting method, or perhaps don't root at all.
This update is already a danger (see the previous brick wave), I would wait until things calm down.
XA2 Ultra owner, not updating. Staying on Android 8 for a good while.st
ish4d0w777 said:
You're rightly afraid. Steer clerar of magisk. Wait for a proper rooting method, or perhaps don't root at all.
This update is already a danger (see the previous brick wave), I would wait until things calm down.
XA2 Ultra owner, not updating. Staying on Android 8 for a good while.st
Click to expand...
Click to collapse
yeah mate Heard the brick update in russia just waiting for the proper Root method hope it will come out soon..
But the pie update is Really Good ! over all 9/10 and also noticed the battery is far longer now :good::good:
yes guys sony xa 2 ultra root in original rom normal the steps is the same of classic all time in all others rom idk if i make a deference but me use this step 1. run adb in my pc and write fastboot boot twrp-3.2.3-1-discovery.img step2. in twrp first install addonsu-16.0-arm64-signed.zip this file take of line age os 16 idk if this make the deference but me install first this file , so step 3. install magisk and reboot phone no install twrp in phone just restart and phone work very well in original rom pie9 H4213_Customized GR_1313-7447_50.2.A.0.352_R1B i hope help good luck to root your xa 2 ultra
malamas said:
yes guys sony xa 2 ultra root in original rom normal the steps is the same of classic all time in all others rom idk if i make a deference but me use this step 1. run adb in my pc and write fastboot boot twrp-3.2.3-1-discovery.img step2. in twrp first install addonsu-16.0-arm64-signed.zip this file take of line age os 16 idk if this make the deference but me install first this file , so step 3. install magisk and reboot phone no install twrp in phone just restart and phone work very well in original rom pie9 H4213_Customized GR_1313-7447_50.2.A.0.352_R1B i hope help good luck to root your xa 2 ultra
Click to expand...
Click to collapse
Strange! I was thinking exactly the same process would've been as you've mentioned but then I intended to wait for some expert reviews or suggestions. So you are saying that you did the root exactly the way Android 8 Oreo was rooted as in the process you mentioned? So how far has it been with Android 9 with Root access with you ?
root
noob_coder said:
Strange! I was thinking exactly the same process would've been as you've mentioned but then I intended to wait for some expert reviews or suggestions. So you are saying that you did the root exactly the way Android 8 Oreo was rooted as in the process you mentioned? So how far has it been with Android 9 with Root access with you ?
Click to expand...
Click to collapse
im not sure if understand you exacly your question but my phone work super fast and very stable just follow my steps and you done 100% safe
im try post some photos in my phone to see is real
Easy-Peasy Interactive root
_/easy[+EASY-PEASY+]easy\_
ii-I/n/T_e r-A-c t_I\v\E-ee i have conjured up a simple tool for rooting the xa2 ultra. nothing special, all you do is download the zip, extract it, and run the .bat file, and follow along in the cmd prompt window. its interactive so you will have to select a few options while in recovery. its really easy. bootloader must be unlocked. make sure to read the read me files, and also follow along with the command prompt.
hope someone tries it out. i would like some opinions. im not new to computers, but im new to scripting.
any feedback would be appreciated. go to the ftp site listed below and download Also stock android 9.0 is included, its seperate from the tool. extract the zip open folder and double click newflasher.exe its all set up. just select no on the 2 options that come up before the flashing, put your device in flashmode
ftp://
192.161.
227.
73
v1nd1cta_d3b3llat0tlr said:
_/easy[+EASY-PEASY+]easy\_
ii-I/n/T_e r-A-c t_I\v\E-ee i have conjured up a simple tool for rooting the xa2 ultra. nothing special, all you do is download the zip, extract it, and run the .bat file, and follow along in the cmd prompt window. its interactive so you will have to select a few options while in recovery. its really easy. bootloader must be unlocked. make sure to read the read me files, and also follow along with the command prompt.
hope someone tries it out. i would like some opinions. im not new to computers, but im new to scripting.
any feedback would be appreciated. go to the ftp site listed below and download Also stock android 9.0 is included, its seperate from the tool. extract the zip open folder and double click newflasher.exe its all set up. just select no on the 2 options that come up before the flashing, put your device in flashmode
ftp://
192.161.
227.
73
Click to expand...
Click to collapse
strange that when I unzip a 1.8GB or so zip it just ends up with 2 small files (bat and readme) (even tried pulling the constituent files out from the zip independently). Also the batch file won't run due to windows security (understand running .bat is always risky no matter how good one's intentions might be)
mac231us said:
strange that when I unzip a 1.8GB or so zip it just ends up with 2 small files (bat and readme) (even tried pulling the constituent files out from the zip independently). Also the batch file won't run due to windows security (understand running .bat is always risky no matter how good one's intentions might be)
Click to expand...
Click to collapse
hey, thanks man, im new to this so i really apprecite it. i unzipped the 1.8gb zip, left it for download, and also left the unzipped folder and unhid everything. i left a NOTE to do explain a little better, not much, but its a little more than i am now. i changed permissions on my end, so it should be ok. as long as everything stays together in the same directory, for example the desktop,...... it doent have to be that folder, but it cant be in any other folder either, as long its all on the desktop, its good. i figure you already know that, but it makes me feel better to let you know. the .bat extracts 3 other .zip, one .zip is a usb driver and it installs it also. you can hit no, cmd will read access denied, but in this script its not considered an error, so it will continue. it will also connect to adb automatically and push 2 files, .img, .zip, to the device. if there is a problem with adb connecting, it will give notice, prompt, and when hit enter it will kill adb server and exit cmd. if everything is ok,it will boot the recovery .img automatically, given you press enter to give it permission. once in recovery it prompts instructions for the user, and a new instruction will show after every enter. well, i guess i did explain it better than i did in that NOTE.
hope i dont sound to retarded and noobish, and i hope you give it another go.
again thank you, much appreciated
.
v1nd1cta
noticed your bat file has the zip file in system32 directory
the bat file does not work due to the paths I am guessing. Why would the zip want to be in system 32 windows directory?
any update? a safe way to root in android 9?
v1nd1cta_d3b3llat0tlr said:
hey, thanks man, im new to this so i really apprecite it. i unzipped the 1.8gb zip, left it for download, and also left the unzipped folder and unhid everything. i left a NOTE to do explain a little better, not much, but its a little more than i am now. i changed permissions on my end, so it should be ok. as long as everything stays together in the same directory, for example the desktop,...... it doent have to be that folder, but it cant be in any other folder either, as long its all on the desktop, its good. i figure you already know that, but it makes me feel better to let you know. the .bat extracts 3 other .zip, one .zip is a usb driver and it installs it also. you can hit no, cmd will read access denied, but in this script its not considered an error, so it will continue. it will also connect to adb automatically and push 2 files, .img, .zip, to the device. if there is a problem with adb connecting, it will give notice, prompt, and when hit enter it will kill adb server and exit cmd. if everything is ok,it will boot the recovery .img automatically, given you press enter to give it permission. once in recovery it prompts instructions for the user, and a new instruction will show after every enter. well, i guess i did explain it better than i did in that NOTE.
hope i dont sound to retarded and noobish, and i hope you give it another go.
again thank you, much appreciated
.
Click to expand...
Click to collapse
ftp not working btw
There only seems to be Magisk root for up to 50.1.A.13.83 (Oreo)... Which is a massive pain because there have been tons of updates since, including Android Pie. I check this site loads and still nothing towards rooting for Pie.
So, not sure if this helps, but magisk seems to install fine in pie, but so far I'm having a ton of issues regarding freezes and reboots. Will search for a kernal fix, anyone have a clue to this? Just thought I'd inset my 2¢ into this and see if anyone has any insight to this. Thanks guys you do great work ?