Related
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 !!
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
This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread
dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?
hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them
thats amazing, will try it as soon as possible
SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx
Work work work, thank you bro .
uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.
I tried it, it's working. Thanks for the mod
I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.
***Root method for .621 update***
THIS IS FOR USERS WITH THE .621 UPDATE ONLY. IF YOU HAVE NOT UPDATED DO NOT USE THIS METHOD.
*****DO NOT USE WINDOWS*****DO NOT USE RSDLITE*****
Instructs are made by Skelente
1.) Download the latest Ubuntu iso for your system. Most processors these days are 64 bit, but if you're running on an older computer or do not know if you have a 32 or 64 bit processor I'd recommend doing 32 bit just to be safe (64 bit processors can run both 32 and 64 bit distributions, but 32 bit systems cannot run 64 bit distributions.) Side note: you can download other distributions, but if you do you will not be able to create the persistent drive using the USB method. It should also be noted that some older systems cannot boot from USB, most newer systems (post 2000/2001 IIRC) can boot from USB, however you should consult Google to verify for your system.
2.) Burn the iso:
2.a If you have a cd burner and blank disc, this is the easiest method but, again, you will not have a persistent drive you will just have a Live CD. Use an iso burner to burn to cd, then skip to step 3a.
2.b If you do not have a burner, a blank disc (or don't feel like wasting a DVD disc) but have a free USB drive (with at least 2 GB of memory, bit overkill but it has to be big enough to hold the iso + changes + the persistent "drive") then I recommend downloading either unetbootin or universal USB installer. Go to either web site and follow their instructions. If you use Ubuntu, you'll have the option of creating a persistent drive, which is basically a fake-partition that allows you to save files to when you reboot Linux after running this Live USB. I would recommend using a persistent size of at least 200 mb so we can save the SBF file and sbf_flash. If you created a persistent drive go to step 4. If you opted out of this, skip to step 4.
3.a So you have a Live CD now. If you have a spare flash drive, load up the 604 SBF and sbf_flash. Either way, you'll need to proceed to booting into linux, go to step 4.
3.b Once the respective application has finished, copy the SBF and sbf_flash file to the persistent drive listed in windows.
4. Now we need to boot from your Live image. Restart your computer. When your computer is booting up it should give you two options, "Enter BIOS" and "Select Boot Order" or similar. For my Lenovo Laptop, I can hit F12 to change the boot order, and from there I can select my USB port and it'll boot from there. If you do not see a boot order option, you will need to go into your bios and change the boot order manually. Again, you will need consult Google for this as the menu selections vary by system. It really isn't that hard to figure out if you go through the menus, but I strongly, strongly, strongly recommend and encourage you to google your motherboard's manual to verify what you need to change if you don't know what you are doing. You are responsible for any changes you make on your system. Your BIOS is crucial for your system to function properly. Once you have found where to change your boot order, select the respective drive (USB, or your CD/DVD drive). These will be listed by the manufacture name (so SamsungXXXX for a Samsung drive or PNYXXXX if you're using a PNY usb stick.)
5. When Ubuntu boots up, it'll give you an option to run "Live" from the CD/USB. Select this option. Installing to your hard drive could mess up your current OS install, and I'm not going to get into partitioning here. Once you've gotten into Ubuntu, select "Dash Home" in the upper left hand corner, and then type terminal in the search box. Click terminal, then open it up.
6. Now you'll need to get to where ever you have the SBF and sbf_flash stored through the terminal. If you chose to use the boot cd, and did not have an available flash drive, you will need to download the SBF from here, as well as sbf_flash and then extract them to the same folder. The default is "Downloads" and I recommend just extracting them to that directory for simplicity.
6.a If you had to download the SBF/sbf_flash, getting there through terminal is rather easy. All you'll need to do is type these commands into the terminal:
cd Downloads
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
6.b If you already copied the required files to a USB drive, we need to get there through terminal. Type these commands:
cd /
cd /media/
ls (This command will list all the drives connected to your system, cdrom, usb, etc. If you used the Universal USB installer it will list the USB drive as "PENDRIVE", I'm not sure what the default is for Unetbootin but you should be able to figure it out and if you just used a spare device it could be completely random.)
cd drivename (obvioiusly this will vary based on the USB method, for me its "cd PENDRIVE"
If your files were just on the main drive, you don't need to do anything else but the following commands. If you put them in another folder, you will need to do "cd foldername" without the quotes obviously. When you're in the directory with both the SBF and sbf_flash you will need to do these commands (again, ignoring the '-'):
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
7.) After sbf_flash is done, you'll need to restart your computer. Its recommended you remove your boot media (cd or usb drive) so that Windows can boot normally. If you changed the boot order in bios you will need to change it back to what it was before, otherwise whenever you have a CD/USB stick plugged in your computer will automatically try to boot from it, and get pissy if it can't boot from the media.
8.) Once you're back in windows you'll need to run the zergrushv4 root method. From there you can do whatever you want. You still cannot SBF to previous versions (602 or 605) and you cannot run Froyo roms.
Downloads:
sbf_flash
SBF File & root tools
*HELP*
If you flashed with RSD Lite and have no data here is your options...
Flash stock .621 sbf and...
Switch devices on your account to reactivate the data
or
Call verizon to have them reporvision your data...
Once you are on the milestone system you can flash a custom rom.
You must SBF in Linux using sbf_flash, otherwise .604's radio will flash over .621's and your phone will no longer be able to take or place phone calls.
Edit: It may just be data, instead of phone capabilities. But still, flashing in Linux is much easier than having to spend time with Verizon's incompetent phone operators.
Sent from my Transformer TF101 using Tapatalk
If you SBF'd using RSD Lite, you flashed the 605 baseband over the 621. I didn't think this would mess up texts/phone calls but just your data connection, but correct me if I'm wrong I'm just going from memory (I had a dx2, just been watching the threads.) This was a big problem for the people over at rootz and they had a few different tactics on how to solve it. Some were able to call VZW and ask the tech support to "re-provision their data" although that was with mixed results (it depended who ya got on the phone, some people had no luck and other people had their data start back up no problems.) You would need to sbf back to 621 and call from a separate phone, however. Another user (skreelink) theorized that it was merely the AUTH code that was being messed up, and suggested that (for those with a secondary smart phone) you just go onto VZW.com, switch out phones for your number, wait 15 minutes, then go back to the website and switch back to your DX. I'm not sure if anyone has had any success with the latter but I know the former worked for a handful of people (with others getting tech support who had no idea what they were talking about.) If you call and don't get someone knowledgeable, I'd just cross your fingers and call back another time and hope you get someone different.
link not working
anyone have updated link that works to download this?
yea i learned about the radio the hard way, but i found a quick fix... maybe...
If you flashed with windows and now cant get data if you have a old smartphone that is compatible with you plan just go online and switch devices and then switch them back. Saves from having to call verizon But some people may not have a extra
I am probably one of those people who will also need to use this alternative root method but I have a question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned off my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
bamx2 said:
I am probably one of those people who will also need to use this alternative root method but I have question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started the downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned of my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
Click to expand...
Click to collapse
If you disabled the download you are still on .605.
Turn your phone on, quickly root it with Pete's Motorola Root Tools, install Titanium Backup and freeze the "2.3.3 Updater" application.
Afterwards, reboot your phone and you should be golden.
Sent from my DROIDX using Tapatalk
nfazzdar - Thanks for the reply . I did a factory reset and that got rid of the yellow triangle. I then rooted as you suggested and installed TiBu . I really is too bad that M and V are pullin this cr#p .
I am going to update the post and host the files. There is also some extra stuff i will put up for download.
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Good to know. I think that I will also install OTA Rootkeeper as well.
deboyz1014 said:
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Click to expand...
Click to collapse
using linux mint and have a ?
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
BRANDENDEUCE said:
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
Click to expand...
Click to collapse
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
landonotis said:
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
Click to expand...
Click to collapse
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
infazzdar said:
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
When exactly do we need to input the code? I am assuming this is in terminal on linux?
BRANDENDEUCE said:
When exactly do we need to input the code? I am assuming this is in terminal on linux?
Click to expand...
Click to collapse
Sorry for not specifying, but you assume correctly.
Sent from my Transformer TF101 using Tapatalk
What roms can we use now?
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
BRANDENDEUCE said:
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
Click to expand...
Click to collapse
I believe this thread will be of help to you. =D
http://rootzwiki.com/index.php?/topic/21337-[ROMS]-Multi-ROM-Thread---Blur-Based-ROMs-for-those-on-.621/.604!
Sent from my DROIDX using Tapatalk 2 Beta-5
This worked great.
Any cwm kernels are we able to use?
Just wondering if we can flash custom kernels since we can do roms? If so any help would be appreciated.
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.