Database Info

[TUT] Telus HTC Desire *UPDATED* - Windows Drivers, Root, Radio and ROM Instructions

Ok, so I just took the tutorial written by Slimdizzy and have modified it for Windows users, as he stated he was using a Mac, and a lot of people seem to be having issues getting this working. Go easy on me this is my first TUT write up, I hope it helps......If anyone has a correction or a suggestion please let me know.
Credit goes to Slimdizzy for his original post here:
http://forum.xda-developers.com/showthread.php?t=750888
When I rooted my Telus HTC Desire the first time it was hit and miss, if I remember correctly I did it 3 times until it worked 100%, by this I mean Unrevoked/Root ran without hitch, and after running Unrevoked I was able to reboot into Android, and then reboot back into recovery on my first try without any weirdness.....
The following steps are what I did to get my drivers installed and working the first time, rooting the phone, installing Radio 5.09.00.20, and getting a custom ROM installed (I used OpenDesire)
First things first you need the drivers, this is the most important part. Nothing will ever work for you if you don't have the right drivers installed.
Drivers:
1. Download the Android SDK here: http://dl.google.com/android/android-sdk_r06-windows.zip
2. Unzip and place the files in C:\Android. You can place the files wherever you want but my steps will use this location.
3. Run SDK Setup.exe , if you get the Failed to fetch URL error, hit close and then go to Settings and enable Force https://. Then click on Available Packages, near the bottom you will see USB Driver Package, place a check mark beside it and then click Install Selected.
Alternatively you can try using these drivers, they have worked for other users but I have not installed my drivers using this method so I can't say how well they will work.....
http://www.unrevoked.com/rootwiki/lib/exe/fetch.php?hash=908951&media=http%3A%2F%2Fwww.unrevoked.com%2Frecovery%2Fandroid-usb-driver.zip
4. Android SDK will download your drivers and place them here C:\android\usb_driver.
Now plugin your Desire with USB Debugging enabled (Settings --> Applications --> Development). Windows will prompt you for the device drivers, point windows to the C:\android\usb_driver folder and it should do it's thing. YOU MUST BE SURE TO INSTALL THE ADB DRIVERS, without those Unrevoked will not run.
5. Once all your drivers are installed, you can verify them by checking with the Android SDK
Open a DOS prompt (CMD in the Run box) and navigate to C:\android\tools and then type "adb devices", it should return a funny device name/ID, if you see a device listed then you are good to go, if you don't then repeat these steps until you do, check your Device Manager for an uninstalled device/driver.
***UPDATED***
Steps for Rooting:
***Follow these steps after you are 100% sure you have the drivers right!***
***DO NOT plug you Desire into your computer yet***
1. Goto http://unrevoked.com and download the software
2. You now have a choice of recovery, Amon RA has released an SLCD version of his recovery, which in my opinion is much better, it has a few more features than Clockwork. I recommend Amon RA, but the choice is yours.
Amon RA Recovery v1.7.0.1 R5 SLCD: http://dl.dropbox.com/u/4481275/recovery-RA-desire-v1.7.0.1-R5-SLCD.img
Clockwork v2.5.0.7 SLCD:http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.zip
3. Go to HBOOT, this is done by shutting down your phone and powering on the device while holding the Power button down and pushing Volume down at the same time, once HBOOT is loaded do a wipe (Clear Storage). You can navigate the menus by using the volume rocker and the Power button to select your option.
4. Load Unrevoked and load the custom SLCD recovery file on your PC:
Goto File>Custom Recovery and point it to the recovery image that you downloaded in step 2.
5. Restart your phone, it will take a few minutes because you did a wipe, just wait it will load (up to 5 minutes). As soon as the welcome screen loads plug your phone in to the PC and Unrevoked should do it's thing. If Unrevoked doesn't start, then hit the Menu button go to Settings --> Applications --> Development and enable USB debugging.
6. The phone will restart a couple of times, and will look like it's hanging on the HTC screen but it's not! If the HTC screen is present for more than 5 minutes pull your battery and start again ( I had to do this a couple times myself). If Unrevoked pauses half way through its process, it could be because for some reason you don't have the proper drivers installed. You can load them as Unrevoked does the root process, while the phone is rebooting if Unrevoked pauses and Windows prompts you for a driver point it to the C:\android\tools directory and it will load the drivers and Unrevoked will continue its root process.
7. When Unrevoked is finished you will be left at the recovery screen,
8. *** VERY IMPORTANT*** Before restarting do a "wipe cache partition", "factory reset". And now would be a good time for a Nandroid Backup
9. Now reboot, and Android should load. Check for Superuser Permissions app, if you see it you're good if not restart from step 3.
10. Shutdown and load HBOOT, wait a few seconds for SD card (you'll see something try to load quickly), then load recovery again, it should load everytime without issue now.
It may take a few tries, but just follow these steps and it will work.
Steps for flashing radio, and custom ROM:
1. Grab a custom ROM from the forum, I used OpenDesire: http://forum.xda-developers.com/showthread.php?t=712615
OpenDesire comes with a nice reboot to Recovery feature built in.
2. Once zip is download, copy it to your SD card
3. Get the updated radio needed from here: http://www.mightyrom.com/mrx/MRX/Bravo/Radio/Signed/32.44.00.32U_5.09.05.30_2.zip
4. Reboot into recovery by powering on the device while holding the Power button down and pushing Volume down at the same time. Select Recovery with the Volume rocker and then click the power button to launch it.
5. Select "install zip from SD card" using the trackpad and select the radio zip that you download in step 3.
6. Let it do its thing (could take up to 10 mins to finish), use the back button to get to main menu and select "reboot system now" with the trackpad. If your phone hangs after rebooting wait at least 10 minutes before pulling the battery, it could be finishing the radio update.
7. Once rebooted check that the new radio is good by loading HBOOT (you should know how to do this by now) and at the top it will show you're radio version.
8. Load recovery again and select "wipe cache partition", "factory reset" (for the 3rd and final time). Then select "install zip from SD card" using the trackpad and select the ROM zip that you download in step 1.
9. The new ROM is now installed, restart the phone and wait up to 20 minutes (it shouldn't take that long) for the new ROM to load, DO NOT PULL YOUR BATTERY UNTIL AT LEAST 20 MINUTES HAVE PASSED.
You should now have your phone rooted, new radio installed, and a new custom ROM loaded.
Sorry for such a long post, but I found all these steps necessary to get the end result.
If I have missed anything or if anyone has comments / corrections post them here and I will try to keep the tutorial updated and easy to use as possible.

Great post man. I found the "dont plug the phone in yet" part out the hard way. I thought I had busted it on the 1st try!
Couple of things.
USB debugging is under development in Apps. (not a big deal)
Those unrevoked drivers worked great for me, I followed the instructions in the HTML doc that came with the zip. I have heard there are extra drivers needed for windows 7, and you have to be sure your running unrevoked as an admin.
Once I was rooted, I used RomManager to get the newest clockwork and flashed it. I used rom manager to flash the rom, HBoot to flash the radio, and did it backwards. Seems to not make a difference.
Thanks for doing this!
Edit: you forgot the most important part! Always Nandroid backup, and copy all the files from the SD card as soon as you are rooted incase something goes wrong.
Below may be wrong info, but it is what happened to me.
//////////////Extra tip, if you format an SD card, be sure you copy back the clockwork files before you unmount the card. I didn't and could not boot at all untill I copyed all the files back. I went straight to a nandroid without trying to boot into android, so I don't know if I messed up Android, but I know it would not boot to anything untill I fixed the SD card.
////////////////////

ajanu said:
Extra tip, if you format an SD card, be sure you copy back the clockwork files before you unmount the card. I didn't and could not boot at all untill I copyed all the files back. I went straight to a nandroid without trying to boot into android, so I don't know if I messed up Android, but I know it would not boot to anything untill I fixed the SD card.
Thanks for doing this!
Click to expand...
Click to collapse
Can you elaborate on this? I'm assuming Clockwork recovery is stored on the SD card?

BIGGGG THANKS, I will try tonight.

Below may be wrong info, but it is what happened to me.
//////////////Yes there is a folder called clockwork mod, in there were my nandroid backups. I copied everything on the SD back and Clockwork booted, so I can't say for sure, but I'd assume all you need is the clockwork folder. There are other folders that look like system folders that may also be important./////////////

ajanu said:
Great post man. I found the "dont plug the phone in yet" part out the hard way. I thought I had busted it on the 1st try!
Couple of things.
USB debugging is under development in Apps. (not a big deal)
Those unrevoked drivers worked great for me, I followed the instructions in the HTML doc that came with the zip. I have heard there are extra drivers needed for windows 7, and you have to be sure your running unrevoked as an admin.
Once I was rooted, I used RomManager to get the newest clockwork and flashed it. I used rom manager to flash the rom, HBoot to flash the radio, and did it backwards. Seems to not make a difference.
Extra tip, if you format an SD card, be sure you copy back the clockwork files before you unmount the card. I didn't and could not boot at all untill I copyed all the files back. I went straight to a nandroid without trying to boot into android, so I don't know if I messed up Android, but I know it would not boot to anything untill I fixed the SD card.
Thanks for doing this!
Edit: you forgot the most important part! Always Nandroid backup, and copy all the files from the SD card as soon as you are rooted incase something goes wrong.
Click to expand...
Click to collapse
This is exactly the part I wanted, when I had to use nandroid

ajanu said:
Yes there is a folder called clockwork mod, in there were my nandroid backups. I copied everything on the SD back and Clockwork booted, so I can't say for sure, but I'd assume all you need is the clockwork folder. There are other folders that look like system folders that may also be important.
Click to expand...
Click to collapse
I believe this is misinformation.. only reason because I was having that endless HTC frozen screen so I formated my SD card, the FAT32 partition and the EXT3 partition in windows using Paragon Partition Manager, finally got back into recovery, wiped everything from cache to davlik cache as well.. then installed my rom.
If Clockwork was stored on the SD card.. I believe it wouldn't have booted.. got a little confused there. However, the Nandroid backups are stored on the SD card.. that I know for sure!

quazis said:
I believe this is misinformation.. only reason because I was having that endless HTC frozen screen so I formated my SD card, the FAT32 partition and the EXT3 partition in windows using Paragon Partition Manager, finally got back into recovery, wiped everything from cache to davlik cache as well.. then installed my rom.
If Clockwork was stored on the SD card.. I believe it wouldn't have booted.. got a little confused there. However, the Nandroid backups are stored on the SD card.. that I know for sure!
Click to expand...
Click to collapse
These devices make no sense to me. Maybe I didn't help anything with the copy and just trying to boot a few times would work. I would expect things to work or not work, but they work intermittently some times. Certainly increases the confusion/frustration levels.

Wouldnt be using the latest radio and using "recovery-clockwork-2.5.0.7-bravo.img" instead of the old one be better?

Juggalo_X said:
Wouldnt be using the latest radio and using "recovery-clockwork-2.5.0.7-bravo.img" instead of the old one be better?
Click to expand...
Click to collapse
Link has been updated to reflect the latest Clockwork recovery version.
Thank you!

Blowtoke said:
Link has been updated to reflect the latest Clockwork recovery version.
Thank you!
Click to expand...
Click to collapse
No problem and here is a link to the new radio if you want to update it. it appears to be much better then the one linked in tut. Here it is

Juggalo_X said:
No problem and here is a link to the new radio if you want to update it. it appears to be much better then the one linked in tut. Here it is
Click to expand...
Click to collapse
Radio link updated as well, thanks!

quazis said:
I believe this is misinformation.. only reason because I was having that endless HTC frozen screen so I formated my SD card, the FAT32 partition and the EXT3 partition in windows using Paragon Partition Manager, finally got back into recovery, wiped everything from cache to davlik cache as well.. then installed my rom.
If Clockwork was stored on the SD card.. I believe it wouldn't have booted.. got a little confused there. However, the Nandroid backups are stored on the SD card.. that I know for sure!
Click to expand...
Click to collapse
What is EXT3 partition ?
I would like to get more details about the sdcard ? I make my backup with nandroid and after I format the sdcard....so if I want restore the back up from Nandroid, it will not be there....sorry for the noob questions

fourire said:
This is exactly the part I wanted, when I had to use nandroid
Click to expand...
Click to collapse
This step has been added to the guide....thank you!

fourire said:
What is EXT3 partition ?
I would like to get more details about the sdcard ? I make my backup with nandroid and after I format the sdcard....so if I want restore the back up from Nandroid, it will not be there....sorry for the noob questions
Click to expand...
Click to collapse
Ext3 partition is for A2SD, I never touched my SD Card until I was rooted, updated radio, and loaded a custom ROM. I can't say whether or not the SD card plays a role in freezing during boot to recovery or not? But like I said I never partitioned my SD until after everything was done.....

Very good tutorial !
Thank you

After all that, what's about the apps, contacts, calendar ?
And for this file: 2. Get the needed recovery image from here: http://koush.tandtgaming.com/recover....0.7-bravo.zip... is it for slcd ?

fourire said:
After all that, what's about the apps, contacts, calendar ?
And for this file: 2. Get the needed recovery image from here: http://koush.tandtgaming.com/recover....0.7-bravo.zip... is it for slcd ?
Click to expand...
Click to collapse
Recovery-clockwork-2.5.0.7-bravo.zip has been confirmed to work with SLCD, the link has been updated.
Thanks!

ok - at step 8
8. *** VERY IMPORTANT*** Before restarting do a "wipe cache partition", "factory reset". And now would be a good time for a Nandroid Backup
Can someone point me to a nandroid backup tutorial.

Blowtoke said:
I've posted a question on the Clockwork forum to find out if the latest version (recovery-clockwork-2.5.0.7-bravo.zip) works with SLCD, once I get an answer I will update the link if necessary.....for now it's reverted back to the old recovery img that I know works....
Thanks!
Click to expand...
Click to collapse
It works ive flashed it as my recovery img

[GT-P6200][CWMRecovery][ROOT]ClockworkMod Recovery and Root

****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary

Hi! I'm a placeholder.

garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.

Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.

Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary

link posted for testing.

thanks again gary loving it.

when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.

chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary

thank you. Gary tried not to get Banned OK? we need you buddy. lol

chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary

not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.

chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.

it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.

Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?

lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary

worked like a charm...backup and restore works perfectly...
thanks gary !!!

Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk

jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary

garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).

[HOW-TO] Fix soft brick & error mounting sdcard

EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J

Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium

archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?

When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?

joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...

I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is

My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?

LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J

If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.

LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium

I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium

j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.

I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...

mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!

Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.

Got it after several tries

hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.

yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2

My phone wont boot into Cmw recovery, Please help.

My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.

Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!

I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app

Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.

WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.

[GUIDE] Fix BOOTLOOP with CWM zip !!! For All Phone

First of all,
Sometimes we facing BOOTLOOP, but we rarely make a backup so DATA in that backup already out to date.
And i found a method which can FIX BOOTLOOP WITHOUT RESTORING OLD BACKUP !
CAUTION !
THIS METHOD ONLY FOR ANYONE WHO FACING BOOTLOOP AFTER INSTALLING APPS, MODS, ETC
AND THAT APP IS NOT IMPORTANT FOR YOUR ROM
Things you will need
PC or Laptop
USB Cable (For connecting SD-CARD)
SD-CARD Reader (If your CWM Recovery can't mount SD-CARD)
WinRAR or WinZip
Notepad++
Patience!
Click to expand...
Click to collapse
So, lets begin..
STEP 1
If you facing bootloop after installing apps, mods, etc.
YOU MUST REMEMBER THE NAME AND LOCATION OF APPS/MODS YOU'VE PREVIOUSLY INSTALLED
Click to expand...
Click to collapse
STEP 2
Download my CWM zip HERE
Click to expand...
Click to collapse
STEP 3
In PC, after download, extract zip, open META-INF > com > google > android
Open updater-script with Notepad++
Click to expand...
Click to collapse
STEP 4
Edit this line
Code:
delete("/system/app/Home.apk","/system/etc/permissions/com.sonyericsson.uxpres.xml");
with name and location of apps/mods you've previously installed
Ex.
Code:
[CENTER]delete("/system/app/Crap.apk");[/CENTER]
And if you installed more than 1 app, you can insert another name and location in 1 line
Ex.
Code:
delete("/system/app/Crap.apk","/system/etc/permissions/com.bluesky.nxp-resolution.xml");
Click to expand...
Click to collapse
STEP 5
Save your modified updater-script and zipped the META-INF and system folder
Click to expand...
Click to collapse
STEP 6
Put your modified zip to your SD-CARD with mount sdcard option in CWM (with USB Cable) or using SD-CARD Reader
Click to expand...
Click to collapse
STEP 7
Flash It !
DONE !
Click to expand...
Click to collapse

Thanks, its is a lot easier to do with adb file manager thingy software I found online, connecting to pc via usb gives full access to phone file system partitions with root access, just deleting the files with it also works. :thumbup:
Why are SMARTphones soo... Freaking Dumb?

Or via adb
Connect phone/tablet to pc
In adb type:
adb delete("/system/app/Whatever.apk")
Done...
Disadv: USB Debugging must be enabled...

You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data

Bert98 said:
You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data
Click to expand...
Click to collapse
You're welcome

Before I tried the tutorial you or even try out all of the tutorials available on the internet, please help me to conclude my problem.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward

hey the link isn't working anymore? can you please reupload?
Do you have to get into recovery? as i have no recovery on my phone Xperia z3