Related
Next week I'll be receiving my GSM HTC Hero and I'm doing a lot of reading in this great forum so that when it arrives, I'll be able to get the most out of my device.
What I'm planning to do is:
1. Use the "One click root method" (described at http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/) to:
a. Install the latest FlashRec (1.1.3 from http://zenthought.org/content/project/flashrec)b. Use FlashRec to:I. backup the current Recovery ImageII. install the latest Amon Ra's Hero Recovery image (1.5.2 from http://forum.xda-developers.com/showthread.php?t=561124)
2. Use the Amon Ra's Hero Recovery image to:
a. Back up the current ROM using Nandroidb. Install:I. MoDaCo Custom ROM 3.0 (from http://forum.xda-developers.com/showthread.php?t=552591)II. The latest Radios (version 63.18.55.06JU_6.35.09.26 according to http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/)
Now for my questions (some may be silly, but remember I'm just starting with all of this):
1. I want to do this with a Spanish HTC Hero. Now in the MoDaCo ROM post, there is a link to different "locales". Do I need to install these if I want the phone to be in Spanish? I'm asking this because the link seems dead.
2. Do I lose the HTC Sense interface if I change to MoDaCo's ROM?
3. Do I need to "wipe"? between steps 2 and 3? I saw from the Recovery Image screenshots that there are many "wipe" options (Wipe data/factory reset, Wipe Dalvik-cache, Wipe SD:ext partition, Wipe battery stats, Wipoe rotate settings). Which one(s) should I use?
4. I have read that the "One click root method" has been patched in the newest versions of the HTC Hero, but I can't seem to find the specific version after which it doesn't work anymore. Is it safe to just try step 1a, and if it doesn't work try an alternative method?
5. I believe the easiest alternative method is to use adb, but the specific command seem to vary. According to the forum post that contains the Recovery Image, the commands would be:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.5.2.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.5.2.img /sdcard/recovery-RA-hero-v1.5.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.5.2.img
adb shell reboot
I have also seen other commands. Would the ones above be the correct ones?
6. If I flash MoDaCo's ROM, do I have to enter settings specific to my operator (Orange Spain) to be able to use the phone and the Internet? If so, can I look up these settings before starting? And again, if so, where do I find them?
7. I'm going to buy a new (bigger and faster) MicroSD card than the one I have now to take full advantage of the Apps2SD later on. For now, I'll just use the 2GB card I have to be able to flash the updates, etc. Will a card with just one FAT partition work as simpe storage for updates? Can I enable the Apps2SD functionality later by inserting a correctly partitioned MicroSD card? Can I then uninstall and reinstall the apps so they get installed on the SD card?
8. If you can use FlashRec or ADB to change the Recovery Image and you can then use the Recovery Image to change the ROM to a rooted one, what is the Goldcard method for?
9. What are the risky parts of the process? (as in "if this fails you can throw away your phone" risky)
Thanks so much in advance for you help answering these questions. I really love the forum!
I'll be waiting for the answers as well, but can i just siggest that when there are some Sensible answers, you update the first post in a Q/A form. I will be the clearest and most simple 'step by step'
So I was trying to root my evo so I could try the fresh rom (please note that this was my first ever root attempt and my phone had the OTA update). I followed the instructions from this guide:
Latest OTA rooted! - Page 2 - Android Central Forums
This is where my problem is:
11. Once back at the Home screen type:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
When I enter the "cat /sdcard/flash_image > /data/flash_image" code I get:
"cannot create /data/flash_image: permission denied"
After some googling I found other people typed "su" prior to typing in the "cat /sdcard/flash_image > /data/flash_image" command. That didn't work for me. I received "su: permission denied" after entering su.
Would going back and starting this tutorial all over cause serious damage? I'm wondering if maybe I messed up earlier.
I'm very worried I really screwed something up. Can anybody please offer up some advice for a newbie?
Weigh the stakes
Man, just try the "SimpleRoot 1.47 OTA update" app for Windows. You save time, money and a lot of feces on your tract by the worries that everything is ok.
Now, I want to remind the stakes. If you haven't looked at my post here at Q&A, I pretty much effed up my phone while being rooted. I don't know if it was too much exposure to heat caused by WiFi Tether, or of mysterious powers regarding the RSA 256 bit encryption update process screwed my phone up. So before trying to crack your phone, please, review the stakes and stay stock.
BTW, you haven't completed the root process, so a simple Factory Reset should do the trick to go back into Stock without any trace of root procedure. That is, if you want to play it safe.
Okay, first things first. Just so I'm clear.
1. Which guide(exactly) did you follow?
2. What software version do you have now?
Yeah i was having problems with my administrator password so I switched from simple root to this method. Maybe I was using the wrong version or something, could you post a link to simple root for ota?
churchwin88 said:
Okay, first things first. Just so I'm clear.
1. Which guide(exactly) did you follow?
2. What software version do you have now?
Click to expand...
Click to collapse
1. http: // forum.androidcentral. com/htc-evo-4g-roms-hacks/ 21043-latest-ota-rooted-2. htm
2. My software number is 1.47.651.1
Thanks for the help
StrummingLevi said:
Yeah i was having problems with my administrator password so I switched from simple root to this method. Maybe I was using the wrong version or something, could you post a link to simple root for ota?
1. http: // forum.androidcentral. com/htc-evo-4g-roms-hacks/ 21043-latest-ota-rooted-2. htm
2. My software number is 1.47.651.1
Thanks for the help
Click to expand...
Click to collapse
For the 1.47 you need to use this version of simple root(if you haven't already) - http://forum.xda-developers.com/showthread.php?t=720565
I'm not sure why it would have problems with the password. Only thing I can think of would be something along the lines of not having administrator privileges.
EDIT: Make sure to have all the requirements and if you successfully run that let me know so we can proceed to the next step(it is really simple).
I did the simple root for 1.47 and it was a success! Although I did not understand what the flash recovery did. I tried the clockwork recovery and it took me to a screen with a bunch of options, but I didn't know what to do so I just rebooted. What's next? I want to try the newest version of the fresh rom.
TO try fresh first download it and place the zip file on your computer, boot into recovery, (power phone off then hold down volume and power untill you get to the white screen) select flash zip fron sd card then select the fresh rom and flas, presto fresh should flash, the recovery is a seperate area which is used to flash a rom, as you cant flash a rom from within a rom.
So do I use the clockwork recovery to flash the fresh rom? I was looking at the guide to flash the new fresh rom and it says that I need to have nand unlocked. How do I do that?
if you did simpleroot nand should be unlocked, and yes clockwork recovery is used to flash the fresh rom. clockwork recovery is what you are in when you boot with the down volume and power button held down. If it doesnt work you may want to try amon ra recovery, find the toast root method and do the last step:
- on your PC open a shell again and do:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
- you should now be in recovery mode
- do a wipe of data and dalvik cache
- navigate to nandroid restore and restore the previous rom setup
- come here to the forum, get and flash the latest radio
- enjoy... you can now reboot into recovery, write to system and other partitions while in Android. Also you now have a Engineering SPL so you can fastboot and much more.
It also wont hurt to do the whole part two of toasts guide if you dont think your nand is unlocked. FYI Nand unlocking allows both a read write option in the recovery which is needed to write the custom roms.
StrummingLevi said:
So do I use the clockwork recovery to flash the fresh rom? I was looking at the guide to flash the new fresh rom and it says that I need to have nand unlocked. How do I do that?
Click to expand...
Click to collapse
Your nand is unlocked. Just download Fresh, boot into recovery, wipe caches, and apply Fresh via zip file.
ifly4vamerica said:
if you did simpleroot nand should be unlocked, and yes clockwork recovery is used to flash the fresh rom. clockwork recovery is what you are in when you boot with the down volume and power button held down. If it doesnt work you may want to try amon ra recovery, find the toast root method and do the last step:
- on your PC open a shell again and do:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
- you should now be in recovery mode
- do a wipe of data and dalvik cache
- navigate to nandroid restore and restore the previous rom setup
- come here to the forum, get and flash the latest radio
- enjoy... you can now reboot into recovery, write to system and other partitions while in Android. Also you now have a Engineering SPL so you can fastboot and much more.
It also wont hurt to do the whole part two of toasts guide if you dont think your nand is unlocked. FYI Nand unlocking allows both a read write option in the recovery which is needed to write the custom roms.
Click to expand...
Click to collapse
Ignore this post, unless you want to flash Fresh with Amon Ra Recovery instead of Clockwork Recovery (what you have now)
Agreed, I was only posting that "if" he had problems using clockwork sorry for the confusion.
jerryparid said:
Your nand is unlocked. Just download Fresh, boot into recovery, wipe caches, and apply Fresh via zip file.
Ignore this post, unless you want to flash Fresh with Amon Ra Recovery instead of Clockwork Recovery (what you have now)
Click to expand...
Click to collapse
So I decided I was going to use Amon Ra's recovery because flipz recommended it. That was going well until "- navigate to nandroid restore and restore the previous rom setup". I selected nandroid restore and it said something like /sdcard/nandroid not found. Aster that I just rebooted , which took a while and had me pretty nervous. It eventually booted up though. This stuff is a lot more confusing than windows mobile was haha. I'm wondering if nandroid was indeed unlocked with simple root. I'm still willing to press forward if the help is still available. By the way, what and how can I make a nandroid backup?
Turn phone off, turn phone on holding down volume and power, when you get to white screen select recovery then scroll through your options, i believe it it backup/restore then creat nandroid backup, FYI you cant restore a nandroid backup if you haven't created one, IE the not found error you got before.
Ok so how exactly would I go about flashing(if that's even the right word) fresh rom from what I already have?
I'm not sure what you actually have, can you get to recovery, then the option to 'flash zip from sd card? if you have that option just place the fresh rom on the root of your sd card (put the zip file there and don't open the zip) then reboot to recovery, ie vilume down and power button when you get to white screen volume down to recovery, then flash zip from sd then select the fresh rom zip, then hit power button to select, hit power button again to confirm and away you go.
Ok that sounds simple enough. I can't thank you guys enough for all your help. What does a nandroid backup do?
it makes a copy of your rom basically, so say you put on fresh do a nandroid backup then flas CM6, you decide you dont like CM6, so you nandroid restore of your fresh and presto right back to where you were before you flashed CM6, also useful if you have screwed something up ... you can go back ... make sense?
Hi everyone, for Christmas my screen was crushed by a car .
The screen is completely destroyed (both touch screen & display screen).
However the phone is booting, so I can put it in recovery mod (I rooted the phone and I have clockworkmod).
After many trials, I succeeded in having adb connecting to my phone in blind mode.
I did this:
Code:
adb mount /data
adb pull /data /a_backup_folder
adb mount /system
adb pull /system /another_backup_folder
... and copied back my SD to my computer. I plan to buy another Desire and to revert the instruction by issuing a push for the data & system. This is:
Code:
adb mount /data
adb push /a_backup_folder /data
adb mount /system
adb push /another_backup_folder /system
Will it work ? Or is the system in sync with the flashed firmware ?
Can I selectively push some of the folders (namely applications, and the whole data). I hope to get back my settings, contacts etc...
I'm afraid I cannot do a whole lot more, since I do everything in blind mode.
Any advice on this ?
Thank you !
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
TheGhost1233 said:
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
Click to expand...
Click to collapse
Thank you for your suggestion.
Can I do it even if I do not have a screen ? I've tried to launch it but I fear it needs busybox (it says that it cannot find nc) and I think I do not have it (and don't know how to put it without the screen).
What are the supplementary steps that nandroid does ?
This is for CWM 2.5.0.7.
Sorry mist the part that you have to do everything blind, when in recovery press 5 times down on the volume rocker and then 2 times on the OJ let it sit for 10 min, should be done sooner but i don't know how to check if it's finished. After 10 min press once again on the OJ, your phone should reboot and in the Clockwork folder on the SD card should be a backup folder with a folder with the current date and time of the back up.
Unfortunately it did not work.
It did the steps as provided, and indeed the phone rebooted, but there is no clockworkmod folder on the sd card.
Is there any way to do a similar operation with adb ? This would be easier since when I'm in adb shell, I can type from the PC .
Try installing amon ra recovery. You should be able to do it. This is what the amon ra thread says:
Scripts available via adb :
* Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
Explenation: http://forum.xda-developers.com/showpost.php?p=3046976&postcount=1
I think that this is what you are looking for
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
mercianary said:
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
Click to expand...
Click to collapse
Ok the first step worked, but unyaffs does not want to open my imgs.
The size are as follow:
Code:
3*145*728 boot.img
3*145*728 boot_ro.img
41*943*040 cache.img
41*943*040 cache_ro.img
655*360 misc.img
655*360 misc_ro.img
4*718*592 recovery.img
4*718*592 recovery_ro.img
262*144*000 system.img
262*144*000 system_ro.img
154*796*032 userdata.img
154*796*032 userdata_ro.img
which seems good (I also made images from the mtdXro). However I should be able to extract userdata and system from my understanding. I tried with unyaffs both on linux and on windows, on both I get a segmentation fault.
Do I have a way to verify that theses images are good ? I do not want to trash the new phone I will buy with a faulty image...
Flash the same rom from recovery on your new phone, then flash the data image from fastboot, if it works the first boot should take a while as it builds the cache. If it doesn't work just clear data and it wont have done any damage to your new phone.
You will have to zip the data image before you fastboot flash it because it's too big for fastboot to receive.
If you have s-off on your old phone I would flash amon-ra recovery from fastboot then use the nandroid script over adb.
As long as you don't try to flash the recovery you backed up I don't think there's any chance of damaging your new phone doing this.
Ok the final solution was to use the new phone (rooted and with clockworkmod) as a reference.
I did the same backup sequence on the two phones, and have been able to restore the backup on the new phone.
Thank you everyone for your help !
Glad you got it sorted...don't drop your phone under a car again.
Sent from my HTC Desire using XDA App
Hi
I'm getting this error when I try to restore:
Code:
Error : run 'nandroid-mobile.sh restore' via adb!
So I tried to restore it through adb.
But then I get this error message:
Code:
"error: unable to mount /system, aborting
/sdcard/nandroid/SH0CJPL05354/BCDAS-20110610-1442"
The thing is it worked the first time I tried it but it won't work anymore and since I've wiped, I can't boot up at all. I can only access Recovery and the Bootloader
I always wipe before restoring and for what it's worth, I had to restore in the first place because I flashed the Bravo Sense hboot.
I'm AmonRa 2.0.1
Alpharev S-Off
Seems like /system is not mounted? Try
Code:
adb remount
then have another go?
stringer7 said:
Seems like /system is not mounted? Try
Code:
adb remount
then have another go?
Click to expand...
Click to collapse
Is that right after I load the adb shell?
If so I'm getting this when I do adb remount:
Code:
/sbin/sh: adb: not found
I think I'm doing it wrong.
Ok, try to get your PC to recognise your device using
Code:
adb devices
There is s good guide on installation and use here:
http://forum.xda-developers.com/showthread.php?t=879701
stringer7 said:
Ok, try to get your PC to recognise your device using
Code:
adb devices
There is s good guide on installation and use here:
http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
The phone is listed under adb devices and I have successfully located the nandroid on my sdcard using adb, it's just the restore fails as above. (Interestingly, it lists the phone under adb devices when I'm in Recovery but it won't do so when I'm in the bootloader screen.)
Anyway, this is what I'm getting with adb remount:
Code:
C:\>adb remount
remount failed: invalid argument
What would suggest from here?
Thanks for helping out, btw. It's very very much appreciated
Ok so you currently have s-off, RA recovery, access to bootloader and recovery, but no working rom and a nandroid backup that won't restore - that right?
stringer7 said:
Ok so you currently have s-off, RA recovery, access to bootloader and recovery, but no working rom and a nandroid backup that won't restore - that right?
Click to expand...
Click to collapse
If it was me I would wipe everything (I know you did already but just to be sure) download fresh version of the rom to your sd via PC, insert in phone and flash it through recovery. That gets you a functioning phone at least!
Then work on the restore issue. The backup was made with the same version of RA that you are currently using I assume? I'm not sure where to go with it really, and hope someone with more knowledge will pitch in...!
Something like that has already happened to me twice. First, I was running low on sd space. Second, my recovery was corrupted somewhat: fixed by reflashing the same recovery. Hope this helps you in troubleshooting.
stringer7 said:
If it was me I would wipe everything (I know you did already but just to be sure) download fresh version of the rom to your sd via PC, insert in phone and flash it through recovery. That gets you a functioning phone at least!
Then work on the restore issue. The backup was made with the same version of RA that you are currently using I assume? I'm not sure where to go with it really, and hope someone with more knowledge will pitch in...!
Click to expand...
Click to collapse
I managed to get it sorted. A guy on another forum mentioned this exact same solution. Which means props to you too.
Thanks for the help.
You are welcome!
Remember to pass it on and help where you can...
sak01 said:
I managed to get it sorted. A guy on another forum mentioned this exact same solution. Which means props to you too.
Thanks for the help.
Click to expand...
Click to collapse
Post the solution here to help other people.
^^sorry I missed your post.
It's this solution posted by stringer7 earlier
stringer7 said:
If it was me I would wipe everything (I know you did already but just to be sure) download fresh version of the rom to your sd via PC, insert in phone and flash it through recovery. That gets you a functioning phone at least!
Click to expand...
Click to collapse
Or as Rastaman over at AF put it:
if youve wiped, try and flash a new rom without restoring nand and see if it rebuilds the system partition
once done see if a nand restore will work (although it was done without ext :/)
Click to expand...
Click to collapse
So basically, flashing a new rom rebuilds the system partition and then the nand restore works.
if so, would be usefull to restore without the boot.img from nandbackup.
never used nandbackup, i have ridden that was availaible through some advanced features from nand restore on amonRA
this is a point already raised early by someone named Brandall
Hi all!
I using root explorer to replace framework-res.apk
But now, my HTC Desire Z have a bootloop. I try to factory reset, wipe cache date, using update.zip but not not effective.
When I up rom in recovery (3e), the system show: E:signature verification failed
Help me fix the bootloop. Thanks!
well first off I hope you made a nandroid backup of your ROM before you did this. If so, just pull the battery, boot straight into recovery, and restore that nandroid backup.
Where did you get this framework-res.apk? did you edit it yourself? if so, what did you change? If you or someone else has changed anything decently major, the .apk needs to be re-signed. Looks like it wasn't.
Everybody help me!
I can't solve this problem
minhquang_ns said:
Everybody help me!
I can't solve this problem
Click to expand...
Click to collapse
Where did the framework-res.apk you are using to replace the stock on come from?
Or is the issue now just trying to get your phone booting again?
cjward23 said:
Where did the framework-res.apk you are using to replace the stock on come from?
Or is the issue now just trying to get your phone booting again?
Click to expand...
Click to collapse
I get framework-res.apk in Uot kitchen > Show all pickup file
I get one in this and replace. I didn't think about consequences
minhquang_ns said:
I get framework-res.apk in Uot kitchen > Show all pickup file
I get one in this and replace. I didn't think about consequences
Click to expand...
Click to collapse
Like I said in my first post that you didn't respond to, did you make a nandroid backup? If you didn't, you should at least have the stock framework-res.apk set aside to go back to? If you don't, and you can boot directly into recovery, then you're going to have to re-flash a fresh ROM in order to break the issues you caused with your current problem.
So if your phone is still bootlooping and you don't have a backup to go to, then follow the normal steps to flash a new ROM from recovery (this will probably be your only option if you don't have a backup):
1) download your ROM of choice
2) enter recovery, mount as USB storage
3) place ROM.zip on root of your SD card
4) install zip from SDcard > select ROM.zip
5) reboot
you'll probably lose your data, unless you flash the exact same ROM as you had before, there may be a chance that it won't.
Here's a lesson to be learned! Backup before messing with major things, and save the old framework-res.apk. And don't just willy-nilly flash random Uot Kitchen framework-res.apk's without precautions. It looks like you just got a framework-res.apk that wasn't signed properly and it messed your ROM up.
martonikaj said:
Like I said in my first post that you didn't respond to, did you make a nandroid backup? If you didn't, you should at least have the stock framework-res.apk set aside to go back to? If you don't, and you can boot directly into recovery, then you're going to have to re-flash a fresh ROM in order to break the issues you caused with your current problem.
So if your phone is still bootlooping and you don't have a backup to go to, then follow the normal steps to flash a new ROM from recovery (this will probably be your only option if you don't have a backup):
1) download your ROM of choice
2) enter recovery, mount as USB storage
3) place ROM.zip on root of your SD card
4) install zip from SDcard > select ROM.zip
5) reboot
you'll probably lose your data, unless you flash the exact same ROM as you had before, there may be a chance that it won't.
Here's a lesson to be learned! Backup before messing with major things, and save the old framework-res.apk. And don't just willy-nilly flash random Uot Kitchen framework-res.apk's without precautions. It looks like you just got a framework-res.apk that wasn't signed properly and it messed your ROM up.
Click to expand...
Click to collapse
Thank you, but I don't have clockmod recovery
When I using Recovery 3e (default), I choose "update.zip"
I try many roms but the system warning:
E: signature verification failed
FAILED TO VERIFY WHOLE-FILE SIGNATURE
Installation aborted.
Click to expand...
Click to collapse
.
minhquang_ns said:
Thank you, but I don't have clockmod recovery
When I using Recovery 3e (default), I choose "update.zip"
I try many roms but the system warning:
Click to expand...
Click to collapse
How can you not have cwm, there isn't another custom recovery for the DZ that I'm aware of.
Hang on, do you still have the stock recovery? OK so I'm going to assume you are actually rooted. Do you nave the eng hboot installed?
Do Androids dream of electric sheep?
cjward23 said:
.
How can you not have cwm, there isn't another custom recovery for the DZ that I'm aware of.
Hang on, do you still have the stock recovery? OK so I'm going to assume you are actually rooted. Do you nave the eng hboot installed?
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
I have HBOOT 0.85.009. How to flash a new rom with out clockmod
minhquang_ns said:
I have HBOOT 0.85.009. How to flash a new rom with out clockmod
Click to expand...
Click to collapse
You can't, you will need to install cwm.
Download rom manager, then select install clockworkmod recovery. Then boot your phone in to recovery and preform a wipe then flash custom rom.
Do you have s-off?
Do Androids dream of electric sheep?
cjward23 said:
You can't, you will need to install cwm.
Download rom manager, then select install clockworkmod recovery. Then boot your phone in to recovery and preform a wipe then flash custom rom.
Do you have s-off?
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
I have a boot loop, my Desire Z stopped in "HTC quietly brilliant" so I can't install cwm. I has been rooted phone.
minhquang_ns said:
I have a boot loop, my Desire Z stopped in "HTC quietly brilliant" so I can't install cwm. I has been rooted phone.
Click to expand...
Click to collapse
Ohh yeah, I forgot that. OK you will need to install recovery using fastboot. But to do that you will need to install the eng hboot. To do that please follow the instructions here http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html. But when you get to point 10 you will need to pull your battery out. And delete the PC10IMG.zip of your sd card.
Then reboot back in to bootloader and if all has gone well we will know have the DZ eng hboot installed.
The top line should now say vision eng s-off
You will then need to execute fastboot commands to install cwm. If you do not have fastboot installed download fastboot.exe from here http://developer.htc.com/adp.html and place in your platform-tools folder. You will is need the cwm recovery.img which you can get from here http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img and rename to recovery.img and place in your platform-tools folder
Open a cmd window and point it towards your platform-tools folder. Then we want to check fastboot is working, so make sure your phone is in bootloader and type fastboot devices and it should bring up your device serial number. Assuming that works type fastboot flash recovery recovery.img
All being well the recovery will flash then you will be able to boot in to recovery and flash a rom.
If you have any problems or are unsure about anything head over to the #G2ROOT irc http://webchat.freenode.net/
Do Androids dream of electric sheep?
cjward23 said:
Ohh yeah, I forgot that. OK you will need to install recovery using fastboot. But to do that you will need to install the eng hboot. To do that please follow the instructions here http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html. But when you get to point 10 you will need to pull your battery out. And delete the PC10IMG.zip of your sd card.
Then reboot back in to bootloader and if all has gone well we will know have the DZ eng hboot installed.
The top line should now say vision eng s-off
You will then need to execute fastboot commands to install cwm. If you do not have fastboot installed download fastboot.exe from here http://developer.htc.com/adp.html and place in your platform-tools folder. You will is need the cwm recovery.img which you can get from here http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img and rename to recovery.img and place in your platform-tools folder
Open a cmd window and point it towards your platform-tools folder. Then we want to check fastboot is working, so make sure your phone is in bootloader and type fastboot devices and it should bring up your device serial number. Assuming that works type fastboot flash recovery recovery.img
All being well the recovery will flash then you will be able to boot in to recovery and flash a rom.
If you have any problems or are unsure about anything head over to the #G2ROOT irc http://webchat.freenode.net/
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
When I using fastboot recovery, cmd warning:
writing ‘recovery’… FAILED (remote: not allowed)
Click to expand...
Click to collapse
Similar, I type adb shell the system wanring:
error:devices not found
Click to expand...
Click to collapse